KR20180036888A - Apparatus and method of DL data scheduling for MTC UEs - Google Patents

Abstract

The present invention suggest a method for transmitting and receiving a downlink data channel (PDSCH) for a machine type communication (MTC) terminal in a 3GPP LTE/LTE-A system. Especially, the present invention suggests a method for scheduling a downlink data channel for a further enhanced MTC terminal supporting an up/down link data channel (i.e. PDSCH and PUSCH) band width improved compared to an MTC terminal (BL/CE UE) defined in LTE rel-13. The method for scheduling a downlink data channel for an MTC terminal comprises the steps of: setting whether same-subframe scheduling is applied to PDSCH scheduling for the MTC terminal; indicating to the MTC terminal that the same-subframe scheduling is applied; and performing a PDSCH receiving operation according to information on the indication.

Description

[0001] The present invention relates to a method and apparatus for scheduling downlink data for an MTC terminal,

The present embodiments relate to a method of transmitting and receiving a downlink data channel (PDSCH) for a MTC (Machine Type Communication) terminal in a 3GPP LTE / LTE-A system.

One embodiment of the present invention provides a downlink data scheduling method for a MTC terminal, the method comprising: setting whether or not to apply the same-subframe scheduling to PDSCH scheduling for the MTC terminal; indicating to the MTC terminal whether same-subframe scheduling is applied; and performing a PDSCH reception operation according to the indication information.

FIG. 1 is a diagram illustrating Exemplary description of MPDCCH and corresponding PDSCH transmission time for rel-13 BL / CE UEs.
FIG. 2 is a diagram illustrating Exemplary description of same-subframe scheduling for HeMTC UEs.
3 is a diagram illustrating a configuration of a base station according to another embodiment of the present invention.
4 is a diagram illustrating a configuration of a user terminal according to another embodiment of the present invention.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. It should be noted that, in adding reference numerals to the constituent elements of the drawings, the same constituent elements are denoted by the same reference symbols as possible even if they are shown in different drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

Herein, the MTC terminal may mean a terminal supporting low cost (or low complexity) or a terminal supporting coverage enhancement. In this specification, the MTC terminal may mean a terminal supporting low cost (or low complexity) and coverage enhancement. Alternatively, the MTC terminal may refer to a terminal defined in a specific category for supporting low cost (or low complexity) and / or coverage enhancement.

In other words, the MTC terminal in this specification may mean a newly defined 3GPP Release-13 low cost (or low complexity) UE category / type for performing LTE-based MTC-related operations. Alternatively, the MTC terminal may support enhanced coverage over the existing LTE coverage or a UE category / type defined in the existing 3GPP Release-12 or lower that supports low power consumption, or a newly defined Release-13 low cost low complexity UE category / type.

The wireless communication system in the present invention is widely deployed to provide various communication services such as voice, packet data and the like. A wireless communication system includes a user equipment (UE) and a base station (BS, or eNB). The user terminal in this specification is a comprehensive concept of a terminal in wireless communication. It is a comprehensive concept which means a mobile station (MS), a user terminal (UT), an SS (User Equipment) (Subscriber Station), a wireless device, and the like.

A base station or a cell generally refers to a station that communicates with a user terminal and includes a Node-B, an evolved Node-B (eNB), a sector, a Site, a BTS A base transceiver system, an access point, a relay node, a remote radio head (RRH), a radio unit (RU), and a small cell.

That is, the base station or the cell in this specification is interpreted as a comprehensive meaning indicating a partial region or function covered by BSC (Base Station Controller) in CDMA, NodeB in WCDMA, eNB in LTE or sector (site) And covers various coverage areas such as megacell, macrocell, microcell, picocell, femtocell and relay node, RRH, RU, and small cell communication range.

Since the various cells listed above exist in the base station controlling each cell, the base station can be interpreted into two meanings. i) the device itself providing a megacell, macrocell, microcell, picocell, femtocell, small cell in relation to the wireless region, or ii) indicating the wireless region itself. i indicate to the base station all devices that are controlled by the same entity or that interact to configure the wireless region as a collaboration. An eNB, an RRH, an antenna, an RU, an LPN, a point, a transmission / reception point, a transmission point, a reception point, and the like are exemplary embodiments of a base station according to a configuration method of a radio area. ii) may indicate to the base station the wireless region itself that is to receive or transmit signals from the perspective of the user terminal or from a neighboring base station.

