WO2013100475A1

WO2013100475A1 - Method and apparatus for applying pusch/phich scheduling timing in inter-band tdd transmission schemes

Info

Publication number: WO2013100475A1
Application number: PCT/KR2012/011093
Authority: WO
Inventors: 박동현; 박경민
Original assignee: 주식회사 팬택
Priority date: 2011-12-27
Filing date: 2012-12-18
Publication date: 2013-07-04

Abstract

The present invention relates to a method and apparatus for applying PUSCH/PHICH scheduling timing in inter-band TDD transmission schemes. According to an embodiment of the present invention, the method for applying PUSCH/PHICH scheduling timing in inter-band TDD transmission schemes by a base station for controlling two or more different TDD bands includes the steps of: selecting a reference Physical Uplink Shared Channel (PUSCH)/Physical Hybrid ARQ Indicator Channel (PHICH) scheduling the timing of a UE, which supports cross-carrier scheduling by using two or more serving cells; transmitting instruction information for instructing the selected reference PUSCH/PHICH scheduling timing to the UE; and allocating an uplink and/or transmitting a PHICH to the UE according to the reference PUSCH/PHICH scheduling timing.

Description

Method and apparatus for applying PCSCH / PHICH scheduling timing in interband TCD transmission method

The present invention relates to a method and apparatus for supporting intercarrier scheduling regardless of a transmission mode of a user terminal in an inter-band time division duplex (TDD) transmission scheme. In other words, in a situation in which TDD transmission schemes between bands are different and scheduling between carriers is set, a method and apparatuses for enabling uplink scheduling while overcoming the limitation of transmission and reception subframes will be described.

As communication systems have evolved, consumers, such as businesses and individuals, have used a wide variety of wireless terminals. Mobile communication systems such as LTE (Long Term Evolution) and LTE-A (LTE Advanced) of the current 3GPP series are high-speed and large-capacity communication systems that can transmit and receive various data such as video and wireless data, beyond voice-oriented services. Therefore, there is a demand for developing a technology capable of transmitting a large amount of data corresponding to a wired communication network. As a method for transmitting a large amount of data, data can be efficiently transmitted through a plurality of CCs. Meanwhile, in a time division duplex (TDD) system, data may be transmitted and received by dividing transmission (Tx) and reception (Reception, Rx) into time slots using specific frequency bands.

On the other hand, in a carrier aggregation (carrier aggregation, or carrier combining, "CA") environment that combines one or more component carriers (CC), the band to which each component carrier belongs may be different. have. That is, when carrier combining is performed in the interband scheme, if the TDD settings of the respective bands are different, restrictions on the transmission and reception subframe may be applied according to the transmission mode of the user terminal. Such a limitation may also affect transmission and reception scheduling, and it is necessary to minimize the effect of such scheduling so that efficient transmission and reception is performed.

Under interband CA, regardless of the performance (full duplex, half duplex) of the user terminal when cross carrier scheduling is set, the current PUSCH / PHICH timing is maintained without any additional resources for all user terminals. I want to reuse it.

The present invention proposes reference PUSCH / PHICH timing that can be commonly used regardless of the characteristics of a UE in TDD under an interband CA, so that all interband CA terminals (ie half or full duplex UEs) To provide optimal system performance by providing optimal PUSCH / PHICH timing.

In an embodiment of the present invention, in a method of applying a PUSCH / PHICH scheduling timing for a base station controlling two or more bands having different time division duplex (TDD) configurations, two or more servings Transmitting uplink allocation or PHICH to a user terminal supporting cross-carrier scheduling using a serving cell and at least one PUSCH / PHICH scheduling timing of the two or more serving cells; Receiving a PUSCH from a user terminal, wherein the PUSCH / PHICH scheduling timing of the scheduling cell (scheduling cell) in the two or more serving cells according to the PUSCH / PHICH scheduling timing according to the TDD configuration of the scheduling cell, the scheduled cell ( PUSCH / PHICH scheduling timing of a scheduled cell according to a preset PUSCH / PHICH scheduling timing A method of applying PUSCH / PHICH scheduling timing in an interband TDD transmission scheme is provided.

In another embodiment of the present invention, in the PUSCH / PHICH (Physical Uplink Shared Channel / Physical Hybrid ARQ Indicator Channel) scheduling timing application method of a user terminal that transmits and receives data in two or more bands having different time division duplex (TDD) settings, Receiving uplink allocation or PHICH from a base station supporting cross-carrier scheduling using two or more serving cells and at least one PUSCH / PHICH scheduling timing of the two or more serving cells. And transmitting the PUSCH to the base station, wherein the PUSCH / PHICH scheduling timing of a scheduling cell in the two or more serving cells follows the PUSCH / PHICH scheduling timing according to the TDD configuration of the scheduling cell and is scheduled. PUSCH / PHICH scheduling timing of a scheduled cell is a preset PUSCH / PHICH scheduling tie In the inter-band TDD transmission scheme, characterized in that according it provides a method of applying the PUSCH / PHICH scheduling timing.

In another embodiment of the present invention, in a base station controlling two or more bands having different time division duplex (TDD) settings, cross-carrier scheduling is supported using two or more serving cells. A transmitter for transmitting an uplink assignment or a Physical Hybrid ARQ Indicator Channel (PHICH) to a user terminal, a receiver for receiving a PUSCH from the user terminal according to at least one PUSCH / PHICH scheduling timing of the at least two serving cells, and the at least two Physical Uplink Shared Channel (PUSCH) / PHICH scheduling timing of a scheduling cell in a serving cell follows PUSCH / PHICH scheduling timing according to the TDD configuration of the scheduling cell, and PUSCH / PHICH scheduling timing of a scheduled cell. Is a base station including a control unit for controlling to follow a preset PUSCH / PHICH scheduling timing; The.

In another embodiment of the present invention, in a user terminal that transmits and receives data in two or more bands having different time division duplex (TDD) settings, cross-carrier scheduling using two or more serving cells. A receiver for receiving an uplink assignment or a Physical Hybrid ARQ Indicator Channel (PHICH) from a base station supporting the UE, a transmitter for transmitting a PUSCH to the base station according to at least one PUSCH / PHICH scheduling timing of the two or more serving cells, and the two In the serving cell, the PUSCH / PHICH scheduling timing of a scheduling cell according to the PUSCH / PHICH scheduling timing according to the TDD configuration of the scheduling cell, and the PUSCH / PHICH scheduling of the scheduled cell The timing includes a controller for controlling to follow a preset PUSCH / PHICH scheduling timing. Provide a user terminal.

1 illustrates a wireless communication system to which embodiments of the present specification are applied.

2 is a diagram illustrating an inter-band CA environment according to an embodiment of the present specification.

3 is a diagram illustrating CA between bands in which different TDD settings are made according to an embodiment of the present specification.

4 is a diagram illustrating an operation method for each subframe according to a transmission mode of a user terminal in the inter-band CA environment of FIGS. 2 and 3.

5 is a diagram illustrating a case where there is no problem in PUSCH / PHICH scheduling timing in a CCS-configured network environment.

FIG. 6 is a diagram illustrating a case where a problem occurs in PUSCH / PHICH scheduling timing in a CCS-configured network environment.

FIG. 7 illustrates another case in which a problem occurs in PUSCH / PHICH scheduling timing in a CCS-configured network environment.

FIG. 8 illustrates a case in which a problem occurs in PUSCH / PHICH scheduling timing in a network environment independently of whether CCS is set.

FIG. 9 is a diagram illustrating a case in which a PCell is TDD # 1, a SCell is TDD # 2, and a reference PUSCH / PHICH timing is TDD # 0 according to an embodiment of the present specification.

FIG. 10 illustrates a case in which a PCell is TDD # 1, a SCell is TDD # 2, and a reference PUSCH / PHICH timing is TDD # 1 according to an embodiment of the present specification.

FIG. 11 is a diagram illustrating another case in which a PCell is TDD # 1, a SCell is TDD # 2, and a reference PUSCH / PHICH timing is TDD # 0 according to an embodiment of the present specification.

12 is a diagram illustrating another case in which a PCell is TDD # 1, a SCell is TDD # 2, and a reference PUSCH / PHICH timing is TDD # 1 according to an embodiment of the present specification.

FIG. 13 is a diagram illustrating a case in which a PCell is TDD # 5, a SCell is TDD # 1, and a reference PUSCH / PHICH timing is TDD # 6 according to an embodiment of the present specification.

14 is a diagram illustrating a PHICH configuration in a UE in full-duplex transmission mode.

FIG. 15 is a diagram illustrating cases classified according to characteristics of a scheduling cell and a scheduled cell.

FIG. 16 is a diagram illustrating PUSCH / PHICH scheduling timing of a cell scheduled in a first case (Case A in FIG. 15).

FIG. 17 is a diagram illustrating PUSCH / PHICH scheduling timing of a cell scheduled in a second case (Case B in FIG. 15).

FIG. 18 is a diagram illustrating a case where a reference PUSCH / PHICH configuration is TDD # 0 and is set to “n + 7” in Equation 1 according to an embodiment of the present specification.

19 is another diagram illustrating a case where a reference PUSCH / PHICH configuration is TDD # 0 and is set to “n + 7” in Equation 1 according to an embodiment of the present specification.

FIG. 20 is a diagram illustrating a process of an eNB signaling reference PUSCH / PHICH scheduling timing information to a UE according to one embodiment of the present specification.

21 is a diagram illustrating a process of providing a reference PUSCH / PHICH scheduling timing to a user terminal by the base station according to an embodiment of the present invention and transmitting uplink allocation and / or PHICH accordingly.

FIG. 22 is a diagram illustrating a process in which a user terminal of an interband TDD transmission method receives indication information on a reference PUSCH / PHICH scheduling timing from a base station and thus receives uplink allocation and / or PHICH according to an embodiment of the present invention. Drawing.

23 is a diagram illustrating a configuration of a base station according to an embodiment of the present invention.

24 is a diagram illustrating a configuration of a user terminal according to an embodiment of the present invention.

25 and 26 are block diagrams of a base station and a user terminal according to the embodiment described with reference to FIGS. 15 to 17.

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

Wireless communication systems are widely deployed to provide various communication services such as voice and packet data.

Referring to FIG. 1, a wireless communication system includes a user terminal 10 (User Equipment, UE) and a base station 20 (Base Station, BS, or eNB). The user terminal 10 in the present specification is a generic concept that means a terminal in wireless communication, WCDMA, UE (User Equipment) in LTE, HSPA, etc., as well as MS (Mobile Station) in GSM, UT (User Terminal) ), SS (Subscriber Station), wireless device (wireless device), etc. should be interpreted as including the concept.

