WO2014157948A1

WO2014157948A1 - Apparatus for transmitting control information and apparatus for receiving control information

Info

Publication number: WO2014157948A1
Application number: PCT/KR2014/002565
Authority: WO
Inventors: 김선우
Original assignee: 인텔렉추얼디스커버리 주식회사
Priority date: 2013-03-27
Filing date: 2014-03-26
Publication date: 2014-10-02

Abstract

The present invention relates to a method and apparatus for scheduling downlink or uplink transmission in a plurality of subframes through one control channel in order to reduce control channel overhead.

Description

Device for transmitting control information and device for receiving control information

The present invention relates to an apparatus for transmitting and receiving control information in a wireless communication system.

As communication systems evolve, consumers, such as businesses and individuals, have used a wide variety of wireless terminals. Currently, mobile communication systems such as Long Term Evolution (LTE) and LTE Advanced (LTE-A) of the 3rd Generation Partenership (3GPP) series can use wired communication to transmit and receive various data such as video and wireless data beyond voice-oriented services. There is a demand for the development of a technology capable of transmitting large amounts of data corresponding to a network.

In such a system, a time-frequency resource is a control region to which a control channel (eg, Physical Downlink Control CHannel) is allocated and a data region to which a data channel (eg, Physical Downlink Shared CHannel (PDSCH)) is allocated. Can be distinguished.

Data may be transmitted through a data region other than the control region in time-frequency resources. In order to transmit a large amount of data, it is necessary to extend the size of the data area. For this purpose, a method capable of efficiently transmitting control information and reducing the size of the control area may be required.

SUMMARY OF THE INVENTION An object of the present invention is to provide an apparatus capable of efficiently transmitting control information to reduce the size of a control region and thus to expand the size of the data region.

One embodiment of the present invention, the control unit for generating downlink control information (Downlink Control Information, DCI) for one or more subframes; And a transmitter for transmitting the downlink control information through a downlink control channel.

Another embodiment of the present invention, the downlink control channel for receiving downlink control information (Downlink Control Information, DCI); And a control unit for extracting control information of a downlink data channel located in at least one subframe or control information of an uplink data channel located in at least one subframe from the downlink control information. do.

Another embodiment of the present invention, the control unit for generating downlink control information (Downlink Control Information, DCI); And a transmitter for transmitting the downlink control information through a downlink control channel, wherein the downlink control information includes a field indicating a subframe in which a data channel to which the downlink control information is applied is located. Provided is a base station.

According to another embodiment of the present invention, a receiver for receiving downlink control information (DCI) including a field indicating a subframe through a downlink control channel; And a controller for controlling a data channel of a subframe indicated by a field indicating the subframe based on the downlink control information.

According to the present invention described above, it is possible to efficiently transmit control information to reduce the size of the control area, and thus to increase the size of the data area.

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

2 is a conceptual diagram of small cell scenarios.

FIG. 3 illustrates one of the small cell scenarios of FIG. 2.

4 and 5 illustrate another one of the small cell scenarios of FIG. 2.

FIG. 6 illustrates another one of the small cell scenarios of FIG. 2.

7 is a diagram for explaining a concept of scheduling through PDCCH.

8 is a diagram illustrating a concept of multi-subframe scheduling through a PDCCH according to an embodiment of the present invention.

FIG. 9 illustrates a concept of multi-subframe scheduling through EPDCCH according to another embodiment of the present invention.

FIG. 10 is a diagram for explaining a concept of cross-carrier / multi-subframe scheduling according to another embodiment of the present invention.

11 is a flowchart illustrating a method for transmitting and receiving control information according to an embodiment of the present invention.

12 and 13 illustrate a concept of cross-subframe scheduling through a PDCCH according to another embodiment of the present invention.

14 and 15 illustrate a concept of cross-subframe scheduling through EPDCCH according to another embodiment of the present invention.

16 and 17 illustrate a concept of cross-carrier / cross-subframe scheduling according to another embodiment of the present invention.

18 is a block diagram showing the configuration of a base station according to an embodiment of the present invention.

19 is a block diagram illustrating a configuration of a terminal according to an embodiment of the present invention.

Hereinafter, some embodiments of the present invention will be described in detail with reference to the accompanying drawings. In adding reference numerals to the components of each drawing, it should be noted that the same reference numerals are assigned to the same components as much as possible even though they are shown in different drawings. In addition, in describing the 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.

Communication systems are widely deployed to provide various communication services such as voice, packet data, and the like.

