Method and terminal for transmitting uplink control channel in wireless communication system

BACKGROUND OF THE INVENTION

0001Field of the Invention

0002The present invention relates to mobile communication.

0003Related Art

00043GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) that is an advancement of UMTS (Universal Mobile Telecommunication System) is being introduced with 3GPP release 8. In 3GPP LTE, OFDMA (orthogonal frequency division multiple access) is used for downlink, and SC-FDMA (single carrier-frequency division multiple access) is used for uplink. The 3GPP LTE adopts MIMO (multiple input multiple output) having maximum four antennas. Recently, a discussion of 3GPP LTE-A (LTE-Advanced) which is the evolution of the 3GPP LTE is in progress.

0005As set forth in 3GPP TS 36.211 V10.4.0, the physical channels in 3GPP LTE may be classified into data channels such as PDSCH (physical downlink shared channel) and PUSCH (physical uplink shared channel) and control channels such as PDCCH (physical downlink control channel), PCFICH (physical control format indicator channel), PHICH (physical hybrid-ARQ indicator channel) and PUCCH (physical uplink control channel).

0006Meanwhile, research on communication that is carried out between devices or between a device and a server without any human interaction, i.e., without any human intervention, i.e., machine type communication (MTC) has recently been extensively carried out. MTC refers to a concept of establishing communication between mechanical devices, and not equipments used by humans, by using the conventional wireless communication network.

0007Since the characteristics of the MTC are different from general user equipments, services that are optimized for the MTC may be different from services that are optimized for human-to-human communication. In comparison with the current Mobile Network Communication Service, the MTC can be characterized as different market scenarios, data communication, lower cost and less effort, a potentially large number of MTC devices, wider service areas, lower traffic per MTC device, and so on.

0008Recently, enhancing (or extending) the cell coverage of a base station has been considered, and diverse methods for cell coverage extension (or cell coverage enhancement) are being discussed. However, in case the coverage of the cell is extended (or enhanced) if the base station transmits a channel as when performing transmission to a general UE, a MTC device that is located in the cell coverage enhancement region may have difficulty in receiving the transmitted channel.

0009Additionally, it may be expected that the MTC devices have low performance in order to have its supply rate increased at lower costs. And, in case of transmitting the PDCCH, EPDCCH or PDSCH just as when transmitting to a general user equipment, the MTC device that is located in the cell coverage enhancement region may have difficulty in receiving the transmitted channel.

0010Additionally, in case the MTC device transmits PUCCH and PUSCH, which correspond to uplink channels, by using a general method, the base station may have difficulty in receiving the transmitted channel from the MTC device, which is located in the cell coverage enhancement region.

SUMMARY OF THE INVENTION

0011The present invention has been made in an effort to solve the above-discussed problem.

0012To achieve the foregoing aspect, a method according to a disclosure of the present specification is a method for a terminal to transmit a physical uplink control channel (PUCCH), which may include: receiving a plurality of explicit configuration information on a PUCCH resource through higher-layer signaling when a PUCCH needs to be repeatedly transmitted on a plurality of subframes; determining a PUCCH resource for transmitting the PUCCH based on the plurality of explicit configuration information; and repeatedly transmitting the PUCCH on the determined PUCCH resource over the plurality of subframes, wherein the PUCCH resource for transmitting the PUCCH may be determined based on at least one of a PDCCH, an EPDCCH, and an identification (ID) of the terminal, which are previously received.

0013Further, a previously received physical downlink shared channel (PDSCH) may be scheduled by the previously received PDCCH or EPDCCH, and the PUCCH may include ACK/NACK information in response to the previously received PDSCH.

0014Further, the previously received PDCCH or EPDCCH may be repeatedly transmitted on a plurality of downlink subframes according to a repetition level, the previously received PDCCH may be received by monitoring a plurality of PDCCH candidates, and the previously received EPDCCH may be received by monitoring a plurality of EPDCCH candidates.

0015Further, the PUCCH resource for transmitting the PUCCH may be determined based on a total aggregate resource (TAR) value for a PDCCH candidate from which the previously received PDCCH is retrieved among the plurality of PDCCH candidates, and the TAR value for the PDCCH candidate may be determined based on a repetition level and the number of resources per subframe for the previously received PDCCH.

0016Further, the PUCCH resource for transmitting the PUCCH may be determined based on a maximum TAR value for the plurality of PDCCH candidates, the maximum TAR value may be a TAR value having a maximum value among respective TAR values for the plurality of PDCCH candidates, and the respective TAR values for the plurality of PDCCH candidates may be determined based on repetition levels and numbers of resources per subframe respectively for the plurality of PDCCH candidates.

0017Further, the ID of the terminal may be a cell radio network temporary identifier (C-RNTI).

0018Further, the PUCCH resource for transmitting the PUCCH may be determined based on a location of a first control channel element (CCE) of the previously received PDCCH or a first enhanced CCE (ECCE) of the previously received EPDCCH.

0019Further, the PUCCH resource for transmitting the PUCCH may be randomly determined based on a predetermined random sequence whenever a PUCCH transmission event occurs.

0020Further, the PUCCH resource for transmitting the PUCCH may be maintained the same while the PUCCH is repeatedly transmitted on the plurality of subframes.

0021Further, the random sequence may be determined based on a subframe index or system frame number (SFN).

0022Further, the random sequence may be a random sequence initialized based on at least one of the PDCCH, EPDCCH, and ID of the terminal, which are previously received.

0023To achieve the foregoing aspect, a terminal according to one disclosure of the present specification, which transmits a PUCCH, may include: an RF unit to receive a plurality of explicit configuration information on a PUCCH resource through higher-layer signaling when a PUCCH needs to be repeatedly transmitted on a plurality of subframes; and a processor to control the RF unit to determine a PUCCH resource for transmitting the PUCCH based on the plurality of explicit configuration information and to repeatedly transmit the PUCCH on the determined PUCCH resource over the plurality of subframes, wherein the PUCCH resource for transmitting the PUCCH may be determined based on at least one of a PDCCH, an EPDCCH, and an ID of the terminal, which are previously received.

0024According to the disclosure of this specification, the above-described problems of the related art may be resolved. Most particularly, according to the disclosure of this specification, the reception performance and the decoding performance of a MTC device (Machine Type Communication) device, which is positioned in a coverage enhancement region of a base station, may be enhanced.

BRIEF DESCRIPTION OF THE DRAWINGS

0025<figref idref="DRAWINGS">FIG. 1</figref> illustrates a wireless communication system.

0026<figref idref="DRAWINGS">FIG. 2</figref> illustrates a structure of a radio frame according to an FDD in a 3GPP LTE.

0027<figref idref="DRAWINGS">FIG. 3</figref> illustrates the architecture of a downlink radio frame according to TDD in 3GPP LTE.

0028<figref idref="DRAWINGS">FIG. 4</figref> is an exemplary diagram illustrating a resource grid with respec to one uplink or downlink slot in a 3GPP LTE.

0029<figref idref="DRAWINGS">FIG. 5</figref> illustrates the architecture of a downlink sub-frame.

0030<figref idref="DRAWINGS">FIG. 6</figref> illustrates an exemplary of resource mapping of a PDCCH.

0031<figref idref="DRAWINGS">FIG. 7</figref> illustrates an exemplary diagram showing monitoring of the PDCCH.

0032<figref idref="DRAWINGS">FIG. 8</figref> illustrates a structure of an uplink subframe in 3GPP LTE.

0033<figref idref="DRAWINGS">FIG. 9</figref> illustrates an example of a subframe having an EPDCCH.

0034<figref idref="DRAWINGS">FIG. 10</figref> illustrates an example of a PRB pair.

0035<figref idref="DRAWINGS">FIG. 11</figref> illustrates a PUCCH and a PUSCH within an uplink subframe.

0036<figref idref="DRAWINGS">FIG. 12<i>a </i></figref>illustrates drawing showing a contention based random access method.

0037<figref idref="DRAWINGS">FIG. 12<i>b </i></figref>illustrates drawing showing a non-contention based random access method.

0038<figref idref="DRAWINGS">FIG. 13<i>a </i></figref>illustrates an exemplary of MTC (Machine Type communication).

0039<figref idref="DRAWINGS">FIG. 13<i>b </i></figref>illustrates an example of cell coverage enhancement for MTC devices.

0040<figref idref="DRAWINGS">FIG. 14<i>a </i></figref>and <figref idref="DRAWINGS">FIG. 14<i>b </i></figref>illustrate exemplary diagrams respectively showing examples of a bundle of (E)PDCCHs and a bundle of PDSCHs being transmitted.

0041<figref idref="DRAWINGS">FIG. 15</figref> illustrates an example of a TAR for an (E)PDCCH according to one disclosure of the present specification.

0042<figref idref="DRAWINGS">FIG. 16</figref> illustrates a problem that two PUCCH resources overlap when a (E)PDCCH for an MTC device and a (E)PDCCH for a legacy UE have the same first (E)CCE.

0043<figref idref="DRAWINGS">FIG. 17</figref> illustrates a problem that two PUCCH resources overlap when (E)PDCCHs for two MTC devices have the same first (E)CCE.

0044<figref idref="DRAWINGS">FIG. 18</figref> is a block diagram illustrating a wireless communication system according to a disclosure of the present specification.

DESCRIPTION OF EXEMPLARY EMBODIMENTS

0045Hereinafter, based on 3rd Generation Partnership Project (3GPP) long term evolution (LTE) or 3GPP LTE-advanced (LTE-A), the present invention will be applied. This is just an example, and the present invention may be applied to various wireless communication systems. Hereinafter, LTE includes LTE and/or LTE-A.

0046The technical terms used herein are used to merely describe specific embodiments and should not be construed as limiting the present invention. Further, the technical terms used herein should be, unless defined otherwise, interpreted as having meanings generally understood by those skilled in the art but not too broadly or too narrowly. Further, the technical terms used herein, which are determined not to exactly represent the spirit of the invention, should be replaced by or understood by such technical terms as being able to be exactly understood by those skilled in the art. Further, the general terms used herein should be interpreted in the context as defined in the dictionary, but not in an excessively narrowed manner.

0047The expression of the singular number in the present invention includes the meaning of the plural number unless the meaning of the singular number is definitely different from that of the plural number in the context. In the following description, the term ‘include’ or ‘have’ may represent the existence of a feature, a number, a step, an operation, a component, a part or the combination thereof described in the present invention, and may not exclude the existence or addition of another feature, another number, another step, another operation, another component, another part or the combination thereof.

0048The terms ‘first’ and ‘second’ are used for the purpose of explanation about various components, and the components are not limited to the terms ‘first’ and ‘second’. The terms ‘first’ and ‘second’ are only used to distinguish one component from another component. For example, a first component may be named as a second component without deviating from the scope of the present invention.

0049It will be understood that when an element or layer is referred to as being “connected to” or “coupled to” another element or layer, it can be directly connected or coupled to the other element or layer or intervening elements or layers may be present. In contrast, when an element is referred to as being “directly connected to” or “directly coupled to” another element or layer, there are no intervening elements or layers present.

0050Hereinafter, exemplary embodiments of the present invention will be described in greater detail with reference to the accompanying drawings. In describing the present invention, for ease of understanding, the same reference numerals are used to denote the same components throughout the drawings, and repetitive description on the same components will be omitted. Detailed description on well-known arts which are determined to make the gist of the invention unclear will be omitted. The accompanying drawings are provided to merely make the spirit of the invention readily understood, but not should be intended to be limiting of the invention. It should be understood that the spirit of the invention may be expanded to its modifications, replacements or equivalents in addition to what is shown in the drawings.

0051As used herein, ‘base station’ generally refers to a fixed station that communicates with a wireless device and may be denoted by other terms such as eNB (evolved-NodeB), BTS (base transceiver system), or access point.

0052As used herein, ‘user equipment (UE)’ may be stationary or mobile, and may be denoted by other terms such as device, wireless device, terminal, MS (mobile station), UT (user terminal), SS (subscriber station), MT (mobile terminal) and etc.

0053<figref idref="DRAWINGS">FIG. 1</figref> illustrates a wireless communication system.

0054As seen with reference to <figref idref="DRAWINGS">FIG. 1</figref>, the wireless communication system includes at least one base station (BS) <b>20</b>. Each base station <b>20</b> provides a communication service to specific geographical areas (generally, referred to as cells) <b>20</b><i>a</i>, <b>20</b><i>b</i>, and <b>20</b><i>c</i>. The cell can be further divided into a plurality of areas (sectors).

0055The UE generally belongs to one cell and the cell to which the UE belong is referred to as a serving cell. A base station that provides the communication service to the serving cell is referred to as a serving BS. Since the wireless communication system is a cellular system, another cell that neighbors to the serving cell is present. Another cell which neighbors to the serving cell is referred to a neighbor cell. A base station that provides the communication service to the neighbor cell is referred to as a neighbor BS. The serving cell and the neighbor cell are relatively determined based on the UE.

0056Hereinafter, a downlink means communication from the base station <b>20</b> to the UE <b>10</b> and an uplink means communication from the UE <b>10</b> to the base station <b>20</b>. In the downlink, a transmitter may be a part of the base station <b>20</b> and a receiver may be a part of the UE <b>10</b>. In the uplink, the transmitter may be a part of the UE <b>10</b> and the receiver may be a part of the base station <b>20</b>.

0057Meanwhile, the wireless communication system may be generally divided into a frequency division duplex (FDD) type and a time division duplex (TDD) type. According to the FDD type, uplink transmission and downlink transmission are achieved while occupying different frequency bands. According to the TDD type, the uplink transmission and the downlink transmission are achieved at different time while occupying the same frequency band. A channel response of the TDD type is substantially reciprocal. This means that a downlink channel response and an uplink channel response are approximately the same as each other in a given frequency area. Accordingly, in the TDD based wireless communication system, the downlink channel response may be acquired from the uplink channel response. In the TDD type, since an entire frequency band is time-divided in the uplink transmission and the downlink transmission, the downlink transmission by the base station and the uplink transmission by the terminal may not be performed simultaneously. In the TDD system in which the uplink transmission and the downlink transmission are divided by the unit of a sub-frame, the uplink transmission and the downlink transmission are performed in different sub-frames.