A base station 20 or a cell generally refers to a station that communicates with the user terminal 10, and includes a Node-B, an evolved Node-B, an Sector, and a Site. Other terms may be referred to as a site, a base transceiver system (BTS), an access point, a relay node, and the like.

That is, in the present specification, the base station 20 or a cell is a generic term representing some areas or functions covered by a base station controller (BSC) in CDMA, a NodeB in WCDMA, an eNB or a sector (site) in LTE, and the like. It should be interpreted as meaning, and it is meant to cover all the various coverage areas such as megacell, macrocell, microcell, picocell, femtocell and relay node communication range.

In the present specification, the user terminal 10 and the base station 20 are two transmitting and receiving entities used in implementing the technology or the technical idea described in the present specification and are used in a comprehensive sense and are not limited by the terms or words specifically referred to. Do not. The user terminal 10 and the base station 20 are two (uplink or downlink) transmission and reception subjects used in implementing the technology or the technical idea described in the present invention, which are used in a comprehensive sense and are specifically referred to terms or words. It is not limited by. Here, the uplink (Uplink, UL, or uplink) means a method for transmitting and receiving data to the base station 20 by the user terminal 10, the downlink (Downlink, DL, or downlink) is the base station 20 By means of transmitting and receiving data to the user terminal 10 by means of.

There is no limitation on the multiple access scheme applied to the wireless communication system. Various multiple access techniques such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), OFDM-FDMA, OFDM-TDMA, OFDM-CDMA Can be used. One embodiment of the present invention can be applied to resource allocation in the fields of asynchronous wireless communication evolving to LTE and LTE-advanced through GSM, WCDMA, HSPA, and synchronous wireless communication evolving to CDMA, CDMA-2000 and UMB. The present invention should not be construed as being limited or limited to a specific wireless communication field, but should be construed as including all technical fields to which the spirit of the present invention can be applied.

The uplink transmission and the downlink transmission may use a time division duplex (TDD) scheme that is transmitted using different times, or may use a frequency division duplex (FDD) scheme that is transmitted using different frequencies.

In addition, in a system such as LTE LTE-A, a standard is configured by configuring uplink and downlink based on one carrier or a pair of carriers. The uplink and downlink transmit control information through control channels such as Physical Downlink Control CHannel (PDCCH), Physical Control Format Indicator CHannel (PCFICH), Physical Hybrid ARQ Indicator CHannel (PHICH), and Physical Uplink Control CHannel (PUCCH). A data channel is configured such as PDSCH (Physical Downlink Shared CHannel), PUSCH (Physical Uplink Shared CHannel) and the like to transmit data.

On the other hand, in the TDD, the downlink and uplink time points are divided. When various TDD configurations exist, these time points may also vary.

Table 1 below shows the TDD configuration. It can be seen that each TDD configuration has a different UL-DL subframe transmission timing.

Table 1 Uplink-downlink configurations

In Table 1, a region denoted by D is a downlink and a region denoted by U is an uplink in a radio frame corresponding to 10 subframes. S is a special subframe, which is a downlink-to-uplink switch-point periodicity that is switched from downlink to uplink.

On the other hand, when using one of the TDD configuration, the UE may know in advance at which time is downlink and at what time. This information allows the terminal to predict and operate in advance.

Meanwhile, the TDD setting may be differently set for each band. However, there is a case in which one terminal uses carriers included in these differently configured bands.

Reference numeral 210 shows that two component carriers are configured, CC1 211 is a carrier having a coverage of the signal transmitted from the eNB at high power, CC2 212 is transmitted from the eNB at low power (low power) It is a carrier having signal coverage. The CC1 211 and the CC2 212 may be included in different bands. The TDD configuration of the CC1 211 is 1 and is the same as the reference number 281, and the TDD configuration of the CC2 212 is 2 and the same as the reference number 282. On the other hand, reference numeral 215 denotes a hot-spot area, which is composed of CA environments of CC1 211 and CC2 212. Reference numeral 210 may also configure a CA for UEs in CC2 coverage.

In this case, the user terminal communicating with the hot spot 215 has different TDD settings called CC1 211 and CC2 212, which means that some subframes have different uplink subframes and downlink subframes for each component carrier. Can be set.

In this case, depending on whether the transmission mode supported by the user terminal is half-duplex or full-duplex, the operation schemes differ for each subframe.

3 shows a different TDD UL-DL configuration on inter-band between interbands that may be used for the purpose of traffic adaptation.

Different TDD UL-DL configurations are required on inter-band CAs to avoid interference issues with other co-existence TDD systems (eg TD-SCDMA, Mobile WiMAX, etc.) in the same band. do.

UL subframes on a low frequency band follow many TDD UL-DL configurations, and on the high frequency band, a TDD UL-DL configuration having many DL subframes can be derived. This configuration is helpful for coverage enhancement, and can also affect peak throughput.

Referring to FIG. 3 in more detail, the TDD configuration is performed such that the band A 310 and the band B 320 are not the same or collide with each other. Accordingly, the component carrier a of the band A 310 operates in the TDD configuration # 1 using the LTE scheme, and the component carrier b operates in the TDD configuration 1 in the LTE-A scheme. The component carrier c of the band B 320 operates in the TDD configuration 2 in the LTE-A scheme. Meanwhile, the component carrier d of the band B 320 is operated by the TD-SCDMA scheme. In the same band, the same TDD UL-DL configuration is configured, or it is configured not to collide with each other like component carriers c and d.

In this case, the TDD configuration is different in the case of the UE having the component carriers b and c as CAs (inter-band CA with different UL-DL configurations). This may mute some subframes or simultaneously perform simultaneous transmission / reception (simultaneous Tx / Rx) as shown in FIG. 4, depending on whether the terminal is in a half-duplex transmission mode or a full-duplex transmission mode.

4 is a diagram illustrating an operation method for each subframe according to a transmission mode of a user terminal in the inter-band CA environment of FIGS. 2 and 3. CC1 is a PCell (Primary Cell) and CC2 is a SCell (Secondary Cell).

Reference numeral 410 of FIG. 4 indicates that when the user terminal supports only the half-duplex transmission mode, only the uplink subframe of the PCell operates in

subframes

3 and 8 of the radio frames, and the downlink subframe of the SCell operates. That is,

subframes

3 and 8 of the SCell operate as muted subframes. In reference numeral 410, a sub-frame in which the downlink and uplink collide with each other (subframes 3 and 8) is operated in a half-duplex transmission mode such that only the downlink or uplink operates in only one subframe.

On the other hand, if the user terminal supports only full-duplex transmission mode, the reference numeral 420, in

subframes

3 and 8 of the radio frame, both the uplink subframe of the PCell and the downlink subframe of the SCell is operated. That is, in the full-duplex transmission mode, since transmission and reception can be simultaneously implemented (Simultaneous Tx / Rx), uplink / downlink in each of the PCell and the SCell can be implemented. In reference numeral 420, even in subframes in which the downlink and uplink collide with each other (subframes 3 and 8), the full-duplex transmission mode is operated, so that each downlink or uplink subframe is operated.