Referring to FIG. 1, a communication system includes a user equipment (UE) 10 and a base station 20 that performs uplink and downlink communication with the terminal 10.

In the present specification, the terminal 10 or a user equipment (UE) is a comprehensive concept that means a user terminal in wireless communication. In addition to the UE in WCDMA, LTE, and HSPA, as well as a mobile station (MS) and a UT (GSM) in GSM, It should be interpreted as a concept that includes a user terminal, a subscriber station (SS), and a wireless device.

The base station 20 or cell generally refers to a station communicating with the terminal 10, and includes a base station, a node-B, an evolved node-B, and a base transceiver system. ), An access point, a relay node, a remote radio head (RRH), and a radio unit (RU).

In the present specification, the base station 20 or a cell is to be interpreted in a comprehensive sense indicating some areas covered by a base station controller (BSC) in a CDMA, a NodeB of a WCDMA, and the like, and a radio remote head connected to the base station ) A comprehensive concept of any type of device capable of communicating with one terminal, such as a relay node, a sector of a macro cell, a site, or a micro cell such as a femtocell or picocell. Used as

In the present specification, the terminal 10 and the base station 20 are used in a generic sense as a transmitting and receiving entity used to implement the technology or technical idea described in the present specification and are not limited to the terms or words specifically referred to.

Although one terminal 10 and one base station 20 are shown in FIG. 1, the present invention is not limited thereto. It is possible for one base station 20 to communicate with the plurality of terminals 10, and also for one terminal 10 to communicate with the plurality of base stations 20.

There are no limitations to the multiple access scheme applied to a communication system, and the present invention provides the code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), and OFDM. Applicable to various multiple access schemes such as FDMA, OFDM-TDMA, and OFDM-CDMA.

In addition, the present invention is a combination of the TDD (Time Division Duplex) method is transmitted using a different time, uplink transmission and downlink transmission, FDD (Frequency Division Duplex) method is transmitted using a different frequency, combining the TDD and FDD Applicable to hybrid duplexing method.

Specifically, embodiments of the present invention are applicable to asynchronous wireless communication that evolves into Long Term Evolution (LTE) and LTE-advanced through GSM, WCDMA, HSPA, and synchronous wireless communication that evolves into CDMA, CDMA-2000, and UMB. Can be. The present invention should not be construed as being limited or limited to a specific wireless communication field, but should be interpreted as including all technical fields to which the spirit of the present invention can be applied.

Referring to FIG. 1, the terminal 10 and the base station 20 may perform uplink and downlink communications.

The base station 20 performs downlink transmission to the terminal 10. The base station 20 may transmit a physical downlink shared channel (PDSCH), which is a primary physical channel for unicast transmission. In addition, the base station 20 grants scheduling control for transmission on downlink control information such as scheduling required for reception of the PDSCH and uplink data channel (for example, a physical uplink shared channel (PUSCH)). A control channel such as a physical downlink control channel (PDCCH) or an extended physical downlink control channel (enhanced PDCCH, EPDCCH) for transmitting information may be transmitted. In this specification, the transmission and reception of signals through each channel will be described in the form of transmission and reception of the corresponding channel.

2 is a conceptual diagram of small cell scenarios.

The small cell may be within the coverage of the macro cell or may be out of coverage. Meanwhile, the small cell may use a common channel with a macro cell (co-channel deployment) or frequency may be separated.

3 illustrates one of the small cell scenarios of FIG. 2.

Referring to FIG. 3, a common channel of a macro cell and a small cell may be used. In this case, a small cell cluster may be considered. In a small cell cluster, the number of small cells may be denser than that of R10 eICIC and R11 FeICIC / CoMP. In a small cell cluster, the number of small cells per cluster, backhaul assumptions between small cells, and time synchronization between small cells may be specified. The small cell scenario shown in FIG. 3 may be an outdoor type. Meanwhile, non-ideal backhaul between macro cell and small cell may be configured between the macro cell and the small cell. At this time, macro coverage may exist.

Coordination may or may not be performed between macro and small cells.

The ideal backhaul and the non-ideal backhaul may be configured between small cells in a small cell cluster or between a cluster of small cells and at least one macro cell (eNB). Non-ideal backhaul may be considered for other interfaces. Non-ideal backhaul means backhaul, not the fiber used to implement RRH (CPRI).

4 and 5 illustrate another one of the small cell scenarios of FIG. 2.