0058Hereinafter, the LTE system will be described in detail.

0059<figref idref="DRAWINGS">FIG. 2</figref> shows a downlink radio frame structure according to FDD of 3rd generation partnership project (3GPP) long term evolution (LTE).

0060The radio frame of <figref idref="DRAWINGS">FIG. 2</figref> may be found in the section 5 of 3GPP TS 36.211 V10.4.0 (2011-12) “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation (Release 10)”.

0061The radio frame includes 10 sub-frames indexed 0 to 9. One sub-frame includes two consecutive slots. Accordingly, the radio frame includes 20 slots. The time taken for one sub-frame to be transmitted is denoted TTI (transmission time interval). For example, the length of one sub-frame may be lms, and the length of one slot may be 0.5 ms.

0062The structure of the radio frame is for exemplary purposes only, and thus the number of sub-frames included in the radio frame or the number of slots included in the sub-frame may change variously.

0063Meanwhile, one slot may include a plurality of orthogonal frequency division multiplexing (OFDM) symbols. The number of OFDM symbols included in one slot may vary depending on a cyclic prefix (CP). One slot includes 7 OFDM symbols in case of a normal CP, and one slot includes 6 OFDM symbols in case of an extended CP. Herein, since the 3GPP LTE uses orthogonal frequency division multiple access (OFDMA) in a downlink (DL), the OFDM symbol is only for expressing one symbol period in a time domain, and there is no limitation in a multiple access scheme or terminologies. For example, the OFDM symbol may also be referred to as another terminology such as a single carrier frequency division multiple access (SC-FDMA) symbol, a symbol period, etc.

0064<figref idref="DRAWINGS">FIG. 3</figref> illustrates the architecture of a downlink radio frame according to TDD in 3GPP LTE.

0065For this, 3GPP TS 36.211 V8.7.0 (2009-05) “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation (Release 8)”, Ch. 4 may be referenced, and this is for TDD (time division duplex).

0066Sub-frames having index #1 and index #6 are denoted special sub-frames, and include a DwPTS (Downlink Pilot Time Slot: DwPTS), a GP (Guard Period) and an UpPTS (Uplink Pilot Time Slot). The DwPTS is used for initial cell search, synchronization, or channel estimation in a terminal. The UpPTS is used for channel estimation in the base station and for establishing uplink transmission sync of the terminal. The GP is a period for removing interference that arises on uplink due to a multi-path delay of a downlink signal between uplink and downlink.

0067In TDD, a DL (downlink) sub-frame and a UL (Uplink) co-exist in one radio frame. Table 1 shows an example of configuration of a radio frame.

0000<tables id="TABLE-US-00001" num="00001"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="35pt" align="center" /><colspec colname="2" colwidth="182pt" align="right" /><thead><row><entry namest="1" nameend="2" rowsep="1">TABLE 1</entry></row></thead><tbody valign="top"><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>UL-DL</entry><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="35pt" align="center" /><colspec colname="2" colwidth="42pt" align="center" /><colspec colname="3" colwidth="140pt" align="center" /><tbody valign="top"><row><entry>configu-</entry><entry>Switch-point</entry><entry>Subframe index</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="12"><colspec colname="1" colwidth="35pt" align="center" /><colspec colname="2" colwidth="42pt" align="center" /><colspec colname="3" colwidth="14pt" align="center" /><colspec colname="4" colwidth="14pt" align="center" /><colspec colname="5" colwidth="14pt" align="center" /><colspec colname="6" colwidth="14pt" align="center" /><colspec colname="7" colwidth="14pt" align="center" /><colspec colname="8" colwidth="14pt" align="center" /><colspec colname="9" colwidth="14pt" align="center" /><colspec colname="10" colwidth="14pt" align="center" /><colspec colname="11" colwidth="14pt" align="center" /><colspec colname="12" colwidth="14pt" align="center" /><tbody valign="top"><row><entry>raiton</entry><entry>periodicity</entry><entry>0</entry><entry>1</entry><entry>2</entry><entry>3</entry><entry>4</entry><entry>5</entry><entry>6</entry><entry>7</entry><entry>8</entry><entry>9</entry></row><row><entry namest="1" nameend="12" align="center" rowsep="1" /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="13"><colspec colname="1" colwidth="35pt" align="center" /><colspec colname="2" colwidth="21pt" align="right" /><colspec colname="3" colwidth="21pt" align="left" /><colspec colname="4" colwidth="14pt" align="center" /><colspec colname="5" colwidth="14pt" align="center" /><colspec colname="6" colwidth="14pt" align="center" /><colspec colname="7" colwidth="14pt" align="center" /><colspec colname="8" colwidth="14pt" align="center" /><colspec colname="9" colwidth="14pt" align="center" /><colspec colname="10" colwidth="14pt" align="center" /><colspec colname="11" colwidth="14pt" align="center" /><colspec colname="12" colwidth="14pt" align="center" /><colspec colname="13" colwidth="14pt" align="center" /><tbody valign="top"><row><entry>0</entry><entry>5</entry><entry>ms</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>U</entry><entry>U</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>U</entry><entry>U</entry></row><row><entry>1</entry><entry>5</entry><entry>ms</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>U</entry><entry>D</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>U</entry><entry>D</entry></row><row><entry>2</entry><entry>5</entry><entry>ms</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>D</entry><entry>D</entry></row><row><entry>3</entry><entry>10</entry><entry>ms</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>U</entry><entry>U</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>D</entry></row><row><entry>4</entry><entry>10</entry><entry>ms</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>U</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>D</entry></row><row><entry>5</entry><entry>10</entry><entry>ms</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>D</entry><entry>D</entry></row><row><entry>6</entry><entry>5</entry><entry>ms</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>U</entry><entry>U</entry><entry>D</entry><entry>S</entry><entry>U</entry><entry>U</entry><entry>D</entry></row><row><entry namest="1" nameend="13" align="center" rowsep="1" /></row><row><entry namest="1" nameend="13" align="left" id="FOO-00001">‘D’ denotes a DL sub-frame, ‘U’ a UL sub-frame, and ‘S’ a special sub-frame. When receiving a UL-DL configuration from the base station, the terminal may be aware of whether a sub-frame is a DL sub-frame or a UL sub-frame according to the configuration of the radio frame.</entry></row></tbody></tgroup></table></tables>

0068<figref idref="DRAWINGS">FIG. 4</figref> illustrates an example resource grid for one uplink or downlink slot in 3GPP LTE.

0069Referring to <figref idref="DRAWINGS">FIG. 4</figref>, the uplink slot includes a plurality of OFDM (orthogonal frequency division multiplexing) symbols in the time domain and NRB resource blocks (RBs) in the frequency domain. For example, in the LTE system, the number of resource blocks (RBs), i.e., N_RB, may be one from 6 to 110.

0070The resource block is a unit of resource allocation and includes a plurality of sub-carriers in the frequency domain. For example, if one slot includes seven OFDM symbols in the time domain and the resource block includes 12 sub-carriers in the frequency domain, one resource block may include 7×12 resource elements (REs).

0071<figref idref="DRAWINGS">FIG. 5</figref> illustrates the architecture of a downlink sub-frame.

0072In <figref idref="DRAWINGS">FIG. 5</figref>, assuming the normal CP, one slot includes seven OFDM symbols, by way of example.

0073The DL (downlink) sub-frame is split into a control region and a data region in the time domain. The control region includes up to first three OFDM symbols in the first slot of the sub-frame. However, the number of OFDM symbols included in the control region may be changed. A PDCCH (physical downlink control channel) and other control channels are assigned to the control region, and a PDSCH is assigned to the data region.

0074The physical channels in 3GPP LTE may be classified into data channels such as PDSCH (physical downlink shared channel) and PUSCH (physical uplink shared channel) and control channels such as PDCCH (physical downlink control channel), PCFICH (physical control format indicator channel), PHICH (physical hybrid-ARQ indicator channel) and PUCCH (physical uplink control channel).

0075The PCFICH transmitted in the first OFDM symbol of the sub-frame carries CIF (control format indicator) regarding the number (i.e., size of the control region) of OFDM symbols used for transmission of control channels in the sub-frame. The wireless device first receives the CIF on the PCFICH and then monitors the PDCCH.

0076Unlike the PDCCH, the PCFICH is transmitted through a fixed PCFICH resource in the sub-frame without using blind decoding.

0077The PHICH carries an ACK (positive-acknowledgement)/NACK (negative-acknowledgement) signal for a UL HARQ (hybrid automatic repeat request). The ACK/NACK signal for UL (uplink) data on the PUSCH transmitted by the wireless device is sent on the PHICH.

0078The PBCH (physical broadcast channel) is transmitted in the first four OFDM symbols in the second slot of the first sub-frame of the radio frame. The PBCH carries system information necessary for the wireless device to communicate with the base station, and the system information transmitted through the PBCH is denoted MIB (master information block). In comparison, system information transmitted on the PDSCH indicated by the PDCCH is denoted SIB (system information block).

0079The PDCCH may carry activation of VoIP (voice over internet protocol) and a set of transmission power control commands for individual UEs in some UE group, resource allocation of an upper layer control message such as a random access response transmitted on the PDSCH, system information on DL-SCH, paging information on PCH, resource allocation information of UL-SCH (uplink shared channel), and resource allocation and transmission format of DL-SCH (downlink-shared channel). A plurality of PDCCHs may be sent in the control region, and the terminal may monitor the plurality of PDCCHs. The PDCCH is transmitted on one CCE (control channel element) or aggregation of some consecutive CCEs. The CCE is a logical allocation unit used for providing a coding rate per radio channel's state to the PDCCH. The CCE corresponds to a plurality of resource element groups. Depending on the relationship between the number of CCEs and coding rates provided by the CCEs, the format of the PDCCH and the possible number of PDCCHs are determined.

0080Control information transmitted through the PDCCH is referred to as downlink control information (DCI). The DCI may include resource allocation of the PDSCH (this is referred to as a DL grant), resource allocation of a PUSCH (this is referred to as a UL grant), a set of transmit power control commands for individual UEs in any UE group, and/or activation of a voice over Internet protocol (VoIP).

0081The base station determines a PDCCH format according to the DCI to be sent to the terminal and adds a CRC (cyclic redundancy check) to control information. The CRC is masked with a unique identifier (RNTI; radio network temporary identifier) depending on the owner or purpose of the PDCCH. In case the PDCCH is for a specific terminal, the terminal's unique identifier, such as C-RNTI (cell-RNTI), may be masked to the CRC. Or, if the PDCCH is for a paging message, a paging indicator, for example, P-RNTI (paging-RNTI) may be masked to the CRC. If the PDCCH is for a system information block (SIB), a system information identifier, SI-RNTI (system information-RNTI), may be masked to the CRC. In order to indicate a random access response that is a response to the terminal's transmission of a random access preamble, an RA-RNTI (random access-RNTI) may be masked to the CRC.