In the configuration of FIG. 4, in case of user terminals in a half-duplex transmission mode, a reference TDD UL-DL configuration may be used. That is, information about which direction (uplink or downlink) to select on a conflicting subframe may be selected (determined) through reference TDD UL-DL configuration information. In this case, problems such as HARQ timing and scheduling timing are raised due to different TDD UL-DL configurations.

[Table 2] Setting of k Scheduling Timing in TDD

Table 2 is a table related to scheduling timing in which PUSCH transmission occurs in n + k subframes when uplink allocation and / or PHICH (UL grant and / or PHICH) is transmitted in subframe n.

Meanwhile, Tables 1 and 2 are combined to show PUSCH / PHICH scheduling timing according to UL / DL configuration.

[Table 3] Uplink-downlink configurations with PUSCH / PHICH scheduling timing according to UL / DL configuration

In Table 3, the gray shaded portion indicates PUSCH / PHICH scheduling timing, and uplink allocation and / or PHICH may be transmitted in gray shaded portion (UL grant and / or PHICH).

Meanwhile, when different TDD settings are made in different CCs considered in the interband CA environment of FIGS. 3 and 4, inter-carrier scheduling (cross carrier scheduling, cross-carrier scheduling, hereinafter referred to as 'CCS') If set, scheduling problems may appear. Of course, a scheduling problem does not occur for a UE that does not have CCS configured, and existing timing rules can be reused.

Even if CCS is configured, the example shows that the problem does not appear in a combination of a specific TDD configuration and a specific UE type (for example, full duplex or half duplex).

In the interband CA environment, CCS is set to the PCell (CCS Serving Cell) and TDD is set to be cell-specific, as shown in FIG. 5. In the PCell, TDD # 2 (TDD Configuration # 2) is used. In the SCell, as shown by reference numeral 520, the PUSCH / PHICH scheduling problem does not appear when the UE, which is a user terminal in full duplex mode, is set in TDD # 1 (TDD Configuration # 1). This is because the user terminal can operate both the downlink in the PCell and the uplink in the SCell in the third and eighth subframes in which the " uplink allocation / PHICH " is transmitted in TDD # 2 as shown by reference numeral 510 (full duplex). ), There is no problem with scheduling.

FIG. 6 is a diagram illustrating a case where a problem occurs in PUSCH / PHICH scheduling timing in a CCS-configured network environment. In FIG. 6, the UE occurs in a full duplex transmission mode. Therefore, the problem of FIG. 6 naturally also occurs in the UE in half-duplex transmission mode.

6,

reference numerals

610 and 620 denote PCells of TDD # 1 and SCells of TDD # 2, respectively. In FIG. 6, if the PCell and the SCell use the PUSCH / PHICH timing used in each TDD configuration, when the CCS is configured on the PCell because the TDD # 1 set to the PCell has a smaller number of DL subframes than the TDD # 2 set to the SCell There is a problem in that PUSCH / PHICH scheduling for PUSCH transmission transmitted on the SCell cannot be performed.

That is, in subframe 3, since the PCell is an uplink subframe, the CCell for PUSCH transmission of the SCell cannot be performed. This is also the case in subframe 8.

In other words, in a situation where CCS is set, the PCell becomes a subject of "UL grant and / or PHICH transmission" at the corresponding timing in the PCell. Because it is a UL subframe

FIG. 7 is another diagram illustrating a case where a problem occurs in PUSCH / PHICH scheduling timing in a CCS-configured network environment. In FIG. 7, the problem occurs in the UE in half-duplex transmission mode.

Reference numerals

710 and 720 of FIG. 7 denote PCell of TDD # 1 and SCell of TDD # 2, respectively. In FIG. 7, if the PCell and the SCell use the PUSCH / PHICH timing used for each TDD configuration, the CCS is configured on the PCell because the TDD # 1 set to the PCell has a smaller number of DL subframes than the TDD # 2 set to the SCell. There is a problem in that PUSCH / PHICH scheduling cannot be performed.

In other words, in a situation where CCS is set, the PCell becomes a subject of "UL grant and / or PHICH transmission" at the corresponding timing in the PCell. This is because it is a UL subframe.

FIG. 8 illustrates a case in which a problem occurs in PUSCH / PHICH scheduling timing in a network environment independently of whether CCS is set. In FIG. 8, this is a problem occurring in the UE in half-duplex transmission mode, and is applied independently of CCS setting.

Reference numerals

810 and 820 of FIG. 8 denote PCell of TDD # 5 and SCell of TDD # 1, respectively.

In FIG. 8, the UE is not a problem in the full duplex transmission mode. Because the PCell has a larger number of DL subframes than the SCell, even when CCS is set, the PUSCH / PHICH timing on the SCell can be maintained as it is. Of course, even when CCS is not set, following the timing of the PCell can not be a problem. However, this may be a problem in the case of a UE in half-duplex transmission mode. If the PUSCH / PHICH timing set on the PCell is followed as it is, if DL subframe 8 of the PCell is muted among colliding subframes, PUSCH transmission cannot be performed on the UL subframe of subframe 2 of the PCell.

6, 7, and 8 described above may appear in the same form in other combinations. Hereinafter, in the present specification, a method of configuring common PUSCH / PHICH scheduling timing and its setting are provided to each UE regardless of the capability of the UE (whether in full duplex mode or half duplex mode) under the above conditions. We will look at the signaling process and configuration.

The method described below applies a common method while reusing the current PUSCH / PHICH timing as it is without wasting additional physical resources for all UEs in half or full duplex mode when CCS is configured. . As a result, it is possible to maximize the performance of the UE, which is an interband CA, and can be applied to a situation in which two or more different TDD settings are made, and thus has scalability.

A method of configuring new PUSCH / PHICH timing according to an embodiment of the present specification is as follows. The following embodiment will be described based on two cells, but the present invention is not limited thereto and may be applied to more cells.

First, the eNB compares TDD settings respectively set in the corresponding serving cells (i.e. PCell and SCells).

A common downlink subframe (DL, Downlink) subframe is found in two cells. In the DL subframes denoted as D / S in each TDD configuration of Table 1 or 3, a common DL subframe number for each TDD configuration is shown in Table 4 below. Table 4 has the same value based on the diagonal due to the nature of the intersection. That is, the common DL subframes in PCell TDD configuration 2 and SCell TDD configuration 5 are the same as the common DL subframes in PCell TDD configuration 5 and SCell TDD configuration 2 {0, 1, 3, 4, 5, 6, 8 , 9}.

[Table 4] Common DL Subframe by TDD Configuration of PCell / SCell

If a common DL subframe is found for each TDD configuration, the common DL subframe is referred to by referring to the PUSCH / PHICH timing supported in each TDD configuration currently used in Rel-8 / 9/10 within the common DL subframes. Finds reference PUSCH / PHICH timing that can be supported through

As such, Candidates of Reference PUSCH / PHICH scheduling timings are shown in Table 5 below. The numbers in Table 5 refer to the TDD configuration of Tables 2 and 3.

[Table 5] Candidate of reference PUSCH / PHICH timing (TDD setting value)

The values in Table 5 refer to TDD set values. Of the candidates in Table 5, when the eNB signals one value to the UE side, the signaled timing becomes the reference PUSCH / PHICH timing, and the eNB and the UE transmit uplink allocation and / or PHICH transmission using the reference PUSCH / PHICH timing. Can be performed.

A signaling rule for signaling a value for the reference PUSCH / PHICH timing will be described.

Table 4 is configured by the eNB and the corresponding information may be set by the eNB in a UE-specific method. Therefore, in Table 5, the information on the reference PUSCH / PHICH timing selected based on the TDD configuration of each PCell and SCell may be transmitted through higher layer signaling (eg, RRC (Radio Resource Control)) or PDCCH.

In addition, the corresponding information may have an offset form and may indicate a configuration regarding reference PUSCH / PHICH timing by lowering an offset value based on a PCell or SCell TDD configuration that is currently set as cell specific. This can be applied to both the method indicated by RRC and PDCCH.

The base station may predefine the appropriate PUSCH / PHICH timing according to the system bandwidth.

The above scheme will be applied to FIGS. 9 to 12.

9 to 12 are both TDD # 1 and TDD # 2 (PCell is TDD # 1, SCell is TDD # 2), performs CCS on the PCell, and scheduling for PUSCH transmission transmitted on the SCell is performed on the PCell. Is done. 9 to 12, when applying Table 4, the common DL subframe becomes

subframes #

0, 1, 4, 5, 6, and 9.

Meanwhile, referring to candidates for the reference PUSCH / PHICH timing of Table 5, which is an intersection between the common DL subframe and the gray colored portion (uplink allocation and / or PHICH transmission subframe) of Table 3, TDD configuration # 0, # 1, # 6. Under these assumptions, consider the following example.

9 and 10 show that PUSCH / PHICH scheduling is possible when the embodiment of the present invention is applied in an interband CA environment in which CCS is configured without muting of subframes collided in a full duplex transmission mode UE.

As indicated by

reference numerals

