Apparatus and method for defining physical channel transmit/receive timings and resource allocation in tdd communication system supporting carrier aggregation
Abstract
This record has no abstract on file.
Term
5.7 yearsleft in the term
Expires 31 May 2032.
- Priority and filed
- Granted
- Today
- Expires
15 claims: 4 independent, 11 dependent
- 1A method for transmitting a signal in a wireless communication system supporting carrier aggregation of a primary cell (401, 601, 701, 801) and a secondary cell (403, 602, 702, 802), wherein the primary cell is configured according to a first uplink/downlink, UL/DL, configuration and the secondary cell is configured according to a second UL/DL configuration, the method comprising:transmitting, by a base station, first data on a first subframe of the secondary cell based on the second UL/DL configuration;and receiving, by the base station, a hybrid automatic repeat request acknowledgement/negative acknowledgement, HARQ ACK/NACK, corresponding to the first data on a second subframe of the primary cell, the second subframe being identified based on the first UL/DL configuration.
- 4A method for receiving a signal in a wireless communication system supporting carrier aggregation of a primary cell (401, 601, 701, 801) and a secondary cell (403, 602, 702, 802), wherein the primary cell is configured according to a first uplink/downlink, UL/DL, configuration and the secondary cell is configured according to a second UL/DL configuration , the method comprising:receiving, by the terminal, first data on a first subframe of the secondary cell based on the second UL/DL configuration;and transmitting, by the terminal, a hybrid automatic repeat request acknowledgement/negative acknowledgement, HARQ ACK/NACK, corresponding to the first data on a second subframe of the primary cell, the second subframe being identified based on the first UL/DL configuration.
- 8A base station for transmitting a signal in a wireless communication system supporting carrier aggregation of a primary cell (401, 601, 701, 801) and a secondary cell (403, 602, 702, 802), wherein the primary cell is configured according to a first uplink/downlink, UL/DL, configuration and the secondary cell is configured according to a second UL/DL configuration, the base station comprising:a transceiver for transmitting and receiving a signal: and a controller (1201) configured to: transmit first data on a first subframe of the secondary cell based on the second UL/DL configuration, and receive a hybrid automatic repeat request acknowledgement/negative acknowledgement, HARQ ACK/NACK, corresponding to the first data on a second subframe of the primary cell (401, 601, 701, 801), the second subframe being identified based on the first UL/DL configuration.
- 12A terminal for receiving a signal by a terminal in a wireless communication system supporting carrier aggregation of a primary cell (401, 601, 701, 801) and a secondary cell (403, 602, 702, 802), wherein the primary cell is configured according to a first uplink/downlink, UL/DL, configuration and the secondary cell is configured according to a second UL/DL configuration, the terminal comprising:a transceiver for transmitting and receiving a signal: and a controller (1301) configured to: receive first data on a first subframe of the secondary cell based on the second UL/DL configuration, and transmit a hybrid automatic repeat request acknowledgement/negative acknowledgement, HARQ ACK/NACK, corresponding to the first data on a second subframe of the primary cell (401, 601, 701, 801), the second subframe being identified based on the first UL/DL configuration.
Independent claims4
179 paragraphs, as filed
<u>BACKGROUND OF THE INVENTION</u>
1. Field of the Invention:
0001The present invention relates to a wireless communication system. More particularly, the present invention relates to a method for defining physical channel transmit/receiving timings and resource allocation in a Time Division Duplex (TDD) communication system supporting carrier aggregation.
2. Description of the Related Art:
0002The mobile communication system has evolved into a high-speed, high-quality wireless packet data communication system (such as 3rd Generation Partnership Project (3GPP) High Speed Packet Access (HSPA) and Long Term Evolution (LTE), 3GPP2 High Rate Packet Data (HRPD), Ultra Mobile Broadband (UMB), and Institute of Electrical and Electronics Engineers (IEEE) 802.16e standard systems) to provide data and multimedia services beyond voice-oriented services.
0003As a representative broadband radio communication standard, LTE adopts Orthogonal Frequency Division Multiplexing (OFDM) in the downlink and Single Carrier Frequency Division Multiple Access (SC-FDMA) in the uplink. Such a multiple access technique is characterized in that the time-frequency resources carrying data or control information are arranged orthogonally to discriminate among the per-user data and/or control information.
0004In order to prepare against a decoding failure that occurs at initial transmission, LTE adopts Hybrid Automatic Repeat Request (HARQ) for retransmission of the decoding-failed data on the physical layer.
0005HARQ is a technique in which, when decoding fails, the receiver sends the transmitter a Negative ACKnowledgement (NACK) such that the transmitter retransmits the decoding-failed data. If the data is decoded successfully, the receiver sends the transmitter an ACKnowledgement (ACK) such that the transmitter sends new data.
0006One of the important features of the broadband communication system is to support a scalable bandwidth for providing a high speed data service. For example, the Long Term Evolution (LTE) system can support various bandwidths, e.g., 20/15/5/3/1.4 Mhz. The service providers can provide the service on a specific bandwidth selected among the diverse bandwidths. Likewise, there can be various terminals having different LTE capabilities for supporting a minimum 1.4 MHz bandwidth and up to a 20 MHz bandwidth.
0007Meanwhile, LTE-Advanced (LTE-A) aiming to meet the IMT-Advanced requirements can provide a broadband service at a data rate of up to 100 MHz through carrier aggregation. In order to support the high data rate transmission, the LTE-A system requires a bandwidth wider than that of the LTE system while preserving backward compatibility to the legacy systems for supporting LTE User Equipment (UE). For backward compatibility, system bandwidth of the LTE-A system is divided into a plurality of subbands or Component Carriers (CC) that can be used for transmission/reception of LTE UEs and aggregated for the high data rate transmission of the LTE-A system with the transmission/reception process of the legacy LTE system per component carrier.
0008Typically, the scheduling information for the data to be transmitted on the component carriers is transmitted to the UE in Downlink Control Information (DCI). The DCI can be defined in various formats, and one of the predefined DCI formats can be used according to whether scheduling information is for uplink or downlink, whether the DCI is compact DCI, whether spatial multiplexing with multiple antennas is applied, and whether the DCI is the power control DCI. For example, the DCI format 1 carrying the control information on the uplink data transmitted without application of Multiple Input Multiple Output (MIMO) can include the following control information. <ul id="ul0001" list-style="bullet" compact="compact"><li>Resource allocation type 0/1 flag: to differentiate between resource allocation type 0 and resource allocation type 1. Type 0 allocates resources in a unit of Resource Block Groups (RBGs) using a bitmap format. In the LTE/LTE-A system, the scheduling resource unit is a Resource Block (RB) representing time and frequency resource region, and each RBG can be composed of a plurality of RBs. The RBG can be a basic unit of scheduling resources in type 0. In type 1, specific RB can be allocated in the RBG.</li><li>Resource block assignment: to indicate resource blocks to be assigned to the UE. The basic unit of radio resource allocation is an RB representing a time and frequency region.</li><li>Modulation and coding scheme and redundancy version: to indicate modulation scheme and coding rate used in data transmission.</li><li>HARQ process number: to indicate the number of a HARQ process.</li><li>New Data Indicator (NDI): to indicate whether the packet is a new transmission or a retransmission.</li><li>Redundancy version: to indicate the redundancy version of HARQ.</li><li>Transmission Power Control (TPC) command for Physical Uplink Shared Channel (PUSCH): to indicate TPC command for PUSCH.</li></ul>
0009The DCI is channel-coded and modulated and then transmitted on a Physical Downlink Control Channel (PDCCH).
0010<figref idref="f0001">FIG. 1</figref> is a diagram illustrating a principle of self-scheduling in an LTE-A system supporting carrier aggregation according to the related art. <figref idref="f0001">FIG. 1</figref> is directed to a situation where an evolved Node B (eNB) schedules downlink data of a UE in an LTE-A system operating with two component carriers (e.g., CC#1 and CC#2).
0011Referring to <figref idref="f0001">FIG. 1</figref>, the DCI 101 transmitted on the CC#1 109 is formatted as defined in the legacy LTE standard, channel-coded, and then interleaved to generate PDCCH 103. The PDCCH 103 carries the scheduling information 113 about the PDCCH as the data channel allocated to the UE on the CC#1 109. The DCI 105 transmitted on the CC#2 111 is formatted as defined in the legacy LTE standard, channel-coded, and then interleaved to generate PDCCH 107. The PDCCH 107 carries the scheduling information 115 about a Physical Downlink Shared Channel (PDSCH) as the data channel allocated to the UE on the CC#2 111.
0012In the LTE-A system supporting carrier aggregation, the data and/or DCI for supporting the data transmission can be transmitted per component carrier as shown in <figref idref="f0001">FIG. 1</figref>. Such a scheduling technique is referred to as self-scheduling. In a case of DCI, however, it can be transmitted on another component carrier different form the component carrier carrying the data, and this is referred to as cross carrier scheduling. In the exemplary case of <figref idref="f0001">FIG. 1</figref>, when it is difficult to expect high reliability of DCI reception performance due to high interference on the CC#2, the DCI can be transmitted on the CC#1, which is experiencing relatively low interference.
0013In a case of PDSCH carrying data, it is possible to overcome the interference with frequency selective scheduling or HARQ. In a case of PDCCH carrying DCI, however, HARQ is not applied and it is not possible to apply the frequency selective scheduling due to system band-wide transmission characteristic and thus there is a need of a method for mitigating interference.
0014<figref idref="f0002">FIG. 2</figref> is a diagram illustrating a principle of cross carrier scheduling in an LTE-A system supporting carrier aggregation according to the related art. <figref idref="f0002">FIG. 2</figref> is directed to an exemplary cross carrier scheduling for an LTE-A UE operating on two aggregated carriers CC#1 209 and CC#2 219. It is assumed that CC#2 experiences relatively large interference as compared to CC#1 such that, when transmitting DCI as the scheduling information for the data transmission on CC#2, it is difficult to expect satisfactory DCI reception performance.
0015Referring to <figref idref="f0002">FIG. 2</figref>, the eNB can transmit the DCI on CC#1 209. In order to support the cross carrier scheduling, the eNB transmits a Carrier Indicator (CI) indicating the component carrier targeted by the DCI along with the DCI indicating the resource allocation information and transmission format of the scheduled data. For example, CI='00' indicates CC#1 209 and, CI= '01' indicates CC#2 219.
0016The eNB combines the DCI 201 indicating resource allocation information and transmission format of the scheduled data 207 and the carrier indicator 202 to generate an extended DCI. The eNB performs channel coding, modulation, and interleaving on the extended DCI to generate a PDCCH 205. Here, the eNB maps the extended DCI to a respective region of the PDCCH 205 of CC#1 209.
0017The eNB combines the DCI 211 indicating the resource allocation information and transmission format of the data 217 scheduled on CC#2 and the carrier indicator 212 to generate an extended DCI. Next, the eNB maps the extended DCI to a respective region of the PDCCH 205 of CC#1 209.
0018The Time Division Duplex (TDD) system uses a common frequency for uplink and downlink which are discriminated in the time domain. In LTE and LTE-A TDD systems, the uplink and downlink signals are discriminated by subframe. A radio frame can be divided into equal number of uplink and downlink subframes according to the uplink and downlink traffic load. The number of uplink subframes may be greater than that of the downlink subframes and vice versa. In the LTE system, the subframe has a length of 1ms, 10 subframes form a radio frame. <tables id="tabl0001" num="0001"><table frame="all"><title>Table 1</title><tgroup cols="11"><colspec colnum="1" colname="col1" colwidth="53mm" /><colspec colnum="2" colname="col2" colwidth="8mm" /><colspec colnum="3" colname="col3" colwidth="8mm" /><colspec colnum="4" colname="col4" colwidth="8mm" /><colspec colnum="5" colname="col5" colwidth="8mm" /><colspec colnum="6" colname="col6" colwidth="8mm" /><colspec colnum="7" colname="col7" colwidth="8mm" /><colspec colnum="8" colname="col8" colwidth="8mm" /><colspec colnum="9" colname="col9" colwidth="8mm" /><colspec colnum="10" colname="col10" colwidth="8mm" /><colspec colnum="11" colname="col11" colwidth="8mm" /><thead><row><entry valign="top"><b>Up link-down link configuration</b></entry><entry namest="col2" nameend="col11" align="left" valign="top"><b>Subframe number</b></entry></row><row><entry valign="top" /><entry valign="top"><b>0</b></entry><entry valign="top"><b>1</b></entry><entry valign="top"><b>2</b></entry><entry valign="top"><b>3</b></entry><entry valign="top"><b>4</b></entry><entry valign="top"><b>5</b></entry><entry valign="top"><b>6</b></entry><entry valign="top"><b>7</b></entry><entry valign="top"><b>8</b></entry><entry valign="top"><b>9</b></entry></row></thead><tbody><row><entry>0</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>U</entry><entry>U</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>U</entry><entry>U</entry></row><row><entry>1</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>U</entry><entry>D</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>U</entry><entry>D</entry></row><row><entry>2</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>D</entry><entry>D</entry></row><row><entry>3</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>U</entry><entry>U</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>D</entry></row><row><entry>4</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>U</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>D</entry></row><row><entry>5</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>D</entry></row><row><entry>6</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>U</entry><entry>U</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>U</entry><entry>D</entry></row></tbody></tgroup></table></tables>
0019Table 1 shows TDD configurations (TDD uplink-downlink configurations) defined in the LTE standard. In Table 1, subframe numbers 0 to 9 indicate the indices of subframes constituting one radio frame. Here, 'D' denotes a subframe reserved for downlink transmission, 'U' denotes a subframe reserved for uplink transmission, and 'S' denotes a special subframe.
0020Downlink Pilot Time Slot (DwPTS) can carry the downlink control information as the normal subframe does. If the DwPTS is long enough according to the configuration state of the special subframe, it is possible to carry the downlink data too. Guard Period (GP) is the interval used for a downlink-to-uplink switch and its length is determined according to the network configuration. Uplink Pilot Time Slot (UpPTS) can be used for transmitting a UE's Sounding Reference Signal (SRS) for uplink channel state estimation and a UE's Random Access Channel (RACH).
0021In a case of TDD uplink-downlink configuration #6, the eNB can transmit downlink data and/or control information at subframes #0, #5, and #9 and uplink data and/control information at subframes #2, #3, #4, #7, and #8. Here, # indicates number or index. The subframes #1 and #6 as special subframes can be used for transmitting downlink control information and/or downlink data selectively and SRS or RACH in uplink.
0022Since the downlink or uplink transmission is allowed for specific time duration in the TDD system, the timing relationship among the uplink and downlink physical channels such as control channel for data scheduling, scheduled data channel, and HARQ ACK/NACK channel (HARQ acknowledgement) corresponding to the data channel should be defined.
0023In LTE and LTE-A TDD systems, the timing relationship between PDSCH and Physical Uplink Control channel (PUCCH) carrying uplink HARQ ACK/NACK corresponding to the PDSCH or PUSCH is as follows.
0024The UE receives the PDSCH transmitted by the eNB at an (n-k)<sup>th</sup> subframe and transmits an uplink HARQ ACK/NACK corresponding to the received PDSCH at an n<sup>th</sup> subframe. Here, k denotes an element of a set K, and K is defined as shown in Table 2. <tables id="tabl0002" num="0002"><table frame="all"><title>Table 2</title><tgroup cols="11"><colspec colnum="1" colname="col1" colwidth="37mm" /><colspec colnum="2" colname="col2" colwidth="8mm" /><colspec colnum="3" colname="col3" colwidth="9mm" /><colspec colnum="4" colname="col4" colwidth="37mm" /><colspec colnum="5" colname="col5" colwidth="17mm" /><colspec colnum="6" colname="col6" colwidth="10mm" /><colspec colnum="7" colname="col7" colwidth="8mm" /><colspec colnum="8" colname="col8" colwidth="8mm" /><colspec colnum="9" colname="col9" colwidth="17mm" /><colspec colnum="10" colname="col10" colwidth="8mm" /><colspec colnum="11" colname="col11" colwidth="8mm" /><thead><row><entry valign="top"><b>UL-DL Configuration</b></entry><entry namest="col2" nameend="col11" align="left" valign="top"><b>Subf rame <i>n</i></b></entry></row></thead><tbody><row><entry /><entry>0</entry><entry>1</entry><entry>2</entry><entry>3</entry><entry>4</entry><entry>5</entry><entry>6</entry><entry>7</entry><entry>8</entry><entry>9</entry></row><row><entry>0</entry><entry>-</entry><entry>-</entry><entry>6</entry><entry>-</entry><entry>4</entry><entry>-</entry><entry>-</entry><entry>6</entry><entry>-</entry><entry>4</entry></row><row><entry>1</entry><entry>-</entry><entry>-</entry><entry>7, 6</entry><entry>4</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>7, 6</entry><entry>4</entry><entry>-</entry></row><row><entry>2</entry><entry>-</entry><entry>-</entry><entry>8, 7, 4, 6</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>8, 7, 4, 6</entry><entry>-</entry><entry>-</entry></row><row><entry>3</entry><entry>-</entry><entry>-</entry><entry>7, 6, 11</entry><entry>6, 5</entry><entry>5, 4</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry></row><row><entry>4</entry><entry>-</entry><entry>-</entry><entry>12, 8, 7, 11</entry><entry>6, 5, 4. 7</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry></row><row><entry>5</entry><entry>-</entry><entry>-</entry><entry>13, 12, 9, 8, 7, 5, 4, 11, 6</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry></row><row><entry>6</entry><entry /><entry>- 7</entry><entry>7</entry><entry>7</entry><entry>5</entry><entry>-</entry><entry>-</entry><entry>7</entry><entry>7</entry><entry>-</entry></row></tbody></tgroup></table></tables>
0025<figref idref="f0003">FIG. 3</figref> is a diagram illustrating a timing relationship between a PDSCH and an uplink HARQ ACK/NACK in a legacy LTE system operating with TDD uplink-downlink configuration #6 according to the related art. <figref idref="f0003">FIG. 3</figref> shows which subframe carries uplink HARQ ACK/NACK corresponding to PDSCH that is transmitted in a downlink subframe or a special subframe in TDD uplink-downlink configuration #6 as defined in Table 2.
0026For example, the UE transmits, at subframe #7 of i<sup>th</sup> radio frame, the uplink HARQ ACK/NACK 303 corresponding to the PDSCH 301 transmitted by the eNB at subframe #1 of i<sup>th</sup> subframe. At this time, the DCI including the scheduling information on the PDSCH 301 is transmitted through a PDCCH of the subframe which also carries the PDSCH. For another example, the UE transmits, at the subframe #4 of (i+1)<sup>th</sup> radio frame, the uplink HARQ ACK/NACK 307 corresponding to PDSCH 305 transmitted by the eNB at subframe #9 of the i<sup>th</sup> radio frame. Likewise, the DCI including the scheduling information on the PDSCH 305 is transmitted through the PDCCH of the subframe which also carries PDSCH.
0027The LTE and LTE-A systems adopt an asynchronous HARQ in the downlink in which the data retransmission timing is not fixed. That is, when an HARQ ACK fed back by the UE in response to the HARQ initial transmission data transmitted by the eNB is received, the eNB determines the next HARQ retransmission timing freely according to the scheduling operation. The UE buffers the data that failed in decoding for a HARQ operation and combines the buffered data with the next HARQ retransmission data. In order to keep the reception buffer space to a predetermined level, a maximum number of HARQ processes are defined per TDD uplink-downlink configuration as shown in Table 3. One HARQ process is mapped to one subframe in time domain. <tables id="tabl0003" num="0003"><table frame="all"><title>Table 3</title><tgroup cols="2"><colspec colnum="1" colname="col1" colwidth="43mm" /><colspec colnum="2" colname="col2" colwidth="63mm" /><thead><row><entry align="center" valign="top"><b>TDD UI/DL configuration</b></entry><entry align="center" valign="top"><b>Maximum number of HARQ processes</b></entry></row></thead><tbody><row><entry align="center">0</entry><entry align="center">4</entry></row><row><entry align="center">I</entry><entry align="center">7</entry></row><row><entry align="center">2</entry><entry align="center">10</entry></row><row><entry align="center">3</entry><entry align="center">9</entry></row><row><entry align="center">4</entry><entry align="center">12</entry></row><row><entry align="center">5</entry><entry align="center">15</entry></row><row><entry align="center">6</entry><entry align="center">6</entry></row></tbody></tgroup></table></tables>
0028Referring to Table 3, if the PDSCH 301 transmitted by the eNB at subframe #0 of the i<sup>th</sup> radio frame fails to decode, the UE transmits an HARQ NACK at the subframe #7 of i<sup>th</sup> radio frame. Upon receipt of the HARQ NACK, the eNB configures the retransmission data corresponding to PDSCH 301 as PDSCH 309 and transmits the PDSCH 309 along with the PDCCH. In the exemplary case of <figref idref="f0003">FIG. 3</figref>, the retransmission data is transmitted in the subframe #1 of (i+1)<sup>th</sup> radio frame by taking notice that the maximum number of downlink HARQ processes is 6 in the TDD uplink-downlink configuration #6 according to the definition of Table 3. This means that there are a total of 6 downlink HARQ processes 311, 312, 313, 314, 315, and 316 between the initial transmission, i.e., PDSCH 301, and the retransmission, i.e., PDSCH 309.
0029In order to apply the timing relationships between a physical channel, which are specified for use in the LTE TDD system, to the LTE-A system, extra operations, in addition to the conventional timing relationships, should be defined. In more detail, there is a need for defining the timing relationship among the PDCCH, PDSCH and uplink HARQ ACK/NACK, and a method for allocating uplink HARQ ACK/NACK transmission resources for supporting self-scheduling and/or cross carrier scheduling in the situation where the TDD uplink-downlink configurations are adopted to the respective carriers aggregated differ from each other.
0030<patcit id="pcit0001" dnum="US2011044239A1"><text>US 2011/044239 A1</text></patcit> relates to a system and method for carrier activation. This document discloses a method for receiving data using a user agent (UA) configured to communicate with a wireless communications network using a first and second communication carrier. The method includes receiving control information at a first time interval using the first communication carrier. The control information allocates a resource on at least one of the first communication carrier and the second communication carrier. The control information indicates whether a carrier switch is required. In one implementation, when the control information indicates a carrier switch is required, the method includes ceasing signal reception on the first communication carrier, and receiving a signal on the second communication carrier.
<u>SUMMARY OF THE INVENTION</u>
0031Aspects of the present invention are to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below. The invention is defined by a method for transmitting a signal in a wireless communication system supporting carrier aggregation of a primary cell and a secondary cell, a method of receiving a signal in a wireless communication system supporting carrier aggregation of a primary cell and a secondary cell, a base station and a terminal corresponding to the methods according to the appended independent claims 1, 4, 8 and 12. Further embodiments are defined by the dependent claims. Embodiments defined herein which are not covered by the claims may be useful for understanding the invention.
0032Accordingly, an aspect of the present invention to define the timing relationship among Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), and uplink Hybrid Automatic Repeat Request (HARQ) ACKnowledgement (ACK)/Negative ACK (NACK) and provide a method for allocating uplink HARQ ACK/NACK transmission resources in a Time Division Duplex (TDD) wireless communication system achieving broadband resources with carrier aggregation, especially when the aggregated carriers use different TDD uplink-downlink configurations.
0033In accordance with an aspect of the present invention, a method for receiving, at a base station, a HARQ acknowledgement from a terminal in a TDD system supporting carrier aggregation of a primary cell and at least one secondary cell is provided. The method includes transmitting a downlink physical channel through one of the primary and secondary cells, receiving the HARQ acknowledgement corresponding to the downlink physical channel of the primary cell at a first timing predetermined for the primary cell, and receiving the HARQ acknowledgement corresponding to the downlink physical channel of the secondary cell at second timing, wherein the second timing is determined according to the first timing.
0034In accordance with another aspect of the present invention, a method for transmitting, at a terminal, a HARQ acknowledgement to a base station in a TDD system supporting carrier aggregation of a primary cell and at least one secondary cell is provided. The method includes receiving a downlink physical channel through one of the primary and second cells, transmitting the HARQ acknowledgement corresponding to the downlink physical channel of the primary cell at a first timing predetermined for the primary cell, and transmitting the HARQ acknowledgement corresponding to the downlink physical channel of the secondary cell at a second timing, wherein the second timing is determined according to the first timing.
0035In accordance with still another aspect of the present invention, a terminal for transmitting a HARQ acknowledgement to a base station in a TDD system supporting carrier aggregation of a primary cell and at least one secondary cell is provided. The terminal includes a transceiver which transmits and receives to and form a base station, and a controller which controls receiving a downlink physical channel through one of the primary and second cells, transmitting the HARQ acknowledgement corresponding to the downlink physical channel of the primary cell at a first timing predetermined for the primary cell, and transmitting the HARQ acknowledgement corresponding to the downlink physical channel of the secondary cell at a second timing, wherein controller configures the second timing according to the first timing.
0036Other aspects, advantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention.
<u>BRIEF DESCRIPTION OF THE DRAWINGS</u>
0037The above and other aspects, features, and advantages of certain exemplary embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which: <ul id="ul0002" list-style="none" compact="compact"><li><figref idref="f0001">FIG. 1</figref> is a diagram illustrating a principle of self-scheduling in a Long Term Evolution-Advanced (LTE-A) system supporting carrier aggregation according to the related art;</li><li><figref idref="f0002">FIG. 2</figref> is a diagram illustrating a principle of cross carrier scheduling in an LTE-A system supporting carrier aggregation according to the related art;</li><li><figref idref="f0003">FIG. 3</figref> is a diagram illustrating a timing relationship between a Physical Downlink Shared Channel (PDSCH) and uplink Hybrid Automatic Repeat Request (HARQ) ACKnowledgement (ACK)/ Negative ACK (NACK) in a legacy Long Term Evolution (LTE) system operating with Time Division Duplex (TDD) uplink-downlink configuration #6 according to the related art;</li><li><figref idref="f0004">FIG. 4</figref> is a diagram illustrating a timing relationship among physical channels for use in a case where TDD uplink-downlink configurations of aggregated carriers are identical with each other according to an exemplary embodiment of the present invention;</li><li><figref idref="f0005">FIG. 5</figref> is a diagram illustrating a timing relationship among physical channels for use in a case where TDD uplink-downlink configurations of aggregated carriers differ from each other according to an exemplary embodiment of the present invention;</li><li><figref idref="f0006">FIG. 6</figref> is a diagram illustrating a timing relationship between a PDSCH and an uplink HARQ ACK/NACK according to a first exemplary embodiment of the present invention;</li><li><figref idref="f0007">FIG. 7</figref> is a diagram illustrating a timing relationship between a PDSCH and an uplink HARQ ACK/NACK according to a second exemplary embodiment of the present invention;</li><li><figref idref="f0008">FIG. 8</figref> is a diagram illustrating a timing relationship between a PDSCH and an uplink HARQ ACK/NACK according to a third exemplary embodiment of the present invention;</li><li><figref idref="f0009">FIG. 9</figref> is a flowchart illustrating an evolved Node B (eNB) procedure in a method according to any of the first to third exemplary embodiments of the present invention;</li><li><figref idref="f0010">FIG. 10</figref> is a flowchart illustrating a User Equipment (UE) procedure in a method according to any of the first to third exemplary embodiments of the present invention;</li><li><figref idref="f0011">FIG. 11</figref> is a diagram illustrating a timing relationship between a PDSCH and an uplink HARQ ACK/NACK according to a fourth exemplary embodiment of the present invention;</li><li><figref idref="f0012">FIG. 12</figref> is a block diagram illustrating a configuration of an eNB according to any of the first to fourth exemplary embodiments of the present invention; and</li><li><figref idref="f0013">FIG. 13</figref> is a block diagram illustrating a configuration of a UE according to any of the first to fourth exemplary embodiments of the present invention.</li></ul>
0038Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures.
<u>DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS</u>
0039The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope of the invention. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.
0040The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the invention. Accordingly, it should be apparent to those skilled in the art that the following description of exemplary embodiments of the present invention is provided for illustration purpose only and not for the purpose of limiting the invention as defined by the appended claims and their equivalents.
0041It is to be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.
0042In the following description, a Base Station (BS) is an entity for allocating resources to a terminal and can be any of an enhanced Node B (eNB), a Node B, a BS, a radio access unit, a base station controller, and a node on a network.
0043The terminal can be a User Equipment (UE), a Mobile Station (MS), a cellular phone, a smartphone, a computer, or a multimedia system equipped with communication function. Although the present description is directed to the Advanced Evolved-Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRA) (or Long Term Evolution-Advanced (LTE-A)) supporting carrier aggregation, the present invention can be applied to other communication systems having similar technical background and channel format, with a slight modification, without departing from the scope of the present invention. For example, the timing relationship defined according to an aspect of an exemplary embodiment of the present invention can be applied to a multicarrier High Speed Packet Access (HSPA) system supporting carrier aggregation.
0044In the LTE-A system supporting carrier aggregation, if the component carrier carrying Downlink Control Information (DCI) for data transmission and the component carrier carrying the data scheduled as indicated by the DCI differ from each other, this is referred to as cross carrier scheduling. Meanwhile, if the component carrier carrying the DCI for data transmission and the component carrier carrying the data scheduled as indicated by the DCI are identical with each other, this is referred to as self-scheduling.
0045In the LTE-A system supporting carrier aggregation, if the probability of inter-carrier interference between the aggregated component carriers is low since the frequency bands of the carriers are not adjacent, it is possible to set the component carriers with different Time Division Duplex (TDD) uplink-downlink configurations. For example, the first component carrier can be configured to operate with the uplink and downlink subframes equal in number while the second component carrier is configured to operate with the downlink subframes larger than uplink subframes in number to increase downlink transmission capacity. For another example, the first component carrier can be configured to operate with the TDD uplink-downlink configuration supporting compatibility with Time Division-Synchronous Code Division Multiple Access (TD-SCDMA) as a legacy 3<sup>rd</sup> Generation (3G) TDD system to avoid interference between TD-SCDMA and Long Term Evolution (LTE) TDD systems while the second component carrier is configured with a TDD uplink-downlink configuration determined according to the traffic load without extra restriction.
0046A description is made of the carrier aggregation system including a Primary Cell (PCell) and a Secondary Cell (SCell). The PCell (or first type cell) provides the UE with basic radio resources on a primary frequency (or Primary Component Carrier; PCC) and is the cell to which the UE attempts initial connection or handover. The SCell (or second type cell) provides the UE with additional resources on the secondary frequency (or Secondary Component Carrier; SCC). It is assumed that a Hybrid Automatic Repeat Request (HARQ) ACKnowledgement (ACK)/ Negative ACK (NACK) which the UE feeds back to the eNB is configured into a Physical Uplink Control Channel (PUCCH) and then transmitted through the PCell.
0047The subject matter of the present disclosure is to define the timing relationship among a Physical Downlink Control Channel (PDCCH), a Physical Downlink Shared Channel (PDSCH), and an uplink HARQ ACK/NACK and provide a method for allocating uplink HARQ ACK/NACK transmission resources in the TDD wireless communication system securing broadband resources through carrier aggregation, especially when the self-scheduling or cross carrier scheduling is selectively applied due to the difference between the TDD uplink-downlink configurations of the aggregated carriers.
0048<figref idref="f0004">FIG. 4</figref> is a diagram illustrating a timing relationship among physical channels for use in a case where TDD uplink-downlink configurations of aggregated carriers are identical with each other according to an exemplary embodiment of the present invention. <figref idref="f0004">FIG. 4</figref> is directed to an exemplary case where both the PCell and SCell use the TDD uplink-downlink configuration #1.
0049Referring to <figref idref="f0004">FIG. 4</figref>, the eNB transmits PDSCH 407 to be transmitted through the PCell 401 and PDCCH 405 for scheduling PDSCH 407 at the subframe #0. The eNB also transmits PDSCH 413 to be transmitted through the SCell 403 and PDCCH 411 for scheduling the PDSCH 413 at the subframe #0. At this time, the transmission timing of the HARQ ACK/NACK corresponding to the PDSCHs 407 and 413 becomes the subframe #7 according to the timing relationship defined in the TDD uplink-downlink configuration #1. The UE transmits the HARQ ACK/NACKs corresponding to the respective PDSCHs 407 and 413 at the subframe #7 409 through the PCell 401.
0050<figref idref="f0005">FIG. 5</figref> is a diagram illustrating a timing relationship among physical channels for use in a case where TDD uplink-downlink configurations of aggregated carriers differ from each other according to an exemplary embodiment of the present invention. <figref idref="f0005">FIG. 5</figref> is directed to an exemplary case where the PCell 501 is configured with the TDD uplink-downlink configuration #3 (TDD UL/DL configuration #3) while the SCell 503 is configured with the TDD uplink-downlink configuration #1 (TDD UL/DL configuration #1).
0051Referring to <figref idref="f0005">FIG. 5</figref>, the eNB transmits PDSCH 507 to be transmitted through PCell 501 and PDCCH 505 for scheduling the PDSCH 507 at the subframe #0. The transmission timing of the HARQ ACK/NACK corresponding to the PDSCH 507 becomes the subframe #4 509 according to the timing relationship defined in the TDD uplink-downlink configuration #3. Accordingly, the UE transmits the HARQ ACK/NACK corresponding to the PDSCH 507 at the subframe #4 509 through the Pcell 501.
0052The eNB also transmits the PDSCH 513 to be transmitted through the SCell 503 and the PDCCH 511 for scheduling the PDSCH 513 at the subframe #0. At this time, the transmission timing of the HARQ ACK/NACK corresponding to the PDSCH 513 becomes the subframe #7 515 according to the timing relationship defined in the TDD uplink-downlink configuration #1. However, since the subframe #7 517 carrying the HARQ ACK/NACK is a DownLink (DL) subframe in view of the PCell, it is not possible to transmit an uplink signal.
0053In order to address this problem, an exemplary embodiment of the present invention proposes the following rules. The rules can be commonly applied to both the cross carrier scheduling and self-scheduling. <ul id="ul0003" list-style="bullet" compact="compact"><li>Rule 1: The HARQ ACK/NACK transmission timing of the UE in a PCell is fixed regardless of whether the carrier aggregation is applied or not.</li><li>Rule 2: The transmission timings of the HARQ ACK/NACK corresponding to the PDSCH to be transmitted through the PCell and the PDSCH to be transmitted through the SCell are identical with each other.</li><li>Rule 3: The transmission timing n' of the HARQ ACK/NACK corresponding to the PDSCH transmitted at an n<sup>th</sup> subframe is equal to or greater than the transmission timing m' of the HARQ ACK/NACK corresponding to the PDSCH transmitted at an m<sup>th</sup> subframe (m<n, m'≤n'). The UE transmits the HARQ ACK/NACK at the UpLink (UL) subframe of a PCell among the subframes satisfying the relationship n'=n+k and m'=m+k (k≥4) after the receipt of the PDSCH. Here, k is set to a value equal to or greater than 4 in consideration of the PDSCH reception processing time and HARQ ACK/NACK transmission processing time.</li><li>Rule 4: The transmission timings of the HARQ ACK/NACK corresponding to the PDSCH transmitted at each DL subframe are distributed in the UL subframe as equally as possible.</li></ul>
0054Hereinafter, a description is made of a method for defining a timing relationship among the PDCCH, PDSCH, and uplink HARQ ACK/NACK that are related to the downlink data transmission. The present invention can be applied without any restriction on the number of component carriers to be aggregated for securing a broadband resource.
0055The first to third exemplary embodiments are directed to the case where the number of UL subframes according to the TDD uplink-downlink configuration of the PCell is greater than the number of UL subframes according to the TDD uplink-downlink configuration of the SCell. Also, it is assumed that, if the SCell is at an UL subframe, the PCell is also at an UL subframe at the same timing. That is, in view of an UL subframe, the position of the UL subframe in the PCell is always super set as compared to the UL subframe in the SCell
0056The fourth exemplary embodiment is directed to the case where any of the above restrictions is not applied in the TDD uplink-downlink configurations of the PCell and SCell.
<First exemplary embodiment>
0057The first exemplary embodiment is directed to the case where the TDD uplink-downlink configurations of the aggregated carriers differ from each other in the TDD wireless communication system securing broadband resources through carrier aggregation. The timing relationship among the PDCCH, PDSCH, and PUCCH for transmitting uplink HARQ ACK/NACK that are related to downlink data transmission is described in association with rules 1 to 3.
0058<figref idref="f0006">FIG. 6</figref> is a diagram illustrating a timing relationship between a PDSCH and an uplink HARQ ACK/NACK according to a first exemplary embodiment of the present invention. <figref idref="f0006">FIG. 6</figref> is directed to an exemplary case where the PCell is configured with the TDD uplink-downlink configuration #3 601 and the SCell is configuration with the TDD uplink-downlink configuration #4 602 in the TDD system operating on the component carriers aggregated. Here, 'D' denotes a DL subframe, 'U' denotes an UL subframe, and 'S' denotes a special subframe.
0059Referring to <figref idref="f0006">FIG. 6</figref>, the timing relationship among PDCCH, PDSCH, and PUSCH for PCell that is defined in the legacy LTE system and the timing relationship among PDCCH, PDSCH, and PUSCH for SCell that is defined in the legacy LTE system are expressed using solid line arrows. The timing relationships for the PCell and SCell that are expressed with the solid line arrows follow the timing relationships defined in the TDD uplink-downlink configurations #3 and #4, respectively.
0060In a case where the timing relationship is defined so as to transmit x (x>0) HARQ ACK/NACK is transmitted at a UL subframe, the UE transmits up to x HARQ ACK/NACK in the PUCCH at the UL subframe. If the UE does not schedule the PDSCH for the UE at some DL subframes corresponding to the UL subframe, or if the UE fails to receive the PDSCH transmitted by the eNB, the PUSCH carries y (y<x) HARQ ACK/NACK.
0061The start point of each solid line arrow denotes the DL subframe carrying the PDCCH and PDSCH. The end point of each solid line arrow denotes the UL subframe carrying the PUSCH. For example, the HARQ ACK/NACKs corresponding to the respective PDSCHs transmitted at subframe #7 613 and subframe #8 614 of i<sup>th</sup> subframe 604 of the PCell are formatted into the PUCCH transmitted at the subframe #3 619 of (i+1)<sup>th</sup> radio frame 605 of the PCell.
0062The transmission timing of the PUSCH carrying the HARQ ACK/NACKs corresponding to the PDSCHs transmitted at the subframes #6 627, subframe #7 628, subframe #8 629, and subframe #9 630 follows the timing relationship defined in the TDD uplink-downlink configuration #4 so as to be transmitted at the subframe #3 634 of the (i+1)<sup>th</sup> radio frame 605. However, since the PUSCH can be transmitted through the PCell, the HARQ ACK/NACKs corresponding to the PDSCHs transmitted at the subframes #6 627, subframe #7 628, subframe #8 629, and subframe #9 630 of the i<sup>th</sup> radio frame 604 are transmitted at the subframe #3 619 of the PCell.
0063However, if following the timing relationships of the LTE system that are defined for the respective PCell and SCell, although the PDSCH is transmitted through the PCell and SCell at the same timing, the transmission timing of the HARQ ACK/NACK corresponding to the PDSCH of the PCell and the transmission timing of the HARQ ACK/NACK corresponding to PDSCH of the SCell differ from each other so as to increase system operation complexity and degrade the efficiency. For example, the HARQ ACK/NACK corresponding to the PDSCH transmitted at the subframe #6 612 of the i<sup>th</sup> radio frame of the PCell is transmitted at the subframe #2 of (i+1)<sup>th</sup> radio frame of the PCell. However, the HARQ ACK/NACK corresponding to the PDSCH transmitted at the subframe #6 of the i<sup>th</sup> radio frame which is identical with the PDSCH of the PCell in transmission timing is transmitted at the subframe #3 619 of the PCell which corresponds to the subframe #3 634 of the (i+1)<sup>th</sup> radio frame.
0064In order to address this problem, the HARQ ACK/NACK transmission timing of the UE operating on the aggregated carriers is determined according to the above described rules 1 and 2, which are repeated below. <ul id="ul0004" list-style="bullet" compact="compact"><li>Rule 1: The HARQ ACK/NACK transmission timing of the UE in the PCell is fixed regardless of whether the carrier aggregation is applied or not.</li><li>Rule 2: The transmission timings of the HARQ ACK/NACK corresponding to the PDSCH to be transmitted through the PCell and the PDSCH to be transmitted through the SCell are identical with each other.</li></ul>
0065Rule 1 is for the PCell to follow the HARQ ACK/NACK transmission timing as indicated in the TDD uplink-downlink configurations specified in LTE. Rule 2 is to follow the HARQ ACK/NACK transmission timing of the PCell aggregated with the SCell as the HARQ ACK/NACK transmission timing corresponding to the PDSCH transmitted through the SCell regardless of the TDD uplink-downlink configuration of the SCell.
0066There may be no PCell's HARQ ACK/NACK transmission timing to reference for applying rule 2 to a certain DL subframe of the SCell. In the exemplary case of <figref idref="f0006">FIG. 6</figref> the subframe #4 625 of the SCell is the DL subframe, the subframe #4 of the PCell at the same timing is the UL subframe. Accordingly, the transmission timing of the HARQ ACK/NACK corresponding to the PDSCH transmitted at the subframe #4 of the second cell cannot be determined by referencing the subframe #4 of the PCell. Therefore, the transmission timing of the HARQ ACK/NACK corresponding to the DL subframe of the SCell is newly defined by applying rule 3, which is repeated below. <ul id="ul0005" list-style="bullet" compact="compact"><li>Rule 3: The transmission timing n' of the HARQ ACK/NACK corresponding to the PDSCH transmitted at an n<sup>th</sup> subframe is equal to or greater than the transmission timing m' of the HARQ ACK/NACK corresponding to the PDSCH transmitted at an m<sup>th</sup> subframe (m<n, m'≤n'). The UE transmits the HARQ ACK/NACK at the UL subframe of a PCell among the subframes satisfying the relationship n'=n+k and m'=m+k (k≥4) after the receipt of the PDSCH. Here, k is set to a value equal to or greater than 4 in consideration of the PDSCH reception processing time and HARQ ACK/NACK transmission processing time.</li></ul>
0067With rule 3, the transmission timing of the HARQ ACK/NACK corresponding to the PDSCH transmitted at subframe #4 625 of i<sup>th</sup> subframe through the SCell is determined by referencing the transmission timing of the HARQ ACK/NACK corresponding to the subframe #1 607 and subframe #5 611 of the PCell that are DL subframes closest to the subframe #4 back and forth. The transmission timing of the HARQ ACK/NACK corresponding to the subframe #1 607 of the PCell becomes the subframe #2 618 of (i+1)<sup>th</sup> subframe, and the transmission timing of the HARQ ACK/NACK corresponding to the subframe #5 611 becomes the subframe #2 618 of (i+1)<sup>th</sup> subframe too. The transmission timing of the HARQ ACK/NACK corresponding to the PDSCH transmitted at the subframe #4 625 of i<sup>th</sup> radio frame that satisfies rule 3 in the SCell becomes the subframe #2 618 of the (i+1)<sup>th</sup> radio frame. In a case where the PDSCH to be transmitted at the subframe #4 625 of the SCell is cross-carrier scheduled in the PCell, the PDCCH is transmitted at the subframe #1 607 as the DL subframe of the PCell which is closest to the subframe #4 625. The PDCCH carried in the subframe #1 607 of the PCell includes an indicator for indicating whether the scheduling is of the PDSCH carried at the subframe #1 622 of the second cell or the PDSCH carried in the subframe #4 of the SCell.
0068Rule 3 can be modified as follows.
0069The subframe of the PCell is configured as a UL subframe at the timing when the PDSCH of the SCell is transmitted, the HARQ ACK/NACK corresponding to the PDSCH of the SCell is transmitted through the PCell according to the HARQ ACK/NACK timing defined in the TDD uplink-downlink configuration of the SCell. In this case, the subframe of the PCell at the transmission timing of the HARQ ACK/NACK is an uplink subframe.
0070If rules 1, 2, and 3 are applied synthetically, the transmission timing of the HARQ ACK/NACK corresponding to the PDSCH of the SCell can be configured as expressed by the dotted line arrows in <figref idref="f0006">FIG. 6</figref> as proposed in the present exemplary embodiment.
0071While <figref idref="f0006">FIG. 6</figref> is directed to the case where the cross-carrier scheduling is applied, the present invention is not limited thereto. By applying rules 1, 2, and 3 synthetically, it is possible to determine the transmission timing of the HARQ ACK/NACK in the self-scheduling mode as in the cross carrier scheduling. In the exemplary case of <figref idref="f0006">FIG. 6</figref>, the dotted link arrow starting at a D or S subframe of the PCell and ending at a D or S subframe of the SCell expresses the cross carrier scheduling operation in which the PDCCH transmitted at the D or S subframe of the PCell schedules the PDSCH to be transmitted at the D or S subframe of the SCell. Also, the dotted line arrows starting at the D or S subframe of the SCell and ending at an U subframe of the PCell expresses an operation in which the HARQ ACK/NACK corresponding to the PDSCH transmitted at the D or S subframe of the SCell is transmitted at the U subframe of the PCell.
0072For example, if the PDCCH is transmitted at the subframe #1 of the i<sup>th</sup> radio frame of the PCell to cross-carrier schedule the SCell, the PDSCH is transmitted at the subframe #1 622 of the i<sup>th</sup> radio frame of the SCell, and the HARQ ACK/NACK corresponding to the PDSCH of the SCell is transmitted at the subframe #2 618 of the (i+1)<sup>th</sup> radio frame of the PCell according to the transmission timing of the HARQ ACK/NACK corresponding to the subframe #1 607 of the PCell according to rule 2.
0073If the PDCCH transmitted at the subframe #1 607 of the i<sup>th</sup> radio frame of the PCell is cross-carrier scheduling the PDSCH to be transmitted at the subframe #4 625 of the i<sup>th</sup> radio frame of the SCell, the HARQ ACK/NACK corresponding to the PDSCH of the SCell is transmitted at the subframe #2 618 of the (i+1)<sup>th</sup> radio frame of the PCell. In this case, although the subframe #4 625 of the SCell is a DL subframe, the subframe #4 610 of the PCell at the same timing is a UL subframe. Accordingly, the PDCCH for cross-carrier scheduling the PDSCH to be transmitted at the subframe #4 625 of the SCell is transmitted at the subframe #1 607 as a DL subframe of the PCell closest to the subframe #4 625. The transmission timing of the HARQ ACK/NACK corresponding to the PDSCH to be transmitted through the PCell follows the HARQ ACK/NACK transmission timing defined in the TDD uplink-downlink configuration #3 predefined according to rule 1.
0074The HARQ ACK/NACK transmission timing according to the first exemplary embodiment can be summarized as shown in Table 4. If the PDSCH transmitted by the eNB at (n-j)<sup>th</sup> subframe is received, the UE transmits an uplink HARQ ACK/NACK corresponding to the PDSCH at the n<sup>th</sup> subframe. Here, j is an element of a set J which is defined as shown in Table 4. Table 4 is directed to the case where the PCell is configured with the TDD uplink-downlink configuration #3, the SCell is configured with the TDD uplink-downlink configuration #4, and the HARQ ACK/NACKs corresponding to the PDSCHs transmitted through the PCell and SCell are transmitted through the PCell. <tables id="tabl0004" num="0004"><table frame="all"><title>Table 4</title><tgroup cols="11"><colspec colnum="1" colname="col1" colwidth="37mm" /><colspec colnum="2" colname="col2" colwidth="8mm" /><colspec colnum="3" colname="col3" colwidth="8mm" /><colspec colnum="4" colname="col4" colwidth="18mm" /><colspec colnum="5" colname="col5" colwidth="10mm" /><colspec colnum="6" colname="col6" colwidth="10mm" /><colspec colnum="7" colname="col7" colwidth="8mm" /><colspec colnum="8" colname="col8" colwidth="8mm" /><colspec colnum="9" colname="col9" colwidth="8mm" /><colspec colnum="10" colname="col10" colwidth="8mm" /><colspec colnum="11" colname="col11" colwidth="8mm" /><thead><row><entry valign="top"><b>UL-DL Configuration</b></entry><entry namest="col2" nameend="col11" align="left" valign="top"><b>Subframe <i>n</i></b></entry></row><row><entry valign="top" /><entry valign="top">0</entry><entry valign="top">1</entry><entry valign="top">2</entry><entry valign="top">3</entry><entry valign="top">4</entry><entry valign="top">5</entry><entry valign="top">6</entry><entry valign="top">7</entry><entry valign="top">8</entry><entry valign="top">9</entry></row></thead><tbody><row><entry>3</entry><entry>-</entry><entry>-</entry><entry>7, 6, 11</entry><entry>6, 5</entry><entry>5, 4</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry></row><row><entry>4</entry><entry>-</entry><entry>-</entry><entry>7, 6, 8, 11</entry><entry>6, 5</entry><entry>5, 4</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry></row></tbody></tgroup></table></tables>
<Second exemplary embodiment>
0075The second exemplary embodiment is directed to the case where the timing relationship among PDCCH, PDSCH, and PUCCH carrying the uplink HARQ ACK/NACK that are related to the downlink data transmission with rules 1 to 4 in the TDD wireless communication system securing broadband resource through carrier aggregation, especially when the TDD uplink-downlink configurations of the carriers differ from each other.
0076<figref idref="f0007">FIG. 7</figref> is directed to the TDD system operating with two aggregated component carriers in which the PCell 701 is configured with the TDD uplink-downlink configuration #6 and the SCell 702 is configured with the TDD uplink-downlink configuration #2. The PCell's timing relationship among the PDCCH, PDSCH, and PUCCH that is defined in the legacy LTE system and the SCell's timing relationship among the PDCCH, PDSCH, and PUCCH that is defined in the legacy LTE system are expressed using solid link arrows. The start point of each solid line arrow denotes the DL subframe carrying the PDCCH and PDSCH, and the end point of each solid link arrow denotes the UL subframe carrying the PUCCH.
0077<figref idref="f0007">FIG. 7</figref> is a diagram illustrating a timing relationship between PDSCH and an uplink HARQ ACK/NACK according to a second exemplary embodiment of the present invention.
0078Referring to <figref idref="f0007">FIG. 7</figref>, the transmission timing of the HARQ ACK/NACK corresponding to the PDSCH of the SCell is expressed with a dotted link arrow. Although the description is directed to the case of using the cross carrier scheduling, the present invention is not limited thereto. That is, a system operating with the self-scheduling can also determine the HARQ ACK/NACK transmission timing in the same manner as the cross carrier scheduling.
0079Here, the dotted link arrows starting at a D or S subframe of the PCell and ending at a D or S subframe of the SCell expresses the cross carrier scheduling operation in which the PDCCH transmitted at the D or S subframe of the PCell schedules the PDSCH to be transmitted at the D or S subframe of the SCell. Also, the dotted line arrows starting at the D or S subframe of the SCell and ending at a U subframe of the PCell expresses an operation in which the HARQ ACK/NACK corresponding to the PDSCH transmitted at the D or S subframe of the SCell is transmitted at the U subframe of the PCell.
0080In <figref idref="f0007">FIG. 7</figref>, the PCell follows the HARQ ACK/NACK transmission timing defined in the TDD uplink-downlink configuration #6 according to rule 1 regardless of the use of carrier aggregation. The transmission timing of the HARQ ACK/NACK corresponding to the PDSCH transmitted through the SCell follows the HARQ ACK/NACK transmission timing of the PCell aggregated with the SCell regardless of the TDD uplink-downlink configuration of the SCell according to rule 2.
0081If the PDCCH is transmitted at the subframe #1 of i<sup>th</sup> radio frame of the PCell to cross-carrier schedule the SCell, the PDSCH of the SCell is transmitted at the subframe #1 722 of the i<sup>th</sup> radio frame. The HARQ ACK/NACK corresponding to the PDSCH of the SCell is transmitted at the subframe #8 714 of the i<sup>th</sup> radio frame of the PCell according to the transmission timing of the HARQ ACK/NACK corresponding to the subframe #1 707 of the PCell according to rule 2.
0082The PDCCH transmitted at the subframe #1 of the i<sup>th</sup> radio frame of PCell is cross-carrier scheduling the PDSCH to be transmitted at the subframe #3 724 of the i<sup>th</sup> radio frame, the HARQ ACK/NACK corresponding to the PDSCH of the SCell may be transmitted earlier than the subframe #8 714 as the transmission timing of the HARQ ACK/NACK corresponding to the PDSCH to be transmitted at the subframe #1 722 of the second cell as DL subframe right before according to rule 3. Accordingly, the HARQ ACK/NACK corresponding to the PDSCH transmitted at the subframe #3 724 of the i<sup>th</sup> radio frame of the SCell is transmitted at the subframe #8 714 of the i<sup>th</sup> subframe of the PCell.
0083The PDCCH transmitted at the subframe #1 707 of the i<sup>th</sup> radio frame of the Pcell. The PDCCH transmitted at the subframe #1 707 of the i<sup>th</sup> radio frame of the PCell carries the cross carrier scheduling information for the PDSCH to be transmitted at the subframe #4 of the i<sup>th</sup> radio frame. The HARQ ACK/NACK corresponding to the PDSCH of the SCell is transmitted at the subframe #8 of the (i+1)<sup>th</sup> radio frame of the PCell since it cannot precede the subframe #8 714 as the transmission timing of the HARQ ACK/NACK corresponding to the PDSCH transmitted at the subframe #3 724 of the second cell as the DL subframe right before according to rule 3.
0084The PDCCH is transmitted at the subframe #5 711 of the i<sup>th</sup> radio frame of the PCell to cross-carrier schedule the SCell, the PDSCH is transmitted at the subframe #5 of the i<sup>th</sup> radio frame of the second cell. The HARQ ACK/NACK corresponding to the PDSCH of the SCell is transmitted at the subframe #2 718 of the (i+1)<sup>th</sup> radio frame of the PCell according to the transmission timing of the HARQ ACK/NACK corresponding to the subframe #5 711 of the PCell as specified in rule 2.
0085If the PDCCH is transmitted at the subframe #6 of the i<sup>th</sup> radio frame of the PCell to cross-carrier schedule the SCell, the PDSCH is transmitted at the subframe #6 727 of the i<sup>th</sup> radio frame through the SCell. The HARQ ACK/NACK corresponding to the PDSCH of the SCell is transmitted at the subframe #3 719 of the (i+1)<sup>th</sup> radio frame of the PCell according to the transmission timing of the HARQ ACK/NACK corresponding to the subframe #5 711 of the PCell as specified in rule 2.
0086The PDCCH transmitted at the subframe #6 of the i<sup>th</sup> radio frame of the PCell carries the cross scheduling information for the PDSCH to be transmitted at the subframe #8 of the i<sup>th</sup> radio frame of the SCell. The HARQ ACK/NACK corresponding to the PDSCH of the SCell is transmitted at the subframe #3 of the (i+1)<sup>th</sup> radio frame of the PCell since it cannot precede the subframe #3 719 as the transmission timing of the HARQ ACK/NACK corresponding to the PDSCH transmitted at the subframe #6 727 of the SCell as the DL subframe right before as specified in rule 3.
0087Once the HARQ ACK/NACK transmission timing is defined as above, the numbers of HARQ ACK/NACKs corresponding to the PDSCHs of the SCell that are transmitted at UL subframes of the PCell has the relationship of (UL subframe #2: UL subframe #3: UL subframe #4: UL subframe #7: UL subframe #8) = (1: 2: 1:1: 3) such that the number of HARQ ACK/NACKs transmitted at the UL subframe #8 is relatively large, resulting in an inequality. This causes degradation of the resource utilization efficiency for the HARQ ACK/NACK transmission.
0088In order to address this problem, the HARQ ACK/NACK timing is determined such that the HARQ ACK/NACK transmission timings are distributed at the UL subframes of a radio frame as equally as possible with rule 4 in addition to rules 1 to 3. <ul id="ul0006" list-style="bullet" compact="compact"><li>Rule 4: The transmission timings of the HARQ ACK/NACKs corresponding to the PDSCHs transmitted at the DL subframes are distributed at the UL subframes as equally as possible.</li></ul>
0089By adding rule 4 to the scheduling method, it is possible to avoid an excessive increase of the number of HARQ ACK/NACKs transmitted at a certain subframe. That is, the HARQ ACK/NACK corresponding to the PDSCH transmitted at the subframe #4 725 of the i<sup>th</sup> radio frame of the SCell can be transmitted at the subframe #2 718 of the (i+1)<sup>th</sup> radio frame of the PCell.
0090By defining the HARQ transmission timing as described above, the distribution of the HARQ ACK/NACKs corresponding to the PDSCHs transmitted at UL subframes of the PCell and the SCell shows the relationship of (UL subframe #2: UL subframe #3: UL subframe #4: UL subframe #7: UL subframe #8) = (2: 2: 1: 1: 2) distributed as equally as possible. As shown in <figref idref="f0007">FIG. 7</figref>, the numbers of the dotted link arrows arriving at the UL subframes of the PCell are equal to each other. Also, the distribution of the number of the HARQ ACK/NACKs corresponding to the PDSCHs transmitted in view of UL subframes of the PCell has the relationship of (UL subframe #2: UL subframe #3: UL subframe #4: UL subframe #7: UL subframe #8) = (1: 1: 1: 1: 1).
0091Accordingly, the total distribution of the numbers of HARQ ACK/NACKs corresponding to the PDSCHs transmitted at the PCell and SCell in view of each UL subframe of the PCell has the relationship of (UL subframe #2: UL subframe #3: UL subframe #4: UL subframe #7: UL subframe #8) = (3: 3: 2: 2: 3) distributed as equally as possible.
0092The HARQ ACK/NACK transmission timings according to the second exemplary embodiment can be summarized as shown in Table 5. If the PDSCH transmitted by the eNB at the (n-j)<sup>th</sup> subframe, the UE transmits the uplink HARQ ACK/NACK corresponding to the PDSCH at n<sup>th</sup> subframe. Here, j is an element of a set J which is defined as shown in Table 5. Table 5 is directed to the case where the PCell is configured with the TDD uplink-downlink configuration #6, the SCell is configured with the TDD uplink-downlink configuration #2, and the HARQ ACK/NACKs corresponding to the PDSCHs transmitted through the PCell and SCell are transmitted through the PCell. <tables id="tabl0005" num="0005"><table frame="all"><title>Table 5</title><tgroup cols="11"><colspec colnum="1" colname="col1" colwidth="37mm" /><colspec colnum="2" colname="col2" colwidth="8mm" /><colspec colnum="3" colname="col3" colwidth="8mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="10mm" /><colspec colnum="6" colname="col6" colwidth="8mm" /><colspec colnum="7" colname="col7" colwidth="8mm" /><colspec colnum="8" colname="col8" colwidth="8mm" /><colspec colnum="9" colname="col9" colwidth="8mm" /><colspec colnum="10" colname="col10" colwidth="10mm" /><colspec colnum="11" colname="col11" colwidth="8mm" /><thead><row><entry valign="top"><b>UL-DL Configurati on</b></entry><entry namest="col2" nameend="col11" align="left" valign="top"><b>Subframe <i>n</i></b></entry></row><row><entry valign="top" /><entry valign="top">0</entry><entry valign="top">1</entry><entry valign="top">2</entry><entry valign="top">3</entry><entry valign="top">4</entry><entry valign="top">5</entry><entry valign="top">6</entry><entry valign="top">7</entry><entry valign="top">8</entry><entry valign="top">9</entry></row></thead><tbody><row><entry>2</entry><entry>-</entry><entry>-</entry><entry>7, 8</entry><entry>5, 7</entry><entry>5</entry><entry>-</entry><entry>-</entry><entry>7</entry><entry>5, 7</entry><entry>-</entry></row><row><entry>6</entry><entry>-</entry><entry>-</entry><entry>7</entry><entry>7</entry><entry>5</entry><entry>-</entry><entry>-</entry><entry>7</entry><entry>7</entry><entry>-</entry></row></tbody></tgroup></table></tables>
<Third exemplary embodiment>
0093<figref idref="f0008">FIG. 8</figref> is a diagram illustrating the timing relationship between the PDSCH and the uplink HARQ ACK/NACK according to the third exemplary embodiment of the present invention. <figref idref="f0008">FIG. 8</figref> shows another exemplary embodiment to help understand the second exemplary embodiment more clearly, and is directed to the TDD system operating with two aggregated component carriers in which the PCell 801 is configured with the TDD uplink-downlink configuration #0 and the SCell 802 is configured with the TDD uplink-downlink configuration #2. By introducing rule 4 in addition to rules 1 to 3, the HARQ ACK/NACK transmission timings are distributed across the UL subframes within a radio frame as equally as possible.
0094In this case, the HARQ ACK/NACK transmission timing can be summarized as shown in Table 6. If the PDSCH transmitted by the eNB at the (n-j)<sup>th</sup> subframe, the UE transmits the uplink HARQ ACK/NACK corresponding to the PDSCH at n<sup>th</sup> subframe. Here, j is an element of a set J which is defined as shown in Table 6.
0095Table 6 is directed to the case where the PCell is configured with the TDD uplink-downlink configuration #0, the SCell is configured with the TDD uplink-downlink configuration #2, and the HARQ ACK/NACKs corresponding to the PDSCHs transmitted through the PCell and SCell are transmitted through the PCell. <tables id="tabl0006" num="0006"><table frame="all"><title>Table 6</title><tgroup cols="11"><colspec colnum="1" colname="col1" colwidth="37mm" /><colspec colnum="2" colname="col2" colwidth="8mm" /><colspec colnum="3" colname="col3" colwidth="8mm" /><colspec colnum="4" colname="col4" colwidth="8mm" /><colspec colnum="5" colname="col5" colwidth="10mm" /><colspec colnum="6" colname="col6" colwidth="8mm" /><colspec colnum="7" colname="col7" colwidth="8mm" /><colspec colnum="8" colname="col8" colwidth="8mm" /><colspec colnum="9" colname="col9" colwidth="8mm" /><colspec colnum="10" colname="col10" colwidth="10mm" /><colspec colnum="11" colname="col11" colwidth="8mm" /><thead><row><entry valign="top"><b>UL-DL Configuration</b></entry><entry namest="col2" nameend="col11" align="left" valign="top"><b>Subframe <i>n</i></b></entry></row><row><entry valign="top" /><entry valign="top">0</entry><entry valign="top">1</entry><entry valign="top">2</entry><entry valign="top">3</entry><entry valign="top">4</entry><entry valign="top">5</entry><entry valign="top">6</entry><entry valign="top">7</entry><entry valign="top">8</entry><entry valign="top">9</entry></row></thead><tbody><row><entry>0</entry><entry>-</entry><entry>-</entry><entry>6</entry><entry>-</entry><entry>4</entry><entry>-</entry><entry>-</entry><entry>6</entry><entry>-</entry><entry>4</entry></row><row><entry>2</entry><entry>-</entry><entry>-</entry><entry>6</entry><entry>4, 5</entry><entry>4</entry><entry>-</entry><entry>-</entry><entry>6</entry><entry>4, 5</entry><entry>4</entry></row></tbody></tgroup></table></tables>
0096By defining the HARQ ACK/ NACK transmission timing as described above, the distribution of the numbers of the HARQ ACK/NACKs corresponding to the PDSCHs transmitted through the SCell in view of the UL subframe of the PCell has the relationship of (UL subframe #2: UL subframe #3: UL subframe #4: UL subframe #7: UL subframe #8: UL subframe #9) = (1: 2: 1: 1: 2: 1) distributed as equally as possible. As shown in <figref idref="f0008">FIG. 8</figref>, the numbers of the dotted link arrows arriving at the UL subframes of the PCell are equal to each other.
0097The distribution of the number of the HARQ ACK/NACKs corresponding to the PDSCHs transmitted in view of UL subframes of the PCell has the relationship of (UL subframe #2: UL subframe #3: UL subframe #4: UL subframe #7: UL subframe #8: UL subframe #9) = (1: 0: 1: 1: 0: 1).
0098Accordingly, the total distribution of the numbers of HARQ ACK/NACKs corresponding to the PDSCHs transmitted at the PCell and SCell in view of UL subframes of the PCell has the relationship of (UL subframe #2: UL subframe #3: UL subframe #4: UL subframe #7: UL subframe #8: UL 9) = (2: 2: 2: 2: 2: 2) distributed as equally as possible.
0099<figref idref="f0009">FIG. 9</figref> is a flowchart illustrating an eNB procedure in a method according to any of the first to third exemplary embodiments of the present invention.
0100The operation of the eNB according to an exemplary embodiment of the present invention is summarized as follows. The method comprises a step of transmitting a downlink physical channel for at least one of the first cell (PCell) and the second cell (SCell) to the UE, a first reception step of receiving a physical uplink channel corresponding to the downlink physical channel of the first cell, and a second reception step of receiving a physical uplink channel for a downlink physical channel of the second cell according to the reception timing of the physical uplink channel of the first cell. In this case, the second reception step can follow rules 1 to 3 described above.
0101Referring to <figref idref="f0009">FIG. 9</figref>, a description is made of the eNB procedure according to an exemplary embodiment of the present invention in detail.
0102The eNB sets the transmission timing of PDSCH to n<sup>th</sup> subframe at step 901. Next, the eNB determines whether to transmit the PDSCH through a PCell, an SCell, or both the PCell and SCell, at step 903.
0103If it is determined to transmit the PDSCH through the PCell, the eNB transmits to the UE the PDSCH and PDCCH for scheduling the PDSCH at the n<sup>th</sup> subframe of the PCell at step 905. Next, the eNB receives a HARQ ACK/NACK corresponding to the PDSCH at a UL subframe of the PCell according to the HARQ ACK/NACK transmission timing defined for the legacy LTE system in the TDD uplink-downlink configuration in step 907 (rule 1). Next, the eNB determines whether to perform retransmission of old data or initial transmission of new data according to the received HARQ ACK/NACK at step 909. If the ACK is received, the eNB transmits the new data to the UE. Otherwise, if the NACK is received, the eNB retransmits the PDSCH.
0104If it is determined to transmit the PDSCH through the SCell at step 903, the eNB checks a subframe state of the PCell and SCell at the n<sup>th</sup> subframe as the PDSCH transmission timing at step 911.
0105If the PCell is in the state of a DL subframe or special subframe and if the SCell is in the state of the DL subframe or special subframe, the eNB transmits the PDCCH at the n<sup>th</sup> subframe of the PCell or SCell at step 913. The PDSCH is transmitted at the n<sup>th</sup> subframe. At this time, if the system is in self-scheduling mode, the eNB transmits the PDCCH at the n<sup>th</sup> subframe of the SCell. If the system is in cross-carrier scheduling mode, the eNB transmits the PDCCH at the n<sup>th</sup> subframe of the PCell. Next, the eNB performs a process for receiving the HARQ ACK/NACK corresponding to the PDSCH at step 907 (rules 1 and 2).
0106If the PCell is in the state of a UL subframe and if the SCell is in the state of a DL subframe or special subframe, the eNB transmits the PDCCH at the closest DL subframe before the n<sup>th</sup> subframe of the PCell at step 915. Or, the eNB transmits the PDCCH at the n<sup>th</sup> subframe of the SCell. Next, the eNB transmits the PDSCH at the n<sup>th</sup> subframe of the SCell and, if the system is in the cross carrier scheduling mode, the eNB transmits the PDCCH at the closest DL subframe before the n<sup>th</sup> subframe of the PCell. Afterward, the eNB receives the HARQ ACK/NACK at the UL subframe of the PCell according to the HARQ ACK/NACK transmission timing defined in rule 3 as described in the first exemplary embodiment and the HARQ ACK/NACK transmission timing defined in rules 3 and 4 as described in the second exemplary embodiment at step 917. Next, the eNB can determine whether to retransmit the PDSCH according to the received HARQ ACK/NACK at step 909. If the ACK is received, the eNB transmits new data to the UE. Otherwise, if the NACK is received, the eNB retransmits the PDSCH to the UE. Afterward, the procedure returns to step 901.
0107Although not depicted in <figref idref="f0009">FIG. 9</figref>, if the PDSCH is transmitted through both the PCell and SCell at step 903, the eNB's PDSCH transmission procedure in the PCell goes to step 905. Meanwhile, the eNB's PDSCH transmission procedure in the SCell goes to step 911.
0108<figref idref="f0010">FIG. 10</figref> is a flowchart illustrating a UE procedure in a method according to any of the first to third exemplary embodiments of the present invention.
0109The operation the UE according to an exemplary embodiment of the present invention is summarized as follows. The method comprises a step of receiving a downlink physical channel for at least one of the first and second cells from the eNB, a first transmission step of transmitting the uplink physical channel of the first cell at a predetermined timing, and a second transmission step of transmitting the uplink physical channel of the second cell according to the uplink physical channel transmission timing of the first cell. Here, the second transmission step can follow rules 1 to 3 described above.
0110A description is made of the UE procedure according to an exemplary embodiment of the present invention with reference to <figref idref="f0010">FIG. 10</figref>.
0111Referring to <figref idref="f0010">FIG. 10</figref>, the UE receives a PDCCH at the m<sup>th</sup> subframe from the eNB at step 1001. The UE is not aware of the timing and component carrier for PDCCH transmission of the eNB. Accordingly, the UE attempts to decode the PDCCH on all of the aggregated component carriers at every subframe. In more detail, the UE performs a Cyclic Redundancy Check (CRC) test with a unique UE IDentifier (ID) allocated to itself on the received PDCCH and, if the CRC test is passed, it is determined that the PDCCH is addressed to the UE.
0112The UE determines whether the received PDCCH is for scheduling the PDSCH of the PCell, the PDSCH of the SCell, or the PDSCHs of both the PCell and SCell at step 1003. If the received PDCCH is for scheduling the PDSCH of the PCell, the UE receives the PDSCH at the m<sup>th</sup> subframe of the PCell at step 1005. Next, the UE transmits the HARQ ACK/NACK corresponding to the PDSCH at the UL subframe of the PCell according to the HARQ ACK/NACK transmission timing defined for the legacy LTE system in the TDD uplink-downlink configuration at step 1007 (rule 1). Afterward, the procedure returns to step 1001.
0113If the received PDCCH is for scheduling the PDSCH of the SCell at step 1003, the UE checks the subframe state of the PCell and SCell at the n<sup>th</sup> subframe as the eNB's PDSCH transmission timing at step 1011. If the PCell is in the state of the DL subframe or special subframe and if the SCell is in the state of the DL subframe or special subframe, the UE receives the PDSCH at the m<sup>th</sup> subframe of the SCell at step 1013. This is the case of m=n such that the PDCCH and PDSCH are received at the same subframe. Afterward, the UE performs a process for transmitting the HARQ ACK/NACK corresponding to the PDSCH at step 1007 (rules 1 and 2).
0114If the PCell is in the state of a UL subframe and if the SCell is in the state of a DL subframe or special subframe at step 1011, the UE receives the PDSCH at the n<sup>th</sup> subframe of the SCell at step 1015. This is the case of m<n such that the PDSCH is received at a subframe located later than the subframe carrying the PDCCH. Afterward, the UE transmits the HARQ ACK/NACK corresponding to the PDSCH at the UL subframe of the PCell, according to the HARQ ACK/NACK transmission timing defined in rule 3 in a case of the first exemplary embodiment and the HARQ ACK/NACK transmission timing defined in rules 3 and 4 in a case of the second exemplary embodiment, at step 1017. Afterword, the procedure returns to step 1001.
0115Although not depicted in the drawing, if it is determined that the PDCCH received is for scheduling the PDSCHs of both the PCell and SCell at step 1003, the UE's PDSCH reception procedure in the PCell goes to step 1005. Meanwhile, the UE's PDSCH reception procedure in the SCell goes to step 1011.
0116The first to third exemplary embodiments are applied to the case where the number of UL subframes defined in the TDD uplink-downlink configuration of the PCell is greater than the number of UL subframes defined in the TDD uplink-downlink configuration of the SCell. If the SCell is in the state of a UL subframe at the same timing, the PCell should be in the UL subframe. That is, the position of the UL subframe of the PCell is always of a superset as compared to the UL subframe of the SCell in view of the UL subframe. Accordingly, when the UE transmits the HARQ ACK/NACK corresponding to the PDSCH of the SCell at the UL subframe of the PCell, it is possible to minimize delay. The combination of the TDD uplink-downlink configurations available for the PCell and SCell from the reference point of the TDD uplink-downlink configurations defined for the current LTE/LTE-A system can be summarized as shown in Table 7. <tables id="tabl0007" num="0007"><table frame="all"><title>Table 7</title><tgroup cols="3"><colspec colnum="1" colname="col1" colwidth="13mm" /><colspec colnum="2" colname="col2" colwidth="13mm" /><colspec colnum="3" colname="col3" colwidth="22mm" /><thead><row><entry valign="top"><b>Case</b></entry><entry valign="top"><b>Pcell</b></entry><entry valign="top"><b>Scell</b></entry></row></thead><tbody><row><entry>1</entry><entry>0</entry><entry>1, 2, 3, 4, 5, 6</entry></row><row><entry>2</entry><entry>1</entry><entry>2, 4, 5</entry></row><row><entry>3</entry><entry>2</entry><entry>5</entry></row><row><entry>4</entry><entry>3</entry><entry>4, 5</entry></row><row><entry>5</entry><entry>4</entry><entry>5</entry></row><row><entry>6</entry><entry>5</entry><entry>-</entry></row><row><entry>7</entry><entry>6</entry><entry>1, 2, 3, 4, 5</entry></row></tbody></tgroup></table></tables> In Table 7, if the PCell is configured with the TDD uplink-downlink configuration #6, the SCell can be configured with one of the TDD uplink-downlink configuration #1, TDD uplink-downlink configuration #2, TDD uplink-downlink configuration #3, TDD uplink-downlink configuration #4, and TDD uplink-downlink configuration #5. The first to third exemplary embodiments can be modified in various ways.
0117For example, the cross carrier scheduling can be allowed only when both the PCell and SCell are in the state of a DL subframe or special subframe at the same timing. That is, if the PCell is in the state of a UL subframe and the SCell is in the state of a DL subframe at a certain timing, the cross carrier scheduling is not permitted. Accordingly, the HARQ ACK/NACK transmission timing is determined according to rules 1 and 2 only.
0118For a modified example, if there is a plurality of subframes satisfying rule 3 in the first exemplary embodiment, the HARQ ACK/NACK transmission timing is determined as the subframe closest to the subframe carrying the PDSCH in the SCell, in addition to rule 3.
0119For another modified example, it is possible to restrict the combinations of the TDD uplink-downlink configurations that are available in the carrier aggregation mode according to the transmission period of the special subframe, with another condition in addition to the conditions of Table 7. That is, the TDD uplink-downlink configurations #0, #6, #1, and #2 having the special subframe transmission period of 5ms are categorized into group #1, and the TDD uplink-downlink configurations #3, #4, and #5 having the special subframe transmission period of 10ms are categorized into group #2. In each group, the HARQ ACK/NACK transmission timing can be defined under the conditions proposed in the description of Table 7 and rules defined in the first and second exemplary embodiments.
<Fourth exemplary embodiment>
0120Unlike the first to third exemplary embodiments, the fourth exemplary embodiment is directed to the case where the TDD uplink-downlink configurations of the PCell and SCell have no restriction.
0121A description is made of the operation according to the fourth exemplary embodiment adopting rule 5 in addition to rules 1 and 2.
0122<figref idref="f0011">FIG. 11</figref> is a diagram illustrating a timing relationship between a PDSCH and an uplink HARQ ACK/NACK according to a fourth exemplary embodiment of the present invention. <figref idref="f0011">FIG. 11</figref> is directed to the TDD system operating with two aggregated component carriers in which the PCell is configured with the TDD uplink-downlink configuration #1 and the SCell is configured with the TDD uplink-downlink configuration #0. In <figref idref="f0011">FIG. 11</figref>, the timing relationship among PDCCH, PDSCH, and PUCCH in the PCell and the timing relationship among PDCCH, PDSCH, and PUCCH in the SCell that are defined for the legacy LTE system are expressed by solid line arrows. The start point of each solid line arrow denotes the DL subframe carrying PDCCH and PDSCH, and the end point of each solid line arrow denotes the UL subframe carrying PUCCH.
0123Referring to <figref idref="f0011">FIG. 11</figref>, the transmission timing of HARQ ACK/NACK corresponding to the PDSCH of the SCell according to the proposed invention is expressed as dotted arrow. Although <figref idref="f0011">FIG. 11</figref> is directed to the case of adopting the cross carrier scheduling, this method can be applied for determining the HARQ ACK/NACK transmission timing in the case of adopting the self-scheduling too.
0124In the exemplary case of <figref idref="f0011">FIG. 11</figref>, the dotted link arrow starting at a D or S subframe of the PCell and ending at a D or S subframe of the SCell express the cross carrier scheduling operation in which the PDCCH transmitted at the D or S subframe of the PCell schedules the PDSCH to be transmitted at the D or S subframe of the SCell. Also, the dotted line arrow starting at the D or S subframe of the SCell and ending at a U subframe of the PCell expresses an operation in which the HARQ ACK/NACK corresponding to the PDSCH transmitted at the D or S subframe of the SCell is transmitted at U subframe of the PCell.
0125In <figref idref="f0011">FIG. 11</figref>, the PCell follows the HARQ ACK/NACK transmission timing according to the TDD uplink-downlink configuration #1 defined in the legacy LTE regardless of the use of carrier aggregation according to rule 1. The SCell follows the HARQ ACK/NACK transmission timing of the PCell aggregated with the SCell regardless of the TDD uplink-downlink configuration of the SCell according to rule 2.
0126In the exemplary case of <figref idref="f0011">FIG. 11</figref>, if the PDSCH is transmitted at the subframe #1 1107 of i<sup>th</sup> radio frame through the PCell to cross-carrier schedule the SCell, the PDSCH is transmitted at the subframe #1 1122 of the i<sup>th</sup> radio frame through the SCell. The HARQ ACK/NACK corresponding to the PDSCH of the SCell is transmitted at the subframe #7 1113 of the i<sup>th</sup> radio frame of the PCell according to the transmission timing of the HARQ ACK/NACK corresponding to the subframe #1 1107 of the PCell according to rule 2.
0127If the PDCCH is transmitted at the subframe #5 of the i<sup>th</sup> radio frame through the PCell to cross carrier schedule the SCell, the PDSCH is transmitted at the subframe #5 1126 of the i<sup>th</sup> radio frame of the SCell. The HARQ ACK/NACK corresponding to the PDSCH of the SCell is transmitted at the subframe #2 1118 of the (i+1)<sup>th</sup> radio frame through the PCell according to the transmission timing of the HARQ ACK/NACK corresponding to the subframe #5 1111 of the PCell according to rule 2.
0128In the exemplary case of <figref idref="f0011">FIG. 11</figref>, however, the PCell is in the state of a DL subframe and the SCell is in the state of a UL subframe at the subframe #4 1110 and 1125 of the i<sup>th</sup> radio frame at the same timing. Accordingly, the PDSCH as DL data of the SCell cannot be transmitted at the subframe #4 1125 of the SCell. This means that the cross carrier scheduling cannot operate at the corresponding subframe. <ul id="ul0007" list-style="bullet" compact="compact"><li>Rule 5: if the SCell is in the state of a UL subframe and the PCell is in the state of a DL subframe at the same timing, the PDSCH of the SCell cannot be cross-carrier scheduled at the corresponding subframe.</li></ul>
0129In this case, the PDCCH for scheduling PDSCH of the PCell and the PDSCH can be transmitted at the corresponding subframe #4 of the PCell. The HARQ ACK/NACK corresponding to the PDSCH of the PCell is transmitted at the subframe #8 of the PCell according to the conventional timing relationship of the HARQ of the PCell.
0130The HARQ ACK/NACK transmission timing according to the fourth exemplary embodiment can be summarized as shown in Table 8. If the PDSCH transmitted by the eNB at (n-j)<sup>th</sup> subframe is received, the UE transmits uplink HARQ ACK/NACK corresponding to the PDSCH at the n<sup>th</sup> subframe. Here, j is an element of a set J which is defined as shown in Table 8. Table 8 is directed to the case where the PCell is configured with the TDD uplink-downlink configuration #1, the SCell is configured with the TDD uplink-downlink configuration #0, and the HARQ ACK/NACKs corresponding to the PDSCHs transmitted through the PCell and SCell are transmitted through the PCell. <tables id="tabl0008" num="0008"><table frame="all"><title>Table 8</title><tgroup cols="11"><colspec colnum="1" colname="col1" colwidth="37mm" /><colspec colnum="2" colname="col2" colwidth="8mm" /><colspec colnum="3" colname="col3" colwidth="8mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="8mm" /><colspec colnum="6" colname="col6" colwidth="8mm" /><colspec colnum="7" colname="col7" colwidth="8mm" /><colspec colnum="8" colname="col8" colwidth="8mm" /><colspec colnum="9" colname="col9" colwidth="10mm" /><colspec colnum="10" colname="col10" colwidth="8mm" /><colspec colnum="11" colname="col11" colwidth="8mm" /><thead><row><entry valign="top"><b>UL-DL Configuration</b></entry><entry namest="col2" nameend="col11" align="left" valign="top"><b>Subframe <i>n</i></b></entry></row><row><entry valign="top" /><entry valign="top">0</entry><entry valign="top">1</entry><entry valign="top">2</entry><entry valign="top">3</entry><entry valign="top">4</entry><entry valign="top">5</entry><entry valign="top">6</entry><entry valign="top">7</entry><entry valign="top">8</entry><entry valign="top">9</entry></row></thead><tbody><row><entry>1</entry><entry>-</entry><entry>-</entry><entry>7, 6</entry><entry>4</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>7, 6</entry><entry>4</entry><entry>-</entry></row><row><entry>0</entry><entry>-</entry><entry>-</entry><entry>7, 6</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>-</entry><entry>7, 6</entry><entry>-</entry><entry>-</entry></row></tbody></tgroup></table></tables>
0131The eNB procedure according to the fourth exemplary embodiment is performed as described with reference to <figref idref="f0009">FIG. 9</figref> with the addition of rule 5. The UE procedure according to the fourth exemplary embodiment is performed as described with reference to <figref idref="f0010">FIG. 10</figref> with the addition of rule 5.
0132Although the first to fourth exemplary embodiments are directed to the method for transmitting HARQ ACK/NACK in PUCCH, the present invention is not limited thereto. Even when transmitting the HARQ ACK/NACK in the PUSCH, the HARQ ACK/NACK is transmitted according to the timing relationship so as to maintain the consistency of HARQ ACK/NACK transmission timing. For example, in the exemplary case of <figref idref="f0006">FIG. 6</figref>, the HARQ ACK/NACK corresponding to the PDSCH transmitted at the subframe #9 630 of the i<sup>th</sup> radio frame of the SCell is transmitted at the subframe #3 of the (i+1)<sup>th</sup> radio frame according to the SCell's own timing relationship. In a case where the UE transmits PUSCH at the subframe #3 634 of the (i+1)<sup>th</sup> radio frame, however, the HARQ ACK/NACK can be transmitted in the PUSCH at the subframe #3 of the SCell. Even in this case, rule 2 is applied such that the PUCCH, or if PUSCH has been scheduled, the HARQ ACK/NACK can be transmitted in the PUSCH.
0133Typically in the legacy LTE and LTE-A systems, the radio resource for transmitting the HARQ ACK/NACK is calculated automatically from the Control Channel Element (CCE) of the PDCCH for scheduling the PDSCH corresponding to the HARQ ACK/NACK. The CCE is a unit of the PDCCH. One CCE is composed of total 36 Resource Elements (REs). The RE is a basic unit of radio resource of the LTE and LTE-A systems and is defined as a combination of a subcarrier in the frequency domain and an OFDM symbol in the time domain.
0134If one PDCCH is used for scheduling PDSCH to be transmitted at a plurality of subframes, it is possible to cross-carrier schedule the PDSCH to be transmitted at the subframe #1 622 of the SCell (hereinafter, referred to as PDSCH 1) and the PDSCH to be transmitted at the subframe #4 625 of the SCell (hereinafter, referred to as PDSCH 2) with one PDCCH transmitted at the subframe #1 676 of the PCell simultaneously. At this time, the transmission resource for the HARQ ACK/NACKs corresponding to the PDSCHs of the PCell and SCell should be defined, respectively.
0135In case that the transmission timing of the PDSCH 1 is earlier than that of the PDSCH 2, the transmission resource of the HARQ ACK/NACK corresponding to the PDSCH 1 is calculated from the CCE having the lowest index (n_CCE). Meanwhile, the transmission resource of the HARQ ACK/NACK corresponding to the PDSCH 2 is calculated from the CCE having the index of n_CCE+1.
0136<figref idref="f0012">FIG. 12</figref> is a block diagram illustrating a configuration of an eNB according to any of the first to fourth exemplary embodiments of the present invention.
0137Referring to <figref idref="f0012">FIG. 12</figref>, the eNB includes a transmission part (TX) comprising a Carrier aggregation/timing controller 1201, a scheduler 1203, a PDCCH block 1205, a PDSCH block 1216, and a multiplexer 1215; and a reception part (RX) comprising a PUCCH block 1239 and a demultiplexer 1249. The PDCCH block 1205 of the transmission part includes a DCI formatter 1207, a channel coder 1209, a rate matcher 1211 and a modulator 1213; and the PDSCH block 1216 includes a data buffer 1217, a channel coder 1219, a rate matcher 1221, and a modulator 1223. The PUCCH block of the reception part includes a demodulator 1247, a channel decoder 1243, and an HARQ ACK/NACK acquirer 1241.
0138The carrier aggregation/timing controller 1201 determines the carrier aggregation scheme and the timing relationship among the physical channels for the UE to be scheduled by referencing the data amount to be transmitted to the UE and the resource amount available in the system and notifies the scheduler 1203 and the PUCCH block 1239 of the determination result. Here, the timing relationship is determined according to the method according to one of the above-described exemplary embodiments of the present invention.
0139The carrier aggregation/timing controller 1201 controls to transmit to the UE the downlink physical channels for at least one of the first and second cells. The carrier aggregation/timing controller 1201 controls to receive the uplink physical channel corresponding to the downlink physical channel at a predetermined timing through the first cell. The carrier aggregation/timing controller 1201 also control such that the uplink physical channel corresponding to the downlink physical channel of the second cell is received at the uplink physical channel reception timing of the first cell.
0140In this case, if the downlink physical channels about the first and second cells are transmitted to the UE at the same timing, the carrier aggregation/timing controller 1201 configures the uplink physical channel reception timing of the second cell to be identical with the uplink physical channel reception timing of the first cell. Meanwhile, if the downlink physical channels of the first and second cells are not transmitted at the same timing, the carrier aggregation/timing controller 1201 configures such that the uplink physical channel reception timing of the second cell is identical with the uplink physical channel reception timing corresponding to the downlink subframe of the first cell which is closest to the downlink physical channel reception timing of the second cell. In this case, the uplink physical channels for the first and second cells can be received as distributed across the uplink subframes as equally as possible.
0141In a case where the first cell is in the state of a DL subframe and the second cell is in the state of a UL subframe, the carrier aggregation/timing controller 1201 may not cross-carrier schedule the second cell at the corresponding timing.
0142The PDCCH block 1205 generates DCI by means of the DCI formatter 1207 under the control of the scheduler 1203. The DCI is channel-coded with the addition of error correction capability by means of the channel coder 1209 and then rate-matched to the resource amount to be mapped thereto by means of the rate matcher 1211. The rate-matched DCI is modulated by the modulator 1213 and multiplexed with other signals by the multiplexer 1215. The multiplexed signals are converted into OFDM signals so as to be transmitted to the UE.
0143The PDSCH block 1215 receives PDSCH data in the data buffer 1217 under the control of the scheduler 1203. The PDSCH data is channel-coded by means of the channel coder 1219 and then rate-matched to the resource amount to be mapped thereto by means of the rate matcher 1221. The rate-matched PDSCH data is modulated by the modulator 1223 and multiplexed with other signals by the multiplexer 1215. The multiplexed signals are converted into OFDM signals so as to be transmitted to the UE.
0144The PUCCH block 1239 of the receiver separates PUCCH signals from the received signal by means of the demultiplexer 1249 and the demodulator 1247 performs demodulation on the PUSCH signal. The PUCCH block 1239 decodes the demodulated PUCCH signal by means of the channel decoder 1243 and acquires HARQ ACK/NACK by means of the HARQ ACK/NACK acquirer 1241. The acquired HARQ ACK/NACK is provided to the scheduler so as to be used for determining whether to retransmit the PDSCH. The acquired HARQ ACK/NACK is also provided to the carrier aggregation/timing controller 1201 so as to be used for determining the PDSCH transmission timing.
0145<figref idref="f0013">FIG. 13</figref> is a block diagram illustrating a configuration of a UE according to any of the first to fourth exemplary embodiments of the present invention.
0146Referring to <figref idref="f0013">FIG. 13</figref>, the UE includes a transmission part (TX) comprising a carrier aggregation/timing controller 1301, a PUCCH block 1305, and a multiplexer 1315; and a reception part (RX) comprising a PDSCH block 1330, a PDCCH block 1339, a demultiplexer 1349. The PUCCH block 1305 of the transmission part includes an HARQ ACK/NACK formatter 1307, a channel coder 1309, and a modulator 1313. The PDSCH block 1330 of the reception part includes a demodulator 1337, a de-rate matcher 1335, a channel decoder 1333, and a data acquirer 1331. The PDCCH block 1339 includes a demodulator 1347, a de-rate matcher 1345, a channel decoder 1343, and a DCI acquirer 1341.
0147The carrier aggregation/timing controller 1301 adjusts the carrier aggregation state of the UE based on the DCI received from the eNB. The carrier aggregation and timing controller 1301 determines the carrier for receiving PDSCH in cross-carrier scheduling mode and the timing relationship among the physical channel and notifies the PUCCH block 1305, PDSCH block 1330, and PDCCH block 1339 of the determination result. The timing relationship is determined according to one of the above-described exemplary embodiments of the present invention.
0148In more detail, the carrier aggregation/timing controller 1301 controls to receive the downlink physical channel transmitted by the eNB through at least one of the first and second cells. The carrier aggregation/timing controller 1301 also controls such that the uplink physical channel is transmitted at a predetermined timing through the first cell. The carrier aggregation/timing controller 1301 also controls such that the uplink physical channel of the second cell is transmitted at the uplink physical channel transmission timing of the first cell.
0149In a case where the downlink physical channels of the first and second cells are transmitted from the eNB at the same timing, the carrier aggregation/timing controller 1301 configures such that the uplink physical channel transmission timing of the second cell matches the uplink physical channel transmission timing of the first cell. Also, when the downlink physical channels of the first and second cells are received from the eNB at different timings, the carrier aggregation/timing controller 1301 configures the uplink physical transmission timing of the second cell to match the uplink physical channel transmission timing configured for the downlink subframe of the first cell which is closest to the downlink physical transmission timing of the second cell.
0150In this case, the carrier aggregation/timing controller 1301 can control such that the uplink physical channels of the first and second cells are transmitted to the eNB as distributed across the uplink subframes as equally as possible.
0151The PUCCH block 1305 of the transmitter configures the HARQ ACK/NACK by means of the HARQ ACK/NACK formatter 1307 under the timing control of the carrier aggregation/timing controller 1201. The HARQ ACK/NACK is channel coded with the addition of error correction code capability by the channel coder 1309, modulated by the modulator 1313, and multiplexed with other signals by the multiplexer 1315.
0152The PDSCH block 1330 of the reception part separates the PDSCH signal from the received signal by means of the demultiplexer 1349. The PDSCH block 1330 demodulates the PDSCH signal by means of the demodulator 1337 and reconfigures the symbols before rate matching by means of the de-rate matcher 1335. The PDSCH block 1330 decodes the reconfigured symbols by means of the channel decoder 1333 and acquires PDSCH data by means of the data acquirer 1331. The data acquirer 1331 notifies the PUSCH block 1305 of the error occurrence in the decoding result to control generation of the uplink HARQ ACK/NACK. The data acquirer 1331 provides the carrier aggregation/timing controller 1301 with the decoding result to adjust the HARQ ACK/NACK transmission timing.
0153The PDCCH block 1339 separates PDCCH signal from the received signal by means of the demultiplexer 1349. The PDCCH block 1339 demodulates the separated PDCCH signal by means of the demodulator 1347 and decodes the demodulated signal by means of the channel decoder 1343. The PDCCH block 1339 acquires DCI from the decoded PDCCH signal by means of the DCI acquirer 1341. The acquired DCI is provided to the carrier aggregation/timing controller 1301 so as to be used for adjusting the HARQ ACK/NACK transmission timing.
0154As described above, the physical channel transmission/reception timing configuration method and apparatus of exemplary embodiments of the present invention is capable of minimizing data and/or control channel transmission/reception error and transmission delay by defining the transmission timing among the physical data and control channels in the TDD wireless communication system securing broadband resource through carrier aggregation.
0155While the invention has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the invention as defined by the appended claims and their equivalents.
0156The invention provides the following fourteen aspects counted from one (the aspects have to be understood as examples useful for understanding the invention): The aspect of a method for receiving, at a base station, a Hybrid Automatic Repeat Request (HARQ) acknowledgement from a terminal in a Time Division Duplex (TDD) system supporting carrier aggregation of a primary cell and at least one secondary cell, the method comprising: transmitting a downlink physical channel through one of the primary and secondary cells; receiving the HARQ acknowledgement corresponding to the downlink physical channel of the primary cell at a first timing predetermined for the primary cell; and receiving the HARQ acknowledgement corresponding to the downlink physical channel of the secondary cell at second timing, wherein the second timing is determined according to the first timing.
0157The method of the first aspect, wherein the second timing is identical with the first timing when the downlink physical channels of the primary and secondary cells are transmitted at the same timing.
0158The method of the first aspect, wherein the second timing is identical with a HARQ acknowledge reception timing corresponding to a downlink subframe of the primary cell which is closest to a transmission timing of the downlink physical channel of the secondary cell, when the downlink physical channels of the primary and secondary cells are transmitted at different timings.
0159The method of the first aspect, further comprising suspending, when the primary cell is in a state of a downlink subframe and the secondary cell is in a state of an uplink subframe at the same timing, cross-carrier scheduling to the secondary cell at the timing.
0160The aspect of a method for transmitting, at a terminal, a Hybrid Automatic Repeat Request (HARQ) acknowledgement to a base station in a Time Division Duplex (TDD) system supporting carrier aggregation of a primary cell and at least one secondary cell, the method comprising: receiving a downlink physical channel through one of the primary and second cells; transmitting the HARQ acknowledgement corresponding to the downlink physical channel of the primary cell at a first timing predetermined for the primary cell; and transmitting the HARQ acknowledgement corresponding to the downlink physical channel of the secondary cell at a second timing, wherein the second timing is determined according to the first timing.
0161The method of the fifth aspect, wherein the second timing is identical with the first timing when the downlink physical channels of the primary and secondary cells are received at the same timing.
0162The method of the fifth aspect, wherein the second timing is identical with a HARQ acknowledge transmission timing corresponding to a downlink subframe of the primary cell which is closest to a reception timing of the downlink physical channel of the secondary cell, when the downlink physical channels of the primary and secondary cells are received at different timings.
0163The aspect of a base station for receiving a Hybrid Automatic Repeat Request (HARQ) acknowledgement from a terminal in a Time Division Duplex (TDD) system supporting carrier aggregation of a primary cell and at least one secondary cell, the base station comprising: a transceiver which transmits and receives to and from the terminal; and a controller which controls transmitting a downlink physical channel through one of the primary and secondary cells, receiving the HARQ acknowledgement corresponding to the downlink physical channel of the primary cell at a first timing predetermined for the primary cell, and receiving the HARQ acknowledgement corresponding to the downlink physical channel of the secondary cell at second timing, wherein the controller configures the second timing according to the first timing.
0164The base station of the eighth aspect, wherein the controller configures, when the downlink physical channels of the primary and secondary cells are transmitted at the same timing, the second timing to be identical with the first timing.
0165The base station of the eighth aspect, wherein the controller configures, when the downlink physical channels of the primary and secondary cells are transmitted at different timings, the second timing to be identical with a HARQ acknowledge reception timing corresponding to a downlink subframe of the primary cell which is closest to a transmission timing of the downlink physical channel of the secondary cell.
0166The base station of the eighth aspect, wherein the controller controls suspending, when the primary cell is in a state of a downlink subframe and the secondary cell is in a state of an uplink subframe at the same timing, cross-carrier scheduling to the secondary cell at the timing.
0167The aspect of a terminal for transmitting a Hybrid Automatic Repeat Request (HARQ) acknowledgement to a base station in a Time Division Duplex (TDD) system supporting carrier aggregation of a primary cell and at least one secondary cell, the terminal comprising: a transceiver which transmits and receives to and form a base station; and a controller which controls receiving a downlink physical channel through one of the primary and second cells, transmitting the HARQ acknowledgement corresponding to the downlink physical channel of the primary cell at a first timing predetermined for the primary cell, and transmitting the HARQ acknowledgement corresponding to the downlink physical channel of the secondary cell at a second timing, wherein controller configures the second timing according to the first timing.
0168The terminal of the twelfth aspect, wherein the controller configures, when the downlink physical channels of the primary and secondary cells are received at the same timing, the second timing to be identical with the first timing.
0169The terminal of the twelfth aspect, wherein the controller configures, when the downlink physical channels of the primary and secondary cells are received at different timings, the second timing to be identical with a HARQ acknowledge transmission timing corresponding to a downlink subframe of the primary cell which is closest to a reception timing of the downlink physical channel of the secondary cell.
13 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| US2011044239A1 | Cites | United States of America |
| ERICSSON ET AL: "Remaining issues in general frame work for aggregation of carriers with different UL/DL configurations", 3GPP DRAFT; R1-120070, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Dresden, Germany; 20120206 - 20120210, 31 January 2012 (2012-01-31), XP050562653, | Non-patent | – |
| ERICSSON ET AL: "Different TDD configurations in inter-band CA", 3GPP DRAFT; R2-121640 DIFFERENT TDD CONFIGURATIONS IN CA, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Jeju, South Korea; 20120326 - 20120330, 20 March 2012 (2012-03-20), XP050606385, | Non-patent | – |
24 members in 9 offices
Members24
| Document | Office | Kind | |
|---|---|---|---|
| EP2530863A2 | European Patent Office (EPO) | A2 | |
| US2012307689A1 | United States of America | A1 | |
| WO2012165875A2 | World Intellectual Property Organization (WIPO) | A2 | |
| KR20120133982A | Republic of Korea | A | |
| WO2012165875A9 | World Intellectual Property Organization (WIPO) | A9 | |
| WO2012165875A3 | World Intellectual Property Organization (WIPO) | A3 | |
| EP2530863A3 | European Patent Office (EPO) | A3 | |
| CN103718484A | China | A | |
| JP2014519757A | Japan | A | |
| US8942202B2 | United States of America | B2 | |
| US2015131602A1 | United States of America | A1 | |
| EP2530863B1 | European Patent Office (EPO) | B1 | |
| ES2603480T3 | Spain | T3 | |
| EP3136639A1 | European Patent Office (EPO) | A1 | |
| US9608775B2 | United States of America | B2 | |
| US2017207900A1 | United States of America | A1 | |
| CN103718484B | China | B | |
| CN107204835A | China | A | |
| US10230518B2 | United States of America | B2 | |
| EP3136639B1This record | European Patent Office (EPO) | B1 | |
| KR101961807B1 | Republic of Korea | B1 | |
| PL3136639T3 | Poland | T3 | |
| HUE045560T2 | Hungary | T2 | |
| CN107204835B | China | B |
71 legal events, as 11 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed because of non-payment of the annual feeLapsedMM | MM | BE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| No opposition filedOpposition26N | 26N | EP | |
| Information on lapse in contracting state deletedLapsedPG2D | PG2D | EP | |
| No opposition filed within time limitOppositionORIGINAL CODE: 0009261PLBE | PLBE | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: NO OPPOSITION FILED WITHIN TIME LIMITSTAA | STAA | EP | |
| No opposition filed against granted patent, or epo opposition proceedings concluded without decisionGrantedR097 | R097 | DE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Filing of the translation of the text of european patentsAG4A | AG4A | HU | |
| Deletion acc. to par. 5 (withdrawal of the translation of the ep patent)MK05 | MK05 | AT | |
| Invalidated european patentMG4D | MG4D | LT | |
| Translation for ep filed (entry of ep into country)FP | FP | NL | |
| Translation of granted ep patentGrantedTRGR | TRGR | SE | |
| Dpma publication of mentioned ep patent grantGrantedR096 | R096 | DE | |
| European patents granted designating irelandGrantedFG4D | FG4D | IE | |
| European patent takes effect as a national patent in ch/liEP | EP | CH | |
| Reference to at number (ep patent validated in austria)REF | REF | AT | |
| Divisional application: reference to earlier applicationAC | AC | EP | |
| Designated contracting statesAK | AK | EP | |
| European patent grantedGrantedFG4D | FG4D | GB | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: THE PATENT HAS BEEN GRANTEDSTAA | STAA | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Intention to grant announcedINTG | INTG | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: GRANT OF PATENT IS INTENDEDSTAA | STAA | EP | |
| Request for examination filed17P | 17P | EP | |
| Designated contracting states (corrected)RBV | RBV | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: REQUEST FOR EXAMINATION WAS MADESTAA | STAA | EP | |
| Divisional application: reference to earlier applicationAC | AC | EP | |
| Designated contracting statesAK | AK | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: THE APPLICATION HAS BEEN PUBLISHEDSTAA | STAA | EP |
Numbers
- Publication
- 3136639
- Application
- 161906672
Titles3
- German
- VORRICHTUNG UND VERFAHREN ZUM DEFINIEREN PHYSIKALISCHER KANALSENDE-/-EMPFANGSZEITPUNKTE UND RESSOURCENZUWEISUNG IN EINEM TDD-KOMMUNIKATIONSSYSTEM MIT UNTERSTÜTZUNG VON TRÄGERAGGREGATION
- English
- APPARATUS AND METHOD FOR DEFINING PHYSICAL CHANNEL TRANSMIT/RECEIVE TIMINGS AND RESOURCE ALLOCATION IN TDD COMMUNICATION SYSTEM SUPPORTING CARRIER AGGREGATION
- French
- APPAREIL ET PROCÉDÉ PERMETTANT DE DÉFINIR DES MOMENTS DE TRANSMISSION/RÉCEPTION DE CANAL PHYSIQUE ET UNE ATTRIBUTION DE RESSOURCES DANS UN SYSTÈME DE COMMUNICATION TDD SUPPORTANT UN REGROUPEMENT DE PORTEUSES
Classification
- CPC, 11
- H04L1/1861
- H04B7/2603
- H04L41/08
- H04L5/22
- H04W56/00
- H04W72/0446
- H04W88/02
- H04W88/08
- H04L1/1812
- H04L5/14
- H04W72/12
- IPC, 1
- H04L1 18
Designated states38
- Contracting states, 38
- Albania
- Austria
- Belgium
- Bulgaria
- Switzerland
- Cyprus
- Czechia
- Germany
- Denmark
- Estonia
- Spain
- Finland
- France
- United Kingdom
- Greece
- Croatia
- Hungary
- Ireland
- Iceland
- Italy
- Liechtenstein
- Lithuania
- Luxembourg
- Latvia
and 14 moreShow fewer
- Monaco
- North Macedonia
- Malta
- Netherlands (Kingdom of the)
- Norway
- Poland
- Portugal
- Romania
- Serbia
- Sweden
- Slovenia
- Slovakia
- San Marino
- Türkiye