0082In 3GPP LTE, blind decoding is used for detecting a PDCCH. The blind decoding is a scheme of identifying whether a PDCCH is its own control channel by demasking a desired identifier to the CRC (cyclic redundancy check) of a received PDCCH (this is referred to as candidate PDCCH) and checking a CRC error. The base station determines a PDCCH format according to the DCI to be sent to the wireless device, then adds a CRC to the DCI, and masks a unique identifier (this is referred to as RNTI (radio network temporary identifier) to the CRC depending on the owner or purpose of the PDCCH.

0083<figref idref="DRAWINGS">FIG. 6</figref> illustrates an exemplary of resource mapping of a PDCCH.

0084R0 indicates a reference signal of a first antenna, R1 indicates a reference signal of a second antenna, R2 indicates a reference signal of a third antenna, and R3 indicates a reference signal of a fourth antenna.

0085A control region within a subframe includes a plurality of CCEs (control channel elements). A CCE refers to a logical allocation unit that is used for providing the PDCCH with a coding rate respective to the state of the radio channel, and the CCE corresponds to a plurality of REGs (resource element groups). A REG includes a plurality of resource elements. Depending on the co-relation between the number of CCEs and a coding rate that is being provided by the CCEs, a format of the PDCCH and a number of bits of an available PDCCH are determined.

0086The number of CCEs that is used for the transmission of the PDCCH is determined by the base station in accordance with the channel state. For example, for a user equipment having a good downlink channel state, one CCE may be used for the PDCCH transmission. For a user equipment having a poor downlink channel state, 8 CCEs may be used for the PDCCH transmission.

0087One REG (being indicated as a quadruplet in the drawing) includes 4 REs, and one CCE includes 9 REGs. In order to configured one PDCCH, {1, 2, 4, 8} CCEs may be used, and each of the elements {1, 2, 4, 8} is referred to as a CCE aggregation level.

0088A control channel that is configured of one or more CCEs performs REG-unit interleaving and, then, is mapped to a physical resource after having a cell-ID based cyclic shift performed thereon.

0089<figref idref="DRAWINGS">FIG. 7</figref> illustrates an exemplary diagram showing monitoring of the PDCCH.

0090The user equipment is incapable of knowing from which location within the control region its PDCCH is being transmitted and by using which CCE aggregation level or DCI format. Since multiple PDCCHs may be transmitted within one subframe, the user equipment monitors multiple PDCCHs for each subframe. Herein, monitoring refers to the user equipment attempting to decode the PDCCH in accordance with the PDCCH format.

0091In 3GPP LTE, in order to reduce any load (or burden) caused by blind decoding, a search space is used. The search space may also be referred to as a monitoring set of the CCE for the PDCCH. The user equipment monitors the PDCCH within the corresponding search space.

0092The search space is divided into a common search space and a UE-specific search space. The common search space corresponds to a space searching a PDCCH having common control information, and the common search space is configured of 16 CCEs corresponding to CCE indexes 0˜15 and supports a PDCCH having a CCE aggregation level of {4, 8}. However, a PDCCH (DCI formats 0 and 1A) carrying UE-specific information may also be transmitted to the common search space. The UE-specific search space supports a PDCCH having a CCE aggregation level of {1, 2, 4, 8}.

0093Table 2 shown below indicates a number of PDCCH candidates being monitored by a wireless device.

0000<tables id="TABLE-US-00002" num="00002"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="168pt" align="center" /><colspec colname="2" colwidth="49pt" align="center" /><thead><row><entry namest="1" nameend="2" rowsep="1">TABLE 2</entry></row></thead><tbody valign="top"><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry /><entry>Number of</entry></row><row><entry>Search space S^(L)_k</entry><entry>PDCCH</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="49pt" align="left" /><colspec colname="2" colwidth="70pt" align="center" /><colspec colname="3" colwidth="49pt" align="center" /><colspec colname="4" colwidth="49pt" align="center" /><tbody valign="top"><row><entry>Type</entry><entry>Aggregation Level L</entry><entry>Size [in CCEs]</entry><entry>candidates M^(L)</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="49pt" align="left" /><colspec colname="2" colwidth="70pt" align="center" /><colspec colname="3" colwidth="49pt" align="char" char="." /><colspec colname="4" colwidth="49pt" align="center" /><tbody valign="top"><row><entry>UE-specific</entry><entry>1</entry><entry>6</entry><entry>6</entry></row><row><entry /><entry>2</entry><entry>12</entry><entry>6</entry></row><row><entry /><entry>4</entry><entry>8</entry><entry>2</entry></row><row><entry /><entry>8</entry><entry>16</entry><entry>2</entry></row><row><entry>Common</entry><entry>4</entry><entry>16</entry><entry>4</entry></row><row><entry /><entry>8</entry><entry>16</entry><entry>2</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0094The size of the search space is determined by Table 2, and the starting point of the search space is defined differently for the common search space and the UE-specific search space. Although the starting point of the common search space is fixed regardless of the subframe, the starting point of the UE-specific search space may vary for each subframe in accordance with a UE identifier (e.g., C-RNTI), a CCE aggregation level, and/or a slot number within a radio frame. In case the starting point of the UE-specific search space is located within the common search space, the UE-specific search space and the common search space may overlap one another.

0095In the aggregation level Lε{1, 2, 4, 8}, the search space S^(L)_kis defined as a set (or group) of PDCCH candidates. The CCE corresponding to PDCCH candidate m of the search space S^(L)_kis given as described below.

0000<br /><i>L</i>{(<i>Y</i>_k<i>+m</i>′)mod └<i>N</i>_CCE,k<i>/L▪}+i</i>  [Equation 1]

0096Herein, i=0, 1, . . . , L−1, N_CCE,krepresents a total number of CCEs that can be used for the transmission of the PDCCH within the control region of subframe k. The control region includes a set of CCEs being numbered from 0 to N_CCE,k−1. M^(L)represents a number of PDCCH candidates at CCE aggregation level L in a given search space.

0097When a CIF (carrier indicator field) is configured in a wireless device, then, m′=m+M^(L)n_cif. n_cifrepresents a value of the CIF. If the CIF is not configured in the wireless device, then, m′=m.

0098In the common search space, Y_kis set (or configured) to 0 with respect to 2 aggregation levels L=4 and L=8.

0099In the UE-specific search space of the aggregation level L, the variable Y_kis defined as described below.

0000<br /><i>Y</i>_k=(<i>A·Y</i>_k-1)mod <i>D</i>  [Equation 2]

0100Herein, Y₋₁=n_RNTI≠0, A=39827, D=65537, k=floor(n_s/2), and n_srepresents a slot number within a radio frame.

0101When the user equipment monitors the PDCCH based on the C-RNTI, the DCI format that is to be monitored and the search space are determined in accordance with the transmission mode of the PDSCH.

0102Meanwhile, when the user equipment monitors the PDCCH based on the C-RNTI, the DCI format that is to be monitored and the search space are determined in accordance with the transmission mode (TM) of the PDSCH. The following Table shows an example of monitoring the PDCCH having a C-RNTI configured therein.

0000<tables id="TABLE-US-00003" num="00003"><table frame="none" colsep="0" rowsep="0" pgwide="1"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="42pt" align="left" /><colspec colname="2" colwidth="49pt" align="left" /><colspec colname="3" colwidth="49pt" align="left" /><colspec colname="4" colwidth="133pt" align="left" /><thead><row><entry namest="1" nameend="4" rowsep="1">TABLE 3</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry>Transmission</entry><entry /><entry /><entry>Transmission mode of PDSCH</entry></row><row><entry>Mode</entry><entry>DCI Format</entry><entry>Search Space</entry><entry>with respect to the PDCCH</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>Transmission</entry><entry>DCI Format</entry><entry>Common and</entry><entry>Single antenna port, Port 0</entry></row><row><entry>Mode 1</entry><entry>1A</entry><entry>UE-specific</entry></row><row><entry /><entry>DCI Format 1</entry><entry>UE-specific</entry><entry>Single antenna port, Port 0</entry></row><row><entry>Transmission</entry><entry>DCI Format</entry><entry>Common and</entry><entry>Transmit diversity</entry></row><row><entry>Mode 2</entry><entry>1A</entry><entry>UE-specific</entry></row><row><entry /><entry>DCI Format 1</entry><entry>UE-specific</entry><entry>Transmit diversity</entry></row><row><entry>Transmission</entry><entry>DCI Format</entry><entry>Common and</entry><entry>Transmit diversity</entry></row><row><entry>Mode 3</entry><entry>1A</entry><entry>UE-specific</entry></row><row><entry /><entry>DCI Format</entry><entry>UE-specific</entry><entry>CDD(Cyclic Delay Diversity) or</entry></row><row><entry /><entry>2A</entry><entry /><entry>Transmit diversity</entry></row><row><entry>Transmission</entry><entry>DCI Format</entry><entry>Common and</entry><entry>Transmit diversity</entry></row><row><entry>Mode 4</entry><entry>1A</entry><entry>UE-specific</entry></row><row><entry /><entry>DCI Format 2</entry><entry>UE-specific</entry><entry>Closed-loop spatial multiplexing</entry></row><row><entry>Transmission</entry><entry>DCI Format</entry><entry>Common and</entry><entry>Transmit diversity</entry></row><row><entry>Mode 5</entry><entry>1A</entry><entry>UE-specific</entry></row><row><entry /><entry>DCI Format</entry><entry>UE-specific</entry><entry>MU-MIMO(Multi-user Multiple Input</entry></row><row><entry /><entry>1D</entry><entry /><entry>Multiple Output)</entry></row><row><entry>Transmission</entry><entry>DCI Format</entry><entry>Common and</entry><entry>Transmit diversity</entry></row><row><entry>Mode 6</entry><entry>1A</entry><entry>UE-specific</entry></row><row><entry /><entry>DCI Format</entry><entry>UE-specific</entry><entry>Closed-loop spatial multiplexing</entry></row><row><entry /><entry>1B</entry></row><row><entry>Transmission</entry><entry>DCI Format</entry><entry>Common and</entry><entry>If the number of PBCH transmission</entry></row><row><entry>Mode 7</entry><entry>1A</entry><entry>UE-specific</entry><entry>ports is equal to 1, Single antenna port,</entry></row><row><entry /><entry /><entry /><entry>Port 0, if not, Transmit Diversity</entry></row><row><entry /><entry>DCI Format 1</entry><entry>UE-specific</entry><entry>Single antenna port, Port 5</entry></row><row><entry>Transmission</entry><entry>DCI Format</entry><entry>Common and</entry><entry>If the number of PBCH transmission</entry></row><row><entry>Mode 8</entry><entry>1A</entry><entry>UE-specific</entry><entry>ports is equal to 1, Single antenna port,</entry></row><row><entry /><entry /><entry /><entry>Port 0, if not, Transmit Diversity</entry></row><row><entry /><entry>DCI Format</entry><entry>UE-specific</entry><entry>Dual layer transmission (Port 7 or 8),</entry></row><row><entry /><entry>2B</entry><entry /><entry>or Single antenna port, Port 7 or 8</entry></row><row><entry>Transmission</entry><entry>DCI Format</entry><entry>Common and</entry><entry>Non-MBSFN Subframe: If the number of</entry></row><row><entry>Mode 9</entry><entry>1A</entry><entry>UE-specific</entry><entry>PBCH antenna ports is equal to 1, Port 0 is</entry></row><row><entry /><entry /><entry /><entry>used as a single antenna port, and, if not,</entry></row><row><entry /><entry /><entry /><entry>Transmit Diversity</entry></row><row><entry /><entry /><entry /><entry>MBSFN Subframe: Port 7 as a single</entry></row><row><entry /><entry /><entry /><entry>antenna port</entry></row><row><entry /><entry>DCI Format</entry><entry>UE-specific</entry><entry>Up to 8 transmission layers, Ports 7-14 are</entry></row><row><entry /><entry>2C</entry><entry /><entry>used, or Port 7 or Port 8 is used as a single</entry></row><row><entry /><entry /><entry /><entry>antenna port</entry></row><row><entry>Transmission</entry><entry>DCI Format</entry><entry>Common and</entry><entry>Non-MBSFN Subframe: If the number of</entry></row><row><entry>Mode 10</entry><entry>1A</entry><entry>UE-specific</entry><entry>PBCH antenna ports is equal to 1, Port 0 is</entry></row><row><entry /><entry /><entry /><entry>used as a single antenna port, and, if not,</entry></row><row><entry /><entry /><entry /><entry>Transmit Diversity</entry></row><row><entry /><entry /><entry /><entry>MBSFN Subframe: Port 7 as a single</entry></row><row><entry /><entry /><entry /><entry>antenna port</entry></row><row><entry /><entry>DCI Format</entry><entry>UE-specific</entry><entry>Up to 8 transmission layers, Ports 7-14 are</entry></row><row><entry /><entry>2D</entry><entry /><entry>used, or Port 7 or Port 8 is used as a single</entry></row><row><entry /><entry /><entry /><entry>antenna port</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0103The purposes of the DCI formats are differentiated as shown in the following table.

0000<tables id="TABLE-US-00004" num="00004"><table frame="none" colsep="0" rowsep="0" pgwide="1"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="56pt" align="left" /><colspec colname="2" colwidth="203pt" align="left" /><thead><row><entry namest="1" nameend="2" rowsep="1">TABLE 4</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>DCI Format</entry><entry>Content</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>DCI Format 0</entry><entry>Used for PUSCH scheduling</entry></row><row><entry>DCI Format 1</entry><entry>Used for scheduling of one PDSCH codeword</entry></row><row><entry>DCI Format 1A</entry><entry>Used for compact scheduling of one PDSCH codeword and</entry></row><row><entry /><entry>random access procedure</entry></row><row><entry>DCI Format 1B</entry><entry>Used for compact scheduling of one PDSCH codeword having</entry></row><row><entry /><entry>precoding information</entry></row><row><entry>DCI Format 1C</entry><entry>Used for a very compact scheduling of one PDSCH codeword</entry></row><row><entry>DCI Format 1D</entry><entry>Used for compact scheduling of one PDSCH codeword having</entry></row><row><entry /><entry>precoding and power offset information</entry></row><row><entry>DCI Format 2</entry><entry>Used for PDSCH scheduling of user equipments that are set to</entry></row><row><entry /><entry>the Closed-loop spatial multiplexing mode</entry></row><row><entry>DCI Format 2A</entry><entry>Used for PDSCH scheduling of user equipments that are set to</entry></row><row><entry /><entry>the Open-loop spatial multiplexing mode</entry></row><row><entry>DCI Format 2B</entry><entry>DCI Format 2B is used for the resource allocation for dual-layer</entry></row><row><entry /><entry>beamforming of the PDSCH.</entry></row><row><entry>DCI Format 2C</entry><entry>DCI Format 2C is used for the resource allocation for Closed-loop</entry></row><row><entry /><entry>SU-MIMO or MU-MIMO operations of up to 8 layers.</entry></row><row><entry>DCI Format 2D</entry><entry>DCI Format 2D is used for the resource allocation of up to 8 layers.</entry></row><row><entry>DCI Format 3</entry><entry>Used for the transmission of TPC commands of PUCCH and PUSCH</entry></row><row><entry /><entry>having 2-bit power adjustments</entry></row><row><entry>DCI Format 3A</entry><entry>Used for the transmission of TPC commands of PUCCH and PUSCH</entry></row><row><entry /><entry>having 1-bit power adjustments</entry></row><row><entry>DCI Format 4</entry><entry>Used for PUSCH scheduling of an uplink (UL) cell operating in the</entry></row><row><entry /><entry>multiple antenna port transmission mode</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0104<figref idref="DRAWINGS">FIG. 8</figref> illustrates a structure of an uplink subframe in 3GPP LTE.

0105Referring to <figref idref="DRAWINGS">FIG. 8</figref>, an uplink subframe may be divided into a control region and a data region in a frequency domain. The control region is allocated with a PUCCH (Physical Uplink Control Channel) for transmitting uplink control information. The data region is allocated with a PUSCH (Physical Uplink Shared Channel) for transmitting data (in some cases, the control information may also be transmitted along with the data).

0106The PUCCH respective to one UE is allocated in resource block pairs (RB pairs) in a subframe. The resource blocks belonging to the resource block pair respectively occupy different sub-carriers within a first slot and a second slot. The frequency that is occupied by the resource blocks belonging to the resource block pair that is allocated to the PUCCH is varied based on the slot boundary. This is referred to as the RB pair that is allocated to the PUCCH as being frequency-hopped at the slot boundary.

0107By transmitting the uplink control information through different sub-carriers in accordance with time, the UE may obtain frequency diversity gain. m corresponds to a position index indicating a logical frequency domain position of a resource block pair that is allocated to the PUCCH within a subframe.

0108The uplink control information being transmitted over the PUCCH may include HARQ (hybrid automatic repeat request) ACK (acknowledgement)/NACK (non-acknowledgement), CQI (channel quality indicator) indicating a downlink channel state, SR (scheduling request), which corresponds to a request for uplink radio resource allocation, and so on.

0109The PUSCH is mapped to UL-SCH, which corresponds to a transport channel. Uplink data that are transmitted over the PUSCH may correspond to a transport block, which is a data block for the UL-SCH that is transmitted during a Transmission Time Interval (TTI). The transport block may correspond to user information. Alternatively, the uplink data may correspond to multiplexed data. The multiplexed data may correspond to a multiplexed result of the transport block for the UL-SCH and the control information. For example, the control information being multiplexed to the data mat include CQI, PMI (precoding matrix indicator), HARQ, RI (rank indicator), and so on. Alternatively, the uplink data may also be configured only of the control information.

0110Hereinafter, a carrier aggregation (CA) system will be described.

0111A carrier aggregation (CA) system refers to aggregating multiple component carriers (CCs). Due to such carrier aggregation, the significance of the conventional cell has changed. According to carrier aggregation, a cell may refer to a set of downlink component carrier and uplink component carrier, or a cell may refer to a single downlink component carrier.

0112Additionally, in carrier aggregation, a cell may be divided into a primary cell, a secondary cell, and a serving cell. A primary cell refers to a cell that operates in a primary frequency, or a cell through which the UE performs an initial connection establishment procedure or a connection re-establishment procedure with the base station, or a cell that is designated as a primary cell during a handover procedure. A secondary cell refers to a cell that operates in a secondary frequency, and, once the RRC connection is established, the secondary cell is configured and used for providing additional radio resources.

0113As described above, unlike the single carrier system, a carrier aggregation system may support multiple component carriers (CCs), i.e., multiple serving cells.

0114Such carrier aggregation system may support cross-carrier scheduling. Cross-carrier scheduling corresponds to a scheduling method that can perform resource allocation of a PDSCH through a PDCCH, which is transmitted through a specific component carrier, wherein the PDSCH is transmitted through another component carrier, or a scheduling method that can perform resource allocation of a PDSCH that is transmitted through a component carrier other than the component carrier being essentially linked to the specific component carrier.

0115Meanwhile, the PDCCH is monitored in a restricted (or limited) region, which is referred to as a control region, within a subframe, and, in order to perform demodulation of the PDCCH, a CRS that is transmitted in all bands is used. As the types of control information become more diverse, and as the size of the control information becomes larger, flexibility in the scheduling is degraded when only using the legacy PDCCH. Additionally, in order to reduce any burden caused by the CRS transmission, an EPDCCH (enhanced PDCCH) is being adopted.

0116<figref idref="DRAWINGS">FIG. 9</figref> illustrates an example of a subframe having an EPDCCH.

0117A subframe may include zero or one PDCCH region <b>410</b> and zero or more EPDCCH regions <b>420</b> and <b>430</b>.

0118The EPDCCH regions <b>420</b> and <b>430</b> correspond to a region where the wireless device monitors the EPDCCH. Although the PDCCH region <b>410</b> is located within a maximum of 4 foremost OFDM symbols of the subframe, the EPDCCH regions <b>420</b> and <b>430</b> may be flexibly scheduled in the OFDM symbol after the PDCCH region <b>410</b>.

0119One or more EPDCCH regions <b>420</b> and <b>430</b> are designated in a wireless device), and the wireless device may monitor the EPDCCH from the designated EPDCCH regions <b>420</b> and <b>430</b>.

