WO2013005991A2 - Method and apparatus for transmitting uplink control information in a time division duplex system - Google Patents

Abstract

Provided are a method and an apparatus for transmitting uplink control information in a wireless communication system. The apparatus of the present invention receives, from a base station and through a first serving cell, a physical downlink control channel to which an uplink grant is mapped; receives, from the base station and through a second serving cell, a physical hybrid automatic repeat request indication channel (PHICH); and transmits an uplink HARQ to the base station through a physical uplink shared channel (PUSCH) on the basis of the uplink grant. If a TDD uplink/downlink configuration of the first serving cell and a TDD uplink/downlink configuration of the second serving cell are not identical, the timing of receiving the PHICH is defined as the location corresponding to a downlink subframe of the first serving cell, and the sum of a PHICH reception timing and a PUSCH transmission timing is set as a minimum value.

Description

Method and apparatus for transmitting uplink control information in time division duplex system

The present invention relates to wireless communication, and more particularly, to a method and apparatus for transmitting uplink control information in a TDD system of a wireless communication system.

Recently, with the introduction of a multiple carrier system, random access can be implemented through multiple component carriers (CCs). The multi-carrier system is a wireless communication system capable of supporting carrier aggregation (CA). In this case, carrier aggregation is a technique for efficiently using a fragmented small band, and combines a plurality of physically non-continuous bands in the frequency domain to produce the same effect as using a logically large band. Technology for.

The component carrier for receiving downlink control information from the base station and the component carrier for receiving downlink data may be configured differently, or the link between the component carrier for receiving downlink control information and the component carrier for transmitting an uplink signal may be different. It is also possible to follow a link relationship different from the link established in the existing LTE. This scheduling method is called cross-carrier scheduling.

In the past, a common TDD configuration was applied among a plurality of serving cells, but an attempt is made to enable efficient data traffic control through flexible TDD uplink-downlink configuration between each serving cell. As described above, when an independent TDD configuration is applied to each of the serving cells, a method of configuring a PUSCH timing or a UL HARQ timing generated is required.

Meanwhile, enhanced Inter Cell Interference Coordination (eICIC) technology is a method for mitigating interference between various cells in this HetNet situation. As an example of this method, the ABS (Almost Blank Subframe) is used to reduce the interference from the Aggressor cell (eg, macro cell or femto cell) to the Victim cell (eg pico cell or macro cell). There is a way to use patterns.

There is also a need for a method of configuring UL HARQ timing, such as a PUSCH timing or a PHICH timing, generated when an independent TDD configuration is applied to each serving cell in an eICIC technology.

There is also a need for a method of transmitting data by controlling a transmission power corresponding to a plurality of component carriers in a multi-component carrier system. This is because, in the TDD scheme, when the component carriers receive different transmission timings of the transmission power control commands, it may cause unstable operation of the system. If the timing of requesting and reporting a downlink channel condition is not correct in the multi-component carrier system, This can cause unstable operation.

An object of the present invention is to provide a method and chapter for performing UL HARQ in a TDD system.

Another technical problem of the present invention is to efficiently configure timing information for performing UL HARQ in a terminal and a base station to which cross-carrier scheduling is applied.

Another technical problem of the present invention is to provide a method and apparatus for configuring timing information for flexible traffic handling when ABS is used as an eICIC scheme in a TDD system.

Another technical problem of the present invention is to provide a method and apparatus for transmitting uplink data by controlling a transmission power of a terminal in a multi-component carrier system.

Another technical problem of the present invention is to provide an apparatus and method for applying independent up / down configuration for each serving cell.

According to an aspect of the present invention, a method for transmitting uplink control information by a terminal in a wireless communication system includes a physical downlink control channel (PDCCH) to which an uplink grant is mapped from a base station through a first serving cell; Receiving; Receiving a Physical Hybrid Automatic Repeat Request Indicator Channel (PHICH) from the base station through a second serving cell; And transmitting an uplink hybrid automatic repeat request (HARQ) based on the uplink grant to the base station through a physical uplink shared channel (PUSCH), wherein the TDD of the first serving cell is included. (Time Division Duplex) When the uplink / downlink configuration and the TDD uplink / downlink configuration of the second serving cell are not the same, the PHICH reception timing is assigned to a downlink subframe of the first serving cell. A corresponding position is defined, and the sum of the PHICH reception timing and the PUSCH transmission timing is determined to be the minimum value.

According to another aspect of the present invention, in a method for transmitting uplink control information by a base station in a wireless communication system, a physical downlink control channel (PDCCH) to which an uplink grant is mapped is transmitted to a terminal through a first serving cell. Transmitting; Transmitting a physical hybrid automatic repeat request indicator channel (PHICH) to the terminal through a second serving cell; And receiving an uplink hybrid automatic repeat request (HARQ) based on the uplink grant from the terminal through a physical uplink shared channel (PUSCH), wherein the TDD of the first serving cell is received. (Time Division Duplex) When the uplink / downlink configuration and the TDD uplink / downlink configuration of the second serving cell are not the same, the PHICH transmission timing is set to a downlink subframe of the first serving cell. Defined as the corresponding position, the sum of the PHICH transmission timing and the PUSCH transmission timing is determined to be the minimum value.

According to another aspect of the present invention, a terminal for transmitting uplink control information in a wireless communication system, the physical downlink control channel (PDCCH) to which an uplink grant is mapped from a base station through a first serving cell A receiving unit for receiving a physical hybrid automatic repeat request indicator channel (PHICH) from the base station through a second serving cell; And a transmitter for transmitting an uplink hybrid automatic repeat request (HARQ) based on the uplink grant to the base station through a physical uplink shared channel (PUSCH), wherein the TDD of the first serving cell is included. (Time Division Duplex) When the uplink / downlink configuration and the TDD uplink / downlink configuration of the second serving cell are not the same, the PHICH reception timing is assigned to a downlink subframe of the first serving cell. A corresponding position is defined, and the sum of the PHICH reception timing and the PUSCH transmission timing is determined to be the minimum value.

According to the present invention, when different TDD settings are applied to a plurality of serving cells, UL HARQ may be efficiently configured by performing UL HARQ timing.

According to the present invention, when an ABS pattern is used in an eICIC situation of a TDD system, uplink transmission may be performed by effectively operating a PUSCH resource and flexibly configuring an ABS pattern.

According to the present invention, when different TDD settings are applied to a plurality of serving cells, UL PUSCH timing and UL HARQ timing can be effectively configured.

According to the present invention, the timing of receiving the transmission power control command for the secondary serving cell can be matched with the timing of the transmission power control command for the main serving cell. In addition, the timing according to the request of the channel status information with respect to the secondary serving cell can be matched with the timing of reporting the channel status information.

According to the present invention, it is possible to solve the fact that uplink / downlink setting for each serving cell is not the same in the multi-component carrier system, an ambiguity of the reception timing of the transmission power control command, or an ambiguity of the channel status information reporting timing.

1 shows a wireless communication system to which the present invention is applied.

2 shows an example of a protocol structure for supporting a multi-carrier system to which the present invention is applied.

3 shows a TDD radio frame structure in a 3GPP LTE system.

4 is an exemplary diagram illustrating a resource grid for one slot.

5 shows a structure of a downlink subframe.

6 shows a structure of an uplink subframe.

7 shows a UL HARQ process.

8 shows an adaptive UL HARQ process.

9 is a flowchart illustrating an optimized PUSCH scheduling method (or UL HARQ timing configuration method) according to the present invention.

10 illustrates an example of applying a configuration method of PUSCH timing or PHICH timing according to the present invention.

11 is a flowchart illustrating another PUSCH timing configuration method or a UL HARQ timing configuration method according to the present invention.

12 shows an example of applying another PUSCH configuration method according to the present invention.

13 illustrates subframe scheduling according to the present invention.

14 is a flowchart illustrating another example of a method of configuring HARQ timing according to the present invention.

15 shows an example of an ABS pattern in a TDD system to which the present invention is applied.

16 is a flowchart illustrating an example of a method of configuring UL HARQ timing according to the present invention.

17 is a flowchart illustrating another example of a method of configuring UL HARQ timing according to the present invention.

18 is a diagram illustrating a k value configured by the UL HARQ timing configuration method of the present invention.

19 illustrates k _PHICH configured by the UL HARQ timing configuration method of the present invention.

20 is a diagram illustrating a value of l according to a newly configured UL HARQ timing when subframe bundling is configured according to the present invention.

21 illustrates configuring PHICH timing using multiplexing according to the present invention.

22 shows a result of resource allocation performed using ACK / NACK multiplexing according to the present invention.

23 is a flowchart illustrating controlling uplink transmission power according to the present invention.

24 is a flowchart illustrating an example of a method of determining a TPC command reception timing (KPUSCH) according to the present invention.

25 illustrates a method of determining a new TPC command reception timing value in accordance with the present invention.

26 illustrates a process of determining a new TPC command reception timing according to the present invention.

27 is a flowchart illustrating another example of a method of determining a TPC command reception timing according to the present invention.

FIG. 28 shows an example of allocating a common search space for transmitting an RAR grant to which a following serving cell is applied.

29 is a flowchart illustrating aperiodic CSI reporting timing in accordance with the present invention.

30 is a block diagram illustrating a base station and a terminal for transmitting control information according to an embodiment of the present invention.

Hereinafter, some embodiments will be described in detail with reference to the accompanying drawings. In adding reference numerals to the components of each drawing, it should be noted that the same reference numerals are assigned to the same components as much as possible even though they are shown in different drawings. In addition, in describing the embodiments of the present specification, when it is determined that a detailed description of a related well-known configuration or function may obscure the gist of the present specification, the detailed description thereof will be omitted.

In addition, in describing the component of this specification, terms, such as 1st, 2nd, A, B, (a), (b), can be used. These terms are only for distinguishing the components from other components, and the nature, order or order of the components are not limited by the terms. If a component is described as being "connected", "coupled" or "connected" to another component, that component may be directly connected or connected to that other component, but between components It will be understood that may be "connected", "coupled" or "connected".

1 shows a wireless communication system to which the present invention is applied.

Referring to FIG. 1, the wireless communication system 10 is widely deployed to provide various communication services such as voice and packet data. The wireless communication system 10 includes at least one base station 11 (evolved NodeB, eNB). Each base station 11 provides a communication service for specific cells 15a, 15b, and 15c. The cell can in turn be divided into a number of regions (called sectors).

A UE 12 may be fixed or mobile and may have a mobile station (MS), a mobile terminal (MS), a mobile terminal (MT), a user terminal (UT), a subscriber station (SS), a wireless device, or a PDA. (personal digital assistant), wireless modem (wireless modem), a handheld device (handheld device) may be called other terms. The base station 11 may be called by other terms such as a base station (BS), a base transceiver system (BTS), an access point, an femto base station, a home node B, a relay, and the like. The cell should be interpreted in a comprehensive sense of a part of the area covered by the base station 11 and encompasses various coverage areas such as megacells, macrocells, microcells, picocells and femtocells.

In the following, downlink means communication from the base station 11 to the terminal 12, and uplink means communication from the terminal 12 to the base station 11. In downlink, the transmitter may be part of the base station 11 and the receiver may be part of the terminal 12. In uplink, the transmitter may be part of the terminal 12 and the receiver may be part of the base station 11. There is no limitation on the multiple access scheme applied to the wireless communication system. Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier-FDMA (SC-FDMA), OFDM-FDMA, OFDM-TDMA For example, various multiple access schemes such as OFDM-CDMA may be used. The uplink transmission and the downlink transmission may use a time division duplex (TDD) scheme that is transmitted using different times, or may use a frequency division duplex (FDD) scheme that is transmitted using different frequencies.

Carrier aggregation (CA) supports a plurality of carriers, also referred to as spectrum aggregation or bandwidth aggregation. Individual unit carriers bound by carrier aggregation are called component carriers (CCs). Each component carrier is defined by a bandwidth and a center frequency. Carrier aggregation supports increased throughput, prevents cost increases due to the introduction of wideband radio frequency (RF) devices, and ensures compatibility with existing systems. For example, if five component carriers are allocated as granularity in a carrier unit having a 20 MHz bandwidth, a bandwidth of up to 100 MHz may be supported.

Carrier aggregation may be divided into contiguous carrier aggregation between continuous component carriers in the frequency domain and non-contiguous carrier aggregation between discontinuous component carriers. The number of carriers aggregated between the downlink and the uplink may be set differently. The case where the number of downlink component carriers and the number of uplink component carriers are the same is called symmetric aggregation, and when the number is different, it is called asymmetric aggregation.

The size (ie, bandwidth) of component carriers may be different from each other. For example, assuming that 5 component carriers are used for the configuration of the 70 MHz band, a 5 MHz component carrier (carrier # 0) + 20 MHz component carrier (carrier # 1) + 20 MHz component carrier (carrier # 2) + 20 MHz component carrier (carrier # 3) + 5MHz component carrier (carrier # 4) may be configured.

Hereinafter, a multiple carrier system refers to a system supporting carrier aggregation. Adjacent carrier aggregation and / or non-adjacent carrier aggregation may be used in a multi-carrier system, and either symmetric aggregation or asymmetric aggregation may be used.

2 shows an example of a protocol structure for supporting a multi-carrier system to which the present invention is applied.

Referring to FIG. 2, the common medium access control (MAC) entity 210 manages a physical layer 220 using a plurality of carriers. The MAC management message transmitted on a specific carrier may be applied to other carriers. That is, the MAC management message is a message capable of controlling other carriers including the specific carrier. The physical layer 220 may operate in a time division duplex (TDD) and / or a frequency division duplex (FDD).

There are several physical control channels used in the physical layer 220. The physical downlink control channel (PDCCH) informs the terminal of resource allocation of a paging channel (PCH) and downlink shared channel (DL-SCH) and hybrid automatic repeat request (HARQ) information related to the DL-SCH. The PDCCH may carry an uplink grant informing the UE of resource allocation of uplink transmission. The physical control format indicator channel (PCFICH) informs the UE of the number of OFDM symbols used for PDCCHs and is transmitted every subframe. PHICH (physical Hybrid ARQ Indicator Channel) carries a HARQ ACK / NAK signal in response to uplink transmission. Physical uplink control channel (PUCCH) carries uplink control information such as HARQ ACK / NAK, scheduling request, and CQI for downlink transmission. Physical uplink shared channel (PUSCH) carries an uplink shared channel (UL-SCH). A physical random access channel (PRACH) carries a random access preamble.

3 illustrates a TDD radio frame structure in a 3GPP LTE system.

Referring to FIG. 3, one radio frame is composed of two half-frames having a length of 10 ms and a length of 5 ms. In addition, one half frame consists of five subframes having a length of 1 ms. One subframe is designated as one of an uplink subframe (UL subframe), a downlink subframe (DL subframe), and a special subframe. One TDD radio frame includes at least one uplink subframe, at least one downlink subframe, and at least one special subframe.

One subframe consists of two slots. For example, one subframe may have a length of 1 ms, and one slot may have a length of 0.5 ms. The time taken for one subframe to be transmitted is called a transmission time interval (TTI). One slot includes a plurality of orthogonal frequency division multiplexing (OFDM) symbols in the time domain and a plurality of subcarriers in the frequency domain. The OFDM symbol is used to represent one symbol period since 3GPP LTE uses OFDMA in downlink, and may be referred to as an SC-FDMA symbol or a symbol period according to a multiple access scheme. The RB includes a plurality of OFDM symbols and a plurality of subcarriers in one slot in resource allocation units.

The structure of the radio frame is only an example, and the number of subframes included in the radio frame or the number of slots included in the subframe and the number of OFDM symbols included in the slot may be variously changed.

The special subframe is a specific period for separating the uplink and the downlink between the uplink subframe and the downlink subframe. At least one special subframe exists in one radio frame, and the special subframe includes a downlink pilot time slot (DwPTS), a guard period (GP), and an uplink pilot time slot (UpPTS). DwPTS is used for initial cell search, synchronization or channel estimation. UpPTS is used for channel estimation at the base station and synchronization of uplink transmission of the terminal. The GP is a protection interval for removing interference caused by the uplink due to the multipath delay of the downlink signal between the uplink and the downlink. In this case, the special subframe may be used as a downlink subframe.

4 is an exemplary diagram illustrating a resource grid for one slot.

Referring to FIG. 4, one downlink slot includes a plurality of OFDM symbols in a time domain. Here, one downlink slot includes 7 OFDM symbols and one resource block includes 12 subcarriers in a frequency domain, but is not limited thereto.

Each element on the resource grid is called a resource element, and one resource block includes 12 를 7 resource elements. The number N _RB of resource blocks included in the downlink slot depends on a downlink transmission bandwidth set in a cell.

5 shows a structure of a downlink subframe.

Referring to FIG. 5, a subframe includes two slots. Up to three OFDM symbols of the first slot in the subframe may be a control region to which control channels are allocated, and the remaining OFDM symbols may be a data region to which a Physical Downlink Shared Channel (PDSCH) is allocated.

Downlink control channels include a Physical Control Format Indicator Channel (PCFICH), a Physical Downlink Control Channel (PDCCH), a Physical Hybrid-ARQ Indicator Channel (PHICH), and the like. The PCFICH transmitted in the first OFDM symbol of the subframe carries information about the number of OFDM symbols (that is, the size of the control region) used for transmission of control channels in the subframe.

The PDCCH includes resource allocation of downlink-shared channel (DL-SCH) (also referred to as downlink grant) and transmission format, resource allocation information of uplink shared channel (UL-SCH) (also referred to as uplink grant). Resource allocation of upper layer control messages, such as paging information on PCH, system information on DL-SCH, random access response transmitted on PDSCH, a set of transmit power control commands for individual UEs in any UE group, and Voice over Internet Protocol (VoIP) can be activated. Control information transmitted through the PDCCH as described above is called downlink control information (DCI). DCI indicates uplink resource allocation information, downlink resource allocation information, and uplink transmission power control command for arbitrary UE groups. The PHICH carries an ACK (Acknowledgement) / NACK (Not-Acknowledgement) signal for an uplink HARQ (Hybrid Automatic Repeat Request). That is, the ACK / NACK signal for the uplink data transmitted by the terminal is transmitted on the PHICH.

The downlink subframe may be set to an undetected subframe in which the UE does not attempt to detect data (eg, does not detect the reference signal and does not perform the reference signal measurement). The undetected subframe may be, for example, a multicast / broadcast single frequency network (MBSFN) subframe.

MBSFN subframe can be used for two purposes. The first use is for multimedia broadcast multicast service (MBMS). MBMS is a service that transmits the same signal in multiple cells of a wireless communication system at the same time. Since the signal for MBMS is transmitted in multiple cells at the same time, unicast and reference signals are transmitted in different cells. Should be inserted differently. To this end, the base station informs the terminal of the location of the subframe in which the MBMS signal is transmitted, and a reference signal insertion scheme different from unicast is used in the subframe.

The second use is to avoid unnecessary signal reception and reference signal measurement to the terminal to which the base station or relay station is connected. For example, in 3GPP LTE, if a terminal does not receive any signal including a reference signal in a specific subframe, there is a possibility of malfunction. To prevent this, the RS sets the subframe receiving the downlink data from the base station as the MBSFN subframe and informs the UE. Then, the UE (more specifically, the 3GPP LTE release-8 UE) does not detect the reference signal in the MBSFN subframe and does not perform the reference signal measurement. In the present invention, the MBSFN subframe may be used for a second purpose.

A plurality of PDCCHs may be transmitted in the control region, and the terminal may monitor the plurality of PDCCHs. The PDCCH is transmitted on an aggregation of one or several consecutive control channel elements (CCEs). CCE is a logical allocation unit used to provide a PDCCH with a coding rate according to a state of a radio channel. The CCE corresponds to a plurality of resource element groups. The format of the PDCCH and the number of bits of the PDCCH are determined according to the correlation between the number of CCEs and the coding rate provided by the CCEs.

Control information transmitted through the PDCCH is called downlink control information (DCI). Table 1 below shows DCI according to various formats.

Table 1 DCI format Explanation 0 Used for scheduling of PUSCH (Uplink Grant) One Used for scheduling one PDSCH codeword in one cell 1A Used for simple scheduling of one PDSCH codeword in one cell and random access procedure initiated by PDCCH command 1B Used for simple scheduling of one PDSCH codeword in one cell using precoding information 1C Used for brief scheduling of one PDSCH codeword and notification of MCCH change 1D Used for simple scheduling of one PDSCH codeword in one cell containing precoding and power offset information 2 Used for PDSCH scheduling for UE configured in spatial multiplexing mode 2A Used for PDSCH scheduling of UE configured in long delay CDD mode 2C Used in transmission mode 9 (multi-layer transmission) 2D Used in linked multicasting scheme 3 Used to transmit TPC commands for PUCCH and PUSCH with power adjustment of 2 bits 3A Used to transmit TPC commands for PUCCH and PUSCH with single bit power adjustment 4 Used for PUSCH scheduling in one uplink cell using a multi-antenna port transmission mode

Referring to Table 1, DCI format 0 indicates uplink resource allocation information, DCI format 1 for scheduling one PDSCH codeword, DCI format 1A for compact scheduling of one PDSCH codeword, and DL-. DCI format 1C for very simple scheduling of SCH, DCI format for PDSCH scheduling in closed-loop spatial multiplexing mode, DCI format for PDSCH scheduling in open-loop spatial multiplexing mode There are format 2A, DCI formats 3 and 3A for transmission of a Transmission Power Control (TPC) command for the uplink channel.

Each field of the DCI is sequentially mapped to _n information bits a ₀ to a _n-1 . For example, if DCI is mapped to information bits of a total of 44 bits in length, each DCI field is sequentially mapped to a ₀ to a _n-1 . DCI formats 0, 1A, 3, and 3A may all have the same payload size. DCI format 0 may be called an uplink grant.

Table 2 below shows information elements included in DCI format 0, which is uplink resource allocation information (or uplink grant).

TABLE 2

Table 3 shows a structure of a radio frame that can be set according to an arrangement of an uplink subframe and a downlink subframe in a 3GPP LTE TDD system, also called TDD configuration. In Table 3, "D" represents a downlink subframe, "U" represents an uplink subframe, and "S" represents a special subframe.

TABLE 3 UL / DL Settings Subframe number 0 One 2 3 4 5 6 7 8 9 0 D S U U U D S U U U One D S U U D D S U U D 2 D S U D D D S U D D 3 D S U U U D D D D D 4 D S U U D D D D D D 5 D S U D D D D D D D 6 D S U U U D S U U D

The point of time from the downlink to the uplink or the time from the uplink to the downlink is called a switching point. The switch-point periodicity means a period in which an uplink subframe and a downlink subframe are repeatedly switched in the same manner, and are 5 ms or 10 ms. For example, in the uplink / downlink configuration (UL / DL configuration) 0, D-> S-> U-> U-> U is switched from 0th to 4th subframe, and 5th to 9th. The subframe is switched to D-> S-> U-> U-> U as before. Since one subframe is 1ms, the periodicity at the switching time is 5ms. That is, the periodicity of the switching time is less than one radio frame length (10ms), and the switching mode in the radio frame is repeated once.

The base station or relay station may set the downlink subframe to the MBFSN subframe and then transmit and receive data. In this case, there are subframes that cannot be set as MBSFN subframes. For example, a wireless communication system is a 3GPP LTE system, i) subframes 0, 1, 5, 6, ii when operating in TDD mode subframes 0, 4, 5, 9 when operating in FDD mode MBSFN It cannot be set as a subframe. This is because it is a subframe that transmits a main control signal such as a synchronization signal (eg, primary synchronization signal and secondary synchronization signal) to the terminal.