910 and 920 of FIG. 9, reference PUSCH / PHICH timing is # 0 for both PCell and SCell, and as a result, PUSCH / PHICH scheduling is performed in

subframes

0, 1, 5, and 6.

In FIG. 6, subframe # 3 of the PCell is used for transmitting the PUSCH in subframe # 7 of the SCell, and subframe # 8 of the PCell is the PUSCH / PHICH scheduling subframe for transmitting the PUSCH in subframe # 2 of the SCell. However, since the PCell of FIG. 6 is TDD # 1, there has been a problem that subframes # 3 and # 8 are uplink subframes. However, in FIG. 9, since the reference PUSCH / PHICH timing is TDD # 0, subframes # 1 and # 6 of the PCell may be used. That is, when the reference PUSCH / PHICH timing is TDD # 0, the application of TDD # 0 shown in Table 2 is as follows. When uplink allocation / PHICH is transmitted in subframe # 1 of the PCell, PUSCH transmission is performed in subframe # 7 of the SCell (910 and 930). If uplink allocation / PHICH is transmitted in subframe # 6 of the PCell, PUSCH transmission is performed in subframe # 2 of the next radio frame of the SCell (920).

FIG. 10 is a diagram illustrating a case in which a PCell is TDD # 1, a SCell is TDD # 2, and a reference PUSCH / PHICH timing is TDD # 1 according to an embodiment of the present specification. In FIG. 10, when the reference PUSCH / PHICH timing is TDD # 1, the application of TDD # 1 shown in Table 2 is as follows. If uplink allocation / PHICH is transmitted in subframe # 1 of the PCell, PUSCH transmission is performed in subframe # 7 of the SCell (1010 and 1030). If uplink allocation / PHICH is transmitted in subframe # 6 of the PCell, PUSCH transmission is performed in subframe # 2 of the next radio frame of the SCell (1020). In addition, in FIG. 10, in order to perform PUSCH transmission in subframe # 8 of the PCell, uplink allocation / PHICH is transmitted in subframe # 4 of the PCell (1040). On the 9th DL subframe of the PCell, PUSCH transmission may be scheduled in subframe # 3 of radio frame # 2 of the PCell (1050). This is because SCell subframe # 3 is a DL, so PUSCH transmission can be scheduled only in subframe # 3 of the PCell.

11 and 12 show that PUSCH / PHICH scheduling is possible when the embodiment of the present invention is applied in an interband CA environment in which CCS is set in a situation where muting of subframes collided in a UE of a half-duplex transmission mode is performed.

FIG. 11 is a diagram illustrating another case in which a PCell is TDD # 1, a SCell is TDD # 2, and a reference PUSCH / PHICH timing is TDD # 0 according to an embodiment of the present specification. The UE in half-duplex transmission mode mutes in the colliding subframe. Muting subframe # 3 of PCell and subframe # 8 of SCell. Even in this situation, the application of the reference PUSCH / PHICH timing TDD # 0 according to the embodiment of the present invention is as follows. When uplink allocation / PHICH is transmitted in subframe # 1 of the PCell, PUSCH transmission is performed in subframe # 7 of the SCell (1110 and 1130). If uplink allocation / PHICH is transmitted in subframe # 6 of the PCell, PUSCH transmission is performed in subframe # 2 of the next radio frame of the SCell (1120). Of course, since the subframes # 1 and # 6 are the "S" subframes of the PCell and the SCell, the muting problem in the UE of the half-duplex transmission mode does not occur.

12 is a diagram illustrating another case in which a PCell is TDD # 1, a SCell is TDD # 2, and a reference PUSCH / PHICH timing is TDD # 1 according to an embodiment of the present specification. The UE in half-duplex transmission mode mutes in the colliding subframe. Muting subframe # 3 of PCell and subframe # 8 of SCell. Even in this situation, the application of the reference PUSCH / PHICH timing TDD # 1, which is an embodiment of the present invention, is as follows. When uplink allocation / PHICH is transmitted in subframe # 1 of the PCell, PUSCH transmission is performed in subframe # 7 of the SCell (1210 and 1230). If uplink allocation / PHICH is transmitted in subframe # 6 of the PCell, PUSCH transmission is performed in subframe # 2 of the next radio frame of the SCell (1220). Of course, since the subframes # 1 and # 6 are the "S" subframes of the PCell and the SCell, the muting problem in the UE of the half-duplex transmission mode does not occur. In addition, in order to perform PUSCH transmission in subframe # 8 of the PCell, uplink allocation / PHICH is transmitted in subframe # 4 of the PCell, and no muting problem occurs in subframe # 4.

When the PUSCH / PHICH timing of

TDD #

0 or 1 is applied to the reference PUSCH / PHICH timing in the embodiments of FIGS. 9 to 12 (PCell with TDD # 1 and SCell with TDD # 2), a full-duplex / half-duplex transmission mode of the UE It can be applied regardless.

The UE in half-duplex transmission mode mutes in the colliding subframe. Mutes subframes # 3, # 7, and # 8 of the PCell.

The candidates for the reference PUSCH / PHICH timing are 0, 1, and 6 according to Table 5. In FIG. 13, # 6 is applied as the reference PUSCH / PHICH timing.

As a result, unlike the situation in which subframes # 7 and # 8 are muted in FIG. 4 and thus cannot operate as a PUSCH / PHICH scheduling subframe, in FIG. 13, PUSCH transmission is performed in subframes # 2 and # 3 of the SCell. For example, subframes # 5 and # 6 of the PCell operate as PUSCH / PHICH scheduling subframes (1330 and 1340). Likewise, in order to perform PUSCH transmission in subframes # 7 and # 8 of the SCell, subframes # 0 and # 1 of the PCell operate as PUSCH / PHICH scheduling subframes (1310, 1320, 1350, and 1360).

In addition, we have considered common PHICH timing (= DL HARQ-ACK timing) for both PCC (PCell) and SCC (SCell), but with backward compatibility issues, e.g., legacy UEs Due to different PHICH timing between Rel-11 UEs, there is a disadvantage in that a solution for a problem resulting from understanding of different control regions is required. Alternatively, the PCC follows the PHICH timing according to the TDD configuration, and the SCCs find the common DL subframes in the TDD configuration of the PCC and the SCCs, and support the PHICH timing on the DL subframe. timing, that is, found in an existing PHICH timing table. The reference PHICH timing thus found is applicable only for SCCs. The DL subframe transmitting the PHICH of the PCC and the DL subframes transmitting the PHICH of the PHICH timing selected from the above reference PHICH timings are compared to cross-carrier only in the DL subframe having the common timing with the PHICH timing of the PCC. Cross-carrier scheduling is allowed, and self scheduling is performed on the DL subframe that is not. That is, it partially permits cross-carrier scheduling.

14 is a diagram illustrating a PHICH configuration in a UE in full-duplex transmission mode. The TDD setting 2110 of the PCell (or PCC) is # 1, and the TDD setting 2120 of the SCell (or SCC) is # 3. Applying Table 5 to select the timing candidate value, TDD settings # 0 and # 6 are derived.

Here, the PCell (or PCC) follows the PHICH timing of TDD configuration 1 as it is, and the SCell (or SCC) applies Table 5 to determine the PHICH timing that can be applied on the PCell (or PCC) and SCell (or SCC) configuration. You can choose. That is, a method of finding a candidate of reference PUSCH / PHICH timing shown in Table 5 by using a TDD setting value may be applied. This means selecting a candidate of common downlink HARQ-ACK timing for the PCell and the SCell.

The possible PHICH timing (= DL HARQ-ACK timing) for the SCell (or SCCs) in FIG. 14 is the PHICH timing of

TDD configuration

0 or 6. However, to maintain backward compatibility, cross-carrier scheduling is allowed only on DL subframes (

ie subframe #

1, or 6, 9) equal to the PHICH timing of PCC at

PHICH timing

0 or 6 applied only for SCC. , Subframes that do not correspond to PHICH timing at 0 or 6 (ie, subframes # 0 and # 5 when PHICH timing 0 or 6) supports only self scheduling. Thus, cross carrier scheduling of SCell (or SCCs) may be partially used in consideration of the PHICH timing of the PCell (or PCC). In this way, the DL HARQ operation via PHICH is provided to the transmission mode (half or full duplex UE) of the UE through a common method without a performance degradation problem even in different TDD UL-DL configuration situations. There is an advantage to this. The full-duplex transmission mode means that both transmission and reception are possible at the same time, and the half-duplex transmission mode means that both transmission and reception are possible, but at any point in time, only transmission or reception is possible.

As another method, when scheduling between carriers is set, a PUSCH / PHICH scheduling timing method is proposed based on a set of specific TDD UL-DL configuration combinations. The PCell operates as a scheduling cell when scheduling between carriers, and the proposed method is applied under the assumption that the SCell is configured as a scheduled cell. Of course, when there are two or more serving cells, a specific SCell may operate as a scheduling cell of other SCells (in this case, at least a PCell and a cell scheduled by a specific SCell). Like the previous method, the scheduling cell (i.e. PCell) always follows the PUSCH / PHICH scheduling timing of the TDD configuration of the scheduling cell.

However, with respect to PUSCH / PHICH scheduling timing of a scheduled cell (i.e. SCell), there may be various methods according to various cases. The following proposals all describe the application method for PUSCH / PHICH scheduling timing for scheduled cells in a case where different TDD UL-DL configurations are configured in a CA environment and intercarrier scheduling is configured.

The following describes PUSCH / PHICH scheduling timing applied to four scheduled cells according to each case, classified into four cases according to the characteristics of a scheduled cell and a scheduled cell. However, the present invention is not limited to the following case classification method, and when the TDD setting values of the scheduled cell and the scheduled cell are the same, it should be interpreted that the same PUSCH / PHICH scheduling timing is applied regardless of the case classification. For example, in the case where the combination of the scheduled cell and the scheduled cell is (0, 1), the classification is described below in the third case, and the PUSCH / PHICH scheduling timing of the scheduled cell is set to 0 along the scheduling cell. In the present invention, the present invention should not be limited to such a case classification. When the combination of the scheduling cell and the scheduled cell is (0, 1), the PUSCH / PHICH scheduling timing of the scheduled cell is All set values 0 should be interpreted as falling within the scope of the present invention.

Referring to FIG. 15, the remaining combinations except for the same combination of the scheduling cell and the scheduled cell are classified into four cases of Case A, Case B, Case C, and Case D.

In a case where different TDD UL-DL configurations are set in a CA environment and intercarrier scheduling is set, the first method of applying a PUSCH / PHICH scheduling timing to scheduled cells is a scheduling cell. TDD of the scheduling cell and the case of having an UL super set compared to this scheduled cell (for example, UL subframes of the PCell include all of the UL subframes of the SCell) and the TDD of the scheduling cell. If the PUSCH HARQ Round Trip Time (RTT) of the configuration is 10 ms (that is, the TDD pair of the scheduling cell and the scheduled cell is (1,2) (1,4) (1,5) (2,5) (3, 4) (3,5) (4,5) case is the case (case A in Fig. 15). In this case, the RTT is a time from when the eNB receives the PUSCH and the A / N (Ack / NAck) information about it arrives at the UE based on the subframe in which the UL allocation (UL grant) is transmitted for the first PUSCH transmission. Means. In this case, the PUSCH / PHICH scheduling timing of the scheduling cell (i.e. PCell) is applied to the scheduled cell (i.e. SCell).

Referring to FIG. 16, when the TDD configuration pair of the scheduled cell and the scheduled cell is (1, 2), the PUSCH / PHICH scheduling timing of the scheduled cell becomes TDD UL-DL configuration value 1 along the scheduling cell. All other TDD configuration pairs belonging to the first case also follow the scheduling cell of the PUSCH / PHICH scheduling timing of the scheduled cell.

In the second case, if the scheduling cell is an uplink subset compared to the scheduled cell and the PUSCH HARQ RTT of the TDD UL-DL configuration of the scheduling cell is 10ms (that is, the TDD of the scheduling cell and the scheduled cell) Set pair is (1,0) (1,6) (2,0) (2,1) (2,6) (3,0) (3,6) (4,0) (4,1) (4, 3), (4,6) (5,0) (5,1) (5,2) (5,3) (5,4) (5,6) In this case, various methods can be applied ( Case B) in FIG. 15. As one of these methods, one of a-i), a-ii), a-iii), and a-iv) may be applied, and each method will be described below.