4 and 5, the frequency of the macro cell and the small cell can be used to be separated. In this case, a small cell cluster may be considered. In a small cell cluster, the number of small cells may be denser than that of R10 eICIC and R11 FeICIC / CoMP. In a small cell cluster, the number of small cells per cluster, backhaul assumptions between small cells, and time synchronization between small cells may be specified. The small cell scenario shown in FIG. 4 may be Outdoor. The small cell scenario shown in FIG. 5 may be indoor.

Meanwhile, non-ideal backhaul between macro cell and small cell may be configured between the macro cell and the small cell. At this time, macro coverage may exist. Coordination may or may not be performed between macro and small cells.

As described above, even in the small cell scenario shown in FIGS. 4 and 5, the ideal backhaul and the non-ideal backhaul may be configured between small cells in a small cell cluster or between a cluster of small cells and at least one macro cell (eNB). Can be. Non-ideal backhaul may be considered for other interfaces.

FIG. 6 illustrates another one of the small cell scenarios of FIG. 2.

Referring to FIG. 6, there is no macro coverage in this small cell scenario. In this case, a small cell cluster may be considered. In a small cell cluster, the number of small cells may be denser than that of R10 eICIC and R11 FeICIC / CoMP. In a small cell cluster, the number of small cells per cluster, backhaul assumptions between small cells, and time synchronization between small cells may be specified. The small cell scenario shown in FIG. 6 may be indoor. Dense and non-dense small cells (both sparse and dense small cells) may be considered.

Meanwhile, scheduling for a downlink data channel (eg, PDSCH) or an uplink data channel (eg, PUSCH) may be performed through a PDCCH or an EPDCCH.

7 is a diagram for explaining a concept of scheduling through PDCCH.

Referring to FIG. 7, the PDCCH 201 may be used to transmit downlink control information such as scheduling required for reception of the PDSCH 202 which is a downlink data channel. The PDCCH 201 may be used to transmit downlink control information for the PDSCH 202 located in the same subframe.

In addition, the PDCCH 203 may be used to transmit scheduling grant information required for transmission of the PUSCH 204, which is an uplink data channel. In the case of FDD, scheduling grant information necessary for transmission of the PUSCH 204 located in the n + 4 subframe is transmitted through the PDCCH 203 located in the n subframe. In the case of TDD, scheduling acknowledgment information necessary for transmission of the PUSCH 204 located in the n + k subframe is transmitted through the PDCCH 203 located in the n subframe, and the value of k corresponds to the TDD configuration and subframe number n).

Although FIG. 7 illustrates a PDCCH located in a control region, an EPDCCH located in a data region may also transmit downlink control information or uplink scheduling grant information in a similar manner.

Meanwhile, in order to reduce the overhead caused by the control channel, it may be considered that control information for a plurality of subframes is transmitted through one control channel (PDCCH or EPDCCH). Although this approach is called multi-subframe scheduling in the present specification, the present invention is not limited to this name.

Referring to FIG. 8, the PDCCH 301 may be used to convey control information for two or

more PDSCHs

302, 303, and 304 located in two or more subframes. The two or more PDSCHs may include not only the PDSCH 302 located in the same subframe as the PDCCH 301 but also the

PDSCHs

303 and 304 located in a subframe different from the PDCCH 301. In this case, control information for two or

more PDSCHs

302, 303, and 304 may be the same.

In addition, the PDCCH 305 may be used to convey control information for two or

more PUSCHs

306, 307, and 308 located in two or more subframes. Two or more PUSCHs are located in an uplink subframe (ie, n + 4 subframe for FDD and n + k subframe for TDD) related to the downlink subframe in which the PDCCH 305 is located. In addition, it may include

PUSCHs

307 and 308 located in an uplink subframe not related to the downlink subframe in which the PDCCH 305 is located. In this case, control information for two or

more PUSCHs

306, 307, and 308 may be the same.

Referring to FIG. 9, the EPDCCH 401 may be used to convey control information for two or

more PDSCHs

402, 403, and 404 located in two or more subframes. The two or more PDSCHs may include not only the PDSCH 402 located in the same subframe as the EPDCCH 401 but also the

PDSCHs

403 and 404 located in a subframe different from the EPDCCH 401. In this case, control information for two or

more PDSCHs

402, 403, and 404 may be the same.

In addition, the EPDCCH 405 may be used to convey control information for two or

more PUSCHs