6 shows a structure of an uplink subframe.

Referring to FIG. 6, an uplink subframe may be divided into a control region and a data region in the frequency domain. The control region is allocated a Physical Uplink Control Channel (PUCCH) for transmitting uplink control information. The data region is allocated a physical uplink shared channel (PUSCH) for transmitting data.

PUCCH for one UE is allocated to an RB pair in a subframe. Resource blocks belonging to a resource block pair occupy different subcarriers in each of the first slot and the second slot. The frequency occupied by the resource block belonging to the resource block pair allocated to the PUCCH is changed based on a slot boundary. This is called that the RB pair allocated to the PUCCH is frequency-hopped at the slot boundary. The terminal may obtain a frequency diversity gain by transmitting uplink control information through different subcarriers over time. m is a location index indicating a logical frequency domain location of a resource block pair allocated to a PUCCH in a subframe.

The uplink control information transmitted on the PUCCH includes a hybrid automatic repeat request (HARQ) acknowledgment (ACK) / non-acknowledgement (NACK), a channel quality indicator (CQI) indicating a downlink channel state, and an SR that is an uplink radio resource allocation request. (Scheduling Request).

PUSCH is mapped to an uplink shared channel (UL-SCH) which is a transport channel. The uplink data transmitted on the PUSCH may be a transport block which is a data block for the UL-SCH transmitted during the TTI. The transport block may be user information. Alternatively, the uplink data may be multiplexed data. The multiplexed data may be a multiplexed transport block and control information for the UL-SCH. For example, control information multiplexed with data may include CQI, PMI (Precoding Matrix Indicator), HARQ, RI (Rank Indicator), and the like. Alternatively, the uplink data may consist of control information only.

On the other hand, cross-carrier scheduling is a resource allocation of a PDSCH transmitted through another component carrier through a PDCCH transmitted through a specific component carrier or another component other than the component carrier basically linked with the specific component carrier. A scheduling method for resource allocation of a PUSCH transmitted through a carrier. That is, the PDCCH and the PDSCH may be transmitted on different DL CCs, and the PUSCH may be transmitted on another UL CC other than the UL CC linked to the DL CC on which the PDCCH including the UL grant is transmitted.

When performing cross-carrier scheduling, the UE can receive scheduling information (UL grant, etc.) only through a specific serving cell (or CC). Hereinafter, a serving cell (or CC) for cross-carrier scheduling is called an ordering serving cell (or CC), and another serving cell (or CC) scheduled by the ordering serving cell (or CC) is following. It is called a serving cell (or CC). The ordering serving cell may be referred to as a scheduling cell, and the following serving cell refers to a cell that receives information on a scheduling cell through an RRC signal. The ordering serving cell and the following serving cell used below may mean an ordering CC and a following CC, respectively.

As such, in a system supporting cross-carrier scheduling, a carrier indicator indicating a DL CC / UL CC through which a PDSCH / PUSCH for which PDCCH provides control information is transmitted is required. A field including such a carrier indicator is hereinafter called a carrier indication field (CIF).

The aforementioned cross carrier scheduling can be classified into downlink cross-carrier scheduling and uplink cross-carrier scheduling. Downlink cross-carrier scheduling means a case in which a component carrier on which a PDCCH including resource allocation information and other information for PDSCH transmission is transmitted is different from a component carrier on which a PDSCH is transmitted. Uplink cross-carrier scheduling means a case in which a component carrier on which a PDCCH including a UL grant for PUSCH transmission is transmitted is different from a DL component carrier linked to a UL component carrier on which a PUSCH is transmitted.

When the same TDD configuration is applied to all of the serving cells in the carrier aggregation situation, the PUSCH timing transmitted by the primary serving cell and the PUSCH timing transmitted by the secondary serving cell are the same. However, it is possible to enable efficient data traffic control through flexible TDD configuration between each serving cell. When independent TDD configuration is applied to each serving cell and cross-carrier scheduling is applied, if the existing PUSCH timing is used, resources may be wasted and the system may operate unstable. Therefore, a specific scheme for UL HARQ timing is required. Here, the UL HARQ timing includes timing of transmitting PHICH as well as timing of transmitting PUSCH. In this case, the main serving cell and the secondary serving cell may exist in different frequency bands (Inter-band) or may exist in the same frequency band (Intra-band).

Table 4 below relates to the exponent k value indicating the PUSCH timing considered in the current TDD. Here, k is an offset of a subframe in which the UE transmits the PUSCH corresponding to the PDCCH after DL subframe n in which the UE receives the PDCCH. That is, the PUSCH is transmitted after k subframes. For example, when the TDD UL / DL configuration is "0", when the UE receives the PDCCH in subframe # 0, the UE transmits the PUSCH corresponding to the PDCCH in subframe # 4. The TDD UL / DL configuration is hereinafter referred to as TDD configuration.

Table 4 TDD UL / DL Settings Subframe number n 0 One 2 3 4 5 6 7 8 9 0 4 6 4 6 One 6 4 6 4 2 4 4 3 4 4 4 4 4 4 5 4 6 7 7 7 7 5

Table 5 below relates to an index k _PHICH indicating the PHICH timing considered in the current TDD. Here, k _PHICH means transmitting the _PHICH in subframe # n + k _PHICH after subframe #n which is a UL subframe. For example, in case of TDD configuration 0, subframe # 2 transmits a PHICH in subframe # 6.

Table 5 TDD UL / DL Settings Subframe index n 0 One 2 3 4 5 6 7 8 9 0 4 7 6 4 7 6 One 4 6 4 6 2 6 6 3 6 6 6 4 6 6 5 6 6 4 6 6 4 7

On the other hand, the UL HARQ, when the base station transmits the UL grant, which is PUSCH scheduling information to the terminal through the PDCCH, the terminal transmits PUSCH data at a predetermined timing and the ACK / NACK for this uplink grant and / or The process of transmitting through the PHICH is a process of repeating for a predetermined period until receiving the ACK signal from the base station.

Alternatively, when a UE receives UL grant information through a random access response (RAR) from a base station in a random access process, a UL HARQ process may be performed.

In the LTE system, UL HARQ is referred to as synchronous UL HARQ transmitted at a predetermined timing.

7 shows a UL HARQ process. UL HARQ when the TDD setting of the serving cell is 0.

Referring to FIG. 7, when the base station transmits ACK / NACK to the terminal through the PHICH, only the ACK / NACK is transmitted except for the UL grant. When performing cross-carrier scheduling, the following serving cells are scheduled to transmit ACK / NACK information (ie, transmit PHICH) except for the UL grant (ie, do not transmit the PDCCH).

8 shows an adaptive UL HARQ process. When the TDD setting of the serving cell is 0, it indicates an adaptive UL HARQ.

Referring to FIG. 8, the adaptive UL HARQ also transmits UL grant information (resource allocation related information, etc.) through the PDCCH at PHICH timing. When performing adaptive UL HARQ when performing cross-carrier scheduling, the base station transmits the PHICH to the terminal through the following serving cell, and at the same timing, the base station transmits the PDCCH to the terminal through the ordering serving cell.

Now, as an example of the method of transmitting uplink control information according to the present invention (Embodiment 1), a method of transmitting data by configuring synchronous UL HARQ timing of the following serving cell will be described. PUSCH scheduling for a following serving cell in an ordering serving cell using cross-carrier scheduling. The present invention relates to a method for configuring an appropriate UL HARQ timing when a TDD configuration of an ordering serving cell and a following serving cell is different.

However, flexible PH UL HARQ scheduling is possible when the PHICH transmission for the following serving cell can be performed in the ordering serving cell, whereas adaptive PH HAR transmission for the following serving cell is not possible in the ordering serving cell. The case of UL HARQ scheduling is limited. Hereinafter, a method of configuring the synchronous UL HARQ timing by distinguishing these two cases will be described.

<Synchronous UL HARQ Timing Method of Following Serving Cell When PHICH Transmission to Following Serving Cell Is Available in Ordering Serving Cell (Example 1-1)>

When the PHICH for the following serving cell can be transmitted through the ordering serving cell, the terminal receives both the UL grant and the PHICH from the base station through the ordering serving cell. However, if the PHICH timing of the following serving cell transmitted from the ordering serving cell is the same as the DL transmission timing of the following serving cell, the PHICH may be transmitted through the following serving cell at this timing.

If the DL transmission timing of the ordering serving cell includes the DL transmission timing of the following serving cell, the PUSCH transmission timing and the PHICH transmission timing depend on the transmission timing of the following serving cell. For example, if the ordering serving cell is TDD configuration 1 and the following serving cell is TDD configuration 0, referring to Table 3 above, if the ordering serving cell is TDD configuration 1, the DL subframe is subframe # 0, the subframe. When subframe # 4, subframe # 4, subframe # 5, subframe # 6, subframe # 9, and the following serving cell is TDD configuration 0, the DL subframe is subframe # 0, subframe # 1, subframe # 5, subframe # 6. Accordingly, the PUSCH transmission timing and the PHICH transmission timing are configured with at least one of subframe # 0, subframe # 1, subframe # 5, and subframe # 6 which are DL transmission timings of the following serving cell.

Such a configuration is not possible when the DL timing of the ordering serving cell does not include the DL timing of the following serving cell (for example, when the ordering serving cell is TDD configuration 3 and the following serving cell is TDD configuration 1). . Accordingly, the present invention describes a method of configuring the optimized PUSCH timing and PHICH timing for the case where the DL timing of the ordering serving cell does not include the DL timing of the following serving cell.

9 is a flowchart illustrating an optimized PUSCH scheduling method (or UL HARQ timing configuration method) according to the present invention. According to the PUSCH scheduling method (or UL HARQ timing configuration method) for each TDD configuration, a PUSCH time table (UL HARQ time table) may be configured and used. The PUSCH time table may be configured by the base station and transmitted to the terminal, and then the terminal may transmit the PUSCH based on the PUSCH time table, and the terminal itself may configure the PUSCH time table and transmit the PUSCH based on this. Similarly, the base station may configure the HARQ time table and transmit HARQ to the terminal based on the base station. After the terminal configures and transmits the HARQ time table to the base station, the base station may transmit the HARQ based on the HARQ time table. Therefore, the subject of the PUSCH configuration method or HARQ configuration method described below may be a terminal or a base station. In addition, transmitting the HARQ and transmitting the PHICH have the same meaning. Hereinafter, the PHICH is expressed as transmitting the PHICH.

First, when performing cross-carrier scheduling, in PUSCH scheduling for a following serving cell, scheduling information such as a UL grant and a position (k _PHICH value) of transmitting a _PHICH are defined as positions of DL subframes of an ordering serving cell. However, (S900), the location of the DL subframe of the following serving cell (except for the DL subframe transmitting PDCCH) and the UL subframe is defined based on the TDD configuration information of the following serving cell (S905). That is, the DL subframe and the UL subframe can be scheduled for the following serving cell at the same timing. In particular, in the ordering serving cell, the PHICH may be transmitted in the following serving cell when the base serving cell also has the DL subframe timing at the timing of the DL subframe in which the base station transmits the PHICH to the terminal. It can be applied when the load of the PHICH of the ordering serving cell is full.

The DL subframe (k value) corresponding to the PUSCH timing is configured to always transmit the UL grant (S910).

The PHICH timing is configured to be at least 4 ms after receiving the PUSCH data, and the PUSCH timing is configured to be at least 4 ms after receiving the UL grant (S920). That is, in Table 4, the k _PHICH value (PHICH timing) is configured to be always greater than or equal to 4, and in Table 3, the k value (PUSCH timing) is configured to be always greater than or equal to 4.

All UL subframes are configured to transmit UL grants or PHICHs one-to-one to other DL subframes (S930).

If at least one sum of k and k _PHICH values satisfying the conditions of steps S900 to S930 for the UL subframe of each following serving cell is present, k and k _PHICHs are configured to be minimum values (S940).

In addition, k and k _PHICH is configured so that HARQ RTT (Round Trip Time) has a value between a minimum of 10ms and a maximum of 16ms (S945), and the sum of all k values and all k _PHICH values is configured to be a minimum value (S946). . In other words, min (sum [total (k + k _PHICH )]) is obtained. In particular, when at least one configuration of k and k _PHICH values having the same value of min (sum [total (k + k _PHICH )]) in step S946 exists, the k or k _PHICH values may be equal to or less than 7, respectively. It is configured to be a value (S947). For example, if k and k _PHICH values for two UL subframes are configured to have 6 and 8, or k and k _PHICH values are configured to have 7 and 7, respectively, k is possible. Value and k _PHICH value consist of 7 and 7, respectively.

In addition, when at least one configuration having the same value of min (sum [total (k + k _PHICH )]) exists, the k value is configured to have a value smaller than the k _PHICH value if possible (S948). For example, if a k value and a k _PHICH value are configured to have 4 and 6, and a k value and k _PHICH value are configured to have 6 and 4, respectively, the k and k _PHICH values may be 4 and 6, respectively. Follow the instructions for configuring to have 6.

Optionally, in case of transmitting scheduling information for the following serving cell or ACK / NACK information through each DL subframe in the ordering serving cell, the UL grant or PHICH is transmitted or the UL grant and PHICH (ACK / NACK) are transmitted. It may be configured to transmit at the same time (S950). However, step S950 is not an essential component.

PHICH timing for successive UL subframes is configured sequentially (S960).

10 illustrates an example of applying a configuration method of PUSCH timing or PHICH timing according to the present invention. The PUSCH timing configuration method according to the present invention is applied when the ordering serving cell is TDD configuration 3 and the following serving cell is TDD configuration 1.

Referring to FIG. 10, it is checked whether the base station can transmit UL grant information through subframes of the ordering serving cell corresponding to 4 ms before for each UL subframe of the following serving cell.

The UL grant may be transmitted in subframe # 8 and subframe # 9 of the ordering serving cell, which is exactly 4 ms before, for subframe # 2 and subframe # 3 among the UL subframes of the following serving cell. However, since subframe # 3 and subframe # 4, which are exactly 4 ms before for subframe # 7 and subframe # 8 of the following serving cell, are UL subframes in the ordering serving cell, UL grants transmitted in DL subframes are not included. Could not send Therefore, the optimal k value is configured such that the k value for each UL subframe of the following serving cell is greater than four. The DL subframe of the nearest ordering serving cell is found to form an optimal k value. According to the optimal k value, the DL subframe of the ordering serving cell capable of transmitting the UL grant is composed of subframe # 0, subframe # 1, subframe # 8, and subframe # 9.

Subsequently, the k _PHICH value is determined after the k value is determined. It may be configured by applying the steps S910 to S930 of FIG.

In step S910, since the UL grant should always be transmitted at the PHICH timing, the DL subframe of the ordering serving cell capable of transmitting the PHICH is one of subframe # 0, subframe # 1, subframe # 8, and subframe # 9. Accordingly, the PHICH may be transmitted after 12 ms with respect to UL subframe # 8 of the following serving cell.

By the way, when configuring the k _PHICH to transmit the PHICH after 12ms, k or k _PHICH value is preferably configured to have a different value of k and k _PHICH value if possible, can not be configured such that a value of seven or less, respectively. Therefore, if a subframe of 7 ms or less is found with respect to subframe # 8 of the following serving cell, subframe # 5 is configured instead of subframe # 8 of the ordering serving cell. For this purpose, if the k value and the k _PHICH are modified, the modified k and the modified k _PHICH may be configured as shown in FIG. 10. According to the modified k and the modified k _PHICH , all the steps of FIG. 9 are satisfied.

On the other hand, if the k value and k _PHICH value that satisfies all the steps of FIG. 9 cannot be configured, or if at least one of steps S930, S945, S947, S948, and S960 of the steps of FIG. 9 cannot be applied, Another PUSCH timing configuration method (or UL HARQ timing configuration method) may be applied.

11 is a flowchart illustrating another PUSCH timing configuration method or a UL HARQ timing configuration method according to the present invention. 11A and 11B are structures in which “A” is connected to FIGS. 11A and 11B in a portion indicated by “A”, and step S1140 of FIG. 11B is performed after step S1130 of FIG. 11A.

First, S1100 to S1120 are performed similarly to steps S900 to S920 of FIG. 9.

In detail, when performing cross-carrier scheduling, in PUSCH scheduling for a following serving cell, scheduling information such as an UL grant and a location of a subframe transmitting PHICH are defined as a location of a DL subframe of an ordering serving cell (S1100). ), The location of the DL subframe of the following serving cell (except for the DL subframe transmitting PDCCH) and the UL subframe is defined based on the TDD configuration information of the following serving cell (S1105).