a-i) applies the PUSCH / PHICH scheduling timing of the scheduled cell as it is to the scheduled cell in order to maintain peak data rate.

FIG. 17 is a diagram illustrating PUSCH / PHICH scheduling timing of a cell scheduled in a second case (Case B in FIG. 15). Figure 17 follows the method a-i).

Referring to FIG. 17, when the TDD configuration pair of the scheduled cell and the scheduled cell is (1,0), the PUSCH / PHICH scheduling timing of the scheduled cell becomes the TDD UL-DL configuration value 0 along the scheduled cell. All other TDD configuration pairs belonging to the second case also follow the scheduled cell PUSCH / PHICH scheduling timing.

a-ii) In the method, reference PUSCH / PHICH scheduling timing is applied to a scheduled cell. The reference PUSCH / PHICH scheduling timing is selected by the eNB from the existing PUSCH / PHICH scheduling timings by applying an appropriate PUSCH / PHICH scheduling timing to the UE by signaling through a higher layer signaling or a dynamic signaling. . In this case, the signaling may be cell-specific or UE-specific. However, the methods ai) and a-ii) above are resource conflicts due to the understanding of different control regions between Rel-8 / 9/10 UEs and Rel-11 UEs as previously described. May cause. Therefore, in order to solve the problem, only a DL subframe in which a DL subframe in which a PHICH and / or UL grant is transmitted is transmitted in a PUSCH / PHICH scheduling timing of a scheduling cell is the same as that of a cell scheduled. Inter-scheduling can be allowed. The a-iii) method follows the PUSCH / PHICH scheduling timing of the scheduling cell just like a-i) and a-ii). However, a-iii) method is the simplest and is not a problem, but the disadvantage is that the peak data rate is reduced. Finally, in the method a-iv), the above methods a-i), a-ii), and a-iii) may be changed to the configuration of the eNB. Therefore, in consideration of the capability (capability) of each UE, a-i), a-ii), a-iii) may be appropriately set among the methods to apply to each UE. In this case, there is a problem that the complexity of the implementation may increase.

The third case is when the PUSCH HARQ RTT of the scheduling cell is not 10ms. (I.e., the TDD configuration pair of the scheduling cell and the scheduled cell is (0,1) (0,2) (0,3) (0,4) (0,5) (0,6) (6,0) ( 6,1) (6,2) (6,3) (6,4) (6,5)) In this case, follow the PUSCH / PHICH scheduling timing of the scheduling cell to avoid further problems. (Case D of FIG. 15). In the case of (6,0) exceptionally, that is, the TDD UL-DL configuration of the scheduling cell is 6 and that of the scheduled cell is 0. Only in this case, the PUSCH / PHICH scheduling timing of the scheduled cell may be used.

The fourth case is the case where there is no correlation between the scheduling cell and the TDD UL-DL configuration of the scheduled cell. In this case, that is, an embodiment in which the scheduling cell and the TDD configuration pair of the scheduled cell are a combination of (1,3) (2,3) (2,4) (3,1) (3,2) (4,2). Corresponds to (case C in Figure 15). Basically, to reduce the complexity of the system implementation, the above combinations may be classified as unsupported combinations. However, if more TDD UL-DL configuration combinations are supported, the following method may be applied. In this case, the PUSCH / PHICH scheduling timing of the scheduled cell may follow the HARQ timing of the scheduling cell. Alternatively, PUSCH HARQ timing of a scheduled cell may be applied by allowing intercarrier scheduling only on a limited DL subframe for the HARQ timing of a scheduled cell. As described above, the restricted DL subframes are compared with the scheduled scheduling cell's PUSCH / PHICH scheduling timing of the scheduled cell and the scheduled scheduling cell's PUSCH / PHICH scheduling timing is different from that of the scheduled cell. Inter-carrier scheduling for cells scheduled on the DL subframe is not allowed. In addition, since a cell scheduled in a specific subframe is a DL subframe, and the scheduling cell is a UL subframe, physical intercarrier scheduling cannot be physically performed. In this case, intercarrier scheduling is not allowed.

Although described using the term PUSCH / PHICH scheduling timing, the present invention is not limited thereto. PUSCH / PHICH scheduling timing may be used as a term of PUSCH HARQ timing or may be used as a term of HARQ / PUSCH scheduling timing. In addition, it may also be used in terms of PUSCH / PHICH timing or HARQ / PUSCH timing.

On the other hand, when the TDD configuration is 0 in the TDD environment, an additional operation may be added and applied to the reference PUSCH timing.