406, 407, and 408 located in two or more subframes. Two or more PUSCHs are located in an uplink subframe (ie, n + 4 subframe for FDD and n + k subframe for TDD) related to the downlink subframe in which EPDCCH 405 is located. In addition, it may include

PUSCHs

407 and 408 located in an uplink subframe not related to the downlink subframe in which the EPDCCH 405 is located. In this case, control information for two or

more PUSCHs

406, 407, and 408 may be the same.

Meanwhile, the terminal 10 and the base station 20 may communicate using a plurality of component carriers (CCs). That is, the terminal 10 and the base station 20 may communicate by using a primary cell (PCell) and one or more secondary cells (SCell). In this case, control information of another component carrier may be transmitted through PDCCH or EPDCCH of one component carrier, which may be referred to as cross-carrier scheduling.

In addition, in the small cell scenarios of FIGS. 4 and 5, the terminal may be used to separate the frequency from the macro cell and the small cell. That is, the component carrier with which the terminal and the macro cell communicate with each other and the component carrier with which the terminal and the small cell communicate may be different. For example, the terminal and the macro cell may communicate through the PCell, and the terminal and the small cell may communicate through the SCell. In this case, downlink control information may be received only from the macro cell through the PCell, and the small cell may be used only for data transmission through the SCell. In this case, when the small cell transmits only data through the SCell, the control region may not be set in the SCell.

Referring to FIG. 10, the PDCCH 501 of the PCell may be used to convey control information for two or

more PDSCHs

502, 503, and 504 located in two or more subframes of the SCell. The two or more PDSCHs may include not only the PDSCH 502 located in the same subframe as the PDCCH 501 but also the

PDSCHs

503 and 504 located in a subframe different from the PDCCH 501. In this case, control information for two or

more PDSCHs

502, 503, and 504 may be the same.

In addition, the PDCCH 505 of the PCell may be used to convey control information for two or

more PUSCHs

506, 507, 508 located in two or more subframes of the SCell. Two or more PUSCHs are located in an uplink subframe (ie, n + 4 subframe for FDD and n + k subframe for TDD) related to the downlink subframe in which the PDCCH 505 is located. In addition, it may include

PUSCHs

507 and 508 located in an uplink subframe not related to the downlink subframe in which the PDCCH 505 is located. In this case, control information for two or

more PUSCHs

506, 507, and 508 may be the same.

In the example of FIG. 10, the macro cell transmits control information to the terminal through the PDCCHs 501 and 505 of the PCell, and the small cell transmits data to the terminal through the

PDSCHs