In particular, in the ordering serving cell, when the base station transmits the PHICH to the UE at the timing of the DL subframe, even in the following serving cell, the PHICH may be transmitted in the following serving cell. It can be applied when the load of the PHICH of the ordering serving cell is full.

The DL subframe corresponding to the PHICH timing is configured to always transmit the UL grant (S1110).

The PHICH timing should be at least 4 ms after receiving the PUSCH data, and the PUSCH timing should be transmitted at least 4 ms after receiving the UL grant (S1120). That is, in Table 4, the k _PHICH value is always configured to be greater than or equal to 4, and in Table 3, the k value is configured to be always greater than or equal to 4.

If at least one sum of k values and k _PHICH values satisfying steps S1100 to S1120 exists, a k value and a k _PHICH value are configured to have a minimum value (S1130).

Subsequently, it is determined whether the number of UL subframes of the following serving cell is greater than the number of DL subframes of the ordering serving cell (S1140), and the number of DL subframes of the following serving cell is the number of DL subframes of the ordering serving cell. If more, the base station performs PUSCH scheduling using the UL index when transmitting scheduling information for the following serving cell through the ordering serving cell (S1145). For example, when the TDD configuration 0 and the TDD configuration 6 are related to the ordering serving cell and the following serving cell, or the following serving cell and the ordering serving cell, PUSCH scheduling may be performed using a new UL index. In this case, a method of scheduling the PUSCH using the "new UL index" will be described below.

Meanwhile, when the number of UL subframes of the following serving cell is not greater than the number of DL subframes of the ordering serving cell in step S1140 (for example, the ordering serving cell is TDD configuration 0 and the following serving cell is TDD configuration). 3 or TDD setting 4), it is determined whether up to 20 TDD HARQ RTTs can be configured (S1150).

When up to 20 TDD HARQ RTTs can be configured, k values and k _PHICH values are configured according to steps S946 to S960 in FIG. 9.

That is, the sum of all k values and all k _PHICH values is configured to be the minimum value (S1151). That is, min (sum [total (k + k _PHICH )]) is calculated. In particular, when at least one configuration of k and k _PHICH values having the same value of min (sum [total (k + k _PHICH )]) exists, the k or k _PHICH value is configured to be 7 or less if possible. (S1152). In addition, when at least one configuration having the same value of min (sum [total (k + k _PHICH )]) exists, the k value is configured to have a value smaller than the k _PHICH value as much as possible (S1153). When the base station transmits scheduling information for the following serving cell or ACK / NACK information through each DL subframe within the ordering serving cell, the base station transmits a UL grant or PHICH or simultaneously transmits the UL grant and PHICH with the ACK / NACK. It may be configured to transmit (S1154). PHICH timing for successive UL subframes is configured sequentially (S1155).

Meanwhile, when up to 20 TDD HARQ RTTs cannot be configured and only up to 16 (S1197), k and k _PHICH values are set except for one UL subframe (S1160). In this case, the excluded one UL subframe may be excluded from the most suitable specific one UL subframe by comparing the configuration according to steps S940 to S948 of FIG. 9. Specifically, when the UL subframe does not satisfy the steps S940 to S948 or the UL subframe that satisfies the steps S940 to S948 but excludes one UL subframe, the sum of all k values and all k _PHICH values is the minimum value in step S946. The one UL subframe may be excluded.

When there are two or more DL subframes of the ordering serving cell capable of transmitting UL grant while satisfying the corresponding RTT condition (for example, when the ordering serving cell is TDD configuration 0 and the following serving cell is TDD configuration 3), PUSCH scheduling using the UL index (S1170).

On the other hand, when there is one DL subframe of the ordering serving cell of the ordering serving cell capable of transmitting the UL grant while satisfying the RTT condition (for example, the ordering serving cell is TDD configuration 0 and the following serving cell is TDD configuration 4). In case of), UL subframe # 3 of the following serving cell cannot be PUSCH scheduled. This is because the new UL index can be used only when there are two or more DL subframes capable of transmitting UL grants.

Meanwhile, the k _PHICH value, which is the PHICH timing for the UL subframe that cannot perform PUSCH scheduling using the k value, is always configured to 7 (S1180).

Now, a method of PUSCH scheduling using the "new UL index" will be described. When the number of UL subframes of the following serving cell is larger than the number of DL subframes of the ordering serving cell using the new UL index, all UL subframes may be scheduled with a small number of DL subframes. This is because there is only one DL subframe in which the PHICH is transmitted for each UL subframe, so the PHICH timing is overlapped. In addition, PHICH timings for UL subframes in one frame (eg, 10 ms) are required to be different from each other, since the number of DL subframes is smaller than the number of UL subframes. That is, the k _PHICH value for each UL subframe may be the same, but since the position of the UL subframe is different, the actual PHICH timing is different.

By using the UL index, it is possible to solve the problem of PHICH timing and resource collision for each of the fixed ULs while scheduling a larger number of UL subframes. The UL index is transmitted on the PDCCH and may be configured with 2 bits in DCI format 0/4 capable of transmitting UL grant information.

First, a method of PUSCH scheduling using a general UL index will be described. The UL index is used only in TDD setting 0. According to the present invention, a PUSCH scheduling method using a new UL index is an invention that applies a PUSCH scheduling method using a general UL index.

Consider I _PHICH simultaneously when using the UL index. I _PHICH is 1 when the PUSCH is transmitted in subframe # 4 or subframe # 9 for TDD configuration 0, and has a value of 0 otherwise.

When the MSB (Most Significant Bit) of the UL index is 1 or the I _PHICH value is 0, when the subframe in which the PHICH is transmitted is subframe # 0 or subframe # 5, the PUSCH timing is subframe #n (ACK / NACK or Subframe receiving the UL grant) + k.

Specifically, when the I _PHICH value is 0 and the subframe where the PHICH is transmitted is subframe # 0, the PUSCH timing is subframe # 4 (condition 1). In addition, when the I _PHICH value is 0 and the subframe in which the PHICH is transmitted is subframe # 5, the PUSCH timing is subframe # 9 (condition 2).