Therefore, a base station is collectively referred to as a base station, collectively referred to as a megacell, macrocell, microcell, picocell, femtocell, small cell, RRH, antenna, RU, low power node do.

Herein, the user terminal and the base station are used in a broad sense as the two transmitting and receiving subjects used to implement the technical or technical idea described in this specification, and are not limited by a specific term or word. The user terminal and the base station are used in a broad sense as two (uplink or downlink) transmitting and receiving subjects used to implement the technology or technical idea described in the present invention, and are not limited by a specific term or word. Here, an uplink (UL, or uplink) means a method of transmitting / receiving data to / from a base station by a user terminal, and a downlink (DL or downlink) .

There are no restrictions on multiple access schemes applied to wireless communication systems. Various multiple access schemes 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- Can be used. An embodiment of the present invention can be applied to asynchronous wireless communication that evolves into LTE and LTE-advanced via GSM, WCDMA, and HSPA, and synchronous wireless communication that evolves into CDMA, CDMA-2000, and UMB. The present invention should not be construed as limited to or limited to a specific wireless communication field and should be construed as including all technical fields to which the idea of the present invention can be applied.

A TDD (Time Division Duplex) scheme in which uplink and downlink transmissions are transmitted using different time periods, or an FDD (Frequency Division Duplex) scheme in which they are transmitted using different frequencies can be used.

In systems such as LTE and LTE-advanced, a standard is constructed by configuring uplink and downlink based on a single carrier or carrier pair. The uplink and the downlink are divided into a Physical Downlink Control Channel (PDCCH), a Physical Control Format Indicator CHannel (PCFICH), a Physical Hybrid ARQ Indicator CHannel, a Physical Uplink Control CHannel (PUCCH), an Enhanced Physical Downlink Control Channel (EPDCCH) Transmits control information through the same control channel, and is configured with data channels such as PDSCH (Physical Downlink Shared CHannel) and PUSCH (Physical Uplink Shared CHannel), and transmits data.

On the other hand, control information can also be transmitted using EPDCCH (enhanced PDCCH or extended PDCCH).

In this specification, a cell refers to a component carrier having a coverage of a signal transmitted from a transmission point or a transmission point or transmission / reception point of a signal transmitted from a transmission / reception point, and a transmission / reception point itself .

The wireless communication system to which the embodiments are applied may be a coordinated multi-point transmission / reception system (CoMP system) or a coordinated multi-point transmission / reception system in which two or more transmission / reception points cooperatively transmit signals. antenna transmission system, or a cooperative multi-cell communication system. A CoMP system may include at least two multipoint transmit and receive points and terminals.

The multi-point transmission / reception point includes a base station or a macro cell (hereinafter referred to as 'eNB'), and at least one mobile station having a high transmission power or a low transmission power in a macro cell area, Lt; / RTI >

Hereinafter, a downlink refers to a communication or communication path from a multipoint transmission / reception point to a terminal, and an uplink refers to a communication or communication path from a terminal to a multiple transmission / reception point. In the downlink, a transmitter may be a part of a multipoint transmission / reception point, and a receiver may be a part of a terminal. In the uplink, the transmitter may be a part of the terminal, and the receiver may be a part of multiple transmission / reception points.

Hereinafter, a situation in which a signal is transmitted / received through a channel such as PUCCH, PUSCH, PDCCH, EPDCCH, and PDSCH is expressed as 'PUCCH, PUSCH, PDCCH, EPDCCH and PDSCH are transmitted and received'.

In the following description, an indication that a PDCCH is transmitted or received or a signal is transmitted or received via a PDCCH may be used to mean transmitting or receiving an EPDCCH or transmitting or receiving a signal through an EPDCCH.

That is, the physical downlink control channel described below may mean a PDCCH, an EPDCCH, or a PDCCH and an EPDCCH.

Also, for convenience of description, the PDCCH, which is an embodiment of the present invention, may be applied to the PDCCH, and the PDCCH may be applied to the portion described with the EPDCCH.

Meanwhile, the High Layer Signaling described below includes RRC signaling for transmitting RRC information including RRC parameters.