0120The number/location/size of the EPDCCH regions <b>420</b> and <b>430</b> and/or information on the subframe that is to monitor the EPDCCH may be notified by the base station to the wireless device through a RRC message, and so on.

0121In the PDCCH region <b>410</b>, the PDCCH may be demodulated based on the CRS. In the EPDCCH regions <b>420</b> and <b>430</b>, a DM (demodulation) RS may be defined instead of the CRS for the demodulation of the EPDCCH. An associated DM RS may be transmitted from the corresponding EPDCCH regions <b>420</b> and <b>430</b>.

0122A RS sequence r_ns(m) for the associated DM RS is as shown below in Equation 3.

0000<maths id="MATH-US-00001" num="00001"><math overflow="scroll"><mtable><mtr><mtd><mrow><mrow><msub><mi>r</mi><mrow><mi>l</mi><mo>,</mo><mi>ns</mi></mrow></msub><mo></mo><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow><mo>=</mo><mrow><mrow><mfrac><mn>1</mn><msqrt><mn>2</mn></msqrt></mfrac><mo></mo><mrow><mo>(</mo><mrow><mn>1</mn><mo>-</mo><mrow><mn>2</mn><mo>·</mo><mrow><mi>c</mi><mo></mo><mrow><mo>(</mo><mrow><mn>2</mn><mo></mo><mi>m</mi></mrow><mo>)</mo></mrow></mrow></mrow></mrow><mo>)</mo></mrow></mrow><mo>+</mo><mrow><mi>j</mi><mo></mo><mfrac><mn>1</mn><msqrt><mn>2</mn></msqrt></mfrac><mo></mo><mrow><mo>(</mo><mrow><mn>1</mn><mo>-</mo><mrow><mn>2</mn><mo>·</mo><mrow><mi>c</mi><mo></mo><mrow><mo>(</mo><mrow><mrow><mn>2</mn><mo></mo><mi>m</mi></mrow><mo>+</mo><mn>1</mn></mrow><mo>)</mo></mrow></mrow></mrow></mrow><mo>)</mo></mrow></mrow></mrow></mrow></mtd><mtd><mrow><mo>[</mo><mrow><mi>Equation</mi><mo></mo><mstyle><mspace width="0.8em" height="0.8ex" /></mstyle><mo></mo><mn>3</mn></mrow><mo>]</mo></mrow></mtd></mtr></mtable></math></maths>

0123Herein, m=0, 1, . . . , 2N_maxRB−1, N_maxRBsignifies a maximum number of RBs, ns represents a slot number within a radio frame, and l signifies an OFDM symbol number within a slot.

0124A pseudo-random sequence c(i) is defined by a Gold sequence having a length of 31, which is shown below.

0125At this point, m=0, 1, . . . , 12N_RB−1, and N_RBcorresponds to a maximum number of RBs. A pseudo-random sequence generator may be initiated to c_init=(floor(ns/2)+1)(2N_EPDCCH,ID+1)2¹⁶+n_EPDCCH,SCIDfrom the beginning of each subframe. ns represents a slot number within the radio frame, N_EPDCCH,ID<img file="US2017180098A1_D0001.tif" /> corresponds to a value that is associated with the EPDCCH set and is given from higher layer signaling, and n_EPDCCH,SCIDmay be given as a specific value.

0126Each of the EPDCCH regions <b>420</b> and <b>430</b> may be used for the scheduling of cells that are different from one another. For example, the EPDCCH within the EPDCCH region <b>420</b> may carry scheduling information for the primary cell, and the EPDCCH of the EPDCCH region <b>430</b> may carry scheduling information for the secondary cell.

0127In the EPDCCH regions <b>420</b> and <b>430</b>, when the EPDCCH is transmitted through multiple antennas, pre-coding that is identical to that of the EPDCCH may be applied to the DM RS within the EPDCCH regions <b>420</b> and <b>430</b>.

0128In comparison with the PDCCH using the CCE in transmission resource units, the transmission resource unit for the EPCCH is referred to as an ECCE (Enhanced Control Channel Element). The aggregation level may be defined as a resource unit that monitors the EPDCCH. For example, when 1 ECCE is said to be the minimum resource for the EPDCCH, the aggregation level may be defined as L={1, 2, 4, 8, 16}.

0129Hereinafter, the EPDCCH search space may correspond to the EPDCCH region. In the EPDCCH search space, one or more EPDCCH candidates may be monitored for one or more aggregation levels.

0130Hereinafter, the resource allocation for the EPDCCH will be described in detail.

0131The EPDCCH is transmitted by using one or more ECCEs. An ECCE includes multiple EREGs (Enhanced Resource Element Groups). In accordance with the subframe type and CP respective to the TDD (Time Division Duplex) DL-UL configuration, an ECCE may include 4 EREGs or 8 EREGs. For example, in a normal CP, the ECCE may include 4 EREGs, and, in an extended CP, the ECCE may include 8 EREGs.

0132A PRB (Physical Resource Block) pair refers to two PRBs having the same RB number within one subframe. A PRB pair refers to a first PRB of a first slot and a second PRB of a second slot within the same frequency domain. In the normal CP, a PRB pair includes 12 sub-carriers and 14 OFDM symbols, and, therefore, includes 168 REs (resource elements).

0133<figref idref="DRAWINGS">FIG. 10</figref> illustrates an example of a PRB pair.

0134Hereinafter, a subframe includes 2 slots, and, in one slot, although it is said that a PRB pair includes 7 OFDM symbols and 12 sub-carriers, the number of OFDM symbols and the number of sub-carriers are merely exemplary.

0135In one subframe, a PRB pair has a total of 168 REs. With the exception for the 24 REs for the DM RS, 16 EREGs are configured from 144 REs. Accordingly, 1 EREG may include 9 REs. However, apart from the DM RS, a CSI-RS or CRS may be positioned in one PRB pair. In this case, the number of available REs may be reduced, and the number of REs being included in 1 EREG may be reduced. Although the number of REs being included in an EREG may vary, the number of EREGs being included in one PRB pair, 16, does not vary.

0136At this point, as shown in <figref idref="DRAWINGS">FIG. 10</figref>, for example, RE indexes may be sequentially assigned starting from a first upper sub-carrier of a first left-side OFDM symbol (l=0) (or RE indexes may be sequentially assigned upward starting from a first lower sub-carrier of a first left-side OFDM symbol (l=0)). It will be assumed that indexes starting from 0 to 15 are assigned to 16 EREGs. At this point, 5 REs having RE index 0 are allocated to EREG 0. Similarly, 9 REs corresponding to RE index k(k=0, . . . , 15) are allocated to EREG k.

0137By grouping multiple EREGs, an EREG group is defined. For example, when an EREG group having 4 EREGs is defined, the EREG groups may be defined as EREG group #0={EREG 0, EREG 4, EREG 8, EREG 12}, EREG group #1={EREG 1, EREG 5, EREG 9, EREG 3}, EREG group #2={EREG 2, EREG 6, EREG 10, EREG 14}, and EREG group #3={EREG 3, EREG 7, EREG 11, EREG 15}. When defining an EREG group having 8 EREGs, the EREG groups may be defined as EREG group #0={EREG 0, EREG 2, EREG 4, EREG 6, EREG 8, EREG 10, EREG 12, EREG 14}, and EREG group #1={EREG 1, EREG 3, EREG 5, EREG 7, EREG 9, EREG 11, EREG 13, EREG 15}.

0138As described above, an ECCE includes 4 EREGs, and, in an extended CP, an ECCE may include 8 EREGs. An ECCE is defined by an EREG group. For example, <figref idref="DRAWINGS">FIG. 6</figref> shows an example wherein ECCE #0 includes EREG group #0, wherein ECCE #1 includes EREG group #1, wherein ECCE #2 includes EREG group #2, and wherein ECCE #3 includes EREG group #3.

0139In ECCE-to-EREG mapping, there are two types: localized transmission and distributed transmission. In the localized transmission, an EREG group configuring one ECCE is selected from an EREG within a PRB pair. In the distributed transmission, an EREG group configuring one ECCE is selected from EREGs of different PRB pairs.

0140<figref idref="DRAWINGS">FIG. 11</figref> illustrates a PUCCH and a PUSCH within an uplink subframe.

0141Uplink control information (UCI) may be transmitted over the PUCCH. At this point, the PUCCH carries diverse types of control information. The UCI includes HARQ ACK/NACK, SR(Scheduling Request), and channel status information (CSI), which indicates the state of the downlink channel.

0142PUCCH Format 1 carries a SR (Scheduling Request). At this point, an OOK (On-Off Keying) method may be applied. PUCCH Format 1a carries an ACK/NACK (Acknowledgement/Non-Acknowledgement), which is modulated by using a BPSK (Binary Phase Shift Keying) scheme with respect to one codeword. PUCCH Format 1b carries an ACK/NACK, which is modulated by using QPSK (Quadrature Phase Shift Keying) scheme with respect to two codewords. PUCCH Format 2 carries a CQI (Channel Quality Indicator), which is modulated by using the QPSK scheme. PUCCH Formats 2a and 2b carry CQI and ACK/NACK.

0143Table 5 shows a PUCCH format.

0000<tables id="TABLE-US-00005" num="00005"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="42pt" align="left" /><colspec colname="2" colwidth="175pt" align="left" /><thead><row><entry namest="1" nameend="2" rowsep="1">TABLE 5</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>Format</entry><entry>Description</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>Format 1</entry><entry>Scheduling Request (SR)</entry></row><row><entry>Format 1a</entry><entry>ACK/NACK of a 1-bit HARQ, Scheduling Request (SR)</entry></row><row><entry /><entry>may exist or may not exist</entry></row><row><entry>Format 1b</entry><entry>ACK/NACK of a 2-bit HARQ, Scheduling Request (SR)</entry></row><row><entry /><entry>may exist or may not exist</entry></row><row><entry>Format 2</entry><entry>CSI (20 code bits)</entry></row><row><entry>Format 2</entry><entry>In case of an extended CP, CSI and 1-bit or 2-bit HARQ</entry></row><row><entry /><entry>ACK/NACK</entry></row><row><entry>Format 2a</entry><entry>CSI and 1-bit HARQ ACK/NACK</entry></row><row><entry>Format 2b</entry><entry>CSI and 2-bit HARQ ACK/NACK</entry></row><row><entry>Format 3</entry><entry>Multiple ACK/NACKs for carrier aggregation</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0144Each PUCCH Format is mapped to the PUCCH region and then transmitted accordingly. For example, PUCCH Format 2/2a/2b is mapped to a resource block (m=0, 1 in <figref idref="DRAWINGS">FIG. 8</figref>) located at an edge portion of the band that is allocated to the user equipment and then transmitted accordingly. A mixed PUCCH RB may be mapped to a neighboring resource block (e.g., m=2), which is adjacent to the resource block to which the PUCCH Format 2/2a/2b are allocated toward the center of the band, and transmitted accordingly. The PUCCH Format 1/1a/1b through which the SR and ACK/NACK are transmitted may be positioned to the resource block corresponding to m=4 or m=5. The number of resource blocks (N(2)RB), which may be used in the PUCCH Format 2/2a/2b through which the CQI is transmitted, may be indicated to the user equipment through a signal that is being broadcasted. The PUCCH Format 3 is used for carrying a 48-bit encoded UCI. The PUCCH Format 3 may carry HARQ ACK/NACK respective to multiple serving cells and a CSI report respective to one serving cell. The PUCCH Format 3 performs transmission based on block spreading. More specifically, the PUCCH Format 3 spreads (or disperses) a modulation symbol sequence, wherein a multiple-bit ACK/NACK is modulated, in the time domain by using a block spreading code and then transmits the spread sequence.