502, 503 and 504 of the SCell and PUSCH ( Data may be received from the terminal through 506, 507, 508.

In the example of FIG. 10, the SCell may be a structure in which a control area for a control channel is not allocated and only a data area exists.

In the example of FIG. 10, the control information conveyed through the PCell is illustrated as for the data channel (PDSCH or PUSCH) of the SCell, but the present invention is not limited thereto. For example, control information delivered through one SCell may be for a data channel of another SCell.

Although control information is illustrated as being transmitted through the PDCCH in FIG. 10, this is merely an example, and control information may be transmitted through the EPDCCH.

In an embodiment of the present invention, downlink control information (DCI) transmitted through a PDCCH or an EPDCCH may include a field indicating one or more subframes.

For example, the field indicating one or more subframes may be in a bitmap format for indicating a subframe to which downlink control information is applied among a plurality of subframes. Alternatively, the field indicating one or more subframes may be a value indicating the number of subframes to which downlink control information is applied. Alternatively, a plurality of patterns for subframes to which downlink control information is applied may be determined according to a preset rule, and a field indicating one or more subframes may be a value indicating one of a plurality of patterns. In this case, the macro cell transmits downlink control information including a field indicating one or more subframes to the terminal, and the small cell transmits data through one or more subframes determined by a field indicating one or more subframes. It can be transmitted to the terminal.

Alternatively, a plurality of patterns for subframes to which downlink control information is applied are determined through higher layer signaling such as RRC (Radio Resource Control), and a field indicating one or more subframes indicates one of a plurality of patterns. Can be a value. In this case, the macro cell transmits a plurality of patterns to the terminal through RRC signaling, and transmits downlink control information including a value indicating one of the plurality of patterns to the terminal, and the small cell is determined to the indicated pattern Data may be transmitted to the terminal through one or more subframes.

When cross-carrier / multi-subframe scheduling is considered, the downlink control information may include a field indicating a component carrier (eg, a channel indication field (CIF)) and a field indicating one or more subframes. have.

Alternatively, some of the values of the field indicating the component carrier are used to indicate the component carrier and one subframe (that is, when no multi-subframe is applied), and the other part is used to indicate the component carrier and the plurality of subframes. Can be used to indicate.

For example, if the CIF may indicate up to eight cases as three bits and five cases may be used to indicate the component carrier, the remaining three may be used for multi-subframe scheduling. Table 1 below shows an example in which three bits of CIF are used for component carrier and multi-subframe scheduling.

Table 1

CIF	CC or multi-subframe scheduling
000	PCell, 1 subframe
001	SCell1, 1 subframe
010	SCell2, 1 subframe
011	SCell3, 1 subframe
100	SCell4, 1 subframe
101	PCell, 2 subframes
110	SCell1, 2 subframes
111	SCell2, 2 subframe

Referring to Table 1, values 000-100 of the CIF indicate one CC and one subframe, and values 101-111 of the CIF indicate one CC and a plurality of subframes.

For another example, CIF may indicate up to 16 cases as 4 bits, 5 cases may be used to indicate component carriers, and the remaining 11 may be used for multi-subframe scheduling.

TABLE 2

CIF	CC or multi-subframe scheduling
0000	PCell, 1 subframe
0001	SCell1, 1 subframe
0010	SCell2, 1 subframe
0011	SCell3, 1 subframe
0100	SCell4, 1 subframe
0101	PCell, 2 subframes
0110	PCell, 3 subframes
0111	SCell1, 2 subframes
1000	SCell1, 3 subframes
1001	SCell2, 2 subframes
1010	SCell2, 3 subframes
1011	SCell3, 2 subframes
1100	SCell3, 3 subframes
1101	SCell4, 2 subframes
1110	SCell4, 3 subframes
1111

Referring to Table 2, the value 0000-0100 of the CIF indicates one CC and one subframe, and the value 0101-1111 of the CIF indicates one CC and a plurality of subframes.

Tables 1 and 2 are provided for purposes of illustration, and alternatively the CIF may indicate component carrier and / or multi-subframe.

In another embodiment, the number of subframes to which one downlink control information is applied may be determined semi-statically through higher layer signaling such as RRC. In this case, the downlink control information may be transmitted in a cycle of the determined number of subframes. For example, when one downlink control information is applied to three subframes, the downlink control information is transmitted in three subframe periods, and the UE decodes PDCCH or EPDCCH in three subframe periods to control downlink. Information can be extracted. To this end, the macro cell transmits information on the period and offset of the subframe in which the downlink control information is transmitted to the terminal to the terminal through the RRC, and downlink through the PDCCH or EPDCCH located in the subframe determined by the period and offset The link control information is transmitted to the terminal, and the small cell may transmit data to the terminal on a periodic basis.

Referring to FIG. 11, the base station generates a DCI for one or more subframes (S1110).

In one embodiment, the DCI may include a field indicating one or more subframes.

Referring back to FIG. 11, the base station transmits the generated DCI to the terminal (S1120), the terminal receiving the DCI extracts control information of PDSCH or PUSCH located in one or more subframes (S1130), and the terminal extracts The downlink data is received through the PDSCH using the control information or the uplink data is transmitted through the PUSCH (S1140).

12 and 13 illustrate a concept of cross-subframe scheduling through PDCCH according to another embodiment of the present invention. 12 illustrates downlink cross-subframe scheduling, and FIG. 13 illustrates uplink cross-subframe scheduling.

Referring to FIG. 12, the PDCCH 601 located in the subframe n is used to transmit control information for the PDSCH 603 located in the subframe n, which is the same subframe, and the PDCCH 602 is another subframe. It is used to convey control information for the PDSCH 604 located in subframe m.

Referring to FIG. 13, the PDCCH 605 located in the subframe n is allocated to an uplink subframe associated with the downlink subframe n (that is, n + 4 subframe for FDD and n + k subframe for TDD). It is used to convey control information for the located PUSCH 607. On the other hand, the PDCCH 606 is used to convey control information for the PUSCH 608 located in an uplink subframe not related to the downlink subframe n.

14 and 15 illustrate a concept of cross-subframe scheduling through EPDCCH according to another embodiment of the present invention. FIG. 14 illustrates downlink cross-subframe scheduling, and FIG. 15 illustrates uplink cross-subframe scheduling.

Referring to FIG. 14, the EPDCCH 701 located in the subframe n is used to transmit control information for the PDSCH 703 located in the subframe n, which is the same subframe, and the EPDCCH 702 is another subframe. It is used to convey control information for the PDSCH 704 located in subframe m.

Referring to FIG. 15, the EPDCCH 705 located in the subframe n is assigned to an uplink subframe associated with the downlink subframe n (that is, n + 4 subframe for FDD and n + k subframe for TDD). It is used to convey control information for the location PUSCH 707. On the other hand, EPDCCH 706 is used to convey control information for PUSCH 708 located in an uplink subframe that is not associated with downlink subframe n.

In addition, in the small cell scenario of FIG. 4, the UE may use the macro cell and the small cell to separate the frequency. That is, the component carrier with which the terminal and the macro cell communicate with each other and the component carrier with which the terminal and the small cell communicate may be different. For example, the terminal and the macro cell may communicate through the PCell, and the terminal and the small cell may communicate through the SCell. In this case, the downlink control information may be received only from the macro cell through the PCell, and the small cell may be used only for data transmission through the SCell. In this case, when the small cell transmits only data through the SCell, the control region may not be set in the SCell.

16 and 17 illustrate a concept of cross-carrier / cross-subframe scheduling according to another embodiment of the present invention. FIG. 16 illustrates downlink cross-carrier / cross-subframe scheduling, and FIG. 17 illustrates uplink cross-carrier / cross-subframe scheduling.

Referring to FIG. 16, the

PDCCHs

801 and 802 of the PCell may be used to carry control information for the

PDSCHs

803 and 804 of the SCell. The PDCCH 801 located in subframe n in the PCell is used to transmit control information for the PDSCH 803 located in subframe n, which is the same subframe in the SCell, and the PDCCH ( 803 is used to convey control information for the PDSCH 804 located in subframe m, which is another subframe in the SCell.

Referring to FIG. 17, the

PDCCHs

805 and 806 of the PCell may be used to convey control information for the

PUSCHs

807 and 808 of the SCell. The PDCCH 805 located in subframe n in the PCell is located in an uplink subframe associated with the downlink subframe n in the SCell (that is, n + 4 subframe for FDD and n + k subframe for TDD). It is used to convey control information for the PUSCH 807. On the other hand, the PDCCH 806 located in subframe n in the PCell is used to convey control information for the PUSCH 808 located in an uplink subframe not related to the downlink subframe n in the SCell.

16 and 17, the macro cell transmits control information to the terminal through the

PDCCHs

801, 802, 805, and 806 of the PCell, and the small cell transmits data to the terminal through the

PDSCHs

803 and 804 of the SCell. It can transmit and receive data from the terminal through the PUSCH (807, 808).

In the example of FIG. 16, the SCell may be a structure in which a control area for a control channel is not allocated and only a data area exists.

In the examples of FIGS. 16 and 17, control information conveyed through the PCell is illustrated as for the data channel (PDSCH or PUSCH) of the SCell, but the present invention is not limited thereto. For example, control information delivered through one SCell may be for a data channel of another SCell.

16 and 17 illustrate that control information is transmitted through the PDCCH, this is only an example, and control information may be transmitted through the EPDCCH.

In another embodiment of the present invention, downlink control information (DCI) transmitted through PDCCH or EPDCCH may include a field indicating a subframe.

For example, in the case of control information related to a PDSCH, a field indicating a subframe may be a value indicating a difference between a subframe in which a PDCCH is located and a subframe in which a PDSCH is indicated by the PDCCH. Alternatively, in the case of TDD, the value of the field indicating the subframe may be a value indicating the number of downlink subframes from the subframe in which the PDSCH is located. When the PDCCH and the PDSCH are located in the same subframe, the value of the field indicating the subframe may be "0".

Meanwhile, in the case of control information related to a PUSCH, a field indicating a subframe may be an uplink subframe associated with a downlink subframe in which the PDCCH is located (that is, n + 4 subframe for FDD and n + k sub for TDD). Frame) and a subframe in which the PUSCH indicated by the PDCCH is located. Alternatively, in the case of TDD, the value of the field indicating the subframe may be a value indicating the number of uplink subframes from the uplink subframe associated with the downlink subframe in which the PUSCH is located. When an uplink subframe associated with a downlink subframe where a PDCCH is located and a subframe where a PUSCH is located are the same, a value of a field indicating a subframe may be "0".

For another example, a plurality of patterns for a subframe to which downlink control information is applied are determined according to a preset rule, and a field indicating a subframe may be a value indicating one of the plurality of patterns.

In this embodiment, the macro cell transmits downlink control information including a field indicating one or more subframes to the terminal, and the small cell through one or more subframes determined by a field indicating one or more subframes. Data can be transmitted to the terminal.

Alternatively, in another embodiment, a plurality of patterns for a subframe to which downlink control information is applied are determined through higher layer signaling such as RRC (Radio Resource Control), and a field indicating a subframe may be one of a plurality of patterns. It may be an indicating value. In this case, the macro cell transmits a plurality of patterns to the terminal through RRC signaling, and transmits downlink control information including a value indicating one of the plurality of patterns to the terminal, and the small cell is determined to the indicated pattern Data may be transmitted to the terminal through one or more subframes.

When cross-carrier / multi-subframe scheduling is considered, the downlink control information may include a field indicating a component carrier (eg, a channel indication field (CIF)) and a field indicating a subframe.

Alternatively, some of the values of the field indicating the component carrier may be used for multi-subframe scheduling.

For example, if the CIF may indicate up to eight cases as three bits and five cases may be used to indicate the component carrier, the remaining three may be used for cross-subframe scheduling. Table 3 below shows an example in which 3 bits of CIF are used for component carrier and cross-subframe scheduling.

TABLE 3

CIF	CC or cross-subframe scheduling
000	PCell, subframe 0
001	SCell1, subframe 0
010	SCell2, subframe 0
011	SCell3, subframe 0
100	SCell4, subframe 0
101	PCell, subframe 1
110	SCell1, subframe 1
111	SCell2, subframe 1

Referring to Table 3, a value 000-100 of a CIF indicates a subframe (subframe 0) associated with control information including one CC and a CIF, and values 101-111 of the CIF include one CC and a CIF. It indicates a subframe 1 that is not related to the control information.

For another example, the CIF may indicate up to 16 cases as 4 bits, 5 cases may be used to indicate component carriers, and the remaining 11 may be used for cross-subframe scheduling.

Table 4

CIF	CC or cross-subframe scheduling
0000	PCell, subframe 0
0001	SCell1, subframe 0
0010	SCell2, subframe 0
0011	SCell3, subframe 0
0100	SCell4, subframe 0
0101	PCell, subframe 1
0110	PCell, subframe 2
0111	SCell1, subframe 1
1000	SCell1, subframe 2
1001	SCell2, subframe 1
1010	SCell2, subframe 2
1011	SCell3, subframe 1
1100	SCell3, subframe 2
1101	SCell4, subframe 1
1110	SCell4, subframe 2
1111

Referring to Table 4, the value 0000-0100 of the CIF indicates a subframe (subframe 0) associated with control information including one CC and the CIF, and the values 0101-1111 of the CIF include one CC and the CIF. Indicates subframes (subframe 1 and subframe 2) not related to the control information.

In Tables 3 and 4, subframe 0 indicates a subframe related to control information including CIF. In the case of control information for the PDSCH, subframe 0 may be the same subframe as the subframe in which the control information including the CIF is transmitted. In case of control information for PUSCH, subframe 0 is an uplink subframe associated with a downlink subframe in which control information including CIF is truncated (that is, n + 4 subframe for FDD and n + k subframe for TDD). May be).