That is, when the TDD configuration is 0 (TDD # 0), since there are more uplink subframes than the downlink subframe, multiple UL grant scheduling is possible in one downlink subframe. . This is related to the PDCCH transmitting the uplink allocation. In the case of PHICH, according to a specific parameter value, it signals which uplink subframe indicates an A / N for the PUSCH transmitted. Therefore, the following equation is satisfied. The following equation shows the condition of scheduling n + k and the condition of n + 7 in TDD # 0.

[Equation 1]

That is, if the condition for operating TDD # 0 is satisfied with n + k, scheduling is performed according to the k value set in Table 2, but if the condition for operating TDD # 0 with n + 7 is satisfied, TDD # The uplink allocation transmitted at 0 is then performed in the uplink subframe at the time point of the seventh timing.

Accordingly, in the case of applying n + k of Equation 1, in the embodiment of FIG. 9, UL grant / PHICH transmission may be transmitted after 4 subframes according to k values in subframe # 0, that is, in subframe # 4. Is not scheduled because it is a DL subframe. However, when n + 7 of Equation 1 is applied, it has a timing of n + 7 according to a specific condition. This timing can be applied as the reference PUSCH timing.

This will be described with reference to FIGS. 18 and 19.

FIG. 18 is a diagram illustrating a case where a reference PUSCH / PHICH configuration is TDD # 0 and is set to “n + 7” in Equation 1 according to an embodiment of the present specification. In FIG. 9, the reference PUSCH / PHICH configuration is # 0 and an n + k scheme is applied.

In FIG. 18, 1410, 1420, and 1430 are the same as 910, 920, and 930 of FIG. 9.

However, since n + 7 of TDD # 0 is applied herein, PUSCH transmission may be scheduled for subframe # 7 in subframe # 0. This is equal to 1440, 1450.

FIG. 19 is a diagram illustrating a case in which a reference PUSCH / PHICH configuration is TDD # 0 and is set to “n + 7” in Equation 1 according to an embodiment of the present specification. In FIG. 11, the reference PUSCH / PHICH configuration is # 0 and an n + k scheme is applied.

In FIG. 19, 1510, 1520, and 1530 are the same as 1110, 1120, and 1130 of FIG. 11.

However, since n + 7 of TDD # 0 is applied herein, PUSCH transmission may be scheduled for subframe # 7 in subframe # 0. This is the same as 1540 and 1550.

9 to 13, 18, and 19 may apply separate reference PUSCH / PHICH scheduling timing settings even when CCS is configured in an interband CA environment. Hereinafter, a process of sharing information on reference PUSCH / PHICH scheduling timing between an eNB and a UE will be described.

First, the UE 1610 receives information on the TDD configuration of the interband CA environment from the eNB 1620 (S1630). This can be done while the UE 1610 is connected to a network governed by the eNB 1620.

The eNB 1620 and the UE 1610 generate values of Candidates of Reference PUSCH / PHICH scheduling Timing or predefine table information as shown in Table 5 according to the respective TDD settings. Can be

Next, the eNB 1620 receives appropriate reference PUSCH / PHICH scheduling timing information among reference PUSCH / PHICH scheduling timing candidates to the UE in consideration of channel environment and geographical location of each UE 1610. It indicates to UE-specific (S1640). Indicative signaling methods may be transmitted on RRC or PDCCH. The eNB 1620 may indicate the reference PUSCH / PHICH timing value directly through the RRC or the PDCCH, and both the eNB 1620 and the UE 1610 are based on the table of Table 5, and the eNB 1620 has an offset ( Reference PUSCH / PHICH timing information may be indicated based on an offset) value.

That is, as shown in FIGS. 9 to 12, when the PCell is TDD # 1 and the SCell is TDD # 2, the reference PUSCH / PHICH timing candidates of Table 5 are {0, 1, 6}. If the eNB 1620 directly selects TDD # 6, the eNB 1620 may signal the information TDD # 6 (for example, the integer "6") to the UE 1610, and the eNB 1620 The offset 5 (offset 5 between the reference timing TDD # 6 and the PCell TDD # 1) may be signaled based on the TDD setting value of the PCell of the UE 1610.

As another method, the candidate values of Table 5 may be ordered to give an offset. That is, in the above {0, 1, 6}, the TDD # 0 is the first, the TDD # 1 is the second, the TDD # 6 is the third, and the UE 1610 is also confirming the candidate values in Table 5 in advance. As the state, the eNB 1620 may signal a value of 3 to indicate TDD # 6.

As a criterion for determining which reference PUSCH / PHICH timing is set for each UE by the eNB 1620, i) the channel environment of each UE, ii) the UL data traffic requirements of each UE, iii) Consider inter-cell interference with respect to PDCCH, which can be considered in a cell deployment environment. In addition, the eNB 1620 may derive optimal performance by setting reference PUSCH / PHICH timing suitable for each UE to all UEs in a full duplex / half duplex transmission mode in a cell.

All UEs in the full duplex / half duplex transmission mode operate the PDSCH HARQ operation with reference PUSCH / PHICH timing based on the above signaling information.

That is, uplink allocation and / or PHICH is transmitted according to the reference PUSCH / PHICH scheduling timing set in step S1640 (UL grant and / or PHICH) (S1650).

First, the base station transmits TDD configuration information in the interband CA environment (S1710). In this process, cross-carrier scheduling is set for two or more serving cells. A reference PUSCH / PHICH scheduling timing of a user terminal supporting inter-carrier scheduling is selected. In more detail, a common downlink subframe is identified in a TDD configuration of the at least two serving cells (S1730). In operation S1730, a reference PUSCH / PHICH scheduling timing is selected from one or more TDD configurations in which PUSCH / PHICH scheduling is possible in the common downlink subframe. This means selecting a reference PUSCH / PHICH scheduling timing that can be transmitted within a common downlink subframe from a conventional PUSCH / PHICH scheduling timing. For the types of two or more serving cells, the reference PUSCH / PHICH is applied by applying Table 5 to each other. One of the scheduling timing candidates may be selected. The selection criterion selects a reference PUSCH / PHICH scheduling timing in consideration of any one or more of a preset environment or one or more candidates (the one or more TDD settings) in consideration of a channel environment, a geographic location of the user terminal, and a size of transmission traffic of the user terminal. Can be. That is, the reference PUSCH / PHICH scheduling timing that can be used by the actual user terminal is selected from among candidates. Of course, the selection is not necessarily required, and the base station and the user terminal may omit a separate signaling process by setting only one reference PUSCH / PHICH scheduling timing applicable to each TDD configuration of each serving cell. In this case, when the TDD configuration information of step S1710 is shared between the base station and the user terminal, the user terminal can determine what reference PUSCH / PHICH scheduling timing is to be applied thereto without additional indication information signaling.

In operation S1740, the indication information indicating the selected reference PUSCH / PHICH scheduling timing is transmitted to the user terminal. The indication information may be indication information directly indicating the reference PUSCH / PHICH scheduling timing or may be indication information indicating offset information with a TDD setting configured in the user terminal. Thereafter, according to the reference PUSCH / PHICH scheduling timing, an uplink is allocated to the user terminal or a PHICH is transmitted (S1740).

The operation of FIG. 17 is operable by a base station such as an eNB and the exact reference timing may be signaled by the base station and may be predefine.

The case in which the PUSCH / PHICH scheduling timing is pre-defined is described in more detail.

When the PUSCH / PHICH scheduling timing is set in advance, the base station and the user terminal can know the PUSCH / PHICH scheduling timing information without additional signaling between the base station and the user terminal.

In this case, the base station transmits an uplink allocation or PHICH to the user terminal, and the user terminal transmits the PUSCH to the base station according to a preset PUSCH / PHICH scheduling timing.

The base station and the user terminal support the scheduling between the carrier using two or more serving cells, the two or more serving cells as described with reference to Figure 15 to 17 PUSCH / PHICH scheduling timing of the scheduling cell is TDD of the scheduling cell The PUSCH / PHICH scheduling timing according to the configuration may be followed, and the PUSCH / PHICH scheduling timing of the scheduled cell may follow a preset PUSCH / PHICH scheduling timing.

In addition, as described with reference to FIG. 16, when the scheduling cell has an uplink super set compared to the scheduled cell or when the PUSCH HARQ RTT (Round Trip Time) in the TDD configuration of the scheduling cell is 10 ms (scheduling cell and If the TDD configuration pair of the scheduled cell is (1,2), (1,4), (1,5), (2,5), (3,4), (3,5), or (4,5) ), The PUSCH / PHICH scheduling timing of the scheduled cell may follow the PUSCH / PHICH scheduling timing of the scheduling cell with a preset PUSCH / PHICH scheduling timing.

In addition, as described with reference to FIG. 17, when the scheduling cell corresponds to an uplink subset (UL subset) compared to the scheduled cell or when the PUSCH HARQ Round Trip Time (RTT) of the TDD configuration of the scheduling cell is 10 ms. (TDD configuration pairs of scheduling cells and scheduled cells are (1,0), (1,6), (2,0), (2,1), (2,6), (3,0), (3, 6), (4,0), (4,1), (4,3), (4,6), (5,0), (5,1), (5,2), (5,3) , (5,4), (5,6) or (6,0)), the PUSCH / PHICH scheduling timing of the scheduled cell is PUSCH / PHICH according to the TDD configuration of the scheduled cell with the preset PUSCH / PHICH scheduling timing. PHICH scheduling timing may be followed.

18 illustrates a process in which a user terminal of an interband TDD transmission method receives indication information on a reference PUSCH / PHICH scheduling timing from a base station according to an embodiment of the present invention and thus receives uplink allocation and / or PHICH accordingly; Drawing.