0145The above-described CSI refers to an indicator indicating the state of the DL channel, and the CSI may include at least one of a CQI (Channel Quality Indicator) and a PMI (Precoding Matrix Indicator). Additionally, a PTI (precoding type indicator), a RI (rank indication), and so on, may also be included.

0146The CQI provides information on a link adaptive parameter that can be supported by the user equipment with respect to a given time. The CQI may designate a data rate, which can be supported by a downlink channel, based on the characteristics and SINR (signal to interference plus noise ratio) of a user equipment receiver. The base station may decide a modulation (QPSK, 16-QAM, 64-QAM, and so on) and a coding rate that are to be applied to the downlink channel by using the CQI. The CQI may be generated by using diverse methods. For example, there is a method of performing feedback by quantizing the channel state without any modification, a method of performing feedback by calculating the SINR (signal to interference plus noise ratio), a method of notifying a state that is actually being applied to the channel, such as a MCS (Modulation Coding Scheme), and so on. In case the CQI is generated based on the MCS, the MCS includes the modulation scheme, the coding method, and the respective coding rate, and so on.

0147The PMI provides information on a precoding matrix during the precoding of a codebook base. The PMI is associated with MIMO (multiple input multiple output). The PMI being fed-back in MIMO is referred to as closed loop MIMO.

0148The RI corresponds to information on a number of layers recommended by the user equipment. More specifically, the RI indicates a number of independent streams that are used for spatial multiplexing. The RI is fed-back only in a case when the user equipment is operated in the MIMO mode using spatial multiplexing. The RI is always associated with one or more CQI feedback. More specifically, the CQI that is being fed-back is calculated by assuming a specific RI value. Since the rank of a channel generally varies at a slower rate as compared to the CQI, the RI is fed-back for a number of times that is slower than the CQI. The transmission cycle period (or period) of the RI may be the multiple of the CQI/PMI transmission period. The RI is given with respect to the entire system band, and a frequency selective RI feedback is not supported.

0149As described above, the PUCCH is only used for the transmission of the UCI. For this, the PUCCH supports multiple Formats. Depending on the modulation scheme that belongs to the PUCCH Format, a PUCCH having different number of bits for each subframe may be used.

0150Meanwhile, the PUSCH that is shown in the drawing is mapped to a UL-SCH (Uplink Shared Channel), which is the transport channel. Uplink data that are transmitted over the PUSCH may correspond to a transport block, which is a data block for the UL-SCH that is being transmitted during a TTI. The transport block may include user data. Alternatively, the uplink data may correspond to multiplexed data. The multiplexed data may correspond to data having a transport block and channel state information of a UL-SCH (uplink shared channel) multiplexed therein. For example, the channel state information (CSI) that is being multiplexed in the data may include CQI, PMI, RI, and so on. Alternatively, the uplink data may only be configured of the channel state information. Periodic or aperiodic channel state information may be transmitted through the PUSCH.

0151The PUSCH is allocated by a UL grant within the PDCCH. Although it is not shown in the drawing, a 4^thsymbol of each slot in a normal CP is used for the transmission of a DM RS (Demodulation Reference Signal) for the PUSCH.

0152Meanwhile, a hybrid automatic repeat request (HARQ) may be used for a wireless communication system. HARQ is a scheme in which a transmitter receives an acknowledgement/non-acknowledgement (ACK/NACK) as receipt notification information relating to data after transmitting the data and transmits new data or retransmits previously transmitted data according to the ACK/NACK.

0153In 3GPP LTE/LTE-A, an ACK/NACK may be transmitted through a PUCCH as an uplink control channel.

0154Hereinafter, time, frequency, and code resources used for transmission of an ACK/NACK signal are referred to as ACK/NACK resources or PUCCH resources. As described above, an index for determining a PUCCH resource (referred to as a PUCCH index), that is, an index necessary to transmit an ACK/NACK signal on a PUCCH may be expressed as at least one of orthogonal sequence index i, cyclic shift index Ics, resource block index m, and indexes (n(l)PUCCH) for obtaining the three indexes. That is, a PUCCH resource may include at least one of an orthogonal sequence, a cyclic shift, a resource block, and combinations thereof, and an index representing the PUCCH resource may be referred to as a PUCCH index.

0155Meanwhile, when an ACK/NACK is transmitted through a PUCCH, a resource forming a PUCCH (PUCCH resource) may implicitly or explicitly be determined. For example, a PUCCH resource may be determined based on a resource occupied by a PDSCH as a response target of the ACK/NACK or a control channel scheduled for data (transport block or codeword), and such a PUCCH resource is referred to as an implicit (or suggested) PUCCH resource. Meanwhile, one or a plurality of resources explicitly indicated by a higher-layer signal for use is referred to an explicit PUCCH resource.

0156Hereinafter, a general random access method will be described. Random access is used to allow the UE to acquire uplink synchronization with the base station or to be allocated with uplink radio resource. Random access may be divided into contention based random access and non-contention based random access.

0157<figref idref="DRAWINGS">FIG. 12<i>a </i></figref>illustrates drawing showing a contention based random access method.

0158Referring to <figref idref="DRAWINGS">FIG. 12<i>a</i></figref>, the UE <b>100</b> randomly selects one random access preamble from a set of random access preambles that are designated through the system information or handover command. And, by selecting a radio resource that can transmit the random access preamble, the UE <b>100</b> transmits the selected random access preamble (Message 1: Msg 1) (S<b>1111</b>). The radio resource may correspond to a specific subframe, and this may be a subframe that selects a PRACH (Physical Random Access Channel).

0159After transmitting the random access preamble, the UE <b>100</b> attempts to receive a Random Access Response (RAR) within a RAR receiving window (RAR window), which is designated through the system information or handover command, and, accordingly, the UE <b>100</b> receives a Random Access Response (RAR) (Message 2: Msg2) (S<b>1112</b>). The Random Access Response (RAR) may be transmitted in a MAC PDU (Protocol data unit) Format.

0160A Random Access Preamble identifier (ID), a UL Grant (uplink radio resource), a temporary C-RNTI (Temporary Cell-Radio Network Temporary Identifier), and a synchronization correction command (e.g., Timing Advance Command (TAC)) may be included in the Random Access Response (RAR). And, since random access response information for one or more UEs <b>100</b> may be included in one Random Access Response (RAR), a random access preamble identifier may be included in order to notify to which UE <b>100</b> the included UL Grant, temporary C-RNTI, and synchronization correction command (e.g., Timing Advance Command (TAC)) are valid. The random access preamble identifier may correspond to an identifier respective to the random access preamble received by the base station (eNodeB) <b>200</b>. The synchronization correction command (e.g., Timing Advance Command (TAC)) may be included as information for allowing the UE <b>100</b> to adjust the uplink synchronization. The random access response may be directed by a random access identifier within the PDCCH, i.e., RA-RNTI (Random Access-Radio Network Temporary Identifier).

0161When the UE receives a Random Access Response (RAR) that is valid to the UE itself, the UE <b>100</b> processes the information included in the Random Access Response (RAR), and, then, the UE <b>100</b> performs a scheduled transmission (Message 3: Msg 3) to the base station (eNodeB) <b>200</b> (S<b>1113</b>). More specifically, the UE <b>100</b> applies a synchronization correction command (e.g., Timing Advance Command: TAC) and stores a temporary C-RNTI. Additionally, by using a UL Grant, the UE <b>100</b> transmits data stored in the buffer of the UE <b>100</b> or newly generated data to the base station (eNodeB) <b>200</b>. In this case, information that can identify the UE <b>100</b> should be included. This is because, during a contention based random access procedure, since it is difficult for the base station (eNodeB) <b>200</b> to determine which UEs <b>100</b> perform random access, the corresponding UE <b>100</b> is required to be identified in order to resolve collision.

0162After the UE <b>100</b> transmits the scheduled message (i.e., MSG3) including its own identifier through a radio resource, which is allocated by the UL Grant being included in the random access response (RAR), the UE <b>100</b> waits for an indication (Message 4: Msg 4) from the base station (eNodeB) <b>200</b> in order to resolve collision (S<b>1114</b>). More specifically, the reception of PDCCH is attempted in order to receive a specific message.

0163<figref idref="DRAWINGS">FIG. 12<i>b </i></figref>illustrates drawing showing a non-contention based random access method.

0164Unlike the contention based random access, the non-contention based random access may be ended by having the UE <b>100</b> receive the random access response.

0165The non-contention based random access may be initiated by a request, such as a handover and/or a command of the base station (eNodeB) <b>200</b>. However, in the two cases that are described above, the contention based random access may also be performed.

0166The UE <b>100</b> is allocated with a designated random access preamble that has no likelihood of collision from the base station (eNodeB) <b>200</b>. The allocation of the random access preamble may be performed through a handover command and a PDCCH command (S<b>1121</b>).

0167After the UE <b>100</b> is allocated with a random access preamble that is designated for the UE <b>100</b> itself, the UE <b>100</b> transmits the corresponding random access preamble to the base station (eNodeB) <b>200</b> (S<b>1122</b>).

0168When the base station (eNodeB) <b>200</b> receives the random access preamble, the base station (eNodeB) <b>200</b> transmits a Random Access Response (RAR) as a response to such reception (S<b>1123</b>).

0169Meanwhile, the MTC will hereinafter be described.

0170<figref idref="DRAWINGS">FIG. 13<i>a </i></figref>illustrates an exemplary of MTC (Machine Type communication).

0171MTC (Machine Type Communication) refers to an information exchange between MTC device <b>100</b> that do not involve human interaction through the base station <b>200</b> or an information exchange between an MTC device <b>100</b> and an MTC server <b>700</b> through the base station.

0172The MTC service <b>700</b> refers to an entity that communicates with an MTC device <b>100</b>. The MTC server <b>700</b> executes an MTC application and provides an MTC-specific service to the MTC device <b>100</b>.

0173As a wireless device providing MTC, the MTC device <b>100</b> may be fixed or have mobility.

0174Services provided through MTC are differentiated from the existing communication services that involve human intervention, and an extended range of MTC services is provided, such as tracking, metering, payment, medical services, remote controlled services, and so on. More specifically, examples of MTC services may include reading meters, measuring water levels, using surveillance cameras, making inventory reports for vending machines, and so on.

0175One of the characteristics of the MTC device is that is has a small transmission data amount and that uplink/downlink data transmission/reception occurs occasionally. And, therefore, it will be effective to decrease a unit cost of the MTC device and to reduce battery consumption in accordance with the low data transmission rate. Another characteristic of the MTC device is that it has low mobility, and, accordingly, its channel environment hardly changes.

0176<figref idref="DRAWINGS">FIG. 13<i>b </i></figref>illustrates an example of cell coverage enhancement for MTC devices.

0177Recently, enhancing the cell coverage of the base station for MTC device <b>100</b> has been considered, and diverse methods for cell coverage enhancement are being discussed.

0178However, in case the coverage of a cell is enhanced, if the base station transmits PDSCH and (E)PDCCH including scheduling information respective to the PDSCH to an MTC device that is located in the coverage enhancement region, just as when the base station performs transmission to general UEs, the MTC device may have difficulty in receiving the channels.

0179Herein, (E)PDCCH signifies a PDCCH or EPDCCH (E-PDCCH).

0180More specifically, in case of a MTC device (or MTC user equipment), since the transmission size is small, and since uplink/downlink data transmission/reception occurs occasionally, it will be efficient to lower the price of the user equipment and to reduce battery consumption in accordance with such low data transmission rate.

0181One of the characteristics of such MTC device is that it has low mobility, and, accordingly, another one of its characteristics is that its channel environment does not change. In the current LTE-A, it is being considered to provide such MTC devices with wider coverage as compared to the legacy MTC device, and, in order to do so, extensive discussions are being carried out on diverse coverage enhancement methods for MTC devices.

0182In case the user equipment (UE) performs initial access to a specific cell, the UE receives MID (master information block) and SIB (system information block) information and RRC (radio resource control) parameters respective to the corresponding cell from the base station (eNodeB), which manages/controls the corresponding cell.

0183At this point, there lies a problem in that the MTC device should have a wider coverage as compared to the legacy UE. Therefore, if the base station (eNodeB) transmits a SIB just as when transmitting it to the legacy UE, the MTC device may have difficulty in receiving the transmitted SIB. In order to resolve this, in case the base station (eNodeB) transmits a SIB of a MTC device having a coverage issue through the PDSCH, the base station (eNodeB) may perform transmission by applying methods for coverage enhancement, such as subframe repetition, subframe bundling, and so on.

0184Additionally, in case the base station (eNodeB) transmits the PDCCH and PDSCH to the MTC devices, when the base station performs transmission by using the same transmission method as when performing transmission to the legacy UE, a MTC device having coverage issues may have difficulty in receiving the PDCCH and PDSCH. In order to resolve this problem, in case the base station (eNodeB) transmits the PDCCH or PDSCH to a MTC device having coverage issues, the base station (eNodeB) may perform transmission by applying methods for coverage enhancement, such as subframe repetition, subframe bundling, and so on. Similarly, even in case the UE (or MTC device) transmits the PUCCH and PUSCH to the base station, in order to enhance the coverage, the UE (or MTC device) may use a method of performing repetitive (or repeated) transmission through multiple frames.

0185In case a MTC device having coverage issues and a legacy UE or a MTC device that does not have any coverage issues are serviced by the same cell, there lies a problem in that a large amount of resource is used in order to transmit data to the MTC device having coverage issues, thereby causing limitations in services that are to be provided to other user equipments. Accordingly, in order to prevent the MTC device having coverage issues from causing any damage (or harm) to other UEs, a TDM (Time division multiplexing) method may be used, wherein the time domain for providing services is divided for the UE having coverage issues and the UE that does not have any coverage issue. The TDM method may be carried out at long-term intervals consisting of units of several tens of minutes, and the TDM method may also be carried out at short-term intervals consisting of subframe units.