The eNB performs downlink transmission to the UEs. The eNB includes a physical downlink shared channel (PDSCH) as a main physical channel for unicast transmission, downlink control information such as scheduling required for reception of PDSCH, and uplink data channel A physical downlink control channel (PDCCH) for transmitting scheduling grant information for transmission in a Physical Uplink Shared Channel (PUSCH). Hereinafter, the transmission / reception of a signal through each channel will be described in a form in which the corresponding channel is transmitted / received.

[ Rel -13 BL / CE UEs  for MTC  operation ]

As the LTE network spreads, mobile operators want to minimize the number of Radio Access Terminals (RATs) to reduce network maintenance costs. However, conventional MTC products based on a GSM / GPRS network are increasing, and MTC using a low data rate can be provided at low cost. Therefore, there is a problem in that two RATs must be operated respectively, since LTE network is used for general data transmission and GSM / GPRS network is used for MTC. Therefore, Of the total revenue. Accordingly, in order to lower the terminal unit price compared to the conventional normal LTE terminal, the transmission / reception bandwidth of the terminal is limited to 6 PRBs (Physical Resource Blocks), and the number of transmission / reception antennas is limited to one, CE UE is defined as a coverage enhancement (CE) mode considering MTC application scenario such as smart metering installed in a 'deep indoor' environment, and a standard technology for supporting the corresponding BL / CE UE is defined in the LTE rel-13 system Defined.

[CE mode definition]

In the LTE rel-13 system, two modes are defined as coverage enhancement modes for BL / CE terminals: CEModeA and CEModeB. CEModeA is a terminal operation mode in which repetition of a wireless channel such as MPDCCH, PDSCH, PUSCH, PUCCH is not applied or a small number of repetition is applied for coverage enhancement of a BL / CE terminal, and CEModeB is a terminal operation mode The CE mode is defined as a terminal operation mode for applying a large number of repetitions to wireless channels and is defined to be signaled for each terminal.

[ Narrowband  definition ]

개의 하향 링크 narrowbands 및

개의 상향 링크 narrowbands가 구성되었다. 단, 임의의 시스템 대역폭에서 상기의 narrowband 구성 시, 해당 시스템 대역폭을 구성하는 전체 PRB의 수를 6으로 나눈 나머지에 해당하는 remaining RB(s)에 대해, 해당 remaining RB(s)를 시스템 대역의 양 쪽 band edge에 even하게 두거나(시스템 대역폭이 짝수의 PRBs로 구성된 경우), 혹은 시스템 대역의 센터(시스템 대역이 25 PRBs로 구성된 경우), 혹은양 edge와 시스템 대역의 센터(시스템 대역이 15 PRBs, 75 PRBs인 경우)에 각각 위치시키고, 이를 제외한 PRBs를 이용해 increasing PRB number로 6개 연속적인 PRBs를 묶어서 상기의 narrowband를 구성하도록 할 수 있다.As described above, in the Rel-13 BL / CE terminal, transmission / reception is possible only at 1.4 MHz (i.e., 6 PRBs) through arbitrary subframes regardless of the system bandwidth. As a result, a transmission band of an arbitrary BL / CE terminal is defined in an arbitrary uplink / downlink subframe, and a narrowband composed of 6 consecutive PRBs is defined as a unit for allocating the bandwidth, and according to each system bandwidth

Lt; RTI ID = 0.0 > narrowbands &

Uplink narrowbands were constructed. However, in the narrowband configuration in the arbitrary system bandwidth, for the remaining RB (s) corresponding to the remaining number obtained by dividing the total number of PRBs constituting the corresponding system bandwidth by six, the remaining RB (s) (System bandwidth is equal to 25 PRBs), or both edge and system bandwidth centers (system bandwidth is 15 PRBs). 75 PRBs), and by using the PRBs other than the PRBs, it is possible to configure the narrowband by grouping six consecutive PRBs with increasing PRB numbers.

Specifically, the narrowband configuration method defined in TS 36.211 document is as follows.

[TS 36.211 v13.2.0]

Downlink narrowbands

6.2.7 Narrowbands

A narrowband is defined as six non-overlapping consecutive physical resource blocks in the frequency domain. The total number of downlink bandwidths in the downlink transmission bandwidth configured in the cell is given by