First, the user terminal receives TDD configuration information in an interband CA environment (S1810). In this process, cross-carrier scheduling is set for two or more serving cells. The user terminal supporting inter-carrier scheduling receives information indicating reference PUSCH / PHICH scheduling timing from the base station (S1820). In more detail, the reference PUSCH / PHICH scheduling timing includes the TPU configuration of PUSCH / PHICH scheduling in a common downlink subframe identified in the TDD configuration of the two or more serving cells. The base station selects or promises the user terminal in advance. When the base station selects, the base station may select one of reference PUSCH / PHICH scheduling timing candidates by applying Table 5 to the two or more types of serving cells. That is, one or more TDD settings may be selected in consideration of any one or more of a channel environment, a geographic location of the user terminal, and a size of transmission traffic of the user terminal.

Meanwhile, the indication information received in S1820 may be indication information directly indicating the reference PUSCH / PHICH scheduling timing or may be indication information indicating offset information with the TDD configuration set in the user terminal. Thereafter, according to the reference PUSCH / PHICH scheduling timing, an uplink is allocated from the base station or a PHICH is received (S1830).

19 is a diagram illustrating a configuration of a base station according to an embodiment of the present invention. The base station provides a reference PUSCH / PHICH scheduling timing to the user terminal in the interband TDD transmission scheme and thus transmits uplink allocation and / or PHICH. The base station 1900 of FIG. 19 is a base station that controls two or more bands of different time division duplex (TDD) configurations. The component is largely composed of a transmitter 1910, a controller 1920, and a receiver 1930.

The controller 1920 selects reference PUSCH / PHICH scheduling timing of a user terminal that supports cross-carrier scheduling using two or more serving cells. In more detail, the controller 1920 controls the transmitter 1910 to transmit TDD configuration information in an interband CA environment. In this process, cross-carrier scheduling is set for two or more serving cells. A reference PUSCH / PHICH scheduling timing of a user terminal supporting inter-carrier scheduling is selected. In more detail, the controller 1920 identifies a common downlink subframe in a TDD configuration of the two or more serving cells. The controller 1920 selects reference PUSCH / PHICH scheduling from one or more TDD settings that can be scheduled in PUSCH / PHICH in the common downlink subframe. This means selecting a reference PUSCH / PHICH scheduling timing that can be transmitted within a common downlink subframe from a conventional PUSCH / PHICH scheduling timing. For the types of two or more serving cells, the reference PUSCH / PHICH is applied by applying Table 5 to each other. One of the scheduling timing candidates may be selected. The controller 1920 may select the reference PUSCH / PHICH scheduling timing as follows. That is, in consideration of any one or more of a channel environment, a geographic location, and a size of the transmission traffic of the user terminal among the predetermined or predetermined criteria with respect to the user terminal or the candidates (the one or more TDD settings). Reference PUSCH / PHICH scheduling timing may be selected. That is, the controller 1920 selects a reference PUSCH / PHICH scheduling timing that can be used by an actual user terminal among candidates. Of course, the selection is not necessarily required, and the base station and the user terminal may omit a separate signaling process by setting only one reference PUSCH / PHICH scheduling timing applicable to each TDD configuration of each serving cell. When the TDD configuration information is shared between the base station and the user terminal, the user terminal may identify what reference PUSCH / PHICH scheduling timing is to be applied thereto without signaling additional indication information.

The transmitter 1910 transmits indication information indicating the selected reference PUSCH / PHICH scheduling timing to the user terminal. The indication information may be indication information directly indicating the reference PUSCH / PHICH scheduling timing or may be indication information indicating offset information with a TDD setting configured in the user terminal. Thereafter, the transmitter 1910 allocates an uplink or transmits a PHICH to the user terminal according to the reference PUSCH / PHICH scheduling timing. The receiver 1930 receives an uplink from the user terminal according to the reference PUSCH / PHICH scheduling timing.

20 is a diagram illustrating a configuration of a user terminal according to an embodiment of the present invention. The user terminal performs a function of receiving a reference PUSCH / PHICH scheduling timing from the base station in the interband TDD transmission scheme, receiving an uplink allocation and / or PHICH accordingly, and transmitting an uplink accordingly. The user terminal 2000 of FIG. 20 wirelessly connects to a base station that controls two or more bands of different time division duplex (TDD) configurations. A component largely consists of a transmitter 2010, a controller 2020, and a receiver 2030.

The transmitter 2010 transmits an uplink according to the reference PUSCH / PHICH scheduling timing described above. The receiver 2030 receives the indication information of the reference PUSCH / PHICH scheduling timing from a base station, and the controller 2020 controls the transmitter 2010 and the receiver 2030.

First, the receiver 2030 receives TDD configuration information in an interband CA environment. In this process, cross-carrier scheduling is set for two or more serving cells. The receiver 2030 of the user terminal supporting intercarrier scheduling receives information indicating reference PUSCH / PHICH scheduling timing from the base station. In more detail, the reference PUSCH / PHICH scheduling timing may be determined based on a TDD configuration in which PUSCH / PHICH scheduling is possible in a common downlink subframe identified in a TDD configuration of the two or more serving cells. The base station selects or promises the user terminal in advance. When the base station selects, the base station may select one of reference PUSCH / PHICH scheduling timing candidates by applying Table 5 to the two or more types of serving cells. That is, one or more TDD settings may be selected in consideration of any one or more of a channel environment, a geographic location of the user terminal, and a size of transmission traffic of the user terminal.

Meanwhile, the indication information received by the receiver 2030 may be indication information directly indicating the reference PUSCH / PHICH scheduling timing or may be indication information indicating offset information with the TDD setting set in the user terminal. have.

Thereafter, the control unit 2020 controls the receiving unit 2030 to receive an uplink or a PHICH from the base station according to the reference PUSCH / PHICH scheduling timing, and the transmitting unit 2010 controls the reference PUSCH / PHICH. Control uplink transmission according to the scheduling timing.

Referring to FIG. 25, the base station 2500 uses up two or more serving cells to perform uplink allocation or physical hybrid ARQ indicator channel (PHICH) to a user terminal that supports cross-carrier scheduling. In the transmitting unit 2510 and the two or more serving cells, the PUSCH / PHICH scheduling timing of the scheduling cell is based on the PUSCH / PHICH scheduling timing according to the TDD configuration of the scheduling cell and is scheduled. The PUSCH / PHICH scheduling timing of the (scheduled cell) may include a controller 2520 that controls to follow a preset PUSCH / PHICH scheduling timing and a receiver 2530 that receives a PUSCH from a user terminal according to the PUSCH / PHICH scheduling timing. Can be.

Referring to FIG. 26, the user terminal 2600 uses up two or more serving cells to perform uplink allocation or physical hybrid ARQ indicator channel (PHICH) from a base station supporting cross-carrier scheduling. In the receiving unit 2610, the two or more serving cells, the PUSCH / PHICH scheduling timing of the scheduling cell (scheduling cell) follows the PUSCH / PHICH scheduling timing according to the TDD configuration of the scheduling cell, and the scheduled cell. The PUSCH / PHICH scheduling timing of the (scheduled cell) may include a controller 2620 for controlling to follow a preset PUSCH / PHICH scheduling timing and a transmitter 2630 for transmitting the PUSCH to the base station according to the PUSCH / PHICH scheduling timing. have.

Table 5 shows candidates for reference PUSCH / PHICH scheduling timing in two different TDD configurations. However, the present invention can also be applied to many different TDD settings. That is, in a three-band interband CA environment, the TDD configuration is different for each band, and there is one cell in each band, so that even if the TDD configuration is different for each cell, a common downlink for each TDD configuration is used. By calculating a subframe, candidates of reference PUSCH / PHICH scheduling timing applicable to the downlink subframe may be selected.

For example, as shown in Table 6, candidates of a common downlink subframe and corresponding reference PUSCH / PHICH scheduling timing in three different TDD configurations are as follows.

TABLE 6

The present invention modifies and applies existing timing rules to support CCS in an interband CA environment. As a result, it is possible to overcome the limitation on TDD configuration of serving cells in an interband CA environment, and this application is a common solution that can be commonly applied in all TDD configuration / UE transmission modes.

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

CROSS-REFERENCE TO RELATED APPLICATION

This patent application is filed with the Korean Patent Application No. 10-2011-0143870 filed on December 27, 2011, and the Korean Patent Application No. 10-2012-0008566 filed on January 27, 2012, and February 2012. Patent application No. 10-2012-0016899, filed in Korea on 20th, claims priority pursuant to Article 119 (a) (35 USC § 119 (a)), all of which are incorporated by reference. Incorporated into the application. In addition, if this patent application claims priority for the same reason for countries other than the United States, all its contents are incorporated into this patent application by reference.

Claims

In the method for applying PUSCH / PHICH scheduling timing of a base station controlling two or more bands having different time division duplex (TDD) settings,

Transmitting uplink allocation or PHICH to a user terminal supporting cross-carrier scheduling using two or more serving cells;

Receiving a PUSCH from the user terminal according to at least one PUSCH / PHICH scheduling timing of the two or more serving cells,