Tables 3 and 4 are provided for purposes of illustration, and in other ways the CIF may indicate component carrier and / or cross-subframe.

Referring to FIG. 18, a base station 1800 according to another embodiment includes a controller 1810, a transmitter 1820, and a receiver 1830.

The controller 1810 controls the overall operation of the base station according to the multi-subframe scheduling required to perform the above-described present invention.

The transmitter 1820 and the receiver 1830 are used to transmit and receive signals, messages, and data necessary for carrying out the present invention.

Referring to FIG. 19, a user terminal 1900 according to another embodiment includes a receiver 1910, a controller 1920, and a transmitter 1930.

The receiver 1910 receives downlink control information, data, and a message from a base station through a corresponding channel.

In addition, the controller 1920 controls the overall operation of the terminal according to the multi-subframe scheduling required to perform the above-described present invention.

The transmitter 1930 transmits uplink control information, data, and a message to a base station through a corresponding channel.

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.

Claims

A controller configured to generate downlink control information (DCI) for at least one subframe; And

And a transmitter for transmitting the downlink control information through a downlink control channel.
The method of claim 1,

The downlink control information base station, characterized in that it comprises a field indicating the one or more subframes.
The method of claim 2,

And the field indicating the one or more subframes includes a bitmap indicating a subframe to which the downlink control information is applied among a plurality of subframes.
The method of claim 2,