0186<Disclosures of the Present Invention>

0187Thus, disclosures of the present specification are provided to solve the foregoing problem.

0188According to the disclosures of the present specification, to solve the foregoing problem, when a BS transmits a PDSCH, a PDCCH, or an EPDCCH to an MTC device <b>100</b> located in a coverage extension region, the BS repeatedly transmits the PDSCH, the PDCCH, or the EPDCCH on a plurality of subframes (for example, a bundle of subframes).

0189Further, according to the disclosures of the present specification, when the MTC device located in the coverage extension region transmits a PUCCH or PUSCH, the MTC device <b>100</b> repeatedly transmits the PUCCH or PUSCH on a plurality of subframes (for example, a bundle of subframes).

0190For example, the MTC device receives a bundle of (E)PDCCHs through a plurality of subframes and decodes the bundle of (E)PDCCHs, thereby decoding success rate.

0191That is, the MTC device may successfully decode a (E)PDCCH by using all or part of (E)PDCCHs in a bundle received through a plurality of subframes. That is, the MTC device may decode a (E)PDCCH bundle in which the same (E)PDCCH is repeated, thereby improving decoding success rate.

0192Likewise, the MTC device receives a bundle of PDSCHs through a plurality of subframes and decodes all or part of the PDSCHs in the bundle, thereby decoding success rate. Similarly, the MTC device located in the coverage extension region may transmit a bundle of PUCCHs through a plurality of subframes. Also, the MTC device may transmit a bundle of PUSCHs through a plurality of subframes.

0193Here, a PDSCH, PDCCH, EPDCCH, PUCCH, or PUSCH bundle may be used to indicate that a PDSCH, PDCCH, EPDCCH, PUCCH, or PUSCH is repeatedly transmitted over a predetermined number of subframes according to a repetition level.

0194The repetition level may refer to repetition number as the number of subframes for repeated transmissions (subframe numbers for repetition) or may be a value (for example, a proportional value) determined corresponding to the number of repetitions.

0195<figref idref="DRAWINGS">FIG. 14<i>a </i></figref>and <figref idref="DRAWINGS">FIG. 14<i>b </i></figref>illustrate an example of transmission of a (E)PDCCH bundle and a PDSCH bundle.

0196Referring to <figref idref="DRAWINGS">FIG. 14<i>a</i></figref>, a BS may transmit a (E)PDCCH bundle in which the same (E)PDCCH is repeated on a plurality of subframes (for example, N subframes) to an MTC device located in a coverage extension region. Further, the BS may transmit a PDSCH bundle in which the same PDSCH is repeated on a plurality of subframes (for example, D subframes). Here, the PDSCH bundle may be transmitted after a predetermined gap, for example, a gap of G subframes, after the PDCCH bundle is completely transmitted.

0197For example, when transmission of the PDCCH bundle is finished on subframe N−1, the PDSCH bundle may be transmitted on D subframes, starting from subframe N+G. Here, N and D may always be set to the same value. Also, G and D may have the same value. G may be known in advance to a UE or be transmitted to the UE via system information, for example, an MIB or SIB.

0198D may be set or designated differently depending on a coverage extension degree. Alternatively, D may be designated differently depending on an aggregation level of each (E)PDCCH. For example, G may be set considering that a (E)PDCCH is repeated in different numbers by aggregation levels.

0199Meanwhile, the MTC device may know that transmission of the PDSCH bundle is started after G subframes after receiving the (E)PDCCH bundle.

0200Referring to <figref idref="DRAWINGS">FIG. 14<i>b</i></figref>, the BS may transmit, for the MTC device located in the coverage extension region, a (E)PDCCH bundle in N subframes and then transmit a PDSCH bundle in D subframes after a certain period of time.

0201Alternatively, the BS may transmit, for the MTC device located in the coverage extension region, a (E)PDCCH bundle in N subframes and then transmit a PDSCH bundle in D subframes after K subframes from a subframe in which transmission of the PDCCH bundle is started.

0202That is, a difference between a location of a subframe in which transmission of the (E)PDCCH bundle is started and a location of a subframe in which transmission of the PDSCH bundle is started is defined as K subframes (for example, K=100 or 200).

0203In this case, the MTC device needs to know in which subframe transmission of the (E)PDCCH bundle is started.

0204For example, defining that K=index of PDSCH bundle transmission start subframe-index of (E)PDCCH bundle transmission start subframe, the MTC device may need to know a timing at which transmission of the PDCCH bundle is started in order to successfully know a timing at which transmission of the PDSCH bundle is started.

0205In this case, the MTC device may know a location of a subframe at which transmission of the PDSCH bundle is started even though not being aware of the number of subframes for transmitting the (E)PDCCH bundle.

0206It may be assumed that K is always fixed. Alternatively, K may be known to the MTC device or be transmitted via an MIB or SIB. K may be set differently depending on a coverage extension degree. K may be set differently depending on an aggregation level of each (E)PDCCH. For example, K may be set considering considering that a (E)PDCCH is repeated in different numbers by aggregation levels.

0207As described above, a subframe location for starting transmission of the (E)PDCCH bundle is not random unlike in a conventional art, and transmission of the (E)PDCCH bundle may be started in a predetermined subframe. A subframe location at which transmission of the (E)PDCCH bundle is started may be defined as a fixed value. The fixed value may be notified to the MTC device through system information, for example, an MIB or SIB. For example, assuming that transmission of the (E)PDCCH bundle is started only in SFN % N=0 (for example, N=20), N may be notified to the MTC device through an MIB. Also, assuming that transmission of the (E)PDCCH bundle is started only in an offset (SFN % N=offset), N may be notified to the MTC device through an MIB. For example, transmission of the (E)PDCCH bundle for the MTC device located in the coverage extension region may be started only in a subframe or SFN corresponding to a multiple of 100 (subframe 0, 100, 200, 300, . . . ).

0208Here, the MTC device may attempt to receive the (E)PDCCH through N subframes starting from a subframe or SFN corresponding to a multiple of 100.

0209The subframe location at which transmission of the PDCCH bundle is started may change depending on an MTC device. That is, the subframe location at which transmission of the (E)PDCCH bundle is started may be determined to be user-specific.

0210In this case, information on the subframe location at which transmission of the PDCCH bundle is started may be notified to the MTC device through a higher-layer signal, such as an RRC signal.

0211Subframes for transmitting a PDCCH/EPDCCH/PDSCH/PUCCH/PUSCH may be consecutive or non-consecutive.

0212However, it may be assumed that a terminal may recognize which subframes a bundle is transmitted through. Further, the number of subframes for transmitting a PDCCH/EPDCCH/PDSCH/PUCCH/PUSCH, repetition number, or a repetition level may be set to vary depending on a coverage enhancement level required by the terminal, be set in advance, be transmitted via an SIB, or be estimate by a UE.

0213The MTC device may not always use all subframes to transmit and receive a control channel and a data channel. If necessary, subframes designated as an MBSFN subframe or special subframe may be unavailable for repetition/bundling of control channels and data channels, and only some subframes may be used for repetition/bundling of control channels and data channels for the MTC device in order to reduce effect on an operation of a legacy UE.

0214Here, a location of a subframe used by the MTC device for repetition/bundling of control channels and/or data channels in downlink and/or uplink environments may be defined in advance or be semi-statically set.

0215In this case, the MTC device may recognize, through a SIB or RRC signaling, the location of the subframe used for repetition/bundling of control channels and/or data channels in the downlink and/or uplink environments.

0216Hereinafter, the term of a total aggregate resource (TAR) for an (E)PDCCH used in the disclosures of the present specification is described.

0217<figref idref="DRAWINGS">FIG. 15</figref> illustrates an example of a TAR for an (E)PDCCH according to one disclosure of the present specification.

0218A TAR for an (E)PDCCH may be defined for a decoding candidate channel such that the TAR is given by Sum (ai) where i=0, . . . , T−1, where T is repetition number and ai is the amount or number of resources in subframe i.

0219For example, the resource may denote an (E)CCE.

0220Further, the repetition number may denote the number of subframes repeatedly transmitted according to a repetition level. For example, when the repetition number is equal to a repetition level, if the repetition level is 4, the repetition number may be 4. Further, when repetition number corresponding to a repetition level is designated in advance, repetition number corresponding repetition level <b>1</b> may be 2 and repetition number corresponding to repetition level <b>2</b> may be 4.

0221Thus, a TAR value may be regarded as being determined based on a repetition level and the amount or number of resources per subframe corresponding to the candidate channel.

0222Specifically, a UE may monitor two or more (E)PDCCH decoding candidates in order to receive an (E)PDCCH repeatedly transmitted through multiple subframes starting from a specific subframe.

0223Here, the (E)PDCCH decoding candidates may have the same TAR value or different TAR values. That is, the UE may monitor at least one TAR for the (E)PDCCH decoding candidates at a time in order to receive the (E)PDCCH repeatedly transmitted through the multiple subframes from the specific subframe.

0224For example, as illustrated in <figref idref="DRAWINGS">FIG. 15</figref>, the UE may monitor two (E)PDCCH candidates, which are (E)PDCCH candidate a and (E)PDCCH candidate b.

0225Here, the locations and number of (E)CCEs in each subframe for transmitting each (E)PDCCH candidate and the number of subframes for transmitting each (E)PDCCH may be the same or different depending on each (E)PDCCH.

0226Here, the locations of some (E)CCEs available for transmission of the respective (E)PDCCHs may overlap. In <figref idref="DRAWINGS">FIG. 15</figref>, (E)PDCCH candidate a may be transmitted through 14 subframes and be transmitted through one (E)CCE in each subframe.

0227(E)PDCCH candidate b may be transmitted through 14 subframes and be transmitted through two (E)CCEs in each subframe. In this case, (E)PDCCH candidate b may have two times greater TARs than (E)PDCCH candidate a.

0228Meanwhile, the following disclosures of the present specification provide approaches for determining, allocating, or setting PUCCH transmission resources when a PUCCH is repeatedly transmitted through multiple subframes for an MTC device located in a coverage extension region.

0229Specifically, a first disclosure of the present specification provides approaches for determining or setting explicit PUCCH resources used for repeated transmission of a PUCCH, while a second disclosure of the present specification provides approaches for determining or setting implicit PUCCH resources used for repeated transmission of a PUCCH. Subframe

0230<First Disclosure of Present Specification—Methods for Determining Explicit PUCCH Resources>

0231As described above, the first disclosure of the present specification provides approaches for determining or setting explicit PUCCH resources used for repeated transmission of a PUCCH.

0232That is, the first disclosure of the present specification provides approaches for determining, setting, or allocating a resource region for transmitting a PUCCH in a subframe when the PUCCH is repeatedly transmitted through multiple subframes for an MTC device located in a coverage extension region.

0233Specifically, a method according to the first disclosure of the present specification is a method for a terminal to transmit a PUCCH, which may include: receiving a plurality of pieces of explicit configuration information on a PUCCH resource through higher-layer signaling when a PUCCH needs to be repeatedly transmitted on a plurality of subframes; determining a PUCCH resource for transmitting the PUCCH based on the plurality of pieces of explicit configuration information; and repeatedly transmitting the PUCCH via the determined PUCCH resource on the plurality of subframes.

0234Here, the PUCCH resource for transmitting the PUCCH may be determined based on at least one of a PDCCH, an EPDCCH, and an identification (ID) of the terminal, which are previously received.

0235Further, the previously received PDSCH may be scheduled by the previously received PDCCH or EPDCCH, and the PUCCH may include ACK/NACK information in response to the previously received PDSCH.

0236Further, the previously received PDCCH or EPDCCH may be repeatedly transmitted on a plurality of downlink subframes according to a repetition level, the previously received PDCCH may be received by monitoring a plurality of PDCCH candidates, and the previously received EPDCCH may be received by monitoring a plurality of EPDCCH candidates.

0237Further, the PUCCH resource for transmitting the PUCCH may be determined based on a total aggregate resource (TAR) value for a PDCCH candidate from which the previously received PDCCH is retrieved among the plurality of PDCCH candidates, and the TAR value for the PDCCH candidate may be determined based on a repetition level and the number of resources per subframe for the previously received PDCCH.

0238Further, the PUCCH resource for transmitting the PUCCH may be determined based on the maximum TAR value for the plurality of PDCCH candidates, the maximum TAR value may be a TAR value having the maximum value among respective TAR values for the plurality of PDCCH candidates, and the respective TAR values for the plurality of PDCCH candidates may be determined based on repetition levels and numbers of resources per subframe respectively for the plurality of PDCCH candidates.

0239Further, the ID of the terminal may be a cell radio network temporary identifier (C-RNTI).

0240Further, the PUCCH resource for transmitting the PUCCH may be determined based on a location of a first control channel element (CCE) of the previously received PDCCH or a first enhanced CCE (ECCE) of the previously received EPDCCH.

0241Further, the PUCCH resource for transmitting the PUCCH may be randomly determined based on a predetermined random sequence whenever a PUCCH transmission event occurs.

0242Further, the PUCCH resource for transmitting the PUCCH may be maintained the same while the PUCCH is repeatedly transmitted on the plurality of subframes.

0243Further, the random sequence may be determined based on a subframe index or system frame number (SFN).

0244Further, the random sequence may be a random sequence initialized based on at least one of the PDCCH, EPDCCH, and ID of the terminal, which are previously received.

0245Meanwhile, a method of transmitting an ACK/NACK of a PDSCH received from an eNodeB when one serving cell is configured for a UE is illustrated as follows.

0246HARQ-ACK transmission on two antenna ports (pε[p₀,p₁]) is supported for PUCCH format 1a/1b.

0247For FDD and one configured serving cell, the UE may use PUCCH resource PUCCH n_PUCCH^{(1,{tilde over (p)})}for transmission of HARQ-ACK in subframe n for {tilde over (p)} mapped to antenna port p for PUCCH format 1a/1b [3].

