[go: up one dir, main page]

WO2014110690A1 - 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 - Google Patents

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 Download PDF

Info

Publication number
WO2014110690A1
WO2014110690A1 PCT/CN2013/000043 CN2013000043W WO2014110690A1 WO 2014110690 A1 WO2014110690 A1 WO 2014110690A1 CN 2013000043 W CN2013000043 W CN 2013000043W WO 2014110690 A1 WO2014110690 A1 WO 2014110690A1
Authority
WO
WIPO (PCT)
Prior art keywords
uplink resource
configuration
tdd
uplink
determining
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2013/000043
Other languages
English (en)
Inventor
Chao Wei
Neng Wang
Peng Cheng
Jilei Hou
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
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 Inc filed Critical Qualcomm Inc
Priority to PCT/CN2013/000043 priority Critical patent/WO2014110690A1/fr
Publication of WO2014110690A1 publication Critical patent/WO2014110690A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0045—Arrangements at the receiver end
    • H04L1/0055—MAP-decoding
    • 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/1861—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames

Definitions

  • Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include code-division multiple access (CDMA) systems, time-division multiple access (TDMA) systems, frequency-division multiple access (FDMA) systems, and orthogonal frequency-division multiple access
  • CDMA code-division multiple access
  • TDMA time-division multiple access
  • FDMA frequency-division multiple access
  • OFDMA frequency division duplex
  • TDD time-division duplex
  • FDD frequency-division duplex
  • 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. Reconfiguration of TDD formats may be
  • the described features generally relate to one or more improved systems, methods, and/or apparatuses for determination of uplink resources for use in transmitting hybrid acknowledgment repeat request (HARQ) information following TDD reconfiguration of one or more user equipments (UEs) from a first uplink-downlink (UL-DL) configuration to a second UL-DL configuration, while one or more other UEs retain the first UL-DL
  • HARQ hybrid acknowledgment repeat request
  • a first uplink resource for transmission of HARQ information associated with the first UL-DL configuration is determined, and a second uplink resource for transmission of HARQ information associated with the second UL-DL configuration is determined based on the first uplink resource.
  • the information related to the second uplink resource for use by the reconfigured UE(s) is transmitted to the reconfigured UE(s).
  • the reconfigured UE(s) receive a reconfiguration message and information on the second uplink resource, and transmit HARQ information using the second resource for the reconfigured frames.
  • a method of wireless communication performed by a base station configured for multiple concurrent time-division duplex (TDD) uplink-downlink (UL-DL) configurations is provided.
  • the method generally includes determining that a first user equipment (UE) is to operate using a first UL-DL configuration and that a second UE is to operate using a second UL-DL configuration for a TDD frame, determining a first uplink resource for transmission of hybrid automatic repeat request (HARQ) information associated with the first UL-DL configuration, determining, based on the first uplink resource, a second uplink resource for transmission of HARQ information associated with the second UL-DL configuration for use by the second UE, and transmitting information related to the second uplink resource for use by the second UE.
  • HARQ hybrid automatic repeat request
  • Determining the second uplink resource may include determining an offset value for the second uplink resource such that the first and second uplink resources are non-overlapping, and transmitting information related to the second uplink resource may include transmitting the second UL-DL configuration for the subsequent TDD frame and the offset value for the second uplink resource to the second UE.
  • determining a second HARQ resource may include determining a set of semi-static uplink resources for use with the second UL-DL
  • the set of semi-static uplink resources may include, for example, four available uplink resources.
  • Transmitting information related to the second uplink resource may include transmitting the second UL-DL configuration for the TDD frame and the selected semi-static uplink resource to the second UE.
  • the selected semi-static uplink resource may transmitted, for example, in a downlink assignment index (DAI) field.
  • DAI downlink assignment index
  • Such a DAI field may include a value
  • the number of scheduled downlink subframes may be used to select the semi-static uplink resource.
  • determining a second uplink resource includes determining common downlink subframes from a bundling set for the first and second TDD UL-DL configurations, determining a first portion of the second uplink resource based on the common downlink subframes that overlaps with the first uplink resource, and determining an offset value for a second portion of the second uplink resource such that the first uplink resource and the second portion of the second uplink resource are non-overlapping.
  • the transmitting information related to the second uplink resource may include transmitting the second UL-DL configuration for the TDD frame and the offset value for the second portion of the second uplink resource to the second UE.
  • transmitting information may include transmitting a TDD UL-DL reconfiguration message to the second UE and transmitting information related to the second uplink resource for use by the second UE.
  • the first UE may be a legacy UE, and the second UE may be a non-legacy UE, for example.
  • a method of wireless communication performed by a UE configured to operate using one of multiple TDD UL-DL configurations is provided.
  • the method generally includes receiving a TDD reconfiguration message indicating the UE is to operate using a second UL-DL configuration for a TDD frame that is different than a first UL-DL configuration received in a system information block (SIB), and processing the TDD reconfiguration message to determine a second uplink resource for transmission of HARQ information associated with the second UL-DL configuration for the TDD frame, the second uplink resource being non-overlapping with a first uplink resource for transmission of HARQ information associated with the first UL-DL configuration.
  • the TDD reconfiguration message may include, for example, the second UL-DL configuration for the TDD frame and an offset value for the second uplink resource for the transmission of HARQ information such that the first and second uplink resources are non-overlapping.
  • the second uplink resource is selected from a set of semi- static uplink resources associated with the second UL-DL configuration.
  • the selected semi- static uplink resource may be received, for example, in a DAI field, which may include a value corresponding to the number of scheduled downlink subframes in a bundling set transmitted to the UE in the TDD frame, and the number of scheduled downlink subframes may used to determine the semi-static uplink resource.
  • the second uplink resource may include a first portion based on common downlink subframes in a bundling set between the first and second TDD UL-DL configurations, and a second portion based on downlink subframes not common to the bundling set.
  • the second portion of the second uplink resource may have a different offset than the first uplink resource for the transmission of a the second portion a second HARQ information.
  • the second portion of the second uplink resource is orthogonal to the first uplink resource.
  • the TDD reconfiguration message may include second UL-DL configuration for the subsequent TDD frame and the offset value for the second portion of the second uplink resource.
  • a base station apparatus configured for multiple concurrent TDD UL-DL configurations.
  • the apparatus generally includes at least one processor and a memory.
  • the at least one processor may be configured to determine that a first UE is to operate using a first UL-DL configuration and that a second UE is to operate using a second UL-DL configuration for a TDD frame, determine a first uplink resource for transmission of HARQ information associated with the first UL-DL configuration, determine, based on the first uplink resource, a second uplink resource for transmission of HARQ information associated with the second UL-DL configuration for use by the second UE, and transmit information related to the second uplink resource for use by the second UE.
  • the at least one processor may be further configured to determine an offset value for the second uplink resource such that the first and second uplink resources are non-overlapping and/or transmit the second UL-DL configuration for the subsequent TDD frame and the offset value for the second uplink resource to the second UE.
  • the at least one processor may be further configured to determine a set of semi-static uplink resources for use with the second UL-DL configuration such that the first and second uplink resources are non-overlapping.
  • the set of semi-static uplink resources may include, for example, four available uplink resources.
  • the at least one processor may be further configured to transmit the second UL-DL configuration for the subsequent TDD frame and the selected semi-static uplink resource to the second UE.
  • Such a semi-static uplink resource may be transmitted in a downlink assignment index (DAI) field, for example.
  • DAI field may include a value corresponding to the number of scheduled downlink subframes in a bundling set transmitted to the UE in the TDD frame, and the number of scheduled downlink subframes may used to select the semi-static uplink resource.
  • the at least one processor may be further configured to determine common downlink subframes from a bundling set for the first and second TDD UL-DL configurations, determine a first portion of the second uplink resource based on the common downlink subframes that overlaps with the first uplink resource, and determine an offset value for a second portion of the second uplink resource such that the first uplink resource and the second portion of the second uplink resource are non-overlapping.
  • the second UL- DL configuration for the TDD frame and the offset value for the second portion of the second uplink resource may be transmitted to the second UE.
  • the at least one processor may be further configured to transmit a TDD UL-DL reconfiguration message to the second UE and transmit information related to the second uplink resource for use by the second UE.
  • a UE apparatus configured for multiple concurrent TDD UL-DL configurations.
  • the apparatus generally includes at least one processor and a memory.
  • the at least one processor may be configured to receive a TDD reconfiguration message indicating the UE is to operate using a second UL-DL configuration for a subsequent TDD frame that is different than a first UL-DL configuration received in a SIB, and process the TDD reconfiguration message to determine a second uplink resource for transmission of HARQ information associated with the second UL-DL configuration for the subsequent TDD frame, the second uplink resource being non-overlapping with a first uplink resource for transmission of HARQ information associated with the first UL-DL
  • the TDD reconfiguration message may include, for example, the second UL- DL configuration for the subsequent TDD frame and an offset value for the second uplink resource for the transmission of a HARQ information such that the first and second uplink resources are non-overlapping.
  • the second uplink resource may be selected from a set of semi-static uplink resources associated with the second UL-DL configuration.
  • the selected semi-static uplink resource may be received in a downlink assignment index (DAI) field.
  • DAI field may include a value corresponding to the number of scheduled downlink subframes in a bundling set transmitted to the UE in the subsequent TDD frame, and the number of scheduled downlink subframes may be used to determine the semi-static uplink resource.
  • the second uplink resource may include a first portion based on common downlink subframes in a bundling set between the first and second TDD UL-DL configurations, and a second portion based on downlink subframes not common to the bundling set.
  • the second portion of the second uplink resource may have a different offset than the first uplink resource for the transmission of second HARQ information.
  • the second portion of the second uplink resource may be orthogonal to the first uplink resource.
  • the TDD reconfiguration message may include the second UL-DL configuration for the subsequent TDD frame and the offset value for the second portion of the second uplink resource.
  • a base station apparatus configured for multiple concurrent TDD UL-DL configurations.
  • the apparatus generally includes means for determining that a first UE is to operate using a first UL-DL configuration and that a second UE is to operate using a second UL-DL configuration for a TDD frame, means for determining a first uplink resource for transmission of HARQ information associated with the first UL-DL configuration, means for determining, based on the first uplink resource, a second uplink resource for transmission of HARQ information associated with the second UL-DL configuration for use by the second UE, and means for transmitting information related to the second uplink resource for use by the second UE.
  • the means for determining the second uplink resource may include means for determining an offset value for the second uplink resource such that the first and second uplink resources are non-overlapping.
  • the means for transmitting information related to the second uplink resource may include means for transmitting the second UL-DL configuration for the subsequent TDD frame and the offset value for the second uplink resource to the second UE.
  • the means for determining a second HARQ resource includes means for determining a set of semi-static uplink resources for use with the second UL-DL configuration such that the first and second uplink resources are non-overlapping.
  • the set of semi-static uplink resources may include, for example, four available uplink resources.
  • the means for transmitting information related to the second uplink resource may include means for transmitting the second UL-DL configuration for the subsequent TDD frame and the selected semi-static uplink resource to the second UE.
  • the selected semi-static uplink resource may be transmitted in a downlink assignment index (DAI) field that includes a value corresponding to the number of scheduled downlink subframes in a bundling set transmitted to the UE in the TDD frame, and the number of scheduled downlink subframes may be used to select the semi-static uplink resource.
  • DAI downlink assignment index
  • the means for determining a second uplink resource may include means for determining common downlink subframes from a bundling set for the first and second TDD UL-DL configurations, means for determining a first portion of the second uplink resource based on the common downlink subframes that overlaps with the first uplink resource, and means for determining an offset value for a second portion of the second uplink resource such that the first uplink resource and the second portion of the second uplink resource are non-overlapping.
  • the means for transmitting information related to the second uplink resource may include means for transmitting the second UL-DL configuration for the TDD frame and the offset value for the second portion of the second uplink resource to the second UE.
  • the means for transmitting information may include means for transmitting a TDD UL-DL reconfiguration message to the second UE and transmitting information related to the second uplink resource for use by the second UE.
  • a UE apparatus configured to operate using one of multiple TDD UL-DL configurations.
  • the apparatus generally includes means for receiving a TDD reconfiguration message indicating the UE is to operate using a second UL-DL configuration for a subsequent TDD frame that is different than a first UL-DL configuration received in a system information block (SIB), and means for processing the TDD reconfiguration message to determine a second uplink resource for transmission of HARQ information associated with the second UL-DL configuration for the subsequent TDD frame, the second uplink resource being non-overlapping with a first uplink resource for transmission of HARQ information associated with the first UL-DL configuration.
  • SIB system information block
  • a computer program product for wireless communications by a base station configured for multiple concurrent TDD UL-DL configurations.
  • the computer program product generally includes a non- transitory computer-readable medium that includes code for determining that a first user equipment (UE) is to operate using a first UL-DL configuration and that a second UE is to operate using a second UL-DL configuration for a TDD frame, determining a first uplink resource for transmission of HARQ information associated with the first UL-DL
  • UE user equipment
  • the code for determining the second uplink resource may include code for determining an offset value for the second uplink resource such that the first and second uplink resources are non-overlapping.
  • the code for transmitting information related to the second uplink resource may include code for transmitting the second UL-DL configuration for the subsequent TDD frame and the offset value for the second uplink resource to the second UE.
  • the code for determining a second HARQ resource may include code for determining a set of semi-static uplink resources for use with the second UL- DL configuration such that the first and second uplink resources are non-overlapping.
  • the set of semi-static uplink resources may include four available uplink resources.
  • the code for transmitting information related to the second uplink resource may include code for transmitting the second UL-DL configuration for the subsequent TDD frame and the selected semi-static uplink resource to the second UE.
  • the code for determining a second uplink resource may include code for determining common downlink subframes from a bundling set for the first and second TDD UL-DL configurations, determining a first portion of the second uplink resource based on the common downlink subframes that overlaps with the first uplink resource, and determining an offset value for a second portion of the second uplink resource such that the first uplink resource and the second portion of the second uplink resource are non-overlapping.
  • the code for transmitting information related to the second uplink resource may include code for transmitting the second UL-DL configuration for the TDD frame and the offset value for the second portion of the second uplink resource to the second UE.
  • the code for transmitting information may include code for transmitting a TDD UL-DL reconfiguration message to the second UE and transmitting information related to the second uplink resource for use by the second UE.
  • a computer program product for wireless communications by a UE configured to operate using one of multiple TDD UL-DL configurations is provided.
  • the computer program product generally includes a non- transitory computer-readable medium that includes code for receiving a TDD reconfiguration message indicating the UE is to operate using a second UL-DL configuration for a subsequent TDD frame that is different than a first UL-DL configuration received in a system information block (SIB), and processing the TDD reconfiguration message to determine a second uplink resource for transmission of hybrid automatic repeat request (HARQ) information associated with the second UL-DL configuration for the subsequent TDD frame, the second uplink resource being non-overlapping with a first uplink resource for
  • SIB system information block
  • FIG. 1 is a diagram illustrating an example of a wireless communications system in accordance with various embodiments
  • FIG. 2 is a table illustrating TDD Uplink-Downlink configurations in exemplary wireless communications system in accordance with various embodiments
  • FIG. 3 illustrates a Cell Clustering Interference Mitigation environment with cells grouped according to cell clusters in accordance with various embodiments
  • FIG. 4 shows a diagram of an exemplary TDD frames with associated HARQ ACK transmission in accordance with various embodiments
  • FIGS. 5 A and 5B show a diagrams of an exemplary TDD frames with UL-DL reconfiguration with associated possible HARQ ACK transmission collisions;
  • FIG. 6 shows a block diagram of an example of a base station in accordance with various embodiments;
  • FIG. 7 shows an exemplary offset value for uplink transmission resources of HARQ information in accordance with various embodiments
  • FIGS. 8A and 8B show exemplary semi-static resources for uplink transmission resources of HARQ information in accordance with various embodiments
  • FIG. 9 shows an exemplary common downlink subframe offset value, and reconfigured downlink subframe offset value for uplink transmission resources of HARQ information in accordance with various embodiments
  • FIG. 10 shows an example of common and reconfigured downlink subframes in bundled sets in accordance with various embodiments
  • FIG. 11 shows a block diagram of an example of a user equipment in accordance with various embodiments
  • FIG. 12 shows a block diagram of an example of a TDD reconfiguration module in accordance with various embodiments
  • FIG. 13 is a block diagram of an example of a wireless communications system including a base station and a mobile device in accordance with various embodiments;
  • FIG. 14 is a flowchart of a method for determination of uplink resources for transmission of TDD HARQ information in accordance with various embodiments
  • FIG. 15 is a flowchart of another method for determination of uplink resources for transmission of TDD HARQ information in accordance with various embodiments
  • FIG. 16 is a flowchart of another method for determination of uplink resources for transmission of TDD HARQ information in accordance with various embodiments.
  • FIG. 17 is a flowchart of another method for determination of uplink resources for transmission of TDD HARQ information in accordance with various embodiments.
  • FIG. 18 is a flowchart of a method for a user equipment to determine uplink resources for transmission of TDD HARQ information in accordance with various embodiments.
  • Various aspects of the disclosure provide for determination of uplink resources for use in transmitting hybrid acknowledgment repeat request (HARQ) information following TDD reconfiguration of one or more user equipments (UEs) from a first uplink-downlink (UL-DL) configuration to a second UL-DL configuration, while one or more other UEs retain the first UL-DL configuration and have concurrent transmissions to an associated base station.
  • a first uplink resource for transmission of HARQ information associated with the first UL-DL configuration is determined, and a second uplink resource for transmission of HARQ information associated with the second UL-DL configuration is determined based on the first uplink resource.
  • the information related to the second uplink resource for use by the reconfigured UE(s) is transmitted to the reconfigured UE(s).
  • the reconfigured UE(s) receive a reconfiguration message and information on the second uplink resource, and transmit HARQ information using the second resource for the subsequent frames.
  • 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 CDMA2000 IX, IX, etc.
  • IS-856 TIA-856
  • 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).
  • the techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies.
  • 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 1 0.
  • 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 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 115 via one or more base station antennas. Each of the base station 105 sites may provide communication coverage for a respective geographic 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 110 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 wireless network 100 may support synchronous or asynchronous operation.
  • the eNBs may have similar frame timing, and transmissions from different eNBs may be approximately aligned in time.
  • the eNBs may have different frame timing, and transmissions from different eNBs may not be aligned in time.
  • some eNBs 105 may be synchronous while other eNBs may be asynchronous.
  • the communication devices 115 are dispersed throughout the wireless network 100, and each device may be stationary or mobile.
  • a communication device 115 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 115 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 115.
  • 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 115, 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 according to an LTE/LTE-A network architecture 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 115 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 115.
  • the eNBs 105 may be connected to other eNBs 105 via backhaul link 134 (e.g., an X2 interface).
  • the eNBs 105 may provide an access point to the EPC 130 for the UEs 115.
  • the eNBs 105 may be connected by backhaul link 132 (e.g., an SI interface) 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).
  • MME 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 Packet Data Network
  • Gateway may provide UE IP address allocation as well as other functions.
  • the PDN may be mapped to IP address allocation as well as other functions.
  • the Gateway may be connected to IP networks and/or the operator's IP Services. These logical nodes may be implemented in separate physical nodes or one or more may be combined in a single physical node.
  • 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
  • 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.
  • a Radio Link Control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • a Medium Access Control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels.
  • the MAC layer may also use Hybrid ARQ (HARQ) to provide retransmission at the MAC layer to improve link efficiency.
  • HARQ Hybrid ARQ
  • 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.
  • RRC Radio Resource Control
  • the transport channels may be mapped to Physical channels.
  • 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 and SC-FDMA partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, or the like.
  • K orthogonal subcarriers
  • 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.
  • a sub-band may cover 1.08 MHz, and there may be 1, 2, 4, 8 or 16 sub-bands.
  • Wireless network 100 may support operation on multiple carriers, which may be referred to as carrier aggregation (CA) or multi-carrier operation.
  • a carrier may also be referred to as a component carrier (CC), a channel, etc.
  • a carrier used for the downlink may be referred to as a downlink CC
  • a carrier used for the uplink may be referred to as an uplink CC.
  • a UE may be configured with multiple downlink CCs and one or more uplink CCs for carrier aggregation.
  • An eNB may transmit data and control information on one or more downlink CCs to the UE.
  • the UE may transmit data and control information on one or more uplink CCs to the eNB.
  • the carriers may transmit bidirectional communications FDD (e.g., paired spectrum resources), TDD (e.g., unpaired spectrum resources).
  • Frame structures for FDD e.g., frame structure type 1
  • TDD e.g., frame structure type 2
  • each subframe may carry UL or DL traffic, and special subframes ("S") may be used to switch between DL to UL transmission.
  • Allocation of UL and DL subframes within radio frames may be symmetric or asymmetric and may be reconfigured semi-statically (e.g., RRC messages via backhaul, etc.).
  • Special subframes 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 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 seven different UL-DL configurations are defined that provide between 40% and 90% DL subframes as illustrated in table FIG. 2 at Table 200. As indicated in table 200, there are two switching periodicities, 5 ms and 10 ms.
  • TDD UL/DL configuration For configurations with 5 ms switching periodicities, there are two special subframes per frame, and for configurations with 10 ms switching periodicities there is one special subframe per frame. Some of these configurations are symmetric, having the same number of uplink and downlink slots, while some are asymmetric, having different numbers of uplink and downlink slots. For example, UL-DL configuration 1 is symmetric, with four uplink and four downlink subframes, UL-DL configuration 5 favors downlink throughput, and UL-DL configuration 0 favors uplink throughput. [0060]
  • the particular TDD UL/DL configuration that is used by a base station may be based on user requirements for the particular coverage area. For example, with reference again to FIG.
  • a base station 105 may be able to dynamically reconfigure TDD UL-DL configurations on a frame- by-frame basis.
  • UEs 115 that are reconfigured may receive the reconfiguration message, and transmit/receive subframes on subsequent TDD frames using the reconfigured UL-DL configuration.
  • Such capabilities allow for relatively fast switching for the reconfigured UEs 115 according to the instantaneous traffic situation, and may provide enhanced packet throughput between the UEs 1 15 and base station 105.
  • a UE 115 may be in communication with a base station 105 using an initial TDD UL-DL configuration. This initial TDD UL-DL configuration, however, may become unfavorable for efficient packet throughput at a later point in time. For example, the user may switch from receiving a relatively large amount of data to transmitting a relatively large amount of data. In such a situation, a ratio of uplink to downlink transmission data may have a significant change, which may result a previously favorable UL-DL configuration becoming an unfavorable UL-DL configuration.
  • FIG. 3 illustrates a CCIM environment 300 with eNBs grouped according to cell clusters.
  • CCIM environment 200 may illustrate, for example, aspects of wireless communication system 100 illustrated in FIG. 1.
  • Cell clusters can include one or more eNBs and eNBs within a cell cluster may be different types (e.g., macro eNB, pico eNB, femto eNB, and/or the like).
  • CCIM CCIM
  • Cell cluster 320-a may include eNB 105-a and eNB 105-b
  • cell cluster 320-b may include eNB 105-c
  • cell cluster 320-c may include eNBs 105-d and 105-e.
  • Cell clusters 320 may be statically or semi-statically defined and each eNB 105 in a cluster 320 may be aware of the other eNBs 105 of its cluster.
  • Cell clusters 320-a, 320-b, and/or 320-c may deploy TDD carriers and TDD UL-DL configuration within each cell cluster may be synchronized.
  • Traffic adaptation for synchronized TDD UL-DL configuration within a cell cluster may be performed by coordination of TDD UL-DL reconfiguration between cells of the cluster.
  • Semi-static (e.g., on the order of tens of frames) TDD UL-DL reconfiguration may be performed by exchange of control-plane messaging among eNBs (e.g., via SI and/or X2 interfaces, etc.). While semi-static TDD UL-DL reconfiguration may provide adequate performance under some conditions, when traffic conditions within the cluster change rapidly, semi-static TDD UL-DL reconfiguration may result in sub-optimal allocation of UL- to-DL subframes for TDD carriers used in the cluster.
  • rapidly changing traffic conditions may be accommodated through allowing the UL-DL configuration for a particular UE 1 15 may be reconfigured dynamically.
  • Such dynamic reconfiguration may be transmitted to a UE 1 15 through signaling from the eNB 105, such as through control channel signaling, and apply to one or more subsequent TDD frames.
  • Such reconfigurations may be accomplished according to "enhanced Interference Management and Traffic Adaptation" (elMTA), which may be implemented in some networks.
  • elMTA compatible UEs may receive dynamic reconfiguration messages indicating that particular subframes within a TDD frame may be switched from an uplink to a downlink subframe.
  • the adaptation rate may be relatively fast, such as 10 ms, thus providing ability in some situations to change TDD UL-DL
  • 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 subframe in an established TDD UL-DL configuration such as indicated in System Information Block 1 (SIBl) 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.
  • ambiguity may exist between the eNB and UEs as related to the timing of transmissions related to HARQ operations, because there are two different TDD configurations for UEs in communication with the eNB, i.e. the UL-DL configuration broadcast in SIBl and that signaled in additional RRC or control channel (e.g., LI) signaling.
  • FIG. 4 illustrates two frames 400 in a TDD system.
  • the first frame 405 (frame n) and second frame 410 (frame n+1) are each transmitted according to TDD UL-DL configuration 2.
  • the UE send a HARQ acknowledgment or negative acknowledgment (ACK/NACK) for subframes 4- 6 and 8 of the first frame 405 during the subframe 2 of the second frame 410.
  • ACK/NACK HARQ acknowledgment or negative acknowledgment
  • the HARQ process includes determining a HARQ ACK/NACK for each subframe and a resource index referred to as i yCCH y
  • the index value may be calculated according to 3rd Generation Partnership Project (3GPP) technical specification 36.213.
  • 3GPP 3rd Generation Partnership Project
  • HARQ ACK/NACK 415 for subframe 4 of the first frame may be determined, along with the associated resource index ⁇ CCH v
  • the resource index determines the uplink resource for transmission of the ACK/NACK information within the designated subframe for transmission of the information. Similar information is determined, as indicated at 420, 425, and 430 for subframes 5, 6, and 8, respectively.
  • the ACK NACK for each noted subframe may be transmitted in subframe 2 of the second frame 410.
  • a UE may convert multiple HARQ ACK NACKs into a single HARQ ACK/NACK via bundling or multiplexing.
  • Bundling of acknowledgments includes combining the outcome of the determined ACK/NACK from multiple subframes into a single HARQ acknowledgment. Such combining may be accomplished through, for example, a logical AND of the respective ACK/NACK determinations.
  • the single HARQ acknowledgement is transmitted from one of the determined HARQ resource index, with the subframes included in the bundling referred to as a bundling set.
  • an eNB may be communicating with both legacy UEs and non- legacy UEs, with one or more of the non-legacy UEs reconfigured to operate according to a different TDD UL-DL configuration than the legacy UEs.
  • the resource index used for the HARQ acknowledgment may be selected to avoid collision between HARQ acknowledgments provided by the legacy and non-legacy UEs.
  • HARQ acknowledgment messages may have the same uplink resources assigned for the transmission the HARQ information.
  • a non-legacy UE may be reconfigured to change from TDD UL-DL configuration 0 in a first frame 505 to TDD UL-DL configuration 1 in a second subframe 510.
  • a legacy UE communicating with the same eNB would continue to operate according to TDD UL-DL configuration 0 during the second frame 510.
  • the legacy UE may have an uplink resource allocated for HARQ acknowledgment 515 in subframe 7 of the second frame 510, and the non-legacy UE may have an uplink resource allocated for
  • the same uplink resource might be assigned to both UEs, resulting in a collision in transmissions received at the eNB.
  • uplink resources for transmission of HARQ information may overlap between legacy UEs and non- legacy UEs.
  • a non-legacy UE may be reconfigured to change from TDD UL-DL configuration 1 in a first frame 555 to TDD UL-DL configuration 2 in a second subframe 560.
  • a legacy UE communicating with the same eNB may operate according to TDD UL-DL configuration 1 during both the first frame 555 and the second frame 560.
  • the legacy UE may bundle HARQ acknowledgment information 565 and 570 for transmission in subframe 7 of the second frame 560.
  • the non-legacy UE may have an uplink resource may bundle HARQ acknowledgement information 575-590 for transmission in subframe 7 of the second frame 560 as well.
  • the same uplink resource might be assigned to both UEs, resulting in a collision in transmissions received at the eNB.
  • various aspects of the present disclosure provide for determination of uplink resources for transmission of HARQ information which do not collide with similar transmission from other UEs.
  • the uplink resource may be, for example, an uplink resource for a physical uplink control channel (PUCCH) transmission when TDD reconfiguration is adopted for a UE.
  • PUCCH physical uplink control channel
  • FIG. 6 shows a block diagram of a communications system 600 that may be configured for determination of uplink resources for transmission of HARQ information which do not collide with similar transmission from other UEs.
  • This system 600 may be an example of aspects of the system 100 depicted in FIG. 1, or system 300 of FIG. 3.
  • System 600 may include a base station 105-f.
  • the base station 105-f may include antenna(s) 645, a transceiver module 650, memory 670, and a processor module 660, which each may be in communication, directly or indirectly, with each other (e.g., over one or more buses 680).
  • the transceiver module 650 may be configured to communicate bi-directionally, via the antenna(s) 645, with UE devices 1 15-a, 1 15-b.
  • the transceiver module 650 (and/or other components of the base station 105-f) may also be configured to communicate bi- directionally with one or more networks.
  • the base station 105-f may communicate with the core network 130-a through network communications module 665.
  • Base station 105-f may be an example of an eNodeB base station, a Home eNodeB base station, a NodeB base station, and/or a Home NodeB base station.
  • Base station 105-f may also communicate with other base stations 105, such as base station 105-m and base station 105-n. In some cases, base station 105-f may communicate with other base stations such as 105-m and/or 105-n utilizing base station communication module 615. In some embodiments, base station communication module 615 may provide an X2 interface within an LTE wireless communication technology to provide communication between some of the base stations 105. In some embodiments, base station 105-f may communicate with other base stations through core network 130-a.
  • the memory 670 may include random access memory (RAM) and read-only memory (ROM).
  • the memory 670 may also store computer-readable, computer-executable software code 675 containing instructions that are configured to, when executed, cause the processor module 660 to perform various functions described herein (e.g., call processing, database management, message routing, etc.).
  • the software code 675 may not be directly executable by the processor module 660 but be configured to cause the processor, e.g., when compiled and executed, to perform functions described herein.
  • the processor module 660 may include an intelligent hardware device, e.g., a central processing unit (CPU), a microcontroller, an application-specific integrated circuit (ASIC), etc.
  • the transceiver module(s) 650 may include a modem configured to modulate the packets and provide the modulated packets to the antenna(s) 645 for transmission, and to demodulate packets received from the antenna(s) 645. While some examples of the base station 105-f may include a single antenna 645, the base station 105-f may include multiple antennas 645 for multiple links which may support carrier aggregation. For example, one or more links may be used to support macro communications with UE devices 115-a, 115-b.
  • the base station 105-f may further include a communications management module 640.
  • the communications management module 640 may manage communications with other base stations 105.
  • the communications management module 640 may be a component of the base station 105-f in communication with some or all of the other components of the base station 105-f via a bus 680.
  • functionality of the communications management module 640 may be implemented as a component of the transceiver module 650, as a computer program product, and/or as one or more controller elements of the processor module 660.
  • the transceiver module 650 in conjunction with antenna(s) 645, along with other possible components of base station 105-f, may determine TDD UL- DL configurations for various UEs communicating with the base station 105-f, and also determine uplink HARQ resources for non-legacy UEs that may be reconfigured with different TDD UL-DL configurations.
  • base station 105-f includes a TDD UL-DL configuration selection module 620 that determines a TDD UL-DL
  • UEs 115-a, 115-b may include legacy UEs and non-legacy UEs, and TDD UL-DL configuration module 620 may determine UL-DL configurations for both legacy and non-legacy UEs.
  • UE 1 15-a may be a legacy UE
  • UE 1 15-b may be a non- legacy UE.
  • the TDD UL-DL configuration for legacy UE 115-a may be transmitted using SIB1.
  • an initial TDD UL-DL configuration for non-legacy UE 115-b may be transmitted using SIB1.
  • TDD UL-DL configuration selection module 620 may determine that the UL-DL configuration for non-legacy UE 1 15-b is to be reconfigured to a different UL-DL configuration. For example, changes in traffic between the base station 105-f and non-legacy UE 1 15-b may change such that additional data is to be transmitted to non-legacy UE 1 15-b, in which case TDD UL-DL configuration selection module 620 may determine that non-legacy UE 1 15-b is to be reconfigured to operate according to a different UL-DL configuration.
  • Base station 105-f may transmit the new TDD UL-DL configuration to the non-legacy UE 1 15-f through TDD UL-DL configuration transmission module 625, in conjunction with transceiver module(s) 650.
  • TDD UL-DL configuration selection module 620 may also periodically determine that the TDD UL-DL configuration for legacy UE 1 15-a is to be changed, in which case updated SIB 1 blocks may be transmitted using TDD UL-DL configuration transmission module 625, in conjunction with transceiver module(s) 650.
  • uplink resources for transmission of HARQ information may be determined so as to avoid collision between transmissions of HARQ information from legacy UEs and non-legacy UEs.
  • Base station 105-f in embodiments includes uplink HARQ resource determination module 630.
  • the uplink HARQ resource determination module 630 may, in some embodiments, assign non-legacy UE 115-b to have a different resource index
  • uplink HARQ resource determination module 630 may assign non-legacy UE 1 15-b a set of semi-static dedicated uplink resources for transmission of HARQ information, one of which may be selected for transmission of HARQ information based on a number of downlink subframes that are included in the HARQ information.
  • uplink HARQ resource determination module 630 may assign uplink resources for HARQ information transmission that are based on common and different downlink subframes that are received at each UE 1 15-a and 115-b.
  • HARQ information for subframes that are common between bundling sets for UEs 1 15-a and 1 15-b are sent in a first portion of an uplink resource-having the same offset value for transmission on the uplink resource, and subframes that are not common between bundling sets for the different TDD UL-DL configurations sent in a second portion of an uplink resource-having different offset value for transmission on the uplink resource of the non- legacy UE.
  • Uplink HARQ resource transmission module 635 in conjunction with transceiver module(s) 650 is used to transmit the uplink resource information to the non-legacy UE 115-b.
  • Legacy UE 115-a will continue to operate according to established standards for determining the uplink resource to be used for transmission of HARQ information.
  • uplink HARQ resource determination module 630 may, in some embodiments, assign non-legacy UE 115-b to have a different resource index
  • FIG. 7 illustrates an example of such different offset values, in which a legacy UE may have a uplink resources 705 that is determined from a first resource index offset (e.g., N_PUCCH A 1, 1), and the non - legacy UE may be signaled with a second resource index offset (e.g., N_PUCCH A 1, 2) that allows the uplink resources 710 for transmission of HARQ information from the non-legacy UE to be non-overlapping, or orthogonal, with uplink resources 705 of a legacy UE.
  • a first resource index offset e.g., N_PUCCH A 1, 1
  • a second resource index offset e.g., N_PUCCH A 1, 2
  • the resource index for the legacy UE may be determined according to, for example, methods as described in 3GPP Technical Specification 36.213.
  • the resource index (n P( , CCH ⁇ ) for the non-legacy UE may be calculated in a manner that is slightly modified from that described in 3GPP Technical Specification 36.213.
  • the resource index for a legacy UE is calculated according ton pyCCH .
  • the uplink resource for the non-legacy UE is has a different offset value that provides uplink resources for the legacy and non-legacy UEs that are non-overlapping.
  • the information related to the index value, or offset, for the non-legacy UE to use may be transmitted along with the UL- DL reconfiguration message that is sent to the non-legacy UE.
  • This information may be determined by the uplink HARQ resource determination module 630, and transmitted by the uplink HARQ resource transmission module 635 of FIG. 6, for example.
  • a set of semi-static resources 805 is determined for uplink transmission of HARQ information from a non-legacy UE that has a reconfigured TDD UL-DL configuration.
  • the semi-static resources 805 may correspond to resource index values between 0 and Np 1 CCH , and dynamic resources 810 may be provided having resource with greater resource index values.
  • the semi-static resources 805 selected for the non-legacy UE uplink resources may be selected such that the uplink resources for legacy and non-legacy UEs are non-overlapping.
  • semi-static resources 805-a include a set of four available uplink resources.
  • the semi-static resources 805-a to be used by a non-legacy UE are transmitted in a downlink assignment index (DAI) field transmitted in the Physical Downlink Control Channel (PDCCH).
  • DAI field in this example, is a binary count of the number of scheduled downlink subframes in a bundling set for the particular TDD UL-DL configuration. Each different value in the DAI field is assigned a different resource index that is selected to provide uplink resources that are non-overlapping with uplink resources assigned to legacy UEs.
  • the information related to the semi-static uplink resources for non-legacy UEs may be transmitted along with the UL-DL reconfiguration message that is sent to the non-legacy UEs. This information may be determined by the uplink HARQ resource determination module 630, and transmitted by the uplink HARQ resource transmission module 635 of FIG. 6, for example.
  • FIG. 9 Another example for determination of uplink resources for transmitting HARQ information is described.
  • common downlink subframes from a bundling set for the legacy and non-legacy UEs are determined, based in the different TDD UL-DL configurations for the UEs.
  • a first portion 905 of the uplink resource is determined for the common downlink subframes between the bundling sets of the different TDD UL-DL configurations for the UEs .
  • a second portion 910 of the uplink resource is then determined for downlink subframes that are additionally defined by reconfiguration.
  • the second portion 910 has an offset value for the resource index such that the uplink resources of the first and second portions 905, 910 are non-overlapping.
  • This information may be determined by the uplink HARQ resource determination module 630, and transmitted by the uplink HARQ resource transmission module 635 of FIG. 6, for example.
  • This particular example may rely on common downlink subframes of the bundling set being distinguished in the uplink resource assignment by the lowest CCE index, according to established techniques to determine such uplink resources.
  • the non-legacy UE uses a different resource index offset value and a different bundling set size that corresponds to the incremental set size of the reconfigured UL-DL configuration to determine uplink resources to use for the non-overlapping subframes.
  • the additional uplink resources corresponding to the HARQ information for the additional downlink subframes are non-overlapping with the first portion 905 of the uplink resources. Furthermore, the incremental uplink resources associated with the additional downlink subframes may consume less PUCCH resources than would be used of completely non-overlapping resources of example in FIG. 7 were used for transmission of all uplink HARQ information.
  • FIG. 10 illustrates an example of common downlink subframes from a bundling set for the legacy and non-legacy UEs being determined and uplink resources determined based on common and incremental downlink subframes, as described with respect to FIG. 9.
  • a first frame 1005 has TDD UL-DL configuration 1
  • second frame 1010 has TDD UL-DL configuration 2 for the non-legacy UE.
  • a legacy UE would to operate according to UL-DL configuration 1 in the second frame 1010.
  • sub frame 7 of the second frame 1010 us used to transmit HARQ information corresponding to multiple downlink subframes using bundling of HARQ information.
  • the legacy UE during the second frame 1010, bundles HARQ acknowledgments 1065 and 1070 from subframes 0 and 1 of the second frame 1010, and transmits the HARQ information in uplink subframe 7.
  • UL- DL configuration 2 has a bundling set 1075-1090 that includes HARQ information from subframe 9 from the first frame 1005, along with subframes 0, 1 , and 3 from the second frame 1010, which is also transmitted during subframe 7 in the second frame 1010.
  • the resource index is calculated for each of the UEs according to established techniques, and uplink resources assigned based on the calculated resource index.
  • the non-legacy UE receives a resource index so as to provide non-overlapping uplink resources between the common subframe uplink resources and the incremental subframe resources.
  • a base station may determine the TDD UL-DL configuration and reconfiguration associated with a UE, and also determine the uplink resources that the UE is to use to transmit HARQ information back to the base station.
  • System 1100 includes a UE 115-d that may communicate with base station 105-g to receive access to one or more wireless networks, and may be an example of aspects of the system 100 of FIG. 1, system 300 of FIG. 3, or system 600 of FIG. 6.
  • UE 115-c may be an example of a user equipment 115 of FIGS. 1 , 3, or 6.
  • UE 115-c includes one or more antenna(s) 1105 communicatively coupled to receiver module(s) 1 1 10 and transmitter module(s) 1115, which are in turn communicatively coupled to a control module 1120.
  • Control module 1120 includes one or more processor module(s) 1 125, a memory 1130 that may include software 1135, and a TDD reconfiguration module 1140.
  • the software 1135 may be for execution by processor module 1125 and/or TDD reconfiguration module 1140.
  • the processor module(s) 1125 may include an intelligent hardware device, e.g., a central processing unit (CPU), a microcontroller, an application specific integrated circuit (ASIC), etc.
  • the memory 1130 may include random access memory (RAM) and read-only memory (ROM).
  • the memory 1130 may store computer-readable, computer-executable software code 1135 containing instructions that are configured to, when executed (or when compiled and executed), cause the processor module 1125 and/or TDD reconfiguration module 1140 to perform various functions described herein (e.g., TDD UL-DL
  • the TDD reconfiguration module 1140 may be implemented as a part of the processor module(s) 1125, or may be implemented using one or more separate CPUs or ASICs, for example.
  • the transmitter module(s) 1115 may transmit to base station 105-g (and/or other base stations) to establish communications with one or more wireless communications networks (e.g., E- UTRAN, UTRAN, etc.), as described above.
  • the TDD reconfiguration module 1 140 may be configured to receive TDD reconfiguration messages from base station 105-g and change a TDD UL-DL configuration based on the received messages.
  • the TDD reconfiguration module 1 140 may also be configured to receive uplink resource information for the transmission of HARQ information, and calculate HARQ information and send the information on the identified resource, in accordance with examples as described above.
  • the receiver module(s) 1110 may receive downlink transmissions from base station 105-d (and/or other base stations), as described above. Downlink transmissions are received and processed at the user equipment 115-c.
  • the components of UE 115-c may, individually or collectively, be implemented with one or more Application Specific Integrated Circuits (ASICs) adapted to perform some or all of the applicable functions in hardware.
  • ASICs Application Specific Integrated Circuits
  • Each of the noted modules may be a means for performing one or more functions related to operation of the UE 1 15-c.
  • FIG. 12 illustrates an example of a TDD reconfiguration module 1140-a, which includes a TDD UL-DL configuration determination module 1205, a HARQ uplink resource determination module 1210, a HARQ ACK/NACK determination module 1215, and a HARQ ACK/NACK transmission module 1220.
  • the TDD UL-DL configuration determination module 1205 may receive TDD UL-DL configuration information from a base station, and set the TDD UL-DL configuration according to the information. This information may be received through a system information block (e.g., SIB1), or may be received through one or more reconfiguration messages received from the base station in accordance with elMTA, for example.
  • SIB1 system information block
  • the HARQ uplink resource determination module 1210 may receive uplink resource information for use in transmitting HARQ information associated with the particular TDD UL-DL configuration.
  • the HARQ uplink resource determination module 1210 may receive uplink resource information similarly as described above, and transmit HARQ information on uplink resources that are orthogonal to uplink resources used by legacy UEs to transmit HARQ information.
  • HARQ ACK/NACK determination module 1215 may determine the appropriate ACK/NACK message to transmit based on the successful or unsuccessful receipt of downlink data in the associated downlink subframes.
  • the HARQ ACK NACK transmission module 1220 may receive the ACK/NACK information and the uplink resource information, and transmit the HARQ information on the identified uplink resource.
  • TDD reconfiguration module 1140-a may, individually or collectively, be implemented with one or more ASICs adapted to perform some or all of the applicable functions in hardware.
  • Each of the noted modules may be a means for performing one or more functions related to operation of the TDD reconfiguration module 1 140-a.
  • FIG. 13 is a block diagram of a system 1300 including a base station 105-h and a mobile device 1 15-d.
  • This system 1300 may be an example of the system 100 of FIGS. 1, system 300 of FIG. 3, system 600 of FIG. 6, or system 1 100 of FIG. 1 1.
  • the base station 105-h may be equipped with antennas 1334-a through 1334-x
  • the mobile device 1 15-d may be equipped with antennas 1352-a through 1352-n.
  • a transmit processor 1320 may receive data from a data source.
  • the transmit processor , 1320 may process the data.
  • the transmit processor 1320 may also generate reference symbols, and a cell-specific reference signal.
  • a transmit (TX) MIMO processor 1330 may perform spatial processing (e.g., precoding) on data symbols, control symbols, and/or reference symbols, if applicable, and may provide output symbol streams to the transmit modulators 1332-a through 1332-x.
  • Each modulator 1332 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream.
  • Each modulator 1332 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink (DL) signal.
  • DL signals from modulators 1332-a through 1332-x may be transmitted via the antennas 1334-a through 1334-x, respectively according to a particular TDD Uplink/Downlink configuration.
  • the mobile device antennas 1352-a through 1352-n may receive the DL signals according to the particular TDD Uplink/Downlink configuration from the base station 105-h and may provide the received signals to the demodulators 1354-a through 1354-n, respectively.
  • Each demodulator 1354 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples.
  • Each demodulator 1354 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols.
  • a MIMO detector 1356 may obtain received symbols from all the demodulators 1354-a through 1354-n, perform MIMO detection on the received symbols if applicable, and provide detected symbols.
  • a receive processor 1358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, providing decoded data for the mobile device 1 15-d to a data output, and provide decoded control information to a processor 1380, or memory 1382.
  • the processor 1380 may be coupled with a TDD reconfiguration module 1384 that may reconfigure the TDD UL-DL configuration of mobile device 115-d, such as described above.
  • the processor 1380 may perform frame formatting according to a current TDD UL/DL configuration, and may thus flexibly configure the TDD UL/DL frame structure based on the current UL/DL configuration of the base station 105-h.
  • a transmit processor 1364 may receive and process data from a data source.
  • the transmit processor 1364 may also generate reference symbols for a reference signal.
  • the symbols from the transmit processor 1364 may be precoded by a transmit MIMO processor 1366 if applicable, further processed by the demodulators 1354-a through 1354-n (e.g., for SC-FDMA, etc.), and be transmitted to the base station 105-h in accordance with the transmission parameters received from the base station 105-h.
  • the UL signals from the mobile device 115-d may be received by the antennas 1334, processed by the demodulators 1332, detected by a MIMO detector 1336 if applicable, and further processed by a receive processor 1338.
  • the receive processor 1338 may provide decoded data to a data output and to the processor 1340.
  • a memory 1342 may be coupled with the processor 1340.
  • the processor 1340 may perform frame formatting according to a current TDD UL/DL configuration.
  • a TDD UL/DL configuration module 1344 may, in some embodiments, configure or reconfigure the base station 105-h, or one or more carriers of the base station 105-h, to operate according to different TDD UL/DL configurations, and transmit information related to the reconfigured UL-DL configurations to mobile device 1 15-d, along with uplink resource information for transmission of HARQ information.
  • system 1300 may support operation on multiple component carriers, each of which include waveform signals of different frequencies that are transmitted between base station 105-h and devices 115-5. Multiple component carriers may carry uplink and downlink transmissions between mobile device 115-d and base station 105-h, and base station 105-h may support operation on multiple component carriers that may each have different TDD configurations.
  • the TDD UL/DL configuration module 1344 may dynamically reconfigure the TDD UL/DL configuration of base station 105-h carriers according to real-time or near real- time communications through the base station 105-h.
  • the components of the mobile device 115-d may, individually or collectively, be implemented with one or more Application Specific Integrated Circuits (ASICs) adapted to perform some or all of the applicable functions in hardware.
  • ASICs Application Specific Integrated Circuits
  • Each of the noted modules may be a means for performing one or more functions related to operation of the system 1300.
  • the components of the base station 105-h may, individually or collectively, be implemented with one or more Application Specific Integrated Circuits (ASICs) adapted to perform some or all of the applicable functions in hardware.
  • ASICs Application Specific Integrated Circuits
  • Each of the noted components may be a means for performing one or more functions related to operation of the system 1300.
  • FIG. 14 illustrates a method 1400 that may be carried out by a base station a wireless communications system according to various embodiments.
  • the method 1 00 may, for example, be performed by a base station of FIG. 1, 3, 6, 11, or 13, or using any combination of the devices described for these figures.
  • the base station determines that a first UE is to operate using a first UL-DL configuration and that a second UE is to operate using a second UL-DL configuration for a TDD frame.
  • the first UE may be a legacy UE
  • the second UE may be a non-legacy UE that may operate according to elMTA to be reconfigured to change TDD UL-DL configurations.
  • the base station determines a first uplink resource for transmission of HARQ information associated with the first UL-DL configuration.
  • the first uplink resource may be determined based on established techniques for determining such a first uplink resource, such as described, for example, in 3GPP Technical Specification 36.213.
  • a second uplink resource is determined for transmission of HARQ information associated with the second UL-DL configuration for use by the second UE, as indicated at block 1415.
  • information related to the second uplink resource is transmitted for use by the second UE.
  • the second UE may thus transmit HARQ information using the second resource in a non-overlapping matter so as to avoid collision with the first uplink resource.
  • the base station determines that a first UE is to operate using a first UL-DL configuration and that a second UE is to operate using a second UL-DL configuration for a TDD frame.
  • the first UE may be a legacy UE
  • the second UE may be a non-legacy UE that may operate according to elMTA to be reconfigured to change TDD UL-DL configurations.
  • the base station determines a first uplink resource for transmission of HARQ information associated with the first UL-DL configuration.
  • the first uplink resource may be determined based on established techniques for determining such a first uplink resource, such as described, for example, in 3GPP Technical Specification 36.213.
  • a set of semi-static uplink resources is determined for use with the second UL-DL configuration such that the first and second uplink resources are non-overlapping, as indicated at block 1515.
  • information related to the set of semi-static uplink resources is transmitted for use by the second UE.
  • the second UE may thus transmit HARQ information using the second resource in a non-overlapping matter so as to avoid collision with the first uplink resource.
  • FIG. 16 illustrates another method 1600 that may be carried out by a base station a wireless communications system according to various embodiments.
  • the method 1600 may, for example, be performed by a base station of FIG. 1, 3, 6, 11, or 13, or using any combination of the devices described for these figures.
  • the base station determines that a first UE is to operate using a first UL-DL configuration and that a second UE is to operate using a second UL-DL configuration for a TDD frame.
  • the first UE may be a legacy UE
  • the second UE may be a non-legacy UE that may operate according to elMTA to be reconfigured to change TDD UL-DL configurations.
  • the base station determines a first uplink resource for transmission of HARQ information associated with the first UL-DL configuration.
  • the first uplink resource may be determined based on established techniques for determining such a first uplink resource, such as described, for example, in 3GPP Technical Specification 36.213.
  • a set of semi-static uplink resources is determined for use with the second UL-DL configuration such that the first and second uplink resources are non-overlapping, as indicated at block 1615.
  • information related to the set of semi-static uplink resources is transmitted for use by the second UE.
  • FIG. 17 illustrates another method 1700 that may be carried out by a base station a wireless communications system according to various embodiments.
  • the method 1700 may, for example, be performed by a base station of FIG. 1, 3, 6, 1 1, or 13, or using any combination of the devices described for these figures.
  • the base station determines common downlink subframes from a bundling set for the first and second TDD UL-DL configurations.
  • the base station determines a first portion of the second uplink resource based on the common downlink subframes that overlaps with the first uplink resource.
  • An offset value is determined for a second portion of the second uplink resource such that the first uplink resource and the second portion of the second uplink resource are non-overlapping, as indicated at block 1715.
  • information related to the offset value is transmitted for use by the second UE.
  • FIG. 18 illustrates another method 1800 that may be carried out by a user equipment in a wireless communications system according to various embodiments.
  • the method 1800 may, for example, be performed by a user equipment of FIG. 1, 3, 6, 11, or 13, or using any combination of the devices described for these figures.
  • the user equipment receives a TDD reconfiguration message indicating the UE is to operate using a second UL-DL configuration for a TDD frame that is different than a first UL-DL configuration received in a system information block (SIB).
  • SIB system information block
  • the user equipment processes the TDD reconfiguration message to determine a second uplink resource for transmission of hybrid automatic repeat request (HARQ) information associated with the second UL-DL configuration for the TDD frame, the second uplink resource being non- overlapping with a first uplink resource for transmission of HARQ information associated with the first UL-DL configuration.
  • the UE may thus transmit HARQ information using the second resource in an orthogonal manner relative to the uplink resource for the first TDD UL-DL configuration, so as to avoid collision with the first uplink resource.
  • HARQ hybrid automatic repeat request
  • 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.
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope and spirit of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • 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 des procédés, des appareils, et des produits programmes d'ordinateur permettant de déterminer des ressources sur la liaison montante pour transmettre une requête automatique de répétition hybride (HARQ) d'une première configuration liaison montante-liaison descendante (UL-DL) à une seconde configuration UL-DL dans une reconfiguration TDD UL-DL. Une première ressource en liaison montante servant à transmettre des informations HARQ associées à la première configuration UL-DL est déterminée, et une seconde ressource en liaison montante servant à transmettre des informations HARQ associées à la seconde configuration UL-DL est déterminée à partir de la première ressource en liaison montante. Les informations associées à la seconde ressource en liaison montante, devant être utilisées par le ou les équipements utilisateurs (UE) reconfigurés, sont transmises au/aux UE reconfigurés. Le ou les UE reconfigurés reçoivent un message de reconfiguration et des informations sur la seconde ressource en liaison montante, et ils transmettent les informations HARQ avec la seconde ressource pour les trames reconfigurées.
PCT/CN2013/000043 2013-01-17 2013-01-17 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 Ceased WO2014110690A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/000043 WO2014110690A1 (fr) 2013-01-17 2013-01-17 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

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/000043 WO2014110690A1 (fr) 2013-01-17 2013-01-17 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

Publications (1)

Publication Number Publication Date
WO2014110690A1 true WO2014110690A1 (fr) 2014-07-24

Family

ID=51208909

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/000043 Ceased WO2014110690A1 (fr) 2013-01-17 2013-01-17 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

Country Status (1)

Country Link
WO (1) WO2014110690A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200037187A1 (en) * 2017-01-16 2020-01-30 Telefonaktiebolaget Lm Ericsson (Publ) Common PDCCH Configuration

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101588337A (zh) * 2008-05-22 2009-11-25 大唐移动通信设备有限公司 时分复用帧结构参数优化方法、通信方法、系统及终端
US20110176461A1 (en) * 2009-12-23 2011-07-21 Telefonakatiebolaget Lm Ericsson (Publ) Determining configuration of subframes in a radio communications system
CN102355731A (zh) * 2011-08-01 2012-02-15 中兴通讯股份有限公司 Tdd系统中进行数据传输的基站、终端、系统及方法
US20120230232A1 (en) * 2011-03-10 2012-09-13 Samsung Electronics Co., Ltd. Flexible time division duplex method and apparatus for communication system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101588337A (zh) * 2008-05-22 2009-11-25 大唐移动通信设备有限公司 时分复用帧结构参数优化方法、通信方法、系统及终端
US20110176461A1 (en) * 2009-12-23 2011-07-21 Telefonakatiebolaget Lm Ericsson (Publ) Determining configuration of subframes in a radio communications system
US20120230232A1 (en) * 2011-03-10 2012-09-13 Samsung Electronics Co., Ltd. Flexible time division duplex method and apparatus for communication system
CN102355731A (zh) * 2011-08-01 2012-02-15 中兴通讯股份有限公司 Tdd系统中进行数据传输的基站、终端、系统及方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200037187A1 (en) * 2017-01-16 2020-01-30 Telefonaktiebolaget Lm Ericsson (Publ) Common PDCCH Configuration
US11622290B2 (en) * 2017-01-16 2023-04-04 Telefonaktiebolaget Lm Ericsson (Publ) Common PDCCH configuration

Similar Documents

Publication Publication Date Title
EP2946627B1 (fr) Procédés et appareil de reconfiguration hybride permettant une adaptation tdd
US11337245B2 (en) TDD reconfiguration with consideration of DTX/DRX
EP3050240B1 (fr) Chronologie de processus harq à retard réduit pour agrégation de porteuses fdd-tdd
US10341896B2 (en) CSI reporting for LTE-TDD eIMTA
JP6208337B2 (ja) 簡単化されたｆｄｄ−ｔｄｄキャリアアグリゲーション
US10263729B2 (en) Uplink signaling for dual connectivity
WO2014180318A1 (fr) Atténuation d'interférence entre des grappes de cellules, basée sur un seuil double, pour eimta
WO2014166060A1 (fr) Signalisation destinée à indiquer la configuration de sous-trame de liaison montante-liaison descendante de drt dans la technologie lte
WO2015018073A1 (fr) Groupage et multiplexage d'a/n hybride en eimta
WO2014153688A1 (fr) Conception de gestion des temps harq pour frontière de reconfiguration 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: 13872086

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: 13872086

Country of ref document: EP

Kind code of ref document: A1