And the field indicating the one or more subframes includes a value indicating the number of subframes to which the downlink control information is applied.
The method of claim 2,

And the field indicating one or more subframes includes a value indicating one of a plurality of patterns indicating one or more subframes, which are previously set or indicated from a base station to a terminal.
The method of claim 2,

And the field indicating one or more subframes is a field indicating a component carrier and one or more subframes.
The method of claim 1,

And the number of subframes indicated by the downlink control information is indicated from the base station to the terminal by higher layer signaling.
The method of claim 7, wherein

The higher layer signaling includes information about a period and an offset of a subframe to which the downlink control information is allocated.
A receiver configured to receive downlink control information (DCI) through a downlink control channel; And

And a control unit for extracting control information of a downlink data channel located in at least one subframe or control information of an uplink data channel located in at least one subframe from the downlink control information.
The method of claim 9,

The downlink control information terminal comprising a field indicating the one or more subframes.
The method of claim 10,

The field indicating the one or more subframes includes a bitmap indicating a subframe to which the downlink control information is applied among a plurality of subframes.
The method of claim 10,

The field indicating the one or more subframes includes a value indicating the number of subframes to which the downlink control information is applied.
The method of claim 10,

And the field indicating one or more subframes includes a value indicating one of a plurality of patterns indicating one or more subframes, which are previously set or indicated from a base station to a terminal.
The method of claim 10,