in order of increasing physical resource-block number where narrowband

is composed of physical resource-block indicesThe narrowbands are numbered

in order of increasing physical resource-block number where narrowband

is composed of physical resource-block indices

where

Uplink narrowbands

5.2.4 Narrowbands

A narrowband is defined as six non-overlapping consecutive physical resource blocks in the frequency domain. The total number of uplink narrowbands in the uplink transmission bandwidth configured in the cell is given by

in order of increasing physical resource-block number where narrowband

is composed of physical resource-block indicesThe narrowbands are numbered

in order of increasing physical resource-block number where narrowband

is composed of physical resource-block indices

where

[Resource allocation and DCI  format for BL / CE UE ]

According to the PDSCH and PUSCH resource allocation method for the BL / CE terminal defined in Rel-13, when a certain base station constructs a DCI including PDSCH or PUSCH resource allocation information for an arbitrary BL / CE terminal, The PDSCH or PUSCH transmission for the / CE terminal is defined to include narrowband index information and RB allocation information within the corresponding narrowband for PRB (or VRB) allocation. In addition, the RB allocation information within the corresponding narrowband is defined to be based on the resource allocation type 2 for the PDSCH and the resource allocation type 0 for the PUSCH based on the continuous VRB resource allocation scheme. However, in case of PUSCH, resource allocation can be performed based on resource allocation type 2 only in a BL / CE terminal in which CEModeB is set.

The specific resource allocation method and the DCI format for the defined BL / CE terminal are extracted from the TS 36.213 document and the TS 36.212 document respectively and attached through the "appendix 1" document.

[ PDSCH subframe  assignment for BL / CE UE ]

According to the PDSCH reception method for the Rel-13 BL / CE terminal, any BL / CE terminal receives the DCI transmitted through the MPDCCH and receives the PDSCH resource allocation information for the corresponding terminal. The DCI including the PDSCH resource allocation information includes the MPDCCH repetition transmission count and the PDSCH repetition transmission count, respectively. Accordingly, the corresponding UE transmits BLs / BLs corresponding to the number of repeated transmissions of the PDSCH set through the corresponding DCI from the second BL / CE subframe among the subframe subsequent subframes of the last repeated transmission for the corresponding MPDCCH based on the number of repetition transmissions of the arbitrary MPDCCH / CE < / RTI > subframe. That is, a cross-subframe scheduling scheme in which MPDCCH and the corresponding PDSCH are transmitted through different subframes is applied.

In connection with the defined MPDCCH and PDSCH receive subframe settings for specific BL / CE terminals, the following TS 36.213 document should be extracted and appended via appendix 2 document.

[Further enhanced MTC ]

As discussed above, a discussion on additional enhanced features for the BL / CE terminal defined in 3GPP rel-13 will be made in the 3GPP rel-14 system, and the specific scope should be attached as an excerpt from the following WID document RP-161321 do.

3 Justification

The Provision of IoT via cellular networks is proving to be a significant opportunity for mobile operators. In Release 13, two classes of low-cost IoT devices with enhanced coverage and long battery life are specified: eMTC devices and NB-IoT devices with UE bandwidths of 6 PRBs and 1 PRB, respectively (1 PRB = a 180-kHz physical resource block).

UE positioning and tracking are important in many IoT applications, such as asset tracking. But GNSS-based positioning method is not suitable for many IoT applications. Additionally, the narrow UE bandwidth poses challenges for the positioning accuracy when using the 3GPP positioning functionalities defined for normal UEs. In Rel-13, only limited positioning functionalities are provided for these UEs. Hence, 3GPP-based IoT eco-system is required to improve the positioning requirements of Rel-13 and considering improvements.

In many cases, the same cell is used for the same information simultaneously, for example in the case of rollout of firmware or software upgrades. Low complexity multicast functionality can be achieved either in the form of a regular MBSFN transmission or as a small extension of the recently introduced single-cell point-to-multipoint transmission (SC-PtM) functionality.

In Rel-13 the requirements of complexity reduction, extended battery life, and coverage enhancements are aimed at devices such as sensors, meters, smart readers, and similar. Other types of devices / use cases, such as voice capable wearable devices and health monitoring devices share some of these requirements. However, a subset of these devices are not fully covered by the Rel-13 because they require higher data rates above 1 Mbps. Rel e-13 eMTC solution is used for the existing Rel-13 eMTC solution. The e-commerce solution is based on the e-commerce solution.