In addition, when the LSB (Least Significant Bit) of the UL index is 1 or the I _PHICH value is 1 (when the subframe in which the PUSCH is transmitted is subframe # 4 or subframe # 9), the subframe in which the PHICH is transmitted is If the frame # 0 or the subframe # 5 or the subframe where the PHICH is transmitted is the subframe # 1 or the subframe # 6, the PUSCH timing is subframe #n (DL subframe with ACK / NACK or UL grant) + 7.

Specifically, when the subframe in which the PUSCH is transmitted is subframe # 4, when the subframe in which the PHICH is transmitted is the subframe # 0, the PUSCH timing is subframe # 7 (condition 3), and the subframe in which the PHICH is transmitted is In the case of subframe # 1, the PUSCH timing is subframe # 8 (condition 4). In addition, when the subframe in which the PUSCH is transmitted is subframe # 9, when the subframe in which the PHICH is transmitted is 5, the PUSCH timing is subframe # 2 (condition 5), and the subframe in which the PHICH is transmitted is the subframe # 6. In this case, the PUSCH timing is subframe # 3 (condition 6).

If the MSB and LSB of the UL index are both 1, the PUSCH timing is subframe # n + k and subframe # n + 7 (condition 7). When the TDD setting of the serving cell is 0, PUSCH timing may be configured by using the condition 1 to condition 7 and the UL index 2 bits (MSB and LSB).

Now, a method of scheduling a PUSCH using a new UL index when the following serving cell is not TDD configuration 0 (that is, TDD configuration 1 to TDD configuration 6) will be described.

A method of scheduling a PUSCH using a new UL index is a combination of conditions 1 to 7 of a method of scheduling a PUSCH using a general UL index and some of conditions for scheduling a PUSCH using MSBs and LSBs of a general UL index. You can make

If the PUSCH scheduling for subframe # 2, subframe # 3, subframe # 4, subframe # 7, subframe # 8, and subframe # 9 that can be used as the UL subframe in the TDD configuration is not possible, a new UL index Some of the above conditions 1 to 7 are applied to schedule the PUSCH using.

For example, to schedule the UL subframe # 4, among the conditions for scheduling the PUSCH using the existing general UL index, "MSB is 1 or I _PHICH value is 0 and the subframe where PHICH is transmitted is subframe # 0. In this case, the PUSCH timing is subframe # 4 "

At this time, even if the corresponding UL subframe can be scheduled, the condition (condition 3 and condition) when I _PHICH is 1 (when the subframe receiving the PUSCH is # 4 or # 9) among the conditions 1 to 7 If 5) is applicable, apply those conditions to use the new UL index. In this case, if condition 3 can be applied, condition 1 is also applied, and if condition 5 is applicable, condition 2 is also applied.

As another example, in a method of scheduling a PUSCH using an existing general UL index, “When I _PHICH is 1 (the subframe in which the PUSCH is transmitted is the subframe # 4), the subframe in which the PHICH is transmitted is the subframe #. Case 0 is present, and subframe # 7 of the following serving cell is configured as a UL subframe ”, condition 1 as well as condition 1 apply to a method of scheduling a PUSCH using a new UL index.

As another example, in a method of scheduling a PUSCH using a conventional UL index, “When I _PHICH is 1 (the subframe in which the PUSCH is transmitted is the subframe # 9), the subframe in which the PHICH is transmitted is the subframe # 5. Is present, and subframe # 2 of the following serving cell is configured with UL ", condition 2 as well as condition 2 apply to a method of scheduling a PUSCH using a new UL index.

In this case, I _PHICH may be newly defined in the new UL index. The meaning of I _PHICH may be newly defined using only a condition used in a method of scheduling a PUSCH using a new UL index. For example, when the PUSCH scheduling is performed using the new UL index, the PUSCH timing is subframe # when the subframe where the PUSCH is transmitted is subframe # 4 and the subframe where the PHICH is transmitted is subframe # 0. If it can be set to 7 (condition 3), and at the same time, and only applies a condition (condition 1) that allows PUSCH timing to subframe # 4 when the subframe in which the PHICH is transmitted is subframe # 0, I _PHICH corresponds to In the TDD configuration corresponding to the TDD configuration of the following serving cell, the PUSCH transmission timing is 1 when the subframe # 4 is defined and 0 otherwise.

In addition, among the methods of scheduling a PUSCH using a general UL index, when the MSB or LSB is 1 (except when both the MBS and LSB are 1), the condition is unconditional to the method of scheduling the PUSCH using the new UL index. Apply. For example, when the MSB is 1, the PUSCH timing is subframe #n (the subframe receiving the ACK / NACK or UL grant) + k, and when the LSB is 1, the PUSCH timing is subframe # n + 7. The condition is always applied.

In addition, the condition (condition 7) when both MSB and LSB are 1 is applied only when the number of UL subframes of the following serving cell is larger than the number of DL subframes of the ordering serving cell. As an example, when the ordering serving cell is TDD configuration 0 and the following serving cell is TDD configuration 6, condition 7 is applied by a method of PUSCH scheduling using a new UL index.

12 shows an example of applying another PUSCH configuration method according to the present invention. The ordering serving cell is TDD configuration 0, the following serving cell is TDD configuration 3, and the TDD HARQ RTT cannot be set from 10 ms to 16 ms. 11, the number of UL subframes of the following serving cell is not greater than the number of DL subframes of the ordering serving cell in step S1140 of FIG. 11.

Referring to FIG. 12, if HARQ RTT can be configured up to 20, it is checked whether PUSCH scheduling can be performed in the DL subframe of the ordering serving cell 4ms before each UL subframe of the following serving cell. For subframe # 2 and subframe # 3, which are UL subframes of the following serving cell, the subframe corresponding to the timing before 4ms is not the D subframe in the ordering serving cell, so the value k is made larger. The first k value of 12 is shown.

Next, the k _PHICH value is determined. The optimal value of the k _PHICH value configured to transmit the UL grant in the DL subframe corresponding to the PHICH timing is shown in the first k _PHICH value in FIG. 12. It can be seen that the HARQ RTT is 18 at most.

On the other hand, if HARQ RTT is possible only up to 16, as described above with reference to FIG. 11, after excluding one UL subframe, a new k-th value and a new k-th _PHICH value should be configured, and the PUSCH is scheduled using the new UL index. do.

First, it is determined which UL subframe to schedule using the new UL index. When one UL subframe is excluded, the specific one UL subframe most appropriate may be excluded by comparing the configuration according to steps S940 to S948 of FIG. 9. Specifically, when the UL subframe does not satisfy the steps S940 to S948 or the UL subframe that satisfies the steps S940 to S948 but excludes one UL subframe, the sum of all k values and all k _PHICH values is the minimum value in step S946. The one UL subframe may be excluded.

configured such that the sum of k values and k _PHICH value is minimized and, k value such that the minimum total sum of k _PHICH, and k and k _PHICH is configured such that each of 7 or less, and k is configured to be smaller than k _PHICH k value and k value were _PHICH is equal to the value 2 k and 2 k the value of _PHICH 12, wherein the UL sub-frame to be excluded is determined as the sub-frame # 3.

When configured with the second k value and the second k _PHICH , PUSCH scheduling for UL subframe # 3 is impossible. In this case, the UL index may be used to schedule the UL subframe # 3. According to the UL index construction method described above, the meaning of the UL index can be used as follows.

If the MSB of the UL index is 1, the PUSCH timing is subframe # n + k.

If the LSB of the UL index is 1 or the PHICH is transmitted in subframe # 6, the PUSCH timing is subframe # n + 7.

The k _PHICH value, which is the PHICH timing for UL subframe # 3 that cannot be scheduled using only the k value, is set to 7.

Accordingly, the k value and the k _PHICH value when HARQ RTT is possible up to 16 may be configured with the third k value and the third k _PHICH value of FIG. 12.

13 illustrates subframe scheduling according to the present invention. Specifically, it indicates a PUSCH scheduled subframe and a subframe that transmits an UL grant or PHICH.

Referring to FIG. 13, it can be seen that PUSCH retransmission scheduling is possible in UL subframe # 3 in a second HARQ process.

Now, an example of the PUSCH time table (k value) applied by the PUSCH timing configuration method according to the present invention will be described for each TDD setting (TDD setting 0 to TDD setting 6) used by the ordering serving cell, and HARQ timing according to the present invention. An example of the HARQ time table k _PHICH to which the configuration method is applied will be described.

Table 6 below shows k values when the ordering CC uses the TDD setting 0.

Table 6 TDD UL / DL Settings Subframe index n 0 One 2 3 4 5 6 7 8 9 Ordering CC: 0 4 6 4 6 One 7 7 7 7 2 6 6 3 4 of 4 7 / D 6.7 4 7 / D 6.7 5 6 6 4 6 7 7

Table 7 below shows the k _PHICH value when the ordering CC uses the TDD setting 0.

TABLE 7 TDD UL / DL Settings Subframe index n 0 One 2 3 4 5 6 7 8 9 0 4 7 6 4 7 6 One 4 7 4 7 2 4 4 3 4 of 4 7/7 6.11 4 4 of 4 12 / - 5 4 6 4 7 6 4 7

Referring to Tables 6 and 7, the TDD HARQ RTT can be configured for up to 16 TDD HARQ RTTs up to 16. If the TDD HARQ RTT is configurable up to 20, the TDD HARQ RTT can be configured up to 20. It was.

If the following serving cell is TDD configuration 3 and TDD HARQ RTT is configurable up to 16, if MSB of UL index is 1, server frame # n + k is PUSCH timing, ULB of LSB is 1 or PHICH is subframe # When transmitted in 6, subframe # n + 7 is PUSCH timing.

When the following serving cell is TDD set to 6, there is a special situation in which one DL subframe is shorter than before. In this case, the UL index may be used as follows.

When the MSB of the UL index is 1 or the I _PHICH is 0, when the PHICH transmitted subframe is the subframe # 0, the subframe # n + k is the PUSCH timing.

When the LSB of the UL index is 1 or the I _PHICH is 1, when the subframe in which the PHICH is transmitted is subframe # 0 or the subframe in which the PHICH is transmitted is subframe # 1, subframe # n + 7 is the PUSCH timing. .

When the MSB is 1 and the LSB is 1, subframe # n + 7 and subframe # n + k are PUSCH timings.

For TDD configuration 6, I _PHICH has a value of 1 when the PUSCH transmission is scheduled in subframe # 4 and 0 otherwise.

Table 8 below shows k values when the ordering CC uses TDD setting 1.

Table 8 TDD UL / DL Settings Subframe index n 0 One 2 3 4 5 6 7 8 9 Ordering CC: 1 6 4 6 4 0 4 6 4 4 6 4 2 6 6 3 4 6 4 4 6 4 5 6 6 4 6 4 6 4

Table 9 below shows the k _PHICH value when the ordering CC uses TDD setting 1.

Table 9 TDD UL / DL Settings Subframe index n 0 One 2 3 4 5 6 7 8 9 0 4 6 6 4 6 6 Ordering CC: 1 4 6 4 6 2 4 4 3 4 6 6 4 4 6 5 4 6 4 6 6 4 6

Table 10 below shows k values when the ordering CC uses TDD setting 2.

Table 10 TDD UL / DL Settings Subframe index n 0 One 2 3 4 5 6 7 8 9 Ordering CC: 2 4 4 0 4 4 4 4 4 4 One 6 4 6 4 3 4 4 4 4 4 4 5 4 6 4 6 4 6 4

Table 11 below shows the k _PHICH value when the ordering CC uses TDD configuration 2.

Table 11 TDD UL / DL Settings Serverframe index n 0 One 2 3 4 5 6 7 8 9 0 6 6 6 6 6 6 One 4 6 4 6 2 6 6 3 6 6 6 4 6 6 5 6 6 4 6 6 4 6

Table 12 below shows k values when the ordering CC uses TDD configuration 3.

Table 12 TDD UL / DL Settings Subframe index n 0 One 2 3 4 5 6 7 8 9 Ordering CC: 3 4 4 4 0 4.7 6.7 4 of 4 6/6 5/5 5/5 One 7 7 7 4 2 6 S 4 4 4 4 5 4 6 7 7 7 5 5

Table 13 below shows a k _PHICH value when the ordering CC uses TDD configuration 3.

Table 13 TDD UL / DL Settings Subframe index n 0 One 2 3 4 5 6 7 8 9 0 4.7 7/7 6.7 4 of 4 7/7 6.7 One 7 7 4 7 2 6 4 3 6 6 6 4 6 6 5 6 6 5 5 6 4 7

In Table 12 and Table 13, the underlined parts are used in case of using the UL index, and are distinguished from the case in which the non-underlined general UL index is not used.

Table 14 below shows k values when the ordering CC uses TDD setting 4.

Table 14 TDD UL / DL Settings Subframe index n 0 One 2 3 4 5 6 7 8 9 Ordering CC: 4 4 4 0 4 6 4 4 6 4 One 6 4 6 4 2 6 4 3 4 4 4 5 4 6 4 6 4 6 4

Table 15 below shows the k _PHICH value when the ordering CC uses TDD setting 4.

Table 15 TDD UL / DL Settings Subframe index n 0 One 2 3 4 5 6 7 8 9 0 4 6 6 4 6 6 One 4 6 4 6 2 6 4 3 6 6 6 4 6 6 5 6 6 4 6 6 4 6

Table 16 below shows k values when the ordering CC uses TDD setting 5.

Table 16 TDD UL / DL Settings Subframe index n 0 One 2 3 4 5 6 7 8 9 Ordering CC: 5 4 0 4 6 4 4 6 4 One 6 4 6 4 2 4 4 3 4 4 4 4 6 4 6 4 6 4

Table 17 below shows the k _PHICH value when the ordering CC uses TDD setting 5.

Table 17 TDD UL / DL Settings Subframe index n 0 One 2 3 4 5 6 7 8 9 0 4 6 6 4 6 6 One 4 6 4 6 2 6 6 3 6 6 6 4 6 6 5 6 6 4 6 6 4 6

Table 18 below shows k values when the ordering CC uses TDD setting 6.

Table 18 TDD UL / DL Settings Subframe index n 0 One 2 3 4 5 6 7 8 9 Ordering CC: 6 7 7 7 7 5 0 4 6 4 6 One 7 7 7 7 2 6 4 3 4 4 4 4 4 4 5 4

Table 19 below shows the k _PHICH value when the ordering CC uses TDD configuration 6.

Table 19 TDD UL / DL Settings Subframe index n 0 One 2 3 4 5 6 7 8 9 0 4 7 6 4 7 6 One 4 7 4 7 2 6 4 3 6 6 6 4 6 6 5 6 6 4 6 6 4 7

<When the PHICH transmission of the following serving cell should be performed only by the following serving cell, a synchronous UL HARQ timing configuration method of the following serving cell (Example 1-2)>

In this case, the UL grant is transmitted from the ordering serving cell and the PHICH is transmitted from the following serving cell. Therefore, only the k value for the UL grant is newly configured, and the rest follows the k value and the k _PHICH value of the following serving cell.

14 is a flowchart illustrating another example of a method of configuring HARQ timing according to the present invention.

Referring to FIG. 14, when performing cross-carrier scheduling, a position of a subframe that transmits UL grant scheduling information in scheduling for a following serving cell is defined as a position of a DL subframe of an ordering serving cell (S1400). On the other hand, the positions of the DL subframe (but not the PDCCH) and the UL subframe of the following serving cell are defined based on the TDD configuration information of the following serving cell (S1405).

The timing of transmitting the UL grant is configured to be at least 4 ms before the UL subframe (S1410).

It is determined whether the number of UL subframes of the following serving cell is greater than the number of DL subframes of the ordering serving cell (S1420), and the number of UL subframes of the following serving cell is smaller than the number of DL subframes of the ordering serving cell. If it is equal to or the same, the UL grant is configured to be transmitted at different DL timings for all UL subframes (S1430).

When the number of UL subframes of the following serving cell is larger than the number of DL subframes of the ordering serving cell, UL grants may not be given at different DL timings for all UL subframes. In this case, at least all DL subframes of the ordering serving cell are configured to give UL grants for different UL timings of the following serving cells (S1440).

The sum of k values capable of transmitting the UL grant is configured to be the minimum (S1450).

In the UL HARQ process, the process except for transmitting the UL grant is configured according to the k value and the k _PHICH value of the following serving cell according to the configuration method of FIG. 9 or 11 (S1460). In this case, if the PHICH transmission timing in the following serving cell and the DL timing in the ordering serving cell are the same, adaptive UL HARQ may be limitedly performed only for the timing (S1470). Of course, it can be set differently for each base station.

The terminal and the base station may know the HARQ timing information of Table 4 and Table 5 in advance.

For example, the UE stores the HARQ timing information of Table 4 and Table 5 in advance in a memory, and may operate in a manner of using the information when necessary. The UE may know TDD configuration information of each serving cell through TDD configuration information (TDD-Config) transmitted through RRC signaling, and may know HARQ timing information of the corresponding serving cell based on this.

As another example, if a UE receives a NACK with a UL grant or PHICH at a specific timing, the PUSCH timing and the PUSCH timing for the corresponding UL grant or NACK based on HARQ timing information (k value or k _PHICH value table) known to the terminal. The PHICH timing information about may be known. In addition, if the base station also receives the PUSCH from the terminal at a specific timing, it can know the PHICH transmission timing information for the corresponding PUSCH.

When cross-carrier scheduling is configured through CrossCarrierSchedulingConfig information transmitted through RRC signaling, the HARQ timing information may be configured according to a table configured by the method of FIGS. 9 to 14.

An example of cross carrier scheduling information is shown in the following table.

Table 20

Here, cif-Presence indicates whether the CIF exists in the PDCCH DCI format (TRUE) or not (FALSE).

Pdsch-Start is the first OFDM symbol of the PDSCH for the following serving cell (or secondary serving cell), and 1,2,3 values can be applied when the dl_Bandwidth for the following serving cell is greater than 10 RB, and the following When dl-Bandwith for the serving cell is less than or equal to 10RB, 2,3,4 values may be applied.

schedulingCellId indicates whether a cell (meaning an ordering cell) signals a downlink allocation or an uplink grant when cross-carrier scheduling is applied to a considered serving cell (following cell).

The base station may transmit the PUSCH timing and the PHICH timing to the terminal through the PDCCH.

When the cross carrier scheduling is configured, the base station transmits the PDCCH for the following serving cell to the terminal through the ordering serving cell, where the PDCCH may include the PUSCH timing information transmitted by the terminal and the PHICH timing to be received by the terminal. . For example, the ULQ 2 bits may be used to command HARQ timing different from the HARQ timing information table. In this case, since the UE knows what the UL index constructed by the method of FIGS. 9 to 14 is used in the corresponding TDD configuration, the UE may know the PUSCH timing using only 2 bits.

Now, as another example of the method of transmitting uplink control information according to the present invention (Example 2), a method of configuring UL HARQ timing by performing cross-subframe scheduling in a TDD system to which eICIC is applied will be described. do.

First, two types of cross subframe scheduling may be applied to the present invention.

In a first type, there is a case where one UE performs PUSCH scheduling for two UL subframes having different UL grant information. In this case, since two uplink transmissions are scheduled by one UL grant information, the uplink transmissions have the same resource allocation information, PHICH resource information, demodulated reference signal (DM RS), cyclic shift information, and the like.

As a second type, one UE may perform PUSCH scheduling for two UL subframes in which two UL grant information are different from each other in one DL subframe. In this case, since one UL grant information schedules only one UL subframe, two different UL subframes have different UL grant information (PHICH resource, resource allocation, DMRS cyclic shift information, etc.).

In this case, in the case of the TDD configuration 0, the TDD configuration 1, and the TDD configuration 6, a subframe bundling operation may be performed. Subframe bundling refers to a TTI bundling configuration for subframe transmission.

Here, the TTI bundling is used to increase the UL coverage in the LTE system. For example, the same data having the same HARQ process number is transmitted on four consecutive UL subframes in four consecutive UL subframes. Can be.

When TTI bundling is used, additional signaling overhead can be avoided when retransmission occurs and the same data is transmitted in four consecutive subframes, thereby improving reliability of data transmission and UL coverage. It is also effective in time-sensitive traffic models such as VoIP.

Table 21 below relates to the index l representing the PHICH timing for the TTI bundled UL subframe. Subframe # n-l is the PHICH timing for four ULs that are TTI bundled.

Table 21 TDD UL / DL Settings Subframe number n 0 One 2 3 4 5 6 7 8 9 0 9 6 9 6 One 2 3 2 3 6 5 5 6 6 8

If TTI bundling in TDD configuration 0, TDD configuration 1, and TDD configuration 6 is set, after receiving UL grant through subframe #n, the sequence is continued from subframe # n + k using the k value of Table 4 above. PUSCH is transmitted in four UL subframes, and PHICH for four UL subframes TTI-bundled in subframe #nl is transmitted using the l value of Table 6 above.

Meanwhile, a method of allocating PHICH resources will be described.

Since the 3GPP LTE system does not support single user-multiple input multiple output (SU-MIMO) in the uplink, the PHICH carries a 1-bit ACK / NACK signal corresponding to the PUSCH for one UE.

The 1-bit ACK / NACK signal performs channel coding using repetition coding at a code rate 1/3. The ACK / NACK signal coded with a 3-bit codeword is generated by 12 BPSK symbols through BPSK modulation and mapped to three modulation symbols. The modulation symbols are spread using an orthogonal sequence of Spreading Factor (SF) N ^PHICH _SF . The number of orthogonal sequences used for spreading is twice that of N ^PHICH _SF to apply I / Q multiplexing. 2N _SF ^PHICH orthogonal 2N _SF ^PHICH of PHICH is spread by using the sequences are defined as one PHICH group. PHICHs belonging to the same PHICH group are distinguished through different orthogonal sequences. Spreaded symbols are hierarchically mapped according to rank. Hierarchically mapped symbols are mapped to resource elements, respectively.

The PHICH resource corresponding to the PUSCH is defined using a _{PRB_Physical} Resource Block (PRB) index I _{PRB_RA} of a resource used for the PUSCH and a cyclic shift n _DMRS of a 3-bit data demodulation reference signal field used for the PUSCH. The demodulation reference signal refers to a reference signal used for demodulation of data transmitted on the PUSCH.

In this case, I _{PRB_RA} is associated when the number of TBs indicated in the first TB (Transport Block) of the PUSCH associated with the PDCCH, or the most recent PDCCH associated with the PUSCH is not equal to the number of TBs known negatively. For the case where there is no PDCCH, it is defined as I ^lowest_index _{PRB_RA} . The second TB of the PUSCH associated with the PDCCH is defined as I ^lowest_index _{PRB_RA} +1.

The PHICH resource is known by an index pair (n ^group _PHICH , n ^seq _PHICH ), and is given by the following equation.

Equation 1

Here, "mod" denotes a modulo operation. n ^group _PHICH is a PHICH group number, and n ^seq _PHICH is an orthogonal sequence index in the PHICH group. I _PHICH is 1 when PUSCH transmission is made in subframe # 4 or subframe # 9 in TDD UL / DL configuration 0, and 0 otherwise.

n ^group _PHICH has a value between 0 and (N ^group _PHICH- 1), and the number of PHICH groups N ^group _PHICH is given by the following equation in the FDD system.

Equation 2

Here, N ^DL _RB is the total number of resource blocks in the downlink subframe and corresponds to the downlink bandwidth. PHICH resource N _g N {1/6, 1/2, 1, 2}, which is obtained from a master information block (MIB) on a physical broadcast channel (PBCH). The PHICH resource may be referred to as a parameter for obtaining the number of PHICH groups.

In a TDD system, N _PHICH ^group has a different number according to m _i · N _PHICH ^group by N _PHICH ^group according to m _i and the expression (2) according to the downlink subframe. Table 22 below shows the values of m _{i in} the TDD system.

Table 22 UL / DL Settings Subframe number i 0 One 2 3 4 5 6 7 8 9 0 2 One - - - 2 One - - - One 0 One - - One 0 One - - One 2 0 0 - One 0 0 0 - One 0 3 One 0 - - - 0 0 0 One One 4 0 0 - - 0 0 0 0 One One 5 0 0 - 0 0 0 0 0 One 0 6 One One - - - One One - - One

The MIB includes PHICH resource N _g which is resource allocation information for acquiring the resource region of the PHICH in the control region.

The reason why the resource allocation of the PHICH is included in the MIB is that the UE needs to know the resource region of the PHICH in order to receive the PDCCH. In the control region, the PDCCH is allocated in the region except for the resource region to which the PCFICH and PHICH are allocated. Since the MIB is cell-specific signaling, the N ^group _PHICH is cell specific information, and the n ^group _PHICH may be differently allocated according to the terminal.

Table 23 below shows an orthogonal sequence of _PHICHs for an orthogonal sequence index n ^seq _PHICHs .

Table 23 Sequence index Orthogonal Sequence n ^seq _PHICH Normal CPN ^PHICH _SF = 4 Extended CPN ^PHICH _SF = 2 0 [+1 +1 +1 +1] [+1 +1] One [+1 -1 +1 -1] [+1 -1] 2 [+1 +1 -1 -1] [+ j + j] 3 [+1 -1 -1 +1] [+ j -j] 4 [+ j + j + j + j] - 5 [+ j -j + j -j] - 6 [+ j + j -j -j] - 7 [+ j -j -j + j] -

Table 24 below relates to mapping of cyclic shifts of a DMRS field in a PDCCH of n _DMRS and UL DCI format 0/4.

Table 24 Cyclic Shift of DMRS Field in PDCCH of UL DCI Format 0/4 n _DMRS 000 0 001 One 010 2 011 3 100 4 101 5 110 6 111 7

Now, enhanced Inter Cell Interference Coordination (eICIC) will be described. eICIC is a method that can mitigate interference between multiple cells (eg, between a single macro cell and a pico cell or femto cell phase in a macro cell) in a hetero network situation. By controlling downlink transmission of the aggressor cell in units of time in inter-cell interference, the downlink of the aggregator cell base station in the inter-cell interference without performing a separate operation at the base station of the Victim cell. The influence of interference due to link transmission can be reduced.

In general, inter-cell interference coordination is a method for supporting a reliable communication to a user when a user belonging to a Victim cell is near an aggregator cell. In order to coordinate inter-cell interference, for example, a scheduler may be imposed on the use of certain time and / or frequency resources. It may also impose a constraint on the scheduler how much power to use for a particular time and / or frequency resource. In order to coordinate interference between adjacent cells, a downlink subframe pattern of cells may be configured.

Herein, the pattern of subframes refers to an arrangement of subframes repeated at regular periods. In this case, the pattern of the subframe may be composed of various subframes. For example, the pattern of the subframe may include an array of low interference subframes that generate less interference between cells, such as a normal subframe and an almost blank subframe (ABS) or a fake subframe. It can be configured repeatedly at regular intervals.

ABS refers to a subframe used to protect a resource that is interfered with by a strong cell. ABS reduces backward transmission power such as control information, data information, and signaling (signals transmitted for channel measurement and synchronization) and transmits backwards compatibility. For this purpose, only control information, data information, signaling, and system information necessary for the terminal can be transmitted. As an ABS, a MBSFN subframe may be used.

Fake subframe can be defined in two types.

In a first type, a DL subframe can be used as a fake UL subframe, where the fake UL subframe is a UL subframe that cannot transmit all signals that can be transmitted in UL. Similarly, a UL subframe can be used as a fake DL subframe, which is a DL subframe that cannot transmit all signals that can be transmitted to the DL. That is, the terminal determines that the fake UL subframe is a UL subframe but cannot operate as a UL subframe, and the terminal determines that the fake DL subframe is a DL subframe but cannot actually operate as a DL subframe.

As a second type, a DL subframe may be used as a fake UL subframe, and unlike the first type, a fake UL subframe may be defined to operate as a UL subframe. At this time, the fake UL subframe may transmit all signaling (SRS, PUCCH, PUSCH) and the like that can be transmitted to the UL. Similarly, when an UL subframe is used as a fake DL subframe, unlike the first type, the fake DL subframe may operate as a DL subframe. Again, the fake DL subframe can transmit all signaling (PHICH, PCFICH, CRS, PDCCh, PDSCH) that can be transmitted to the DL.

Hereinafter, a normal subframe means a subframe excluding an ABS or fake subframe.

In the present invention, the ABS pattern refers to a subframe pattern including an ABS or fake subframe.

In the TDD system, the ABS pattern may have a 20 ms period for the TDD settings 1 to TDD 5, a 70 ms period for the TDD setting 0, and a 60 ms period for the TDD setting 6.

15 shows an example of an ABS pattern in a TDD system to which the present invention is applied.

Referring to FIG. 15, subframe # 8 and subframe # of the aggregator cell (TDD configuration 3) in order to reduce interference with the UL subframe of subframe # 2 and subframe # 3 of the victor cell (TDD configuration 1). When the ABS or fake subframe is used in 9, PUSCH scheduling (UL grant transmission) cannot be performed in subframe # 8 and subframe # 9 of the aggregator cell. Because in the FDD system, since the UL grant can be given in all subframes, many subframes can transmit the UL grant even though the ABS cannot transmit the UL grant, whereas in the TDD system, the subframe capable of transmitting the UL grant is predetermined. In addition, since these subframes are engaged with UL scheduling timing, the number of subframes capable of transmitting UL grants may be reduced and UL resources may not be used when these subframes are used as ABS. Also, considering all these timings, the configuration of the ABS pattern is limited.

Meanwhile, the UE needs to know the ABS (or fake subframe) pattern in advance so that the UE can transmit the PUSCH at the PUSCH timing. There are two ways for the UE to know the ABS (or fake subframe) pattern.

First, the UE can know the ABS pattern through the measurement pattern information per ABS pattern period transmitted through the RRC signaling.

In the case where the measurement is made at the portion of bitmap information, the DL subframe is determined when the cell configuration information is determined. When the measurement pattern is 0, the subframe may be determined as ABS. Here, the bitmap information refers to the transmission of the subframePatternTDD information transmitted in Table 25 as a bit string.

When a subframe capable of receiving a UL grant is used as an ABS, the UE may receive a PUSCH scheduling in a subframe capable of substituting the ABS according to the present invention, and may proceed with UL HARQ based on this.

Table 25

Second, the ABS pattern can be known through the ABS / fake subframe pattern information transmitted through RRC signaling. The ABS / fake subframe pattern information may be transmitted through a bitmap, or may be transmitted as an ABS / fake pattern index value as shown in Table 11 including the ABS / fake subframe pattern information.

Alternatively, the information on the ABS pattern and the information on the fake subframe pattern may be transmitted separately. Each pattern information may be transmitted as a bitmap or as an index value as shown in Table 11 below.

Table 26 below shows the ABS / fake pattern index for the ABS / fake subframe pattern expressed as a bitmap. For 20ms period of TDD setting 1.

Table 26 ABS / Fake Subframe Pattern ABS / fake pattern index 11110111111111011111 0 11111111101111011111 One 11110111101111111110 2 11100111111111011111 3 11111111001111011110 4 11010111111101111110 5 11011111101111111110 6 11110111011111011110 7

If the bitmap is 0, it means ABS / fake subframe, and if 1, it means normal subframe.

Table 26 shows an example of expressing 3 bits with respect to TDD configuration 1 and may have different indices according to each TDD configuration.

In this case, the fake subframe pattern information may be implicitly known by the terminal according to the following method.

For example, a DL subframe capable of giving the first UL grant among the DL subframes after the subframe to which the cross subframe scheduling is applied may be recognized as a fake UL subframe.

However, if an ABS or fake subframe is used in a TDD system, if the ABS is a subframe capable of transmitting a PHICH or UL grant, the corresponding UL PUSCH cannot also be scheduled, resulting in twice the waste of resources. .

Now, in order to more flexibly allocate ABS and fake subframes and minimize the impact on the number of UL grants when configuring an ABS pattern in a TDD system according to the present invention, the subframe to which the UL grant is transmitted is ABS (or fake UL sub). Frame), when performing UL HARQ on behalf of this subframe, and cross-subframe scheduling when a subframe to which UL grant is to be transmitted is used as an ABS (or fake UL subframe). Next, a method of configuring UL HARQ timing will be described.

Here, the UL HARQ timing configuration method includes PUSCH scheduling and PHICH scheduling.

In addition, the following UL HARQ timing configuration method may be performed by a terminal or a base station, and since the terminal and the base station know the UL HRAQ timing information according to the present invention, the UL HARQ timing according to the present invention may be performed. Can be. The base station may also transmit UL HARQ timing information while transmitting UL grant information.

In this case, a case where PHICH can be transmitted in the ABS or fake UL subframe and a case where it is not is described will be described separately.

<When PHICH can be transmitted in an ABS or fake UL subframe (Example 2-1)>

In this case, since the ABS or fake UL subframe can transmit the PHICH, it is required to configure so that the UL grant of the ABS or fake UL subframe can be transmitted instead in the closest DL subframe.

16 is a flowchart illustrating an example of a method of configuring UL HARQ timing according to the present invention.

Referring to FIG. 16, it is determined whether there is a DL subframe available without transmitting a UL grant (S1600). That is, it is determined whether the number of DL subframes available without transmitting the PUSCH scheduling information among the normal DL subframes is greater than or equal to the number of ABSs (or fake UL subframes) that do not receive UL HARQ timing.

When there is a DL subframe that does not transmit an UL grant and there is an available DL subframe, the UL grant is not transmitted on behalf of the ABS or fake UL subframes and the UL grant is transmitted in the available normal DL subframe. At this time, UL HARQ timing is configured such that the UL HARQ RTT (Round Trip Time) is 10 or more and 16 or less (S1605).

The k value configures UL HARQ timing to be greater than or equal to 4 (S1610).

When two or more ABSs (or fake UL subframes) satisfying steps S1600 to S1610 exist, each ABS is configured to be replaced by a normal DL subframe that did not transmit different UL grants, UL HARQ timing is configured such that the sum of k values is minimum (S1615).

If two or more such DL subframes exist, the UL HARQ timing is configured to transmit the UL grant in the DL subframe in which the RTT is the minimum (S1620).

UL HARQ is performed based on the UL HARQ timing configured as described above (S1635).

If the UL grant is not transmitted in step S1600 and there are no available DL subframes, that is, the number of ABS (or fake UL subframes) is DL subframes available without transmitting PUSCH scheduling information among the normal DL subframes. If greater than the number, the UL HARQ timing is configured to perform cross-subframe scheduling in the nearest DL subframe of the previous DL subframe of the ABS (or fake UL subframe) (S1625). In particular, UL HARQ timing is configured to perform cross-subframe scheduling in a DL subframe capable of minimizing k value while allowing k value of 4 ms or more among DL subframes closest to the ABS or fake UL subframe (S1630). .

For example, a cross subframe scheduling indicator indicating whether cross subframe scheduling is performed in UL HARQ may be included in DCI format 0/4. The cross subframe scheduling indicator may be 1 bit, and in this case, 1 bit may be added to DCI format 0/4. When the indicator is 1, it may indicate that cross subframe scheduling is performed, and when 0, it may indicate that cross subframe scheduling is not performed. The opposite may be true.

As another example, the cross subframe scheduling indicator may be added to RRC signaling and may also be 1 bit. If the cross subframe scheduling indicator (1 bit) transmitted through RRC signaling is 1, it indicates that the cross subframe scheduling is performed, and the UE includes the cross subframe scheduling indicator in DCI format 0/4, so that DCI format 0/4 is included. It may be determined that the length of 1 is added by 1 bit, and the DCI format 0/4 may be decoded. On the other hand, if the cross subframe scheduling indicator 1 bit transmitted through RRC signaling is 0, it indicates that the cross subframe scheduling is not performed, and the UE interprets the length of DCI format 0/4 as the original length to DCI format 0 Can decode / 4 Of course, the opposite can also be true.

As described above, the UL HARQ is transmitted based on the UL HARQ timing configured using the cross subframe scheduling (S1635).

<When PHICH cannot be transmitted in an ABS or fake UL subframe (Example 2-2)>

In this case, it is required to configure the UL HARQ timing so that not only the UL grant timing but also the PHICH timing can be transmitted instead in the other DL subframe closest to the ABS or fake UL subframe.

17 is a flowchart illustrating another example of a method of configuring UL HARQ timing according to the present invention.

Referring to FIG. 17, it is determined whether there is an available DL subframe without transmitting the UL grant and the PHICH (S1700). That is, it is determined whether the number of DL subframes usable without transmitting PUSCH scheduling information and PHICH scheduling information among the normal DL subframes is greater than or equal to the number of ABS (or fake UL subframes).

If no UL grant and PHICH are transmitted and there is an available DL subframe (normal DL subframe), the UL grant and PHICH are not transmitted in the available normal DL subframe on behalf of the ABS or fake UL subframes To transmit. At this time, UL HARQ timing is configured so that the UL HARQ RTT is 10 or more and 16 or less (S1705).

The k value and the k _PHICH value configure UL HARQ timing to be greater than or equal to 4, respectively (S1710).

The UL HARQ timing is configured to transmit the UL grant in the DL subframe corresponding to the PHICH timing (S1715).

If at least one sum of k and k _PHICH values satisfying steps S1700 to S1715 exists, UL HARQ timing is configured to minimize RTT (S1720).

If two or more ABSs (or fake UL subframes) satisfying steps S1700 to S1720 exist, each ABS is configured to be replaced by a different DL subframe, and the sum of k values and k _PHICHs of DL subframes to be substituted is substituted. UL HARQ timing is configured to be the minimum (S1725).

When the PHICH timing is changed, the m _i value of Table 22 must also be changed. Instead of the ABS or fake UL sub-frame to transmit the PHICH and replace the value m _i of the DL subframe to the value m _i of the ABS or fake UL subframe. At this time, the m _i value corresponding to the ABS or fake UL subframe is set to 0 (S1727).

FIG. 18 is a diagram illustrating k values configured by the UL HARQ timing configuration method described with reference to FIG. 17, and FIG. 19 is a diagram illustrating k _PHICH configured by the UL HARQ timing configuration method described with reference to FIG. 17.

18 and 19, the values indicated by the arrows represent k values and k _PHICH values according to UL HARQ timing newly configured according to the present invention.

For example, when downlink subframe # 4 is used as an ABS or fake subframe in TDD configuration 1, UL grant and PHICH are not transmitted in UL HARQ according to Tables 4 and 5, and subframe # 4 and The UL grant may be transmitted instead in the closest normal downlink subframe # 0. In addition, since the PHICH timing for UL subframe # 8 was previously subframe # 4, since subframe # 4 cannot transmit PHICH, it is after 4ms of subframe # 8, and the UL grant and PHICH are transmitted in UL HARQ. If not, the PHICH may be transmitted instead in the normal downlink subframe # 5 closest to the subframe # 4. In this case, in order to satisfy step S1715, the UL grant may be transmitted in subframe # 5 instead of subframe # 9, and the PHICH for subframe # 3 may also be transmitted in subframe # 0 instead of subframe # 9. have.

20 is a diagram illustrating a value of l according to a newly configured UL HARQ timing when subframe bundling is configured according to the present invention.

Referring to FIG. 20, a value indicated by an arrow indicates an l value according to a UL HARQ timing newly configured according to the present invention. It may be used as PHICH timing for subframe bundling in a subframe capable of PUSCH scheduling instead of the ABS.

In step S1700 of FIG. 17, when the UL grant and the PHICH are not transmitted and there are no available DL subframes, that is, the number of ABS (or fake UL subframes) is equal to the PUSCH scheduling information among the normal DL subframes. If the number of DL subframes that are available without transmitting PHICH scheduling information is larger than that, the UL grant is configured to perform cross subframe scheduling in the nearest DL subframe among the previous DL subframes of the ABS, and transmit a value of k. The UL HARQ timing is configured to be greater than or equal to and have a minimum value (S1730). UL HARQ timing is configured to perform cross subframe scheduling as in steps S1625 to S1630 of FIG. 16.

For example, a cross subframe scheduling indicator indicating whether cross subframe scheduling is performed in UL HARQ may be included in DCI format 0/4. The cross subframe scheduling indicator may be 1 bit, and in this case, 1 bit may be added to DCI format 0/4. If the indicator is 1, it may indicate that the cross subframe scheduling is performed. If the indicator is 0, it may indicate that the cross subframe scheduling is not performed.

As another example, the cross subframe scheduling indicator may be added to RRC signaling and may also be 1 bit. When the cross subframe scheduling indicator (1 bit) transmitted through RRC signaling is 1, it indicates that the cross subframe scheduling is performed, and the UE includes the cross subframe scheduling indicator in DCI format 0/4, so that DCI format 0/4 is included. It may be determined that the length of 1 is added by 1 bit, and the DCI format 0/4 may be decoded. On the other hand, if the cross subframe scheduling indicator 1 bit transmitted through the RRC signaling is 0, it indicates that the cross subframe scheduling is not performed, the terminal interprets the length of DCI format 0/4 to the original length to DCI format 0 Can decode / 4

Subsequently, the PHICH timing may be configured using bundling or multiplexing (S1735).

For example, PHICH timing may be configured using bundling. A PHICH that cannot be received due to the ABS (or fake UL subframe) may be replaced with an ACK / NACK for the DL subframe closest to the subframe 4 ms after the existing PUSCH timing of the ABS (or fake UL subframe). That is, ACK / NACK for the closest DL subframe may be used as a response for two PUSCHs. At this time, the base station transmits NACK if any of the two PUSCH is NACK.

If the ACK / NACK of the closest DL subframe is ACK, the UE determines that the base station has transmitted ACK for all PUSCHs, and if the ACK / NACK of the closest DL subframe is NACK, the base station is determined for all PUSCHs. It is determined that the NACK is transmitted.

As another example, PHICH timing may be configured using multiplexing.

That is, a PHICH that cannot be received due to an ABS (or fake UL subframe) may be transmitted by multiplexing ACK / NACK in the DL subframe closest to 4 ms after the existing PUSCH timing of the ABS (or fake UL subframe). In this case, it is applicable only to a case where PUSCH scheduling is performed for two UL subframes in which one UL grant information is different from each other in the first type of two types of definitions of cross subframe scheduling. At this time, since the two uplink transmissions are scheduled by one UL grant information, they have the same resource allocation information, PHICH resource information, and DM RS cyclic shift information.

Specifically, when a cross subframe scheduling indicator indicates cross subframe scheduling, a method of distinguishing ACK / NACK for multiplexing PUSCH data scheduled for cross subframe scheduling will be described. However, even if the n _DMRS value and the I _{PRB_RA} value are changed in the present invention, this only affects PHICH resources and PHICH Orthogonal Complementary Code (OCC) for ABS (or fake UL subframe), and performs cross-subframe scheduling. The DM RS value and PUSCH resource allocation information of two PUSCH resources indicated at the time are not changed.

As an example using multiplexing of ACK / NACK, a PUSCH that is cross-subframe scheduled by adding "cyclic shift (n _DMRS ) 3 bits for DM RS and OCC index" to replacement subframe scheduling information (DCI format 0/4) ACK / NACK may be multiplexed to indicate a PHICH for data.

In this case, the additional 3 bits are transmitted only when the cross subframe scheduling indicator downlinking through the RRC signaling indicates the cross subframe scheduling. In this case, the UE determines the length of the DCI format 0/4 from the existing DCI format 0/4. Recognize that it is 3 bits long and decode DCI format 0/4.

As another example using multiplexing of ACK / NACK, n ^seq _PHICH (OCCC of PHICH) and n ^group _PHICH (PHICH resource) for PUSCH data scheduled for cross-subframe scheduling are known as " the last TB of n _DMRS (3 bits). Can be determined by +1 ". That is, the resource allocation information may be instructed to allocate another resource using an offset value (for example, "1"). In this case, the newly configured n ^seq _PHICH and n ^group _PHICH are as follows.

Equation 3

Here, n is "the number of TBs scheduled in one UL grant-1", where the number of TBs includes the number of TBs scheduling cross subframes.

In this case, I _{PRB_RA} is always I ^lowest_index _{PRB_RA} , and k is “the number of original TBs scheduled in one UL grant _minus 1”, where the number of original TBs is the number of TBs scheduled for cross-subframe scheduling. It means the number of TBs excluded.

For example, when scheduling two TBs, the OCC and PHICH resources of the PHICH for the cross-subframe scheduled TB1 and TB2 (PUSCH) are as shown in Equations 4 and 5, respectively. I also _{PRB_RA} in the following Equation 4 and 5 is I ^lowest_index _{PRB_RA} regardless TB 1 and 2.

Equation 4

Equation 5

As another example using multiplexing of ACK / NACK, an OCC (n ^seq _PHICH ) and a PHICH resource (n ^group _PHICH ) of a PHICH for PUSCH data scheduled for cross-subframe scheduling are known as an XOR of n _DMRS (3 bits) of the last TB. (exclusive or) operation result ".

As another example using multiplexing of ACK / NACK, an OCC (n ^seq _PHICH ) and a PHICH resource (n ^group _PHICH ) of a PHICH for PUSCH data scheduled for cross-subframe may be determined by an existing " last TB I _{PRB_RA} + 1 &quot;. Can be. This is as follows.

Equation 6

Here, n is "the number of TBs scheduling in one UL grant-1", where the number of TBs includes the number of TBs scheduling cross subframes. I _{PRB_RA} is always I ^lowest_index _{PRB_RA} .

As another example using multiplexing of ACK / NACK, in changing an OCC (n ^seq _PHICH ) and a PHICH resource (n ^group _PHICH ) of a PHICH for PUSCH data scheduled for cross-subframe, it may be determined as follows.

Equation 7

Where k is " | number of original TBs scheduling in one UL grant / 2 | Also,

And, and I _{PRS_RA} is always I ^lowest_index _{PRB_RA} .

If only one TB is allocated, it may be determined by I _{PRB_RA} and “n _DMRS +1” instead of the existing I _{PRB_RA} and n _DMRS .

In addition, when two TBs are allocated, it is determined by I _{PRB_RA} (I ^lowest_index _{PRB_RA} + 1) and n _{PRB_RA} and "n _DMRS +1" instead of n _DMRS for _TB1, and TB2 for _TB1 . It may be determined by "I _{PRB_RA} +1" and "n _DMRS +1" instead of I _{PRB_RA} and n _DMRS . The n ^seq _PHICH and the PHICH resource n ^group _PHICH of the PHICH for the cross-subframe scheduled TB1 and TB2 (PUSCH) are the following Equations 8 and 9, respectively. In addition, in Equations 8 and 9, I _{PRB_RA} is I ^lowest_index _{PRB_RA} regardless of TB 1 and 2.

Equation 8

Equation 9

Subsequently to step S1735, the UL HARQ is transmitted based on the UL HARQ timing configured using the cross subframe scheduling (S1740).

21 illustrates configuring PHICH timing using multiplexing according to the present invention. It relates to the PUSCH timing of TDD configuration 6 in an eICIC situation.

Referring to FIG. 21, since subframe # 9 is an ABS (or fake UL subframe), UL grants G4 and G5 are transmitted using sub-subframe scheduling in subframe # 6. At this time, the PHICH timing for PUSCH U4 is I4, which is subframe # 9, that is, ABS (or fake UL subframe). Therefore, the PHICH timings I5 and I4 for U5 are multiplexed and transmitted.

22 shows a result of resource allocation performed by using ACK / NACK multiplexing according to the present invention when N ^group _PHICH is 4. FIG.

Referring to FIG. 22, when two original TBs are scheduled, n ^seq _PHICH of TB1 is 0, n ^group _PHICH is 0, n ^seq _PHICH of TB2 is 0, and n ^group _PHICH is 1.

First, when n ^seq _PHICH (OCC of PHICH) and n ^group _PHICH (PHICH resource) for PUSCH data scheduled for cross subframe are determined by the existing " n _DMRS (3 bits) + 1 " , N ^seq _PHICH of TB1 is 1, n ^group _PHICH is 2, n ^seq _PHICH of TB2 is 2 and n ^group _PHICH is 3.

And, if the OCC (n ^seq _PHICH ) and PHICH resource (n ^group _PHICH ) of the PHICH for the PUSCH data scheduled for cross subframe are determined by the existing "I _{PRB_RA} +1 of the last TB", n ^seq _{PHICH of} TB1 Is 0, n ^group _PHICH is 2, n ^seq _PHICH of TB2 is 0, and n ^group _PHICH is 3.

In addition, the OCC (n ^seq _PHICH ) and PHICH resource (n ^group _PHICH ) of _PHICHs for PUSCH data scheduled for cross-subframe scheduling, I _{PRB_RA} and “n _DMRS +1” instead of I _{PRB_RA} and n _DMRS of the original last TB for TB1. Is determined by " I _{PRB_RA} + 1 " and " n _DMRS + 1 " instead of I _{PRB_RA} and n _DMRS of the original last TB for TB2, n ^seq _PHICH is 1 and n ^group _PHICH is 2 N ^seq _PHICH of TB2 is 1 and n ^group _PHICH is 3.

When a DL subframe capable of granting a UL grant is used as an ABS or fake UL subframe, the terminal and the base station preconfigure HARQ timing information configured according to FIGS. 16 and 17 of the present invention, and then UL according to the present invention. Send HARQ.

Referring to the operation of the terminal and the base station, for example, the terminal recognizes the ABS or fake subframe pattern through the RRC signaling, and instead of the corresponding ABS or fake subframe UL HARQ according to the UL HARQ timing according to the present invention Perform. As an example, the base station transmits ABS and fake subframe pattern information to the terminal and then performs UL HARQ according to the UL HARQ timing according to the present invention.

Now, as another example of the method for transmitting uplink control information according to the present invention (Embodiment 3), a method for determining the reception timing of an optimized TPC command of an ordering serving cell for a following serving cell and controlling the transmission power of the terminal How to do it.

은 첫번째로 적어도 하나의 PUSCH 전송이 이루어지는 안테나의 개수와 전송방식에 따라 구성된 안테나의 개수로 조정(scale)된다. 상기 조정된 전체 전력은 적어도 하나의 PUSCH 전송이 이루어지는 안테나에 대하여 동등하게 나누어져 할당된다. 반면, PUCCH 또는 SRS의 경우, 송신 전력

또는

은 PUCCH 또는 SRS에 대해 구성된 안테나 포트들에 동등하게 할당된다.First, uplink power control will be described. Uplink power control is to control each different uplink physical channel. In the case of PUSCH, transmit power

Is first scaled by the number of antennas for which at least one PUSCH transmission is performed and the number of antennas configured according to the transmission scheme. The adjusted total power is equally divided and allocated for antennas in which at least one PUSCH transmission is performed. On the other hand, in the case of PUCCH or SRS, the transmission power

or

Is equally assigned to the antenna ports configured for PUCCH or SRS.

First, control of the transmission power of the PUSCH will be described.

If the PUSCH is not transmitted simultaneously with the PUCCH for any serving cell c, the UE transmits the power P _{PUSCH, c} (i) defined as follows for PUSCH transmission in subframe #i for the serving cell c. do.

Equation 10

If a PUSCH is simultaneously transmitted with a PUCCH for an arbitrary serving cell c, a power P _{PUSCH, c} (i) defined as in the following equation is transmitted.

Equation 11

는 P_CMAX,c(i) dB를 선형으로 변환한 값이다.

는 P_PUCCH(i) 값을 선형으로 변환한 값이며, 이하에서 설명한다. M_PUSCH,c(i)는 서빙셀 c에 대한 서브프레임 #i 에서 PUSCH이 할당된 자원의 대역폭을 RB의 개수로 표현한 값이다. Here, P _{CMAX, c} (i) is the maximum terminal transmission power configured for the serving cell c

Is a linear conversion of P _{CMAX, c} (i) dB.

Is a value obtained by linearly converting a P _PUCCH (i) value and will be described below. M _{PUSCH, c} (i) is a value in which the bandwidth of a resource allocated with a PUSCH in subframe #i for the serving cell c is expressed by the number of RBs.

P _{O_PUSCH, c} (j) is the sum of P _{O_NOMINAL_PUSCH, c} (j) and P _{O_UE_PUSCH, c} (j) determined by signaling of a higher layer when j value for the serving cell c is 0 and 1. In this case, in the case of semi-persistent grant PUSCH transmission (or retransmission), j has a value of "0". On the other hand, j has a value of "1" for dynamic scheduled grant PUSCH transmission (or retransmission). And, in case of random access response grant PUSCH transmission (or retransmission), j has a value of "2". In addition, in case of random access response grant PUSCH transmission (or retransmission), P _{O_UE_PUSCH, c} (2) is 0 and P _{O_NOMINAL_PUSCH, c} (2) = P _{O_PRE} + Δ _{PREAMBLE_Msg3} , where the parameter preamble initial receive target power (preambleInitialReceivedTargetPower, P _{O_PRE} ) and Δ _{PREAMBLE_Msg3} are signaled from higher layers.

값들 중에서 하나가 선택될 수 있다. j가 "2"인 경우 항상 α_c(j)는 1이다.If j is "0" or "1", the 3-bit parameter provided by the upper layer

One of the values can be selected. If j is "2" is always α _c (j) it is one.

PL _c refers to an estimated downlink path attenuation value for the serving cell c calculated by the terminal (in dB), and its value is expressed by the following equation.

Equation 12

Here, referenceSignalPower is a value provided by an upper layer and is provided in dBm as an Energy Per Resource Element (EPRE) value of a downlink reference signal. Reference Signal Received Power (RSRP) is a reception power value of a reference signal for a reference serving cell. The determination of the serving cell selected as the reference serving cell and the referenceSignalPower and higherlayerfilteredRSRP used for the calculation of the PL _c is configured by the pathlossReferenceLinking which is an upper layer parameter. Here, the reference serving cell configured by the pathlossReferenceLinking may be a DL SCC of a primary serving cell or a secondary serving cell correlated with a UL CC and SIB2.

이고, K_s가 0일 때는 0이다. 여기서, K_s는 서빙셀 c, BPRE 및 β^PUSCH _offset 각각에 대하여 상위 계층(higher layers)에 의해 제공된 파라미터 deltaMCS-Enabled로부터 주어진다. 전송 다이버시티를 위한 모드인 전송 모드 2에서 K_s는 0이다. When K _s in Equation 10 is 1.5,

And zero when K _s is zero. Here, K _s is given from the parameter deltaMCS-Enabled provided by the higher layers for each of the serving cells c, BPRE and β ^PUSCH _offset . In transmission mode 2, which is a mode for transmission diversity, K _s is zero.

이다. 여기서 C는 코드블록의 개수이며, K_r은 코드블록의 크기이며, O_CQI는 CRC 비트수를 포함한 CQI/PMI 비트 개수이며, N_RE는 결정된 리소스 엘리먼트(Resource Element)들의 개수이다. 즉,

이다. 만약, PUSCH를 통해 UL-SCH 데이터 없이 제어정보만이 전송되는 경우 β^PUSCH _offset=β^CQI _offset로 설정하고, 그 이외의 경우는 항상 1로 설정한다.In addition, when only control information is transmitted through the PUSCH without UL-SCH data, the BPRE is O _CQI / N _RE .

to be. Where C is the number of code blocks, K _r is the size of the code blocks, O _CQI is the number of CQI / PMI bits including the number of CRC bits, and N _RE is the number of determined resource elements. In other words,

to be. If only control information is transmitted without UL-SCH data through the PUSCH, β ^PUSCH _offset = β ^CQI _offset is set. Otherwise, it is always set to 1.

δ _{PUSCH, c} refers to a transmit power control (TPC) command present in DCI format 0 or 4 for serving cell c or a TPC command in DCI format 3 / 3A that is coded and transmitted jointly with other terminals. Is a correction value determined by In the DCI format 3 / 3A, CRC parity bits are scrambled with TPC-PUSCH-RNTI, so only terminals assigned the RNTI value can be identified. In this case, the RNTI value may be assigned a different RNTI value for each serving cell to distinguish each of the serving cells when an arbitrary terminal is configured with a plurality of serving cells. In Equation 10, the transmission power may be controlled by adjusting δ _{PUSCH, c} .

The PUSCH power control adjustment state for the current serving cell c is given by f _c (i) and is defined as follows.

Equation 13

This is the case when accumulation is activated by the upper layer for the serving cell c or when the DCI format 0 scrambled by the TPC command δ _{PUSCH, c} by the temporary C-RNTI is included in the PDCCH.

Where δ _{PUSCH, c} (iK _PUSCH ) is a TPC command in DCI format 0/4 or 3 / 3A in the PDCCH that was transmitted in the iK _PUSCH th subframe, and f _c (0) is the first value after a cumulative reset.

In relation to the K _PUSCH value, in case of FDD, K _PUSCH is 4, and when TDD is 1 to 6, K _PUSCH values are shown in Table 27 below.

Table 27 TDD UL / DL Settings Subframe number i 0 One 2 3 4 5 6 7 8 9 0 - - 6 7 4 - - 6 7 4 One - - 6 4 - - - 6 4 - 2 - - 4 - - - - 4 - - 3 - - 4 4 4 - - - - - 4 - - 4 4 - - - - - - 5 - - 4 - - - - - - - 6 - - 7 7 5 - - 7 7 -

Referring to Table 27, a portion indicated by "-" is a DL subframe and a portion indicated by a number is a UL subframe.

In case of TDD configuration 0, if there is a PDCCH scheduling PUSCH transmission in subframe # 2 or subframe # 7, a LSB (Least Significant Bit) value of a 2-bit UL index is present in DCI format 0/4 in the PDCCH. If set to "1", K _PUSCH is 7. K _PUSCH values in all other cases are shown in Table 4 above. The 2-bit UL index is used for scheduling UL subframes that cannot be scheduled in Table 27.

On the other hand, the UE attempts to decode the PDCCH in all subframes except when the DRX (discontinous reception) operation. This includes the PDCCH of DCI format 0/4 for the C-RNTI of the UE or DCI format 0 for the SPS C-RNTI and DCI format 3 / 3A for the TPC-PUSCH-RNTI of the UE.

If DCI format 0/4 and DCI format 3 / 3A for the serving cell c are simultaneously received in the same subframe, the UE should use only δ _{PUSCH, c} of DCI format 0/4.

For a certain subframe _, δ _{PUSCH, c} is 0dB when there is no TPC command for the serving cell c, during DRX operation, or when the corresponding subframe is an UL subframe of TDD.

When the TPC command fields in DCI format 0/3/4 are 0, 1, 2, and 3, respectively, the accumulated delta _PUCCH dB values are -1, 0, 1, 3, respectively. If the PDCCH of DCI format 0 is approved as an SPS activation or release PDCCH, δ _{PUSCH, c} is 0 dB.

When the TPC command fields in DCI format 3A are 0 and 1, respectively, the accumulated δ _PUCCH dB values are -1 and 1, respectively.

If the UE reaches P _CMAX, c for the serving cell c, the positive TPC command will not accumulate. If the terminal reaches the minimum power, negative TPC commands will not accumulate.

If the value of P _{O_UE_PUSCH,} c for the serving cell c is changed by the higher layer or the terminal receives the random access response message for the main serving cell, the terminal will reset the accumulation.

In Equation 10, when accumulation is deactivated by the upper layer with respect to the serving cell c, f _c (i) is as follows.

Equation 14

Here, δ _{PUSCH, c} (iK _PUSCH ) is transmitted through DCI format 0/4 in PDCCH for serving cell c in subframe #iK _PUSCH .

The K _PUSCH value is 4 for FDD and is given as shown in Table 4 in TDD UL / DL configuration # 1 to # 6.

In TDD UL / DL configuration # 0, if PUSCH transmission in subframe # 2 or subframe # 7 is scheduled and the LSB of the 2-bit UL index of DCI format 0/4 in the PDCCH is set to "1", K _PUSCH is 7. Otherwise, K _PUSCH is given as shown in Table 27 above.

If DCI format 0/4 in the PDCCH for serving cell c is not decoded, DRX occurs, or subframe #i is not an UL subframe in TDD, f _c (i) is equal to f _c (i-1). same.

If the value of P _{O_UE_PUSCH, c} is changed by the higher layer and the serving cell c is the main serving cell, or if the value of P _{O_UE_PUSCH, c} is received by the higher layer and the serving cell c is the secondary serving cell, f _c (0) Is zero. In other cases, if the serving cell c is the main serving cell, f _c (0) = ΔP _rampup + δ _msg2 , where δ _msg2 is a TPC command indicated by a random access response. In addition, ΔP _rampup is provided by the upper layer and is for the total power ramp-up from the first preamble to the last preamble.

Now, control of the transmission power of the SRS will be described.

The UE transmits the SRS for the serving cell c to the UE transmit power P _SRS as shown in the following equation in subframe #i.

Equation 15

dB를 선형으로 변환한 값이다. P_{SRS_OFFSET,c}(m)는 4 비트의 상위 계층 시그널링을 통해 전송된다. M_SRS,c는 서빙셀 c에 대한 서브프레임 #i에서 전송되는 SRS의 대역폭으로써, RB 수로 표현된다.Here, P _{CMAX, c} (i) is the maximum terminal transmission power configured for the serving cell c

This is a linear conversion of dB. P _{SRS_OFFSET, c} (m) is transmitted through 4-bit higher layer signaling. M _{SRS, c} is a bandwidth of the SRS transmitted in subframe #i for the serving cell c, and is expressed as an RB number.

f _c (i) is a current PUSCH power control adjustment state for the serving cell c.

P _{O_PUSCH, c} (j) and α _c (j) are the same as the parameters described in Equations 10 and 11 for the PUSCH.

Hereinafter, the timing of controlling the transmission power of the SRS according to the present invention is applied in the same manner as the transmission power of the PUSCH according to the present invention.

Now, power control of the PUCCH will be described.

The UE transmits the power P _{PUCCH, c} (i) defined as the following equation for PUCCH transmission in subframe #i for the main serving cell c.

Equation 16

dB를 선형으로 변환한 값이다. Δ_{F_PUCCH}(F) 및 Δ_TxD(F')는 상위계층을 통해서 정해진다. h(n_CQI,n_HARQ,n_SR)는 PUCCH 포맷에 따라 다른 값을 가진다. P_{O_PUCCH}는 상위 계층에서 전송되는 P_{O_NOMINAL_PUCCH}와 P_{O_UE_PUCCH}의 합의 값을 가진다. Here, P _{CMAX, c} (i) is the maximum terminal transmission power configured for the serving cell c

This is a linear conversion of dB. Δ _{F_PUCCH} (F) and Δ _TxD (F ′) are determined through higher layers. h (n _CQI , n _HARQ , n _SR ) has a different value depending on the PUCCH format. P _{O_PUCCH} has a _sum of P _{O_NOMINAL_PUCCH} and P _{O_UE_PUCCH} transmitted from a higher layer.

δ _PUCCH is a UE-specific value, a TPC command transmitted through DCI format 1A / 1B / 1D / 1 / 2A / 2 / 2B / 2C, or a TPC in DCI format 3 / 3A coded and transmitted jointly with other terminals. Determined with reference to the command. In the DCI format 3 / 3A, since the CRC parity bit is scrambled to TPC-PUCCH_RNTI, only terminals to which the RNTI value is assigned can be identified. In this case, the RNTI value may be assigned a different RNTI value for each serving cell to distinguish each of the serving cells when an arbitrary terminal is configured with a plurality of serving cells.

In particular, the current PUCCH power control adjustment state is given by g (i) and is defined as follows.

Equation 17

Here, M is the number of elements of the set K, that is, the number of downlink subframes associated with the i-th subframe. For an FDD system, M is 1 and k ₀ is 4. For a TDD system, k _m is shown in Table 28 below.

Table 28 UL-DL Settings Subframe number i 0 One 2 3 4 5 6 7 8 9 0 - - 6 - 4 - - 6 - 4 One - - 7, 6 4 - - - 7, 6 4 - 2 - - 8, 7, 4, 6 - - - - 8, 7, 4, 6 - - 3 - - 7, 6, 11 6, 5 5, 4 - - - - - 4 - - 12, 8, 7, 11 6, 5, 4, 7 - - - - - - 5 - - 13, 12, 9, 8, 7, 5, 4, 11, 6 - - - - - - - 6 - - 7 7 5 - - 7 7 -

When the TPC command fields in DCI format 1A / 1B / 1D / 1 / 2A / 2 / 2B / 2C are 0,1,2,3, respectively, the delta _PUCCH dB value is -1,0,1,3, respectively.

If the DCI format 1 / 1A / 2 / 2A / 2B / 2C / 3 in the PDCCH is approved as an SPS activated PDCCH, or if DCI format 1A in the PDCCH is approved as an SPS release PDCCH, δ _PUCCH is 0 dB.

When the TPC command fields of DCI format 3A in the PDCCH are 0 and 1, respectively, the δ _PUCCH dB value is -1 and 1, respectively, and is semi-statically set by the higher layer.

If P _{O_UE_PUCCH} value is changed by higher layer, g (0) is zero. Otherwise, G (0) = ΔP _rampup + δ _msg2 . Where δ _msg2 is the TPC command indicated by the random access response, ΔP _rampup is provided by the upper layer, and is the total power ramp-up from the first preamble to the last preamble.

If the terminal reaches P _{CMAX, c} for the main serving cell, the positive TPC command for the main serving cell will not accumulate. If the terminal reaches the minimum power, negative TPC commands will not accumulate.

When the P _{O_UE_PUCCH} value is changed by the higher layer or when the terminal receives the random access response message, the terminal resets the accumulation.

If subframe #i is not an UL subframe in a TDD system, g (i) is g (i-1).

Now, when cross-carrier scheduling is applied according to the present invention, a method of determining a reception timing of an optimized TPC command of an ordering serving cell for a following serving cell and a method of controlling a transmission power of a terminal will be described.

When cross carrier scheduling is applied, a transmission power control command is received from the base station through the ordering serving cell, and the terminal applies the transmission power to perform transmission through the following serving cell. When the ordering serving cell and the following serving cell have different TDD settings, there is a need for a method of determining a TPC command reception timing so that a UE can properly receive a TPC command and perform transmission.

A case where the UE transmits a PUSCH (or SRS) and a case of transmitting a PUCCH will be described. In the case of transmitting the SRS, the same method as in the case of transmitting the PUSCH is applied.

<1. A UE Transmitting PUSCH or SRS to a Base Station (Embodiment 3-1)>

The ordering serving cell transmits a TPC command to the terminal through a DCI format (for example, DCI format 0/4/3 / 3A), and the terminal transmits the terminal by applying a PUSCH transmission power or an SRS transmission power based on the TPC command. Applies if

23 is a flowchart illustrating controlling uplink transmission power according to the present invention.

Referring to FIG. 23, when cross-carrier scheduling is performed, the UE determines a TPC command reception timing based on the TDD settings of the ordering serving cell (or the first serving cell) and the following serving cell (or the second serving cell) ( S2300). The UE may know in advance what the TDD settings of the ordering serving cell and the following serving cell are, and the base station may transmit the information to the terminal in advance before the terminal determines the reception timing of the TPC command.

Here, the timing of receiving a TPC command means that when the UE transmits a PUSCH or SRS in subframe #i (hereinafter, expressing to transmit a _PUSCH also includes transmitting an SRS), the subframe #iK that is before the K _PUSCH th subframe. refers to a receiving timing (K _PUSCH) in the TPC command that is based on a TPC command received on the _PUSCH to control the transmit power of the terminal. That is, the UE determines K _PUSCH in advance based on TDD settings of each of the ordering serving cell and the following serving cell, and then includes a TPC included in a subframe before the K _PUSCH determined among TPC commands included in the PDCCH received from the base station. After applying the transmission power based on the command, the PUSCH or SRS is transmitted to the base station.

In the case of cross-carrier scheduling, the subframe of the ordering serving cell transmitting the TPC command related to the control of the uplink transmission power for the following serving cell to the terminal is a DL subframe and is defined based on the TDD configuration of the ordering serving cell. . The position of the UL subframe of the following serving cell in which the UE transmits the uplink transmission power is determined based on the TDD configuration of the following serving cell. Therefore, since different TDD settings are used, the timing of the ordering serving cell corresponding to the subframe to which the TPC command related to the UL subframe of the following serving cell to which the PUSCH or the SRS is to be transmitted is not broken. It is required to determine the TPC command reception timing (K _PUSCH ) value so that the frame does not become an UL subframe.

The UE receives a PDCCH including a TPC command through an ordering serving cell (S2305), and the UE applies transmission power based on the K _PUSCH determined in advance in step S2300, and transmits the PUSCH or SRS to the base station through the following serving cell. It transmits (S2310). Among the TPC commands included in the PDCCH, the transmission power is applied based on the received TPC command at the timing indicated by the K _PUSCH , and then the PUSCH or SRS is transmitted according to the applied transmission power. The base station serves to adjust or control the transmission power, and the terminal receives the instruction of the base station and applies the same to control the transmission power of the terminal.

The TPC command reception timing may be determined by the terminal in advance, but may be determined by the base station and transmitted to the terminal. The TPC command reception timing information may be transmitted together with the TPC command through the PDCCH, or may be separately transmitted to the UE through RRC signaling.

The terminal and the base station may know the timing information of Tables 29 to 37 below.

For example, the terminal stores the timing information of Table 29 in the memory in advance, and may operate by using the information when necessary. The UE may know TDD configuration information of each serving cell through TDD configuration information transmitted through RRC signaling, and may know timing information of the corresponding serving cell based on this.

For example, if the UE receives the TPC command at a specific timing, the UE may know the PUSCH timing information for the corresponding TPC command based on the timing information (K _PUSCH value table) known to the UE. In addition, the base station can also know the PUSCH timing information for a specific TPC command.

When cross-carrier scheduling is configured through CrossCarrierSchedulingConfig information transmitted through RRC signaling, the timing information is configured according to a table configured by the method of FIG.

Cross carrier scheduling information is shown in the following table.

Table 29

Here, cif-Presence indicates whether the CIF exists in the PDCCH DCI format (TRUE) or not (FALSE).

Pdsch-Start is the first OFDM symbol of the PDSCH for the following serving cell (or secondary serving cell), and 1,2,3 values can be applied when the dl_Bandwidth for the following serving cell is greater than 10 RB, and the following When dl-Bandwith for the serving cell is less than or equal to 10RB, 2,3,4 values may be applied.

schedulingCellId indicates whether a cell (meaning an ordering cell) signals a downlink allocation or an uplink grant when cross-carrier scheduling is applied to a considered serving cell (following cell). The base station may transmit the PUSCH timing, the SRS timing, and the aperiodic CSI timing to the terminal through the PDCCH.

When the cross carrier scheduling is configured, the base station transmits the PDCCH for the following serving cell to the terminal through the ordering serving cell, where the PDCCH may include PUSCH timing information transmitted by the terminal, SRS timing, and aperiodic CSI timing. have. For example, the UL index 2 bits or 1 bit may be used to command HARQ timing different from the TPC command reception timing (K _PUSCH ) table. In this case, since the UE knows what the UL index constructed by the method of FIG. 24 is used in the corresponding TDD configuration, the UE may know the PUSCH timing according to the corresponding TPC command using only 2 bits or 1 bit.

24 is a flowchart illustrating an example of a method of determining a TPC command reception timing (K _PUSCH ) according to the present invention.

Referring to FIG. 24, first, a DL subframe of an ordering serving cell transmitting a TPC command to a UE is 4ms before a UL subframe of a following serving cell transmitting a PUSCH or SRS, that is, K _PUSCH is greater than four. The TPC command reception timing of the terminal is determined to be greater than or equal to (S2400).

In this case, determining the TPC command reception timing is determined according to whether the number of UL subframes of the following serving cell is larger than the number of DL subframes of the ordering serving cell.

If the number of UL subframes of the following serving cell is less than or equal to the number of DL subframes of the ordering serving cell, the TPC command is performed through DL subframes of different ordering serving cells for all UL subframes of the following serving cell. To determine the timing of receiving the TPC command. Accordingly, the DL subframes of the ordering serving cell may determine a timing to receive a TPC command with respect to UL subframes of different following serving cells (S2405). That is, UL subframes of the following serving cells are matched with DL subframes of different ordering serving cells.

At this time, with respect to a TDD setting the sum of the reception timing (K _PUSCH) the value of the TPC command is minimized, i.e., to have a _{min (sum [total (K PUSCH} )]) determined the K _PUSCH (S2410).

On the other hand, if the number of UL subframes of the following serving cell is larger than the number of DL subframes of the ordering serving cell, the TPC command in the DL subframes of different ordering serving cells for all UL subframes of the following serving cell It is not possible to determine the timing of receiving the TPC command to send a. That is, at least one DL subframe of the ordering serving cell should determine the TPC command reception timing to transmit TPC commands for the plurality of UL subframes of the following serving cell. One example of such a case is when the ordering serving cell is TDD configuration 0 and the following serving cell is TDD configuration 6.

At this time, first, K _PUSCH is determined to transmit a TPC command for each different UL subframe of the following serving cell in all DL subframes of the ordering serving cell (S2415). This is to minimize the number of UL subframes of the ordering serving cell transmitting TPC commands for a plurality of UL subframes of the following serving cell.

In order to transmit TPC commands for a plurality of UL subframes of the following serving cell, one DL subframe of the ordering serving cell is determined using the 1-bit UL index according to the present invention (S2420). . In this case, unlike the existing 2-bit UL index, the UL index according to the present invention may have a size of 1 bit. The UL index may be included in the DCI format for transmitting the TPC command, and the UE may decode the DCI format for transmitting the TPC command to a length of 1 bit added according to the configuration of the ordering serving cell and the following serving cell.

The terminal or the base station may be set in advance to have different K _PUSCH values when the UL index is set to "0" and when it is set to "1". For example, if the UL index is set to "0", K _PUSCH may be 6, and if the UL index is set to "1", K _PUSCH may be 7. The terminal or the base station may know in advance about the UL index.

Also in this case, with respect to a TDD setting the sum of the reception timing (K _PUSCH) the value of the TPC command is minimized, i.e., to have a _{min (sum [total (K PUSCH} )]) determined the K _PUSCH (S2410) .

25 illustrates a method of determining a K _PUSCH value according to the present invention.

The case in which the ordering serving cell is TDD setting 6 of the following serving cell when the TDD setting is 0 will be described. When the following serving cell is TDD configuration 6 as in the case of Table 27, the subframe # of the ordering serving cell whose K _PUSCH value for subframe 4 is "5" and is 5 subframes before subframe # 4. 9 cannot receive a TPC command because it is a UL subframe (S800). Therefore, according to the method of FIG. 24, a new K _PUSCH value is configured to receive a TPC command at a new timing.

First, in subframe # 2 of the following serving cell, a PUSCH or SRS is transmitted by applying transmission power of a UE based on a TPC command received through subframe # 5 of an ordering serving cell, which is 7 subframes before. In subframe # 3 of the following serving cell, a PUSCH or SRS is transmitted by applying transmission power of a UE based on a TPC command received through subframe # 6 of an ordering serving cell, which is 7 subframes before.

A new K _PUSCH value is determined for subframe # 4 of the following serving cell. According to the method of FIG. 24, the new K _PUSCH value is greater than or equal to 4, since 4 DL subframes of the ordering serving cell and 6 UL subframes of the following serving cell are min (sum [total (K _PUSCH) To have)]), the new K _PUSCH value is determined to be 4. The PUSCH or the SRS is transmitted by applying the transmission power of the UE based on the TPC command received through subframe # 0 of the ordering serving cell, which is before 4 subframes. In this way, by applying the existing K _PUSCH values instead of the transmission power of the terminal to the new K to the _PUSCH value determined as "4" based on a TPC command received on the sub-frame # 0 of ordering the serving cell transmits the PUSCH or SRS .

In subframe # 7 of the following serving cell, PUSCH or SRS is transmitted by applying the transmit power of the UE based on the TPC command received through subframe # 1 of the ordering serving cell, which is six subframes before, and the following serving In subframe # 8 of a cell, a PUSCH or SRS is transmitted by applying a transmission power of a UE based on a TPC command received through subframe # 1 of an ordering serving cell that is 7 subframes before. That is, the PUSCH or the SRS is transmitted by controlling both transmission powers of the UE in subframe # 7 and subframe # 8 of the following serving cell through subframe # 1 of the ordering serving cell.

In this case, even if the K _PUSCH value for subframe # 7 of the following serving cell has a value of "7", the TPC command may be transmitted using subframe # 0 and the UL index of the ordering serving cell, but min (sum [ In order to determine the K _PUSCH value to have a total (K _PUSCH )]), the new K _PUSCH value is determined as "6". In addition, the K _PUSCH value for the subframe # 8 of the following serving cell has a value of "7", but when the UL index is set to "0" using the UL index, the following serving cell When the TPC command for subframe # 7 of the UL index is set to "1", the TPC command may be distinguished as being a TPC command for subframe # 8 of the following serving cell.

Although TPC commands for a plurality of DL subframes may be transmitted in subframes other than the subframe # 1 of the ordering serving cell, a new K _PUSCH is determined as shown in FIG. 25 because the total sum of K _PUSCH values should be minimized.

In the following Tables 30 to 36, an embodiment of the optimal TPC command reception timing (K _PUSCH ) determined according to FIG. 24 for the TDD setting 0 to TDD setting 6 of the ordering serving cell is shown for each TDD of the following serving cell. Displayed by setting.

Table 30 below determines the TPC command reception timing (K _PUSCH ) when the ordering serving cell is TDD configuration 0.

Table 30 TDD UL / DL Settings Subframe number i 0 One 2 3 4 5 6 7 8 9 Ordering CC: 0 6 7 4 6 7 4 One 7 7 7 7 2 6 6 3 7 7 4 4 7 7 5 6 6 7 7 4 6 7

In the case of Table 30, when the following serving cell is TDD configuration 6, when scheduling transmission power for subframe # 8 which is a UL subframe, UL index 1 in DCI format 0/4 in the PDCCH received from the ordering serving cell If the bit is set to "1", K _PUSCH is seven. If one bit of the UL index is 0, then transmission power is scheduled for subframe # 7. That is, in this case, two UL subframes may be distinguished and scheduled for the following serving cell in subframe # 0 of the ordering serving cell.

Table 31 shows an optimal reception power reception timing when the ordering serving cell uses TDD configuration 1.

Table 31 TDD UL / DL Settings Subframe number i 0 One 2 3 4 5 6 7 8 9 Ordering CC: 1 6 4 6 4 0 6 4 4 6 4 4 2 6 6 3 6 4 4 4 6 4 5 6 6 6 4 4 6 4

Table 32 below shows an optimal reception power reception timing when the ordering serving cell uses TDD setting 2.

Table 32 TDD UL / DL Settings Subframe number i 0 One 2 3 4 5 6 7 8 9 Ordering CC: 2 4 4 0 4 4 4 4 4 4 One 6 4 6 4 3 4 4 4 4 4 4 5 4 6 6 4 4 6 4

Table 33 below shows an optimal reception power reception timing when the ordering serving cell uses TDD configuration 3.

Table 33 TDD UL / DL Settings Subframe number i 0 One 2 3 4 5 6 7 8 9 Ordering CC: 3 4 4 4 0 6 5 5 7 7 4 One 6 4 7 7 2 4 6 4 4 4 5 4 6 7 5 5 7 7

Table 34 below shows an optimal reception power reception timing when the ordering serving cell uses the TDD setting 4.

Table 34 TDD UL / DL Settings Subframe number i 0 One 2 3 4 5 6 7 8 9 Ordering CC: 4 4 4 0 6 4 4 6 4 4 One 6 4 6 4 2 4 6 3 4 4 4 5 4 6 6 4 4 6 4

Table 35 below shows an optimal reception power reception timing when the ordering serving cell uses the TDD setting 5.

Table 35 TDD UL / DL Settings Subframe number i 0 One 2 3 4 5 6 7 8 9 Ordering CC: 5 4 0 6 4 4 6 4 4 One 6 4 6 4 2 4 4 3 4 4 4 4 6 6 4 4 6 4

Table 36 below shows an optimal reception power reception timing when the ordering serving cell uses TDD setting 6.

Table 36 TDD UL / DL Settings Subframe number i 0 One 2 3 4 5 6 7 8 9 Ordering CC: 6 7 7 5 7 7 0 6 7 4 6 7 4 One 6 4 7 7 2 6 6 3 6 4 4 4 6 4 5 6

Referring to Table 36, when the following serving cell is TDD configuration 0, as described in Table 27, the UL index 2 bits used in the existing TDD configuration 0 are used.

Now, another example of a method of determining the TPC command reception timing (K _PUSCH ) according to the present invention will be described.

According to an embodiment of the present invention, in case of cross-carrier scheduling, TPC command information of a following serving cell is transmitted only in subframe # 0, subframe # 1, subframe # 5, and subframe # 6 of the ordering serving cell. Timing can be determined. Since subframe # 0, subframe # 1, subframe # 5, and subframe # 6 are DL subframes that can transmit PDCCH in common in all TDD configurations, it is possible to create and apply only one K _PUSCH table in this case. . In this case, unlike the previous embodiment, a process of comparing the number of subframes is unnecessary.

The following table shows an example of scheduling TPC command reception timing so that the UE controls transmission power by transmitting a TPC command only in subframe # 0, subframe # 1, subframe # 5, and subframe # 6 of the ordering serving cell. will be.

Table 37 TDD UL / DL Settings Subframe number i 0 One 2 3 4 5 6 7 8 9 0 6 7 4 6 7 4 One 7 7 7 7 2 6 6 3 7 7 4 4 7 7 5 6 6 7 7 4 6 7

Referring to Table 37, regardless of the TDD configuration of the ordering serving cell, TPC commands may be received through 4 DL subframes. When the following serving cell is TDD configuration 0 or TDD configuration 6, the UL of the following serving cell is determined. The number of subframes is five or more. Therefore, TPC commands cannot be matched one-to-one through only four DL subframes of the ordering serving cell, and TPCs for UL subframes of a plurality of following serving cells through at least one DL subframe of the ordering serving cell. You must receive the command. Therefore, the UL index is used to receive the TPC command through the ordering serving cell. In this case, the UL index may be 1 bit and may be included in the DCI format in the PDCCH.

First, when the following serving cell is TDD configuration 0, it is transmitted as it is at the timing of transmitting the TPC command of the conventional TDD configuration 0. In this case, as described in Table 27, a 2-bit UL index may be used.

When the following serving cell is TDD configuration 6, cross-carrier scheduling is enabled through RRC signaling and one bit is added to the DCI format of the PDCCH that transmits a TPC command for TDD configuration 6 of the following serving cell. Can be decoded to the specified length.

Since there are five UL subframes, at least one UL index may be used. If the UL index is set to "0", K _PUSCH may be "6", and if the UL index is set to "1", K _PUSCH may be "7". The terminal or the base station may know in advance about the UL index. If the UL index is used, all TPC commands for subframe # 7 and subframe # 8 of the following serving cell may be received in subframe # 1 of the ordering serving cell.

On the other hand, when the TDD configuration of the following serving cell is TDD configuration 1 to TDD configuration 5, since the number of UL subframes of the following serving cell is 4 or less, subframe # 0, which is a DL subframe of the ordering serving cell, subframe Each UL subframe may be scheduled one by one in # 1, subframe # 5, and subframe # 6. At this time, for one UE of one serving cell, the K _PUSCH value is determined so as not to schedule two or more UL subframe TPCs in one DL subframe at one timing. Further, with respect to a TDD setting the sum of the reception timing (K _PUSCH) the value of the TPC command is minimized, i.e., to have a _{min (sum [total (K PUSCH} )]) determined the K _PUSCH

Now, another example of a method of determining the TPC command reception timing (K _PUSCH ) according to the present invention will be described.

When the TPC command reception timing for the following serving cell according to K _PUSCH values of Table 27 is not a DL subframe of the ordering serving cell, the TPC command is not transmitted from the ordering serving cell to the following serving cell for one UE. If at least one DL subframe exists, the timing at which the TPC command should be transmitted for the following serving cell according to Table 27 among the DL subframes that do not transmit the TPC command, but the timing configured as the UL subframe in the ordering serving cell The K _PUSCH value may be determined to transmit a TPC command instead in an adjacent DL subframe at.

26 illustrates a process of determining a new TPC command reception timing (K _PUSCH ) according to the present invention. The ordering serving cell is TDD configuration 1 and the following serving cell is TDD configuration 3.

Referring to FIG. 26, according to the K _PUSCH value, subframe # 2 of the following serving cell transmits a PUSCH by controlling a transmit power of the UE based on a TPC command transmitted through subframe # 8 of the ordering serving cell. The subframe # 3 of the following serving cell transmits a PUSCH whose transmission power is controlled based on the TPC command transmitted through the subframe # 9 of the ordering serving cell, and the subframe # 4 of the following serving cell represents an ordering serving. The PUSCH with the controlled transmit power is transmitted based on the TPC command transmitted through the subframe # 0 of the cell. However, since subframe # 8 of the ordering serving cell is a UL subframe rather than a DL subframe (or an S subframe), a TPC command cannot be transmitted.

Accordingly, a new K _PUSCH value is determined to receive a TPC command in one of the DL subframes that do not transmit the TPC command for the following serving cell among the DL subframes of the serving cell. In particular, the new K _PUSCH is determined from a value of 4 or more, but determined as the minimum value.

That is, the TPC for subframe # 2 of the following serving cell in subframe # 6, which is the DL subframe closest to subframe # 8 among the DL subframes of the ordering serving cell that does not transmit the TPC command for the following serving cell. Determine a new K _PUSCH to send the command instead.

According to the new K _PUSCH value, the transmission power of the UE is controlled based on the TPC command received in subframe # 6 of the ordering subframe to transmit the PUSCH through subframe # 2 of the following serving cell.

<2. A UE Transmitting PUCCH to a Base Station (Example 3-2)>

In the ordering serving cell, the TPC command is transmitted to the terminal through the DCI format 1A / 1B / 1D / 1 / 2A / 2 / 2B / 2C / 3 / 3A in the PDCCH to the following serving cell. This is applied when a PUCCH transmission power is applied based on the TPC command.

When the UE transmits the PUCCH, the TPC command reception timing is based on the TPC command received based on the TPC command received in subframe #ik _m that is before the k _mth subframe when the UE transmits the PUCCH in subframe #i. Receive timing of the TPC command for control. That is, the terminal determines k _m based on the TDD settings of the ordering serving cell and the following serving cell.

In the case of cross-carrier scheduling, a subframe of an ordering serving cell that transmits a TPC command related to control of uplink transmission power for the following serving cell to the terminal is a DL subframe and is defined based on the TDD configuration of the ordering serving cell. The location of the UL subframe of the following serving cell to which the UE applies uplink transmission power is determined based on the TDD configuration of the following serving cell. Therefore, since it is based on different TDD settings, it is required to determine the k _m value so that the timing is not broken.

Table 38 below shows the TPC command reception timing (k _m ).

Table 38 UL-DL Settings subframe i 0 One 2 3 4 5 6 7 8 9 0 - - 6 - 4 - - 6 - 4 One - - 7, 6 4 - - - 7, 6 4 - 2 - - 8, 7, 4, 6 - - - - 8, 7, 4, 6 - - 3 - - 7, 6, 11 6, 5 5, 4 - - - - - 4 - - 12, 8, 7, 11 6, 5, 4, 7 - - - - - - 5 - - 13, 12, 9, 8, 7, 5, 4, 11, 6 - - - - - - - 6 - - 7 7 5 - - 7 7 -

Referring to Table 38, i is a subframe number and the downlink subframe set associated with the subframe of that number is determined by K = {k ₀ , k ₁ , ..., k _M-1 } (k _{M -1} ≥ 4), ik _m indicates a downlink subframe associated with the current subframe as the subframe index of the _m- th previous frame in the i-th subframe. The associated downlink subframe means a subframe carrying a PDCCH including a TPC command. M is the number of downlink subframes associated with the i-th subframe.

In Table 38, the k _m values of Table 28 are underlined for UL subframes that cannot receive TPC commands through DL subframes subframe # 0, subframe # 1, subframe # 5, and subframe # 6. Distinguished. That is, the PUCCH may be transmitted in the UL subframe according to the remaining k _m except for the underlined k _m value.

Since subframe # 0, subframe # 1, subframe # 5, and subframe # 6 are always DL subframes for all TDD configurations, even if the ordering serving cell and the following serving cell have different TDD settings, they can always be scheduled. .

Therefore, there is a need for a method capable of always scheduling transmission power for transmission to a following serving cell from an ordering serving cell only for an underlined UL subframe.

27 is a flowchart illustrating another example of a method of determining a TPC command reception timing k _m according to the present invention.

In this method, since the DL subframe timing of the ordering serving cell does not include the DL subframe timing of the following serving cell, a UL subframe capable of transmitting transmit power from the DL subframe of the ordering serving cell to the PUCCH of the following serving cell. Applicable only if the TPC command for the frame cannot be received (underlined in Table 38 above). However, in determining the PUCCH transmission power, an M value, which is the number of DL subframes associated with subframe #i, is also applied according to the table of k _m values (hereinafter, Tables 39 to 43) according to the present invention.

In principle, it is not possible to schedule UL subframes of a plurality of following serving cells in a DL subframe of one ordering serving cell. Therefore, for the UL subframe (underlined in Table 38) of the following serving cell that cannot receive the TPC command because the TDD settings of the ordering serving cell and the following serving cell are different, If there is an UL subframe (that is, a UL subframe having a plurality of k _m values, such as subframe # 2) that can receive a TPC command from the DL subframe of two or more ordering serving cells of the UL subframes, One of k _m values of the UL subframe is selected (S2700). Through the DL subframe indicated by the k _m value, a new k _m value is determined such that the UL subframe of the following serving cell that cannot receive the TPC command can receive the TPC command (S2705).

In this case, a new K _m value is determined such that the sum of the K _m values is minimum for one TDD setting, that is, a min (sum [total (K _m )]) value (S2710).

In addition, when there is no subframe capable of receiving a TPC command from two or more DL subframes among the UL subframes, the 1-bit UL index may be scheduled for the UL subframe in which the TPC command cannot be received ( S2715). The 1 bit UL index may be transmitted in addition to the DCI format 1A / 1B / 1D / 1 / 2A / 2 / 2B / 2C / 3 / 3A. This is the case when the ordering serving cell is TDD configuration 0 and the following serving cell is TDD configuration 6.

When the ordering serving cell is TDD configuration 0 and the following serving cell is TDD configuration 6, cross-carrier scheduling is enabled through RRC signaling, and the length of the DCI format for transmitting the TPC command can be decoded to an additional length of 1 bit. Can be. If the UL index 1 bit is set to "1", it may be determined as information for scheduling UL subframe # 4 of the following serving cell. Or a 1-bit UL index, if set to "1", can be seen that K _m has a value of "7".

Even in this case, a new k _m value is determined such that the sum of k _m values is minimum for one TDD setting, that is, min (sum [total (k _m )]) value (S2710).

In the following Tables 39 to 40, an embodiment of an optimal TPC command reception timing (k _m ) determined according to the present invention for the case of TDD setting 0 to TDD setting 6 of an ordering serving cell is set for each TDD of the following serving cell. Not represented.

Table 39 below determines the TPC command reception timing (k _m ) when the ordering serving cell is TDD configuration 0. Table 39 may also be used when applying a table of one k _m value to all TDD settings.

Table 39 UL-DL Settings Subframe number i 0 One 2 3 4 5 6 7 8 9 0 - - 6 - 4 - - 6 - 4 One - - 7 7 - - - 7 7 - 2 - - 8, 7, 4, 6 - - - - 8, 7, 4, 6 - - 3 - - 7, 11 7, 6, 5 5, 4 - - - - - 4 - - 12, 8, 7, 11 6, 5, 4, 7 - - - - - - 5 - - 13, 12, 9, 8, 7, 5, 4, 11, 6 - - - - - - - 6 - - 7 7 - - - 7 7 -

Table 40 below determines the TPC command reception timing (k _m ) when the ordering serving cell is TDD configuration 1.

Table 40 UL-DL Settings Subframe number i 0 One 2 3 4 5 6 7 8 9 0 - - 6 - 4 - - 6 - 4 One - - 7, 6 4 - - - 7, 6 4 - 2 - - 8, 7, 4, 6 - - - - 8, 7, 4, 6 - - 3 - - 7, 6, 11 4 4 - - - - - 4 - - 12, 8, 7, 11 6, 5, 4, 7 - - - - - - 5 - - 13, 12, 9, 8, 7, 5, 4, 11, 6 - - - - - - - 6 - - 7 7 5 - - 7 7 -

Table 41 below determines the TPC command reception timing (k _m ) when the ordering serving cell is TDD setting 2, 4, or 5.

Table 41 UL-DL Settings Subframe i 0 One 2 3 4 5 6 7 8 9 0 - - 6 - 4 - - 6 - 4 One - - 7, 6 4 - - - 7, 6 4 - 2 - - 8, 7, 4, 6 - - - - 8, 7, 4, 6 - - 3 - - 7, 6, 11 6, 5 5, 4 - - - - - 4 - - 12, 8, 7, 11 6, 5, 4, 7 - - - - - - 5 - - 13, 12, 9, 8, 7, 5, 4, 11, 6 - - - - - - - 6 - - 7 7 5 - - 7 7 -

Table 42 below determines the TPC command reception timing (k _m ) when the ordering serving cell is TDD configuration 3.

Table 42 UL-DL Settings Subframe number i 0 One 2 3 4 5 6 7 8 9 0 - - 6 - 4 - - 6 - 4 One - - 7, 6 4 - - - 7, 6 10,11 - 2 - - 8, 7, 4, 6 - - - - 8, 7, 4, 6 - - 3 - - 7, 6, 11 6, 5 5, 4 - - - - - 4 - - 12, 8, 7, 11 6, 5, 4, 7 - - - - - - 5 - - 13, 12, 9, 8, 7, 5, 4, 11, 6 - - - - - - - 6 - - 7 7 5 - - 7 7 -

Table 43 below determines the TPC command reception timing (k _m ) when the ordering serving cell is TDD configuration 6.

Table 43 UL-DL Settings Subframe i 0 One 2 3 4 5 6 7 8 9 0 - - 6 - 4 - - 6 - 4 One - - 7, 6 4 - - - 7 7 - 2 - - 8, 7, 4, 6 - - - - 8, 7, 4, 6 - - 3 - - 7, 6, 11 4 4 - - - - - 4 - - 12, 8, 7, 11 6, 5, 4, 7 - - - - - - 5 - - 13, 12, 9, 8, 7, 5, 4, 11, 6 - - - - - - - 6 - - 7 7 5 - - 7 7 -

Now, a method of determining the CSI reporting timing will be described. The timing of receiving TPC commands of the PUSCH and the SRS according to the present invention (Tables 30 to 37) may also be applied to the timing of reporting aperiodic CSI.

In the LTE system, the downlink transmission method is adaptively determined according to the downlink channel situation. This is because the determination of the downlink transmission method can be optimized when the downlink channel condition is made. Since the downlink transmission method is determined by the base station, the base station needs to first recognize the downlink channel condition.

The channel state information (CSI) of the downlink is represented by a channel quality indicator (CQI) and a precoding matrix indicator (PMI) or a rank indicator (RI), and the terminal uplinks the information on the downlink channel situation to the base station. By transmitting through the link, the base station can know the channel status of the downlink.

CSI allows for periodic reporting or aperiodic reporting. Periodic reporting is reported according to a period determined by higher layer signaling, and aperiodic reporting is transmitted when a CSI request field is set through PDCCH information transmitted from a base station. do.

The present invention relates to a method for determining aperiodic CSI reporting timing so that aperiodic CSI reporting can be properly performed when cross carrier scheduling is applied. The CSI request field is transmitted through a UL DCI format 0/4 or a random access response grant (RAR grant). Aperiodic CSI report is transmitted through the PUSCH.

FIG. 28 shows an example of allocating a common search space for transmitting an RAR grant to which a following serving cell is applied.

Referring to FIG. 28, since the RAR grant is transmitted through a common search space (CSS), the CSS for the following serving cell is set. By configuring the CSS for the following serving cell, the RAR grant for the following serving cell can be transmitted through the ordering serving cell. In this case, the CSS resource for the ordering serving cell and the CSS resource for the following serving cell may be set not to overlap each other.

If there is insufficient resources to transmit control information, CSS of the ordering serving cell and CSS of the following serving cell cannot overlap each other. In this case, when the CSS of the following serving cell cannot be set or only resources other than the CSS of the ordering serving cell are defined.

As another example of the method of transmitting the RAR grant for the following serving cell, a new RA-RNTI is generated as in the following equation. The new RA-RNTI is hereinafter referred to as M-RA-RNTI (Multiple-RA-RNTI).

Equation 18

Here, the value of m_ta_offset is an offset value that determines the existing RA-RNTI value to be distinguished from the M-RA-RNTI value. For example, since the maximum value of the existing RA-RNTI is 60 (1 + 9 + 10 * 5 = 60), if m_ta_offset is 60, the M-RA-RNTI value and the RA-RNTI value can be completely separated without any complicated mechanism. have.

Here, t _id is an index of the first subframe of the specialized Physical Random Access Channel (PRACH) (0 ≦ t _id <10). And f _id is an index of the specified PRACH of the ascending order of the frequency domain in the subframe. (0 ≦ f _id <6).

29 is a flowchart illustrating aperiodic CSI reporting timing in accordance with the present invention.

Referring to FIG. 29, when applying cross-carrier scheduling, aperiodic CSI report timing determination is a method of determining the reception timing of an optimized TPC command of an ordering serving cell for the following serving cell described with reference to FIGS. 23 and 26. The same applies to the method. However, aperiodic CSI reporting timing of UL subframe #n (see Table 44) of the CSI transfer request information of the DL sub-frame #i K _PUSCH one sub-frame before the sub-frame as the #iK _PUSCH, K _PUSCH more sub The difference is that the subframe # i + K _PUSCH after the frame. In the following, the k value is the same as the K _PUSCH value, but the TPC command reception timing is configured based on the UL subframe, whereas the aperiodic CSI reporting timing is configured based on the DL subframe. Therefore, when configuring the aperiodic CSI reporting timing (k) table in Tables 30 to 37, the K _PUSCH is applied to the k value in the # i-K _PUSCH subframe (which becomes #i in the aperiodic CSI reporting timing table). By configuring the aperiodic CSI reporting timing table, the UE determines the aperiodic CSI reporting timing based on the TDD settings of the ordering serving cell and the following serving cell (S2900). The UE may know in advance information about each TDD configuration of the ordering serving cell and the following serving cell, and the base station may separately transmit the UE to the UE before determining the aperiodic CSI reporting timing.

When configured to trigger an aperiodic CSI report in a CSI request field in the UL DCI format, the aperiodic CSI report timing k is 4 in an FDD system. Aperiodic CSI reporting is performed after four subframes from the subframe receiving the CSI request field.

In addition, in the TDD settings 0 to 6, the aperiodic CSI reporting timing k is shown in Table 44 below. Also, in the TDD setting 0, if the MSB of the 2-bit UL index included in the DCI format is set to "1" and the LSB of the 2-bit UL index is set to "0", the aperiodic CSI reporting timing is shown in the following table. Same as 44. Or, if the MSB of the 2-bit UL index is set to "0" and the LSB is set to "1", the aperiodic CSI reporting timing is 7. Alternatively, if the MSB and LSB of the 2-bit UL index are set to "1", the aperiodic CSI reporting timing is shown in Table 44 below.

Table 44 TDD UL / DL Settings Subframe number i 0 One 2 3 4 5 6 7 8 9 0 4 6 4 6 One 6 4 6 4 2 4 4 3 4 4 4 4 4 4 5 4 6 7 7 7 7 5

After determining the k value that is the aperiodic CSI reporting timing in advance, the terminal receives the CSI request field from the base station (S2905).

The aperiodic CSI request field may be included in the UL DCI format 0/4 or the RAR grant and transmitted to the terminal.

For example, since K _PUSCH is 6 in subframe # 2 of TDD configuration 0 of Table 27, a TPC command for PUSCH is received in subframe # 6, which is six subframes before. Applying this to aperiodic CSI, in Table 44, the k value of subframe # 6 of TDD configuration 0 is 6, and PUSCH is transmitted to perform aperiodic CSI reporting in subframe # 2 after 6 subframes.

On the other hand, when transmitting the aperiodic CSI request through the RAR grant, after receiving the RAR grant for the following serving cell through the ordering serving cell according to the above method, the non-periodic CSI report of the subframe after 6ms in the following serving cell Transmits a PUSCH on an available UL subframe. At this time, if one bit of the delay field is set to "1", it transmits on the next UL subframe among UL subframes capable of aperiodic CSI reporting.

As an example of requesting aperiodic CSI, if the CSI request field is set to 1 bit, if the CSI request field is set to '1', it may indicate that the base station requests the aperiodic CSI report to the terminal.

As another example, if the CSI request field is 2 bits, the indication indicated by the CSI request field is shown in Table 45 below.

Table 45 CSI Request Field Explanation 00 Aperiodic CSI reporting not triggered 01 Aperiodic CSI reporting is triggered for serving cell c 10 Aperiodic CSI reporting is triggered for the first set of serving cells configured by higher layer 11 Aperiodic CSI reporting is triggered for the second set of serving cells configured by higher layer

Here, the 1 ^st set and the 2 ^nd set refer to respective subframe patterns when there are two subframe patterns for measuring CSI for one serving cell.

In operation S2910, aperiodic CSI reporting is performed on the determined subframes after the k subframes.

In the case of cross-carrier scheduling, the subframe of the ordering serving cell receiving the CSI request field is a DL subframe and is defined based on the TDD configuration of the ordering serving cell. The subframe in which the UE performs the aperiodic CSI report is an UL subframe and the location of the UL subframe is determined based on the TDD configuration of the following serving cell. Therefore, since it is based on different TDD settings, it is required to determine the aperiodic CSI reporting timing (k) value so that the subframe of the following serving cell to perform aperiodic CSI reporting does not become a DL subframe.

On the other hand, the aperiodic CSI reporting timing may be adjusted (or delayed) to another subframe using an UL delay field.

If the CSI request field in the random access response grant is set to trigger reporting and is not reserved, then if the UL Delay field is set to "0", the aperiodic CSI reporting timing is (UL to send CSI after receiving CSI request). Time to subframe) is equal to k ₁ . Here, k ₁ means the time (timing) until the CSI is transmitted after receiving the aperiodic CSI transmission request through the RAR grant. If the PDCCH in subframe #i is detected with the associated RA-RNTI and the corresponding DL-SCH transport block includes a response to the transmitted preamble sequence, the UE according to the information of the response UL-SCH transport block Is transmitted in the first subframe # i + k ₁ , where k ₁ is greater than or equal to 6, and if the UL delay field is set to “0”, subframe # i + k ₁ is used for PUSCH transmission. It is the first UL subframe capable of aperiodic CSI reporting. If the UL delay field is set to '1', the PUSCH transmission is deferred to the UL subframe capable of the aperiodic CSI report immediately following the subframe # i + k ₁ .

30 is a block diagram illustrating a base station and a terminal for transmitting control information according to an embodiment of the present invention.

Referring to FIG. 30, according to an example (Embodiment 1) of the present invention, the terminal 3000 includes a terminal receiver 3005, a terminal processor 3010, and a terminal transmitter 3020.

The terminal receiver 3005 may receive a PDCCH or PHICH from the base station 3050. The PDCCH may include PUSCH timing information configured by the base station in the configuration method as illustrated in FIGS. 9 to 14. The PDCCH may be received from the first serving cell and the PHICH from the second serving cell.

The processor 3010 may configure HARQ timing information in the same manner as in FIGS. 9 to 14. HARQ timing information may be configured based on the PDCCH or the PHICH.

The terminal transmitter 3020 transmits a PUSCH to the base station 3050 based on the HARQ timing information.

The base station 3050 includes a base station transmitter 3055, a base station receiver 3060, and a base station processor 3070.

The base station transmitter 3055 transmits the PDCCH or PHICH to the terminal 3000. In this case, the PUSCH timing information applied to the terminal may be transmitted together.

The base station receiver 3060 may receive a PUSCH from the terminal 3000 and simultaneously receive HARQ timing information of the corresponding PUSCH.

The base station processor 3070 may configure the PUSCH timing information by using the method described with reference to FIGS. 9 to 14. The PUSCH timing information may be transmitted from the base station transmitter 3055 to the terminal 3000 together with the PDCCH or PHICH.

According to another example (Embodiment 2) of the present invention, the terminal receiver 3005 may receive a PDCCH or PHICH from the base station 3050. In performing UL HARQ based on the PDCCH or PHICH, the UL HARQ timing information may be configured by the configuration method as shown in FIGS. 16 to 17, and the terminal may include such UL HARQ timing information in advance.

The processor 3010 may configure HARQ timing information. In this case, HARQ timing information may be configured in the same manner as in FIGS. 16 to 17.

The terminal transmitter 3020 transmits a PUSCH to the base station 3050 based on the HARQ timing information.

The base station transmitter 3055 transmits the PDCCH or PHICH to the terminal 3000. In this case, UL HARQ timing information applied to the terminal may be transmitted together.

The base station receiver 3060 may receive a PUSCH from the terminal 3000 and simultaneously receive UL HARQ timing information for the corresponding PUSCH.

The base station processor 3070 may configure UL HARQ timing information using the method described with reference to FIGS. 16 to 17. The UL HARQ timing information may be transmitted from the base station transmitter 3055 to the terminal 3000 by transmitting ABS or fake subframe pattern related information along with the PDCCH or PHICH.

According to another embodiment (Embodiment 3) of the present invention, the terminal receiver 3005 receives a TDD up / down configuration message as shown in Tables 26 to 45 from the base station 3050, and the terminal processor 3010. To pass). In addition, the terminal receiver 3005 receives the PDCCH on each serving cell. Or, from the base station 3050 receives a DCI format or RSR grant including a CSI request field. In this case, the terminal receiver 3005 may receive a plurality of transport blocks over at least one downlink subframe.

The terminal processor 3010 applies a TDD configuration specific to each serving cell or a band specific to the serving cell configured in the terminal 3000 according to the TDD configuration. For example, TDD configuration 0 may be applied to the primary serving cell and TDD configuration 1 may be applied to the secondary serving cell. In addition, the terminal processor 3010 is a primary serving cell in which uplink transmission or downlink transmission is performed according to a first uplink / downlink configuration, and secondary serving in which uplink transmission or downlink transmission is performed according to a second uplink / downlink configuration. The cell may be configured in the terminal 3000.

In addition, the terminal processor 3010 applies the transmission power of the terminal based on the TPC command included in the PDCCH received by the terminal receiver 3005. In this case, after determining an adaptive TPC command reception timing based on uplink / downlink configuration for each serving cell in advance, the transmission power may be applied by receiving the TPC command. In addition, the DCI format of the PDCCH may further include an UL index.

In addition, the terminal processor 3010 may determine in advance the aperiodic CSI report timing for performing the aperiodic CSI report from the received CSI request field. At this time, it may be determined based on the TDD setting for each serving cell.

The terminal transmitter 3020 transmits a PUSCH, SRS or PUCCH to the base station 3050 through the following serving cell based on the controlled transmission power.

In addition, the terminal transmitter 3020 may transmit a PUSCH for performing the aperiodic CSI report to the base station 3050.

The base station 3050 includes a base station transmitter 3055, a base station receiver 3060, and a base station processor 3070.

The base station transmitter 3055 may configure a TDD configuration message as shown in Table 27 or Table 56 and transmit the same to the terminal 3000. In addition, the base station transmitter 3055 transmits the PDCCH including the TPC command to the terminal 3000 through the ordering serving cell based on the TDD setting of each serving cell. In addition, the DCI format of the PDCCH may further include an UL index. In addition, the base station transmitter 3055 may transmit a DCI format or RAR grant to the terminal 3000 including a CSI request field for requesting an aperiodic CSI report.

The base station receiver 3060 receives a PUSCH, an SRS, or a PUCCH from the terminal 3000 based on the controlled transmission power. In addition, the base station receiver 3060 receives a PUSCH including an aperiodic CSI report from the terminal 3000.

The above description is merely illustrative of the technical idea of the present invention, and those skilled in the art to which the present invention pertains may make various modifications and changes without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are not intended to limit the technical idea of the present invention but to describe the present invention, and the scope of the technical idea of the present invention is not limited thereto. The protection scope of the present invention should be interpreted by the following claims, and all technical ideas within the equivalent scope should be interpreted as being included in the scope of the present invention.

Claims (14)

In the method for transmitting uplink control information by a terminal in a wireless communication system, Receiving a physical downlink control channel (PDCCH) to which an uplink grant is mapped from a base station through a first serving cell; Receiving a Physical Hybrid Automatic Repeat Request Indicator Channel (PHICH) from the base station through a second serving cell; And Transmitting an uplink hybrid automatic repeat request (HARQ) based on the uplink grant to the base station through a physical uplink shared channel (PUSCH), When the time division duplex (TDD) uplink / downlink configuration of the first serving cell and the TDD uplink / downlink configuration of the second serving cell are not the same, the PHICH reception timing is determined by the first serving. Defined as a position corresponding to a downlink subframe of a cell, And the PUSCH transmission timing is determined such that a sum of the PHICH reception timing and the PUSCH transmission timing becomes a minimum value. The method of claim 1, The PUSCH transmission timing is within 7ms after 4ms after receiving the uplink grant, The PHICH reception timing is within 4ms after 4ms after transmitting the PUSCH. The method of claim 1, Control information transmission method, characterized in that configured to receive the uplink grant and the PHICH at the same time when the scheduling information for the second serving cell or the PHICH through a downlink subframe in the first serving cell . The method of claim 1, The uplink index, which is a 2-bit bitmap indicator indicating the timing of transmitting the PUSCH, is included in the PDCCH. The uplink index is a control information transmission method, characterized in that for scheduling the uplink subframe of the second serving cell based on the downlink subframe of the first serving cell. The method of claim 4, wherein The timing of transmitting the PUSCH and the timing of receiving the PHICH are configured such that HARQ Round Trip Time (RTT) is less than or equal to 20 ms, respectively. A method for receiving uplink control information by a base station in a wireless communication system, Transmitting a physical downlink control channel (PDCCH) to which an uplink grant is mapped to a terminal through a first serving cell; Transmitting a physical hybrid automatic repeat request indicator channel (PHICH) to the terminal through a second serving cell; And Receiving an uplink hybrid automatic repeat request (HARQ) from the terminal through a physical uplink shared channel (PUSCH) based on the uplink grant, When the time division duplex (TDD) uplink / downlink configuration of the first serving cell and the TDD uplink / downlink configuration of the second serving cell are not the same, the PHICH transmission timing is determined by the first serving cell. Defined as a position corresponding to a downlink subframe of a cell, And the PUSCH transmission timing is determined such that a sum of the PHICH transmission timing and the PUSCH transmission timing becomes a minimum value. The method of claim 6, The PUSCH reception timing is within 7ms after 4ms after transmitting the uplink grant, The PHICH transmission timing is within 7ms after 4ms after receiving the PUSCH control information receiving method. The method of claim 6, Control information receiving method, characterized in that configured to transmit the uplink grant and the PHICH at the same time when the scheduling information for the second serving cell or the PHICH through a downlink subframe in the first serving cell . The method of claim 6, The uplink index, which is a 2-bit bitmap indicator indicating the timing of receiving the PUSCH, is included in the PDCCH. And wherein the uplink index schedules an uplink subframe of the second serving cell based on a downlink subframe of the first serving cell. The method of claim 9, The timing of receiving the PUSCH and the timing of transmitting the PHICH are configured such that HARQ RTT (Round Trip Time) is less than or equal to 20ms, respectively. In a terminal for transmitting uplink control information in a wireless communication system, Receive a Physical Downlink Control Channel (PDCCH) to which an uplink grant is mapped from a base station through a first serving cell, and receive a Physical Hybrid Automatic Repeat Request Indicator Channel (PHICH). A receiver which receives from the base station through a second serving cell; And A transmitter for transmitting an uplink hybrid automatic repeat request (HARQ) based on the uplink grant to the base station through a physical uplink shared channel (PUSCH), When the time division duplex (TDD) uplink / downlink configuration of the first serving cell and the TDD uplink / downlink configuration of the second serving cell are not the same, the PHICH reception timing is determined by the first serving. Defined as a position corresponding to a downlink subframe of a cell, The PUSCH transmission timing is determined so that the sum of the PHICH reception timing and the PUSCH transmission timing is a minimum value. The method of claim 11, The transmitter transmits the PUSCH within 4ms after 4ms after receiving the uplink grant, The receiver, characterized in that for receiving the PHICH within 7ms after 4ms after transmitting the PUSCH. The method of claim 11, The receiving unit, And receiving the uplink grant and the PHICH simultaneously when receiving scheduling information or the PHICH for the second serving cell through a downlink subframe in the first serving cell. A base station for receiving uplink control information in a wireless communication system, A physical downlink control channel (PDCCH) to which an uplink grant is mapped is transmitted to a terminal through a first serving cell, and a physical hybrid automatic repeat request indicator channel (PHICH) is transmitted. A transmitter for transmitting to the terminal through a second serving cell; And On the basis of the uplink grant includes a receiving unit for receiving an uplink hybrid automatic repeat request (HARQ) from the terminal through a physical uplink shared channel (PUSCH), When the time division duplex (TDD) uplink / downlink configuration of the first serving cell and the TDD uplink / downlink configuration of the second serving cell are not the same, the PHICH transmission timing is determined by the first serving cell. Defined as a position corresponding to a downlink subframe of a cell, The PUSCH transmission timing is determined so that the sum of the PHICH transmission timing and the PUSCH transmission timing is a minimum value.

Images