The PUSCH / PHICH scheduling timing of a scheduling cell in the two or more serving cells follows the PUSCH / PHICH scheduling timing according to the TDD configuration of the scheduling cell, and the PUSCH / PHICH scheduling timing of the scheduled cell is preset. A method of applying PUSCH / PHICH scheduling timing in an interband TDD transmission method characterized in that it follows the PUSCH / PHICH scheduling timing.
The method of claim 1,

When the scheduling cell has an uplink super set compared to the scheduled cell or when the PUSCH HARQ RTT (Round Trip Time) of the TDD configuration of the scheduling cell is 10ms,

The preset PUSCH / PHICH scheduling timing is a PUSCH / PHICH scheduling timing of the scheduling cell.
The method of claim 1,

The TDD configuration pair of the scheduling cell and the scheduled cell is (1,2), (1,4), (1,5), (2,5), (3,4), (3,5) or (4 , 5),

The preset PUSCH / PHICH scheduling timing is a PUSCH / PHICH scheduling timing of the scheduling cell.
The method of claim 1,

When the scheduling cell corresponds to an uplink subset (UL subset) compared to the scheduled cell or when the PUSCH HARQ Round Trip Time (RTT) of the TDD configuration of the scheduling cell is 10 ms,

The predetermined PUSCH / PHICH scheduling timing is a PUSCH / PHICH scheduling timing in the interband TDD transmission method, characterized in that the PUSCH / PHICH scheduling timing according to the TDD configuration of the scheduled cell.
The method of claim 1,

TDD configuration pairs of the scheduling cell and the scheduled cell are (1,0), (1,6), (2,0), (2,1), (2,6), (3,0), (3 , 6), (4,0), (4,1), (4,3), (4,6), (5,0), (5,1), (5,2), (5,3 ), (5,4), (5,6), or (6,0),

The predetermined PUSCH / PHICH scheduling timing is a PUSCH / PHICH scheduling timing in the interband TDD transmission method, characterized in that the PUSCH / PHICH scheduling timing according to the TDD configuration of the scheduled cell.
In the method of applying PUSCH / PHICH scheduling timing of a user terminal for transmitting and receiving data in two or more bands having different time division duplex (TDD) settings,

Receiving uplink allocation or PHICH from a base station supporting cross-carrier scheduling using two or more serving cells;

Transmitting a PUSCH to the base station according to at least one PUSCH / PHICH scheduling timing of the two or more serving cells,

The PUSCH / PHICH scheduling timing of a scheduling cell in the two or more serving cells follows the PUSCH / PHICH scheduling timing according to the TDD configuration of the scheduling cell, and the PUSCH / PHICH scheduling timing of the scheduled cell is preset. A method of applying PUSCH / PHICH scheduling timing in an interband TDD transmission method characterized in that it follows the PUSCH / PHICH scheduling timing.
The method of claim 6,

When the scheduling cell has an uplink super set compared to the scheduled cell or when the PUSCH HARQ RTT (Round Trip Time) of the TDD configuration of the scheduling cell is 10ms,

The preset PUSCH / PHICH scheduling timing is a PUSCH / PHICH scheduling timing of the scheduling cell.
The method of claim 6,

The TDD configuration pair of the scheduling cell and the scheduled cell is (1,2), (1,4), (1,5), (2,5), (3,4), (3,5) or (4 , 5),

The preset PUSCH / PHICH scheduling timing is a PUSCH / PHICH scheduling timing of the scheduling cell.
The method of claim 6,

When the scheduling cell corresponds to an uplink subset (UL subset) compared to the scheduled cell or when the PUSCH HARQ Round Trip Time (RTT) of the TDD configuration of the scheduling cell is 10 ms,

The predetermined PUSCH / PHICH scheduling timing is a PUSCH / PHICH scheduling timing in the interband TDD transmission method, characterized in that the PUSCH / PHICH scheduling timing according to the TDD configuration of the scheduled cell.
The method of claim 6,

TDD configuration pairs of the scheduling cell and the scheduled cell are (1,0), (1,6), (2,0), (2,1), (2,6), (3,0), (3 , 6), (4,0), (4,1), (4,3), (4,6), (5,0), (5,1), (5,2), (5,3 ), (5,4), (5,6), or (6,0),

The predetermined PUSCH / PHICH scheduling timing is a PUSCH / PHICH scheduling timing in the interband TDD transmission method, characterized in that the PUSCH / PHICH scheduling timing according to the TDD configuration of the scheduled cell.
A base station for controlling two or more bands of different time division duplex (TDD) settings,

A transmitter for transmitting uplink allocation or a Physical Hybrid ARQ Indicator Channel (PHICH) to a user terminal supporting cross-carrier scheduling using two or more serving cells;

A receiver for receiving a PUSCH from the user terminal according to at least one PUSCH / PHICH scheduling timing of the two or more serving cells;

Physical Uplink Shared Channel (PUSCH) / PHICH scheduling timing of a scheduling cell in the two or more serving cells follows PUSCH / PHICH scheduling timing according to the TDD configuration of the scheduling cell and PUSCH / of the scheduled cell. The base station PHICH scheduling timing comprises a control unit for controlling to follow the preset PUSCH / PHICH scheduling timing.
The method of claim 11,

When the scheduling cell has an uplink super set compared to the scheduled cell or when the PUSCH HARQ RTT (Round Trip Time) of the TDD configuration of the scheduling cell is 10ms,

And the preset PUSCH / PHICH scheduling timing is a PUSCH / PHICH scheduling timing of the scheduling cell.
The method of claim 11,

The TDD configuration pair of the scheduling cell and the scheduled cell is (1,2), (1,4), (1,5), (2,5), (3,4), (3,5) or (4 , 5),

And the preset PUSCH / PHICH scheduling timing is a PUSCH / PHICH scheduling timing of the scheduling cell.
The method of claim 11,

When the scheduling cell corresponds to an uplink subset (UL subset) compared to the scheduled cell or when the PUSCH HARQ Round Trip Time (RTT) of the TDD configuration of the scheduling cell is 10 ms,

The preset PUSCH / PHICH scheduling timing is a PUSCH / PHICH scheduling timing according to the TDD configuration of the scheduled cell.
The method of claim 11,

TDD configuration pairs of the scheduling cell and the scheduled cell are (1,0), (1,6), (2,0), (2,1), (2,6), (3,0), (3 , 6), (4,0), (4,1), (4,3), (4,6), (5,0), (5,1), (5,2), (5,3 ), (5,4), (5,6), or (6,0),

The preset PUSCH / PHICH scheduling timing is a base station characterized in that the PUSCH / PHICH scheduling timing according to the TDD configuration of the scheduled cell
A user terminal for transmitting and receiving data in two or more bands having different time division duplex (TDD) settings,

A receiver for receiving an uplink assignment or a Physical Hybrid ARQ Indicator Channel (PHICH) from a base station supporting cross-carrier scheduling using two or more serving cells;

A transmitter for transmitting a PUSCH to the base station according to at least one PUSCH / PHICH scheduling timing of the two or more serving cells;

Physical Uplink Shared Channel (PUSCH) / PHICH scheduling timing of a scheduling cell in the two or more serving cells follows PUSCH / PHICH scheduling timing according to the TDD configuration of the scheduling cell and PUSCH / of the scheduled cell. PHICH scheduling timing comprises a control unit for controlling to follow the preset PUSCH / PHICH scheduling timing.
The method of claim 16,

When the scheduling cell has an uplink super set compared to the scheduled cell or when the PUSCH HARQ RTT (Round Trip Time) of the TDD configuration of the scheduling cell is 10ms,

The preset PUSCH / PHICH scheduling timing is a user equipment, characterized in that the PUSCH / PHICH scheduling timing of the scheduling cell.
The method of claim 16,

The TDD configuration pair of the scheduling cell and the scheduled cell is (1,2), (1,4), (1,5), (2,5), (3,4), (3,5) or (4 , 5),

The preset PUSCH / PHICH scheduling timing is a user equipment, characterized in that the PUSCH / PHICH scheduling timing of the scheduling cell.
The method of claim 16,

When the scheduling cell corresponds to an uplink subset (UL subset) compared to the scheduled cell or when the PUSCH HARQ Round Trip Time (RTT) of the TDD configuration of the scheduling cell is 10 ms,

The preset PUSCH / PHICH scheduling timing is a PUSCH / PHICH scheduling timing according to the TDD configuration of the scheduled cell.
The method of claim 16,

TDD configuration pairs of the scheduling cell and the scheduled cell are (1,0), (1,6), (2,0), (2,1), (2,6), (3,0), (3 , 6), (4,0), (4,1), (4,3), (4,6), (5,0), (5,1), (5,2), (5,3 ), (5,4), (5,6), or (6,0),

The preset PUSCH / PHICH scheduling timing is a PUSCH / PHICH scheduling timing according to the TDD configuration of the scheduled cell.