4 Objective

4.1 Objective of SI or Core part WI or Testing part WI

The objective is to specify the following improvements for machine-type communications for BL / CE (eMTC) UEs.

Positioning [RAN4, RAN1]

E-CID: RSRP/RSRQ measurement

E-CID: RSRP / RSRQ measurement

E-CID: UE Rx-Tx time difference measurement

E-CID: UE Rx-Tx time difference measurement

OTDOA: core requirements

OTDOA: core requirements

From RAN#73: (considering the outcome of the NB-IoT) accuracy, UE complexity and power consumption for OTDOA can be studied

From RAN # 73: Considering the outcome of the NB-IoT accuracy, UE complexity and power consumption for OTDOA can be studied

Multicast [RAN2 lead, RAN1]

Extend Rel-13 SC-PTM to support multicast downlink transmission (e.g. firmware or software updates, group message delivery)

Extend Rel-13 SC-PTM to support multicast downlink transmission (eg firmware or software updates, group message delivery)

Introduction of necessary enhancements to support narrowband operation, e.g. support of MPDCCH, and coverage enhancement, e.g. repetitions

Introduction to enhancements to support narrowband operation, eg support of MPDCCH, and coverage enhancement, eg repetitions

Mobility enhancements [RAN4 only]

Full standard support for inter-frequency measurements for eMTC [RAN4]

Full standard support for inter-frequency measurements for eMTC [RAN4]

Higher data rates [RAN1, RAN2, RAN4]

Specify HARQ-ACK bundling in CE mode A in HD-FDD

Specify HARQ-ACK bundling in CE mode A in HD-FDD

Larger maximum TBS

Larger maximum TBS

Larger max. PDSCH/PUSCH channel bandwidth in connected mode at least in CE mode A in order to enhance support e.g. voice and audio streaming or other applications and scenarios

Larger max. PDSCH / PUSCH channel bandwidth in connected mode at least in CE mode A in order to enhance support for voice and audio streaming or other applications and scenarios

Up to 10 DL HARQ processes in CE mode A in FD-FDD

Up to 10 DL HARQ processes in CE mode A in FD-FDD

In the present invention, a new rel-14 MTC terminal supporting an extended PDSCH / PUSCH channel bandwidth compared to a rel-13 BL / CE terminal (referred to as a HeMTC terminal for convenience of explanation in the present invention, The present invention is not limited thereto).

As described above, in the case of the HeMTC terminal requiring improved data rates compared to the existing rel-13 BL / CE terminal, the narrow band defined as the size of 6 PRBs based on the maximum transmission / reception bandwidth of the existing rel-13 BL / CE terminal Supports extended PDSCH transmit / receive bandwidth. However, the DCI including the scheduling control information for the PDSCH for the corresponding HeMTC terminal is defined to be transmitted through the MPDCCH, which is a downlink control channel defined for the rel-13 BL / CE terminal.

When PDSCH scheduling is performed through the MPDCCH, as shown in FIG. 1, the MPDCCH and the PDSCH transmission are performed through different subframes, that is, the PDSCH repeated transmission start subframe is the MPDCCH last repeated transmission subframe subsequent downlink subframe Since cross subframe scheduling is applied, latency - critical HeMTC application services such as VoLTE can be limited. In the present invention, a scheduling latency reduction scheme for a HeMTC terminal supporting extended bandwidth is proposed as a method for solving the problem.

Point 1. Definition of same- subframe  SCHEDING indicator

As a PDSCH scheduling scheme for an arbitrary HeMTC terminal, same-subframe scheduling can be applied as shown in FIG.

For this purpose, a higher layer parameter for indicating a scheduling scheme for a PDSCH in a base station / network (in the present invention, it is referred to as PDSCH_scheduling_config) for a HeMTC terminal in which DCI transmission / reception including resource allocation information for a PDSCH is performed through an MPDCCH However, the present invention is not limited to such a name), and it is possible to set whether same-scheduling is applied through higher layer signaling as shown in FIG. Specifically, an arbitrary base station / cell can indicate whether the same-subframe scheduling is applied to the HeMTC terminal in the corresponding cell through cell-specific RRC layer signaling. Or an arbitrary base station / cell can indicate whether same-subframe scheduling is applied to each HeMTC terminal through UE-specific RRC signaling.