0248For PDSCH transmission indicated by the detection of a corresponding PDCCH in subframe n−4, or for a PDCCH indicating downlink semi-persistent scheduling (SPS) release in) subframe n−4, the UE may use n_PUCCH^{(1,{tilde over (p)}}^{<sub2>0</sub2>}⁾=n_CCE+N_PUCCH⁽¹⁾for antenna port p0, where n_CCEis the index of a first CCE (i.e. lowest CCE index used to construct the PDCCH) used for transmission of the corresponding DCI (that is, assignment of a downlink resource for reception of downlink data as a target of an ACK/NACK signal) and N_PUCCH⁽¹⁾is a parameter notified by the eNodeB to via a higher-layer message. For two antenna port transmission, a PUCCH resource for antenna port p1 is given by n_PUCCH^{(1,{tilde over (p)}}^{<sub2>1</sub2>}⁾=n_CCE+1+N_PUCCH⁽¹⁾.

0249For PDSCH transmission on the primary cell where there is not a corresponding PDCCH/EPDCCH detected in subframe n−4, the value of n_PUCCH^{(1,{tilde over (p)})}is determined according to higher-layer configuration. For a UE configured for two antenna port transmission, a PUCCH resource value maps to two PUCCH resources, which are a first PUCCH resource n_PUCCH^{(1,{tilde over (p)}}^{<sub2>0</sub2>}⁾for antenna port p0 and a second PUCCH resource n_PUCCH^{(1,{tilde over (p)}}^{<sub2>1</sub2>}⁾for antenna port p1. Otherwise, the PUCCH resource value maps to a single PUCCH resource n_PUCCH^{(1,{tilde over (p)}}^{<sub2>0</sub2>}⁾for antenna port p0.

0250If EPDCCH-PRB-set q is configured for distributed transmission, a PUCCH index (or PUCCH resource) is determined according to the following equation.

0000<maths id="MATH-US-00002" num="00002"><math overflow="scroll"><mtable><mtr><mtd><mrow><msubsup><mi>n</mi><mi>PUCCH</mi><mrow><mo>(</mo><mrow><mn>1</mn><mo>,</mo><msub><mover><mi>p</mi><mo>~</mo></mover><mn>0</mn></msub></mrow><mo>)</mo></mrow></msubsup><mo>=</mo><mrow><msub><mi>n</mi><mrow><mi>ECCE</mi><mo>,</mo><mi>q</mi></mrow></msub><mo>+</mo><mrow><munderover><mo>∑</mo><mrow><mrow><mi>i</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mn>1</mn></mrow><mo>=</mo><mn>0</mn></mrow><mrow><mi>m</mi><mo>-</mo><mn>1</mn></mrow></munderover><mo></mo><msub><mi>N</mi><mrow><mi>ECCE</mi><mo>,</mo><mi>q</mi><mo>,</mo><mrow><mi>n</mi><mo>-</mo><msub><mi>k</mi><mrow><mi>i</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mn>1</mn></mrow></msub></mrow></mrow></msub></mrow><mo>+</mo><msub><mi>Δ</mi><mi>ARO</mi></msub><mo>+</mo><msubsup><mi>N</mi><mrow><mi>PUCCH</mi><mo>,</mo><mi>q</mi></mrow><mrow><mo>(</mo><mrow><mi>c</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mn>1</mn></mrow><mo>)</mo></mrow></msubsup></mrow></mrow></mtd><mtd><mrow><mo>[</mo><mrow><mi>Equation</mi><mo></mo><mstyle><mspace width="0.8em" height="0.8ex" /></mstyle><mo></mo><mn>4</mn></mrow><mo>]</mo></mrow></mtd></mtr></mtable></math></maths>

0251If EPDCCH-PRB-set q is configured for localised transmission, a PUCCH index (or PUCCH resource) is determined according to the following equation.

0000<maths id="MATH-US-00003" num="00003"><math overflow="scroll"><mtable><mtr><mtd><mrow><msubsup><mi>n</mi><mi>PUCCH</mi><mrow><mo>(</mo><mrow><mn>1</mn><mo>,</mo><msub><mover><mi>p</mi><mo>~</mo></mover><mn>0</mn></msub></mrow><mo>)</mo></mrow></msubsup><mo>=</mo><mrow><mrow><mrow><mo>⌊</mo><mfrac><msub><mi>n</mi><mrow><mi>ECCE</mi><mo>,</mo><mi>q</mi></mrow></msub><msubsup><mi>N</mi><mi>RB</mi><mrow><mi>ECCE</mi><mo>,</mo><mi>q</mi></mrow></msubsup></mfrac><mo>⌋</mo></mrow><mo>·</mo><msubsup><mi>N</mi><mi>RB</mi><mrow><mi>ECCE</mi><mo>,</mo><mi>q</mi></mrow></msubsup></mrow><mo>+</mo><mrow><munderover><mo>∑</mo><mrow><mrow><mi>i</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mn>1</mn></mrow><mo>=</mo><mn>0</mn></mrow><mrow><mi>m</mi><mo>-</mo><mn>1</mn></mrow></munderover><mo></mo><msub><mi>N</mi><mrow><mi>ECCE</mi><mo>,</mo><mi>q</mi><mo>,</mo><mrow><mi>n</mi><mo>-</mo><msub><mi>k</mi><mrow><mi>i</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mn>1</mn></mrow></msub></mrow></mrow></msub></mrow><mo>+</mo><msup><mi>n</mi><mi>′</mi></msup><mo>+</mo><msub><mi>Δ</mi><mi>ARO</mi></msub><mo>+</mo><msubsup><mi>N</mi><mrow><mi>PUCCH</mi><mo>,</mo><mi>q</mi></mrow><mrow><mo>(</mo><mrow><mi>e</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mn>1</mn></mrow><mo>)</mo></mrow></msubsup></mrow></mrow></mtd><mtd><mrow><mo>[</mo><mrow><mi>Equation</mi><mo></mo><mstyle><mspace width="0.8em" height="0.8ex" /></mstyle><mo></mo><mn>5</mn></mrow><mo>]</mo></mrow></mtd></mtr></mtable></math></maths>

0252In the foregoing equation, N_ECCE,qdenotes the number of a first ECCE used for transmission of corresponding DCI assignment in subframe n-k_mand EPDCCH-PRB-set q of corresponding m, for antenna port p₀. N^(e1)_PUCCH,qis configured by a higher layer. N_ECCE,q,n-ki1denotes the number of ECCEs in EPDCCH-PRB-set q configured in subframe n-k_ki1. Δ_AROis a value determined from an HARQ-ACK resource offset field included in the DCI format of a corresponding EPDCCH.

0253For two antenna transmission, a PUCCH resource for antenna port p1 is given for distributed transmission as follows.

0000<br /><i>n</i>_PUCCH^{(1,{tilde over (p)}}^{<sub2>1</sub2>}⁾<i>=n</i>_ECCE,q+1+Δ_ARO<i>+N</i>^(e1)_PUCCH,q  [Equation 6]

0254Further, for two antenna transmission, a PUCCH resource for antenna port p1 is given for localized transmission as follows.

0000<maths id="MATH-US-00004" num="00004"><math overflow="scroll"><mtable><mtr><mtd><mrow><msubsup><mi>n</mi><mi>PUCCH</mi><mrow><mo>(</mo><mrow><mn>1</mn><mo>,</mo><msub><mover><mi>p</mi><mo>~</mo></mover><mn>1</mn></msub></mrow><mo>)</mo></mrow></msubsup><mo>=</mo><mrow><mrow><mrow><mo>⌊</mo><mfrac><msub><mi>n</mi><mrow><mi>ECCE</mi><mo>,</mo><mi>q</mi></mrow></msub><msubsup><mi>N</mi><mi>RB</mi><mrow><mi>ECCE</mi><mo>,</mo><mi>q</mi></mrow></msubsup></mfrac><mo>⌋</mo></mrow><mo>·</mo><msubsup><mi>N</mi><mi>RB</mi><mrow><mi>ECCE</mi><mo>,</mo><mi>q</mi></mrow></msubsup></mrow><mo>+</mo><mn>1</mn><mo>+</mo><msup><mi>n</mi><mi>′</mi></msup><mo>+</mo><msub><mi>Δ</mi><mi>ARO</mi></msub><mo>+</mo><msubsup><mi>N</mi><mrow><mi>PUCCH</mi><mo>,</mo><mi>q</mi></mrow><mrow><mo>(</mo><mrow><mi>e</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mn>1</mn></mrow><mo>)</mo></mrow></msubsup></mrow></mrow></mtd><mtd><mrow><mo>[</mo><mrow><mi>Equation</mi><mo></mo><mstyle><mspace width="0.8em" height="0.8ex" /></mstyle><mo></mo><mn>7</mn></mrow><mo>]</mo></mrow></mtd></mtr></mtable></math></maths>

0255Δ_AROvalues according to an ACK/NACK resource offset field in DCI formats 1A/1B/1D/1/2A/2/2B/2C/2D are illustrated in the following table.

0000<tables id="TABLE-US-00006" num="00006"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="offset" colwidth="28pt" align="left" /><colspec colname="1" colwidth="126pt" align="center" /><colspec colname="2" colwidth="63pt" align="center" /><thead><row><entry /><entry namest="offset" nameend="2" rowsep="1">TABLE 6</entry></row><row><entry /><entry namest="offset" nameend="2" align="center" rowsep="1" /></row><row><entry /><entry>ACK/NACK resource offset field in DCI</entry><entry /></row><row><entry /><entry>formats 1A/1B/1D/1/2A/2/2B/2C/2D</entry><entry>Δ_ARO</entry></row><row><entry /><entry namest="offset" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="offset" colwidth="28pt" align="left" /><colspec colname="1" colwidth="126pt" align="center" /><colspec colname="2" colwidth="63pt" align="char" char="." /><tbody valign="top"><row><entry /><entry>0</entry><entry>0</entry></row><row><entry /><entry>1</entry><entry>−1</entry></row><row><entry /><entry>2</entry><entry>−2</entry></row><row><entry /><entry>3</entry><entry>2</entry></row><row><entry /><entry namest="offset" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0256Here, the location of a PUCCH transmission resource for transmitting ACK/NACK information in response to a PDSCH of an MTC device that needs coverage enhancement may be determined according to the first (E)CCE (first CCE or ECCE: lowest (E)CCE index used to construct the (E)PDCCH) of an (E)PDCCH scheduling the PDSCH as in the conventional method.

0257<figref idref="DRAWINGS">FIG. 16</figref> illustrates a problem that two PUCCH resources overlap when a (E)PDCCH for an MTC device and a (E)PDCCH for a legacy UE have the same first (E)CCE.

0258Referring to <figref idref="DRAWINGS">FIG. 16</figref>, even when (E)PDCCHs for the MTC device located in the coverage extension region and the legacy UE or terminal are transmitted through different subframes, PUCCHs may be transmitted through the same subframe.

0259Here, when the (E)PDCCH for the MTC device and the (E)PDCCH for the legacy UE have the same first (E)CCE, transmission resources for the two PUCCHs may overlap.

0260To prevent such a problem, the PUCCH of the MTC device that needs coverage enhancement may be transmitted using an explicit PUCCH resource.

0261The explicit PUCCH resource may be assigned by a higher layer and be user-specific. Further, a plurality of explicit PUCCH resources may be assigned for one terminal in order to select an appropriate PUCCH resource index according to an interference condition or channel environment.

0262Influential Factors in Determining Explicit PUCCH Resource

0263Meanwhile, when a plurality of explicit PUCCH resources is assigned for one UE, the UE actually needs to determine a PUCCH resource to use for PUCCH transmission.

0264To this end, the UE may receive a plurality of pieces of explicit configuration information on the PUCCH resources through higher-layer signaling in order to determine or set the PUCCH resource (or explicit PUCCH resource).

0265In determining the index of a PUCCH resource, multiplexing with other UEs assigned the same resource as an explicit PUCCH resource may also be considered. The following factors may be considered in determining the index of an explicit resource for transmitting a PUCCH.

0266(a) TAR Value of (E)PDCCH Received by UE

0267The explicit resource for the PUCCH (or explicit PUCCH resource) may be determined, set, or assigned based on the TAR value of the (E)PDCCH.

0268Here, the (E)PDCCH may be an (E)PDCCH scheduling a PDSCH when the UE transmits a PUCCH including ACK/NACK (A/N) information in response to the PDSCH.

0269That is, the PDSCH may be a previously received PDSCH, the previously received PDSCH may be scheduled by a previously received PDCCH or EPDCCH, and the PUCCH may include ACK/NACK information in response to the previously received PDSCH.

0270Further, the (E)PDCCH may be an (E)PDCCH received most recently (or successfully decoded) by the UE before transmitting the PUCCH. Alternatively, the (E)PDCCH may be an (E)PDCCH received most recently (or successfully decoded) by the UE via a subframe which is n subframes (for example, n=4) before a subframe for transmitting the PUCCH.

0271Specifically, the previously received PDCCH or EPDCCH is repeatedly transmitted on a plurality of downlink subframes according to a repetition level, the previously received PDCCH may be received by monitoring a plurality of PDCCH candidates, and the previously received EPDCCH may be received by monitoring a plurality of EPDCCH candidates.

0272Here, the PUCCH resource for transmitting the PUCCH may be determined based on a TAR value of a PDCCH candidate from which the previously received PDCCH is retrieved among the plurality of PDCCH candidates, and the TAR value of the PDCCH candidate may be determined based on a repetition level and the number of resources per subframe for the previously received PDCCH.

0273(b) Maximum TAR Value for (E)PDCCH Candidates Monitored by UE

0274The index of the explicit resource for the PUCCH may be determined according to the maximum TAR value among TARs for the (E)PDCCH candidates monitored by the UE.

0275Specifically, the PUCCH resource for transmitting the PUCCH may be determined based on the maximum TAR value for the plurality of PDCCH candidates, the maximum TAR value may be a TAR value having the maximum value among the respective TAR values for the plurality of PDCCH candidates, and the respective TAR values for the plurality of PDCCH candidates may be determined based on repetition levels and numbers of resources per subframe respectively for the plurality of PDCCH candidates.

0276(c) ID of UE Transmitting PUCCH

0277For the randomization of the PUCCH resource, the index of the explicit PUCCH resource may be implicitly determined according to the ID (for example, C-RNTI) of the UE that transmits the PUCCH.

0278(d) First (E)CCE for (E)PDCCH Received by UE

0279When the UE transmits the PUCCH including the A/N information in response to the PDSCH, the index of the explicit PUCCH resource may be implicitly determined according to the index of the first (E)CCE for transmitting the (E)PDCCH scheduling the PDSCH (lowest (E)CCE index used to construct the (E)PDCCH).

0280That is, the PUCCH resource for transmitting the PUCCH may be determined based on the index of a first CCE of the previously received PDCCH or a first ECCE of the previously received ECCE.

0281(e) Index of (E)PDCCH Candidate Received by UE

0282The index of the explicit PUCCH resource may be determined according to the index of the (E)PDCCH received by the UE, which may be useful particularly when resources to construct one (E)PDCCH candidate may be set as resources in multiple subframes.

0283Hereinafter, methods for determining an explicit PUCCH resource index will be illustrated.

0284Determination Method 1-1

0285In order to determine the index of an explicit resource for transmitting a PUCCH considering the foregoing factors (a) to (e), an explicit PUCCH resource for a UE may be determined according to (a), (b), (c), (d), and/or (e). Here, the foregoing factors may be used in combinations with other factors to determine the index of the explicit PUCCH resource for the UE. Here, the index of the explicit PUCCH resource may be determined according to the value of each factor by a table or equation. The table or equation may be defined in the specification or set for the UE through an SIB or RRC signal. For example, when the explicit PUCCH resource to be used by the UE is determined according to the TAR value of a (E)PDCCH received by the UE as in (a), the explicit PUCCH resource according to the TAR value of the (E)PDCCH may be determined as listed in Table 1.

0000<tables id="TABLE-US-00007" num="00007"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="offset" colwidth="21pt" align="left" /><colspec colname="1" colwidth="63pt" align="center" /><colspec colname="2" colwidth="133pt" align="center" /><thead><row><entry /><entry namest="offset" nameend="2" rowsep="1">TABLE 7</entry></row><row><entry /><entry namest="offset" nameend="2" align="center" rowsep="1" /></row><row><entry /><entry>TAR of (E)PDCCH</entry><entry>Index of explicit PUCCH resource</entry></row><row><entry /><entry namest="offset" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>10</entry><entry>0</entry></row><row><entry /><entry>20</entry><entry>1</entry></row><row><entry /><entry>40</entry><entry>2</entry></row><row><entry /><entry namest="offset" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0286In another example, when the index of the explicit PUCCH resource is determined according to the ID of the UE as in (c), defining the number of explicit PUCCH resources as N, the index of the explicit PUCCH resource to be used by the UE may be determined by UE_ID mod N.

0287In this case, particularly, when the PUCCH is repeatedly transmitted through multiple subframes, the index of the explicit PUCCH resource for transmitting the PUCCH may be maintained the same during the repetition. In particular, the same index of the explicit PUCCH resource as used in a first subframe in which the PUCCH is transmitted may be used for the repetition.

0288Determination Method 1-2

0289The index of an explicit resource for transmitting a PUCCH may change randomly (according to a determined random sequence) whenever a UE transmits a PUCCH bundle. According to this method, a PUCCH transmission resource may be maintained the same while the PUCCH is repeatedly transmitted (during a repetition period). However, a PUCCH transmission resource may change whenever a PUCCH bundle is transmitted. For example, the PUCCH transmission resource may change (be determined) according to a repetition level for PUCCH transmission (or repetition number or the number of subframes). That is, the index of a PUCCH transmission resource for the UE to repeatedly transmit PUCCH1 through N1 subframes may be different from the index of a PUCCH transmission resource for the UE to repeatedly transmit PUCCH2 through N2 subframes. However, the same PUCCH transmission resource may be used in the N1 subframes for transmitting PUCCH1, and the PUCCH transmission resource may be used in the N2 subframes for transmitting PUCCH2. Particularly, the index of a resource for transmitting a PUCCH in a PUCCH bundle may be the same as a PUCCH resource used in a first subframe for the PUCCH bundle.

0290When a PUCCH is transmitted through multiple subframes, the index of an explicit PUCCH resource in a first subframe for transmitting the PUCCH may change depending on a subframe index (or SFN) of the first subframe for transmitting the PUCCH. For example, defining a random sequence as c(n), when the index of the first subframe for transmitting the PUCCH is k, the index of the explicit PUCCH resource in the first subframe for transmitting the PUCCH may be c(k). Alternatively, the index of the explicit PUCCH resource in the first subframe for transmitting the PUCCH may change according to an SFN to which the first subframe for transmitting the PUCCH belongs. For example, defining a random sequence as c(n), when the first subframe for transmitting the PUCCH belongs to SFN m, the index of the explicit PUCCH resource in the first subframe for transmitting the PUCCH may be c(m).

0291Here, the index of the explicit PUCCH resource for transmitting the PUCCH may also change according to the foregoing factors (a) to (e). That is, the index of the explicit PUCCH resource in the first subframe for transmitting the PUCCH may change according to a specific random sequence, and a value resulting from the random sequence may change according to the factors (a), (b), (c), (d), and/or (e). For example, a random sequence c(n) that determines the index of the explicit PUCCH resource may be a random sequence initialized by the factors (a), (b), (c), (d), and/or (e). For example, the random sequence may change according to the subframe index of the first subframe for transmitting the PUCCH and may be initialized based on the ID of the UE (C_initmay be determined according to the ID of the UE).

0292Determination Method 1-3 Subframe

0293The index of an explicit resource for transmitting a PUCCH may change randomly (according to a determined random sequence) whenever a UE transmits the PUCCH. According to this method, a PUCCH transmission resource may change by each subframe or multiple subframes even while the PUCCH is repeatedly transmitted. The index of an explicit PUCCH resource in a specific subframe may change according to the index of the subframe.

0294That is, even though the same PUCCH is repeatedly transmitted, if the index of a subframe for transmitting the PUCCH changes, the PUCCH may be transmitted through different explicit PUCCH resources. For example, defining a random sequence as c(n), the index of an explicit PUCCH resource in a subframe with index k may be c(k). Alternatively, the index of an explicit PUCCH resource in a specific subframe may change according to an SFN for transmitting the PUCCH. For example, defining a random sequence as c(n) and defining an SFN of subframe k as m_k, the index of the explicit PUCCH resource in subframe with index k may be c(m_k).

0295Here, the index of the explicit PUCCH resource for transmitting the PUCCH may also change according to the foregoing factors (a) to (e). That is, the index of the explicit PUCCH resource in the subframe for transmitting the PUCCH may change according to a specific random sequence, and a value resulting from the random sequence may change according to the factors (a), (b), (c), (d), and/or (e). For example, a random sequence c(n) that determines the index of the explicit PUCCH resource may be a random sequence initialized by the factors (a), (b), (c), (d), and/or (e). For example, the random sequence may change according to the index of the subframe for transmitting the PUCCH and may be initialized based on the ID of the UE (C_initmay be determined according to the ID of the UE).

0296Further, the index of the explicit PUCCH resource may change (be determined) according to a repetition level or repetition number.

0297<Second Disclosure of Present Specification—Methods for Determining Implicit PUCCH Resources>

0298As described above, the second disclosure of the present specification provides approaches for determining or setting implicit PUCCH resources used for repeated transmission of a PUCCH.

0299The foregoing description has been made on a method for an MTC device needing coverage enhancement to transmit a PUCCH using an explicit resource. However, a method for the MTC UE to transmit a PUCCH using an implicit PUCCH resource may still be considered.

0300Even when the MTC UE needing coverage enhancement transmits a PUCCH using an implicit PUCCH resource, the foregoing methods for setting a PUCCH transmission resource illustrated in the first disclosure of the present specification may also be applied. The PUCCH transmission resource may change by each subframe while the PUCCH is repeatedly transmitted.

0301<figref idref="DRAWINGS">FIG. 17</figref> illustrates a problem that two PUCCH resources overlap when (E)PDCCHs for two MTC devices have the same first (E)CCE.

0302Referring to <figref idref="DRAWINGS">FIG. 17</figref>, although (E)PDCCHs for two MTC devices performing coverage extension are transmitted through different subframe regions, the two (E)PDCCHs may be transmitted with the same first (E)CCE. In this case, a problem that the two UEs need to transmit PUCCHs via the same subframe region may occur, in which case the same first (E)CCE is used for the two (E)PDCCHs, thus causing a collision between the PUCCH transmission resources.

0303Considering this problem, when a PUCCH for an MCT device needing coverage enhancement is transmitted using an implicit PUCCH resource, the resource for transmitting the PUCCH may change by each subframe while the PUCCH is repeatedly transmitted. The index of an explicit PUCCH resource in each subframe may be determined considering the following factors.

0304(a) PUCCH repetition index

0305(b) Index of (E)PDCCH transmission start subframe

0306(c) Number of (E)PDCCH transmission subframes and/or number of PDSCH transmission subframes

0307(d) UE ID (for example, C-RANTI)

0308(e) Index of (E)PDCCH candidate received by UE

0309The index of an explicit PUCCH resource may be determined according to the index of an (E)PDCCH candidate received by the UE, which may be useful particularly when resources to construct one (E)PDCCH candidate may be set as resources in multiple subframes.

0310To determine the index of an implicit PUCCH resource in each subframe, a PUCCH resource for the UE may be determine according to (a), (b), (c), (d), and/or (e).

0311For example, the index of the implicit PUCCH resource may be set in view of an index (PUCCH repetition index, k) indicating how many times a PUCCH transmitted via a specific subframe is repeated as in (a). When a PUCCH is transmitted through subframes n to n+R, the PUCCH transmitted via subframe n has a PUCCH repetition index (k) of 0, the PUCCH transmitted via subframe n+1 has a PUCCH repetition index of 1, and the PUCCH transmitted via subframe n+2 has a PUCCH repetition index of 2. Here, as in a conventional method, defining the index of an implicit PUCCH resource set according to a first (E)CCE as PUCCH_resource ((E)CCE) and defining a subframe index as k, the index of a resource for transmitting a PUCCH for the MTC device needing coverage enhancement may actually be set as PUCCH_resource ((E)CEE)+k.

0312<figref idref="DRAWINGS">FIG. 18</figref> is a block diagram illustrating a wireless communication system according to a disclosure of the present specification.

0313ABS <b>200</b> includes a processor <b>201</b>, a memory <b>202</b>, and a radio frequency (RF) unit <b>203</b>. The memory <b>202</b> is coupled to the processor <b>201</b>, and stores a variety of information for driving the processor <b>201</b>. The RF unit <b>203</b> is coupled to the processor <b>201</b>, and transmits and/or receives a radio signal. The processor <b>201</b> implements the proposed functions, procedures, and/or methods. In the aforementioned embodiment, an operation of the BS may be implemented by the processor <b>201</b>.

0314An MTC device <b>100</b> includes a processor <b>101</b>, a memory <b>102</b>, and an RF unit <b>103</b>. The memory <b>102</b> is coupled to the processor <b>101</b>, and stores a variety of information for driving the processor <b>101</b>. The RF unit <b>103</b> is coupled to the processor <b>101</b>, and transmits and/or receives a radio signal. The processor <b>101</b> implements the proposed functions, procedures, and/or methods.

0315The processors may include Application-specific Integrated Circuits (ASICs), other chipsets, logic circuits, and/or data processors. The memories may include Read-Only Memory (ROM), Random Access Memory (RAM), flash memory, memory cards, storage media and/or other storage devices. The RF units may include a baseband circuit for processing a radio signal. When the above-described embodiment is implemented in software, the above-described scheme may be implemented using a module (process or function) which performs the above function. The module may be stored in the memories and executed by the processors. The memories may be disposed inside or outside the processors and connected to the processors using a variety of well-known means.

0316A terminal according to one disclosure of the present specification, which transmits a PUCCH, may include: an RF unit to receive a plurality of pieces of explicit configuration information on a PUCCH resource through higher-layer signaling when a PUCCH needs to be repeatedly transmitted on a plurality of subframes; and a processor to control the RF unit to determine a PUCCH resource for transmitting the PUCCH based on the plurality of pieces of explicit configuration information and to repeatedly transmit the PUCCH via the determined PUCCH resource on the plurality of subframes, wherein the PUCCH resource for transmitting the PUCCH may be determined based on at least one of a PDCCH, an EPDCCH, and an ID of the terminal, which are previously received.

0317Further, the previously received PDCCH or EPDCCH may be repeatedly transmitted on a plurality of downlink subframes according to a repetition level, the previously received PDCCH may be received by monitoring a plurality of PDCCH candidates, and the previously received EPDCCH may be received by monitoring a plurality of EPDCCH candidates.

0318Further, the PUCCH resource for transmitting the PUCCH may be determined based on a total aggregate resource (TAR) value for a PDCCH candidate from which the previously received PDCCH is retrieved among the plurality of PDCCH candidates, and the TAR value for the PDCCH candidate may be determined based on a repetition level and the number of resources per subframe for the previously received PDCCH.

0319Further, the PUCCH resource for transmitting the PUCCH may be determined based on the maximum TAR value for the plurality of PDCCH candidates, the maximum TAR value may be a TAR value having the maximum value among respective TAR values for the plurality of PDCCH candidates, and the respective TAR values for the plurality of PDCCH candidates may be determined based on repetition levels and numbers of resources per subframe respectively for the plurality of PDCCH candidates.

0320Further, the ID of the terminal may be a C-RNTI.

0321Further, the PUCCH resource for transmitting the PUCCH may be determined based on a location of a first CCE of the previously received PDCCH or a first ECCE of the previously received EPDCCH.

0322In the above exemplary systems, although the methods have been described on the basis of the flowcharts using a series of the steps or blocks, the present invention is not limited to the sequence of the steps, and some of the steps may be performed at different sequences from the remaining steps or may be performed simultaneously with the remaining steps. Furthermore, those skilled in the art will understand that the steps shown in the flowcharts are not exclusive and may include other steps or one or more steps of the flowcharts may be deleted without affecting the scope of the present invention.