The field indicating the one or more subframes is a field indicating a component carrier and one or more subframes.
The method of claim 9,

And the number of subframes indicated by the downlink control information is indicated from the base station to the terminal by higher layer signaling.
The method of claim 15,

The higher layer signaling includes information about a period and an offset of a subframe to which the downlink control information is allocated.
A control unit for generating downlink control information (DCI); And

And a transmitter for transmitting the downlink control information through a downlink control channel.

And the downlink control information includes a field indicating a subframe in which a data channel to which the downlink control information is applied is located.
The method of claim 17,

The data channel is a downlink data channel,

And a field indicating the subframe includes a value indicating a difference between a subframe in which the downlink data channel is located and a subframe in which the downlink control channel is located.
The method of claim 17,

The data channel is a downlink data channel,

The field indicating the subframe includes a value indicating a number of downlink subframes from the subframe in which the downlink control channel is located. .
The method of claim 17,

The data channel is an uplink data channel,

The field indicating the subframe includes a value indicating a difference between a subframe in which the uplink data channel is located and an uplink subframe related to the subframe in which the downlink control channel is located. .
The method of claim 17,

The data channel is an uplink data channel,

The field indicating the subframe includes a value indicating the number of uplink subframes from the uplink subframe associated with the subframe in which the downlink control channel is located. A base station characterized in that.
The method of claim 17,

And the field indicating the subframe includes a value indicating one of a plurality of patterns indicating a subframe, which are previously set or indicated from the base station to the terminal.
The method of claim 17,

The field indicating the subframe is a field indicating one component carrier and one subframe.
A receiver configured to receive downlink control information (DCI) including a field indicating a subframe through a downlink control channel; And

And a control unit for controlling the data channel of the subframe indicated by the field indicating the subframe based on the downlink control information.
The method of claim 24,

The data channel is a downlink data channel,

The field indicating the subframe includes a value indicating a difference between a subframe in which the downlink data channel is located and a subframe in which the downlink control channel is located.
The method of claim 24,

The data channel is a downlink data channel,

The field indicating the subframe includes a value indicating a number of downlink subframes from the subframe in which the downlink control channel is located. .
The method of claim 24,

The data channel is an uplink data channel,

The field indicating the subframe includes a value indicating a difference between a subframe in which the uplink data channel is located and an uplink subframe related to the subframe in which the downlink control channel is located. .
The method of claim 24,

The data channel is an uplink data channel,

The field indicating the subframe includes a value indicating the number of uplink subframes from the uplink subframe associated with the subframe in which the downlink control channel is located. Terminal, characterized in that.
The method of claim 24,

And the field indicating the subframe includes a value indicating one of a plurality of patterns indicating a subframe, which are previously set or indicated from the base station to the terminal.
The method of claim 24,

The field indicating the subframe is a field indicating one component carrier and one subframe.