According to the PDSCH_scheduling_config configuration information transmitted through the cell-specific / UE-specific RRC signaling, the corresponding HeMTC terminal determines whether to perform the PDSCH reception based on the existing cross-subframe scheduling MPDCCH and PDSCH timing relationship, it can be determined whether to perform the PDSCH reception operation based on the MPDCCH and PDSCH timing relationship of the -subframe scheduling scheme.

The timing relationship between the MPDCCH based on the existing cross-subframe scheduling as shown in FIG. 1 and the PDSCH corresponding thereto is defined as a default operation, the PDSCH_scheduling_config indicates whether to support additional same-subframe scheduling, (I.e., PDSCH allocation based on cross-subframe scheduling or PDSCH allocation based on same-subframe scheduling) through the DCI including the resource allocation information corresponding to the timing relationship between the corresponding MPDCCH and the PDSCH A PDSCH scheduling method based on a 2-step can be defined to indicate to the HeMTC terminal. In this case, the HeMTC defines a PDSCH transmission / reception subframe for the UE according to the PDSCH_scheduling_config setting information, and performs a cross-subframe scheduling based on the timing relationship between MPDCCH / PDSCH defined for the BL / Subframe scheduling and cross-subframe scheduling based on the DCI format of the DCI format (i.e., the DCI format that does not include the 1-bit scheduling subframe indication) bit scheduling subframe indication information based on the DCI format including the bit scheduling subframe indication information.

In addition, when PDSCH allocation based on the same-subframe scheduling is performed as shown in FIG. 2, the number of repetitions of the corresponding PDSCH is always set to the value of the corresponding MPDCCH regardless of the RRC signaling defined for the BL / It can be defined to follow the number of repeated transmissions. For this, when the same-subframe scheduling is set by higher layer signaling, the DCI format for transmitting the PDSCH resource allocation information for the corresponding HeMTC terminal can be defined so as not to include the information area for setting the corresponding PDSCH repetition level. Or if the same subframe scheduling is set to include the corresponding PDSCH repetition level setting information area in the same manner as the DCI format for the existing BL / CE terminal, regardless of the set value of the corresponding PDSCH repetition level, Follow the number of repeated transmissions.

3 is a diagram illustrating a configuration of a base station 1000 according to another embodiment of the present invention.

3, a base station 1000 according to another embodiment includes a control unit 1010, a transmission unit 1020, and a reception unit 1030.

The controller 1010 sets whether to apply the same-subframe scheduling to the downlink data scheduling for the MTC terminal according to the present invention described above, and controls the overall operation of the base station 1000 according to indication to the MTC terminal.

The transmitting unit 1020 and the receiving unit 1030 are used to transmit and receive signals, messages, and data necessary for carrying out the present invention to and from the terminal.

FIG. 4 is a diagram illustrating a configuration of a user terminal 1100 according to another embodiment of the present invention.

4, a user terminal 1100 according to another embodiment includes a receiving unit 1110, a control unit 1120, and a transmitting unit 1130.

The receiving unit 1110 receives downlink control information, data, and messages from the base station through the corresponding channel.

In addition, the controller 1120 determines whether the same-subframe scheduling is applied to the downlink data scheduling for the MTC terminal according to the present invention described above, and controls the overall operation of the user terminal 1100 upon receiving the downlink data.

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

The standard content or standard documents referred to in the above-mentioned embodiments constitute a part of this specification, for the sake of simplicity of description of the specification. Therefore, it is to be understood that the content of the above standard content and some of the standard documents is added to or contained in the scope of the present invention, as falling within the scope of the present invention.

The foregoing description is merely illustrative of the technical idea of the present invention, and various changes and modifications may be made by those skilled in the art without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas within the scope of equivalents should be construed as falling within the scope of the present invention.

Claims (1)

A method for downlink data scheduling for an MTC terminal,
Setting whether to apply the same-subframe scheduling to the PDSCH scheduling for the MTC terminal;
Indicating whether the same-subframe scheduling is applied to the MTC terminal; And
And performing a PDSCH reception operation according to the indication information.

Images