WO2012163170A1 - Method and device for data transmission - Google Patents

Abstract

Disclosed in the present invention is a data transmission method used to transmit data during dynamic allocation of uplink and downlink subframes. The dynamic subframe system consists of at least four types of subframe: the first subframe can only be used for downlink transmission; the second subframe can only be used for uplink transmission; the third subframe can be dynamically configured for uplink or downlink transmission, but cannot be simultaneously used for uplink and downlink transmission; the fourth subframe is a special time slot, comprising a downlink pilot time slot, a guard period, and an uplink pilot time slot. At the receiving end, receiving end the method comprises: a receiving end receives data from the first subframe, the third subframe, or the downlink pilot time slot of fourth subframe; the receiving end, having received data, sends a feedback ACK or NACK only in the second subframe. Also disclosed in the present application are an implementation method for the transmission side and a device for implementing said method.

Description

The present invention claims the priority of a Chinese patent application filed on June 1, 2011 by the Chinese Patent Office, Application No. 201110146060.0, entitled "A Method and Apparatus for Data Transmission", The entire contents are incorporated herein by reference. TECHNICAL FIELD The present invention relates to the field of communications, and in particular, to a method and apparatus for data transmission. Background Art In common TDD (Time Division Duplexing, time division duplex) system, comprising a 3G (3 ^rd -Generation, a third generation communication system) of the TD-SCDMA (Time Division-Synchronous Code Division Multiple Access, Time Division Synchronous Code Division multiple access) system and a 4G (4 ^th -Generation, fourth-generation communication system) TD-LTE (Time division long Term Evolution, LTE division) systems, uplink and downlink time slots are divided into static or semi-static The usual practice is to determine the proportion of uplink and downlink time slots according to the type of cell and the approximate proportion of services in the network planning process and keep unchanged. This is a relatively simple approach in the context of large coverage of macro cells, and is also more effective. With the development of technology, more and more low-power base stations such as Pico cells and Home NodeBs are deployed to provide local small coverage. In such cells, the number of users is small, and The user service requirements vary greatly. Therefore, there is a dynamic change in the proportion of uplink and downlink services in the cell.

 The patent application number 201010567764.0 proposes a dynamic uplink and downlink subframe allocation scheme. The solution is: setting a four-seed frame type in a certain period of time, including a subframe fixed for downlink transmission, a subframe fixed for uplink transmission, a special subframe, and a flexible allocated subframe, the subframe may be Used for uplink or downlink transmission. As shown in FIG. 1 , the time period is a radio frame (only one example, and may be other time periods), where subframe 0 and subframe 5 are fixed downlink subframes, and subframe 2 and subframe 7 are Fixed uplink subframes, subframe 1 and subframe 6 are special subframes (which can also be classified as fixed downlink subframes), and other subframes (ie, subframes 3, 4, 8, and 9) are flexible allocated subframes (Flexible Subframe) ). For flexible allocation of subframes, the base station can be dynamically configured according to real-time service requirements and channel conditions to adapt to dynamic changes in service requirements.

 In the prior art, the division of uplink and downlink time slots is static or semi-static, so HARQ (Hybrid Automatic)

Repeat Request, Hybrid Automatic Retransmission) Timing and uplink and downlink configurations are binding designs. For the scheme of dynamically allocating uplink and downlink subframes, the subframe structure is different from the static or semi-statically allocated subframes. Therefore, the existing HARQ timing design cannot be directly applied to the scheme of dynamically allocating uplink and downlink subframes, and the retransmission scheduling and The timing of data retransmission needs to be improved, but there is no effective solution at present. SUMMARY OF THE INVENTION Embodiments of the present invention provide a data transmission method and apparatus, which are used to implement data transmission when dynamically uplink and downlink subframes are allocated.

 A method for downlink transmission on a data receiving end in a dynamic subframe system, where the dynamic subframe system is composed of at least four types of subframes, wherein the first type of subframe can only be used for downlink transmission, and the second type of subframe can only be used for downlink transmission. For the uplink transmission, the third type of subframe may be dynamically configured for uplink or downlink transmission, the third type of subframe may not be used for both uplink and downlink transmission, and the fourth type of subframe is a special time slot, The fourth type of subframe includes a downlink pilot time slot (DwPTS), a guard interval (GP) and an uplink pilot time slot (UpPTS); the method includes the following steps:

 Receiving, by the receiving end, data in a downlink pilot time slot of the first type of subframe or the third type of subframe or the fourth type of subframe;

 After receiving the data, the receiving end only feeds back ACK or NACK in the second type of subframe.

 A method for downlink transmission on a data transmitting end in a dynamic subframe system, where the dynamic subframe system is composed of at least four types of subframes, wherein the first type of subframes can only be used for downlink transmission, and the second type of subframes can only be used for downlink transmission. For the uplink transmission, the third type of subframe may be dynamically configured for uplink or downlink transmission, the third type of subframe may not be used for both uplink and downlink transmission, and the fourth type of subframe is a special time slot, The fourth type of subframe includes a downlink pilot time slot (DwPTS), a guard interval (GP) and an uplink pilot time slot (UpPTS); the method includes the following steps:

 Transmitting, by the sending end, the data in a downlink pilot time slot of the first type or the third type of subframe or the fourth type of subframe;

 The transmitting end only receives an ACK or a NACK in the second type of subframe.

 A receiving end device for downlink transmission in a dynamic subframe system, where the dynamic subframe system is composed of at least four types of subframes, wherein the first type of subframe can only be used for downlink transmission, and the second type of subframe is only used for downlink transmission. Can be used for uplink transmission, the third type of subframe can be dynamically configured for uplink or downlink transmission, the third type of subframe cannot be used for both uplink and downlink transmission, and the fourth type of subframe is a special time slot. The fourth type of subframe includes a downlink pilot time slot (DwPTS), a guard interval (GP) and an uplink pilot time slot (UpPTS); the receiving device includes:

 An interface module, configured to receive data in a downlink pilot time slot of the first type of subframe or the third type of subframe or the fourth type of subframe; and only in the second type of subframe Feedback ACK or NACK;

 The control module is configured to detect the received data, and according to the detection result, instruct the interface module to feed back an ACK or a NACK only in the second type of subframe.

A transmitting end device for downlink transmission in a dynamic subframe system, where the dynamic subframe system is composed of at least four types of subframes, wherein the first type of subframes can only be used for downlink transmission, and the second type of subframes only Can be used for uplink transmission, the third type of subframe can be dynamically configured for uplink or downlink transmission, the third type of subframe cannot be used for both uplink and downlink transmission, and the fourth type of subframe is a special time slot. The fourth type of subframe includes a downlink pilot time slot (DwPTS), and a guard interval (GP) And an uplink pilot time slot (UpPTS); the sender device includes:

 An interface module, configured to send data in a downlink pilot time slot of the first type or the third type of subframe or the fourth type of subframe; and receive an ACK only in the second type of subframe Or NACK;

 The control module is configured to determine that the received feedback only occurs in the second type of subframe according to the subframe in which the transmitted data is located, and instruct the interface module to receive an ACK or a NACK only in the second type of subframe.

 In the embodiment of the present invention, a new HARQ timing relationship is designed for the dynamic subframe system, and the downlink transmission and feedback are performed by using the timing relationship, and data transmission is realized when the uplink and downlink subframes are dynamically allocated. BRIEF DESCRIPTION OF DRAWINGS FIG. 1 is a schematic diagram of a radio frame structure in the prior art;

 2 is a flowchart of a method for downlink transmission on a data receiving end in a dynamic subframe system according to an embodiment of the present invention; FIG. 3 is a flowchart of a method for downlink transmission at a data transmitting end in a dynamic subframe system according to an embodiment of the present invention; A schematic diagram of a timing relationship in an embodiment of the present invention;

 5 is a flowchart of a detailed method for downlink data transmission in a dynamic subframe system according to an embodiment of the present invention; FIG. 6 is a schematic diagram of a timing relationship of configuration 0 according to an embodiment of the present invention;

 FIG. 7 is a schematic diagram of a timing relationship of configuration 1 according to an embodiment of the present invention; FIG.

 FIG. 8 is a schematic diagram of a timing relationship of configuration 3 in an embodiment of the present invention; FIG.

 FIG. 9 is a schematic diagram of a timing relationship of configuration 6 in an embodiment of the present invention; FIG.

 FIG. 10 is a structural diagram of a receiving end device according to an embodiment of the present invention;

 FIG. 11 is a structural diagram of a device at a transmitting end according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION In the embodiment of the present invention, a new HARQ timing relationship is designed for a dynamic subframe system, and downlink transmission and feedback are performed by using the timing relationship, and data transmission is realized when dynamically uplink and downlink subframes are allocated.

 In this embodiment, the dynamic subframe system is composed of at least four types of subframes, where the first type of subframes can only be used for downlink transmission, and can be called fixed downlink subframes; the second type of subframes can only be used for uplink transmission, which can be called Fixed uplink subframes; the third type of subframes can be dynamically configured for uplink or downlink transmission, which can be called flexible configured subframes, but the third type of subframes cannot be used for both uplink and downlink transmissions; The subframe is a special time slot, and the fourth type of subframe includes a downlink pilot time slot (DwPTS), a guard interval (GP), and an uplink pilot time slot (UpPTS).

Referring to FIG. 2, the method for downlink transmission on the data receiving end in the dynamic subframe system is as follows: Step 201: The receiving end is in the first type subframe or the third type subframe or the fourth class. The data is received in the downlink pilot time slot of the subframe. Step 202: After the receiving end receives the data, only the ACK (correct response) or NACK (error response) is fed back in the second type of subframe.

 Referring to FIG. 3, corresponding to the UE, the method for downlink transmission on the data sending end in the dynamic subframe system in this embodiment is as follows:

 Step 301: The transmitting end sends the data in a downlink pilot time slot of the first type or the third type of subframe or the fourth type of subframe.

 Step 302: The transmitting end only receives an ACK or a NACK in the second type of subframe.

 The transmitted data includes at least downlink data on a downlink shared channel (DSCH, Downlink Shared Channel) or data on a downlink control channel (PDCCH) indicating downlink semi-persistent scheduling (SPS) release. The downlink pilot time slot of the first type of subframe or the third type of subframe or the fourth type of subframe that is available for data transmission corresponds to one feedback subframe, and the feedback subframe is the data. The subframe in which the corresponding ACK or NACK is located. In this embodiment, scheduling signaling for data occurs in a subframe in which data is transmitted, and the receiving end receives and detects data at a corresponding location according to scheduling signaling.

 The data transmission in this embodiment may occur between the UE and the base station, between the UE and the relay node (RN), or between the relay node and the base station. When it occurs between the UE and the base station, the receiving end is the UE, and the transmitting end is the base station. When it occurs between the UE and the relay node, the receiving end is the UE, and the transmitting end is the relay node. When it occurs between the relay node and the base station, the receiving end is a relay node, and the transmitting end is a base station.

 Preferably, when transmitting data in the subframe n, the transmitting end receives the ACK or NACK corresponding to the data only in the subframe n+k. Similarly, when receiving data in subframe n, the receiving end feeds back the ACK or NACK corresponding to the data only in subframe n+k. Where k is determined by the subframe n and the preset timing relationship, and the timing relationship specifies that the ACK or NACK of the feedback only occurs in the second type of subframe.

 In this embodiment, the timing relationship is pre-stored between the transmitting end and the receiving end, and then data transmission and feedback are respectively performed according to the timing relationship. For an example of a timing relationship, see FIG. 4, where D represents a first type of subframe, U represents a second type of subframe, S represents a fourth type of subframe, X is a third type of subframe, and Xd is flexibly configured as a downlink. Subframe, A denotes the subframe in which the feedback is transmitted, and the corresponding subframe of "#" is used for data transmission (including the first data transmission and retransmission of data). The timing relationship shown in Table 1 can be extracted from Figure 4:

 Table 1

Wherein, n represents a PDSCH (Physical Downlink Shared Data Channel) or a subframe number of a downlink control channel (PDCCH, Physical Downlink Control Channel) indicating downlink half-persistent scheduling (SPS) release, and k represents ACK or NACK feedback and PDSCH data transmission. The number of subframes between them, so n+k means ACK or NACK Subframe number. The ACK or the NACK is transmitted through a PUCCH (Physical Uplink Control CHannel) or a PUSCH (Physical Uplink Shared Channel).

 The timing relationship shown in Figure 4 can have another form of representation, as shown in Table 2.

 Table 2

 Where n represents the subframe number of the ACK or NACK feedback, and k represents the number of subframes between the ACK or NACK feedback and the PDSCH data transmission, so n+k represents the PDSCH (Physical Downlink Shared Data Channel) or indicates downlink semi-persistent scheduling (SPS) The subframe number in which the downlink control channel (PDCCH) is released. The ACK or NACK is transmitted through PUCCH (Physical Uplink Control Channel) or PUSCH (Physical Uplink Shared Data Channel).

 Specifically, when the data is received in the subframe n, and n=0 or 5, the receiving end only sends the ACK or NACK feedback corresponding to the data in the subframe n+7.

 When the data is received in subframe n, and n = 1 or 6, the receiving end transmits the ACK or NACK feedback corresponding to the data only in subframe n+6.

 When the data is received in subframe n, and n=3 or 8, the receiving end transmits the ACK or NACK feedback corresponding to the data only in subframe n+4.

 When the data is received in subframe n, and n = 4 or 9, the receiving end transmits the ACK or NACK feedback corresponding to the data only in subframe n+8.

 The specific implementation of the sender is as follows:

 When the data is transmitted in subframe n, and n = 0 or 5, the transmitting end receives the ACK or NACK feedback corresponding to the data only in subframe n+7.

 When the data is transmitted in subframe n, and n = 1 or 6, the transmitting end receives the ACK or NACK feedback corresponding to the data only in subframe n+6.

 When the data is transmitted in subframe n, and n = 3 or 8, the transmitting end receives the ACK or NACK feedback corresponding to the data only in subframe n+4.

 When the data is transmitted in subframe n, and n = 4 or 9, the transmitting end receives the ACK or NACK feedback corresponding to the data only in subframe n+8.

 The implementation process of downlink data transmission is described in detail below through an embodiment.

 Referring to FIG. 5, the detailed method for downlink data transmission in the dynamic subframe system in this embodiment is as follows:

 Take the transmission between the base station and the UE as an example.

Step 501: The base station sends downlink scheduling signaling through the PDCCH on the downlink subframe, and transmits data through the PDSCH. Step 502: The UE receives the downlink scheduling signaling by using the PDCCH on the corresponding subframe, and detects the PDSCH according to the PDCCH. Step 503: The UE receives data through the PDSCH.

 Step 504: The UE detects whether the data is correctly received, and if yes, proceeds to step 505, otherwise proceeds to step 506. Step 505: The UE feeds back an ACK on the second type of subframe indicated by the timing relationship.

 Step 506: The UE feeds back a NACK on the second type of subframe indicated by the timing relationship.

 For a UE that does not support dynamic TDD uplink and downlink configuration, this embodiment may provide a compatible solution. The control information sent by the base station also includes uplink and downlink configuration type information. The base station schedules the downlink data in the same timing in the two timing relationships according to the timing relationship corresponding to the uplink and downlink configuration type and the timing relationship preset by the dynamic subframe system. The timing relationship shown in Figure 4 in this embodiment is compatible with at least some of the timings of Configuration 0, Configuration 1, Configuration 3, and Configuration 6 specified in the current protocol. Refer to the HARQ timing relationship of configuration 0, configuration 1, configuration 3, and configuration 6 shown in Figure 6-9, where the timing relationship determined by the block is a compatible timing relationship. As can be seen from Fig. 6, the timing relationship in this embodiment is compatible with configuration 0 on timings 2 and 6. As can be seen from Fig. 7, the timing relationship in this embodiment is compatible with configuration 1 at timings 1, 2, 5, and 6. As can be seen from Fig. 8, the timing relationship in this embodiment is compatible with the configuration 3 at timings 5 and 6. As can be seen from Fig. 9, the timing relationship in this embodiment is compatible with the configuration 6 at timings 1, 5. Therefore, the sending end can also carry process information (such as a process number) in the scheduling signaling.

 Specifically, if the base station notifies the Rd-8/9/10 UE of the use of TDD UL/DL configurationO, the downlink service can be scheduled on timings 2 and 6.

 If the base station notifies the Rel-8/9/lO UE of the use of TDD UL/DL configuration 1, the downlink traffic can be scheduled on the timings 1, 2, 5 and 6.

 If the base station notifies the Rel-8/9/lO UE of the use of TDD UL/DL configurations, the downlink traffic can be scheduled on the timings 5 and 6.

 If the base station notifies the Rel-8/9/lO UE of the use of the TDD UL/DL configuration, the downlink traffic can be scheduled on the timings 1 and 5.

 Through the above description, the implementation process of downlink data transmission is understood. The process is mainly implemented by the receiving end and the transmitting end. The internal structure and functions of the receiving end device and the transmitting end device are introduced below.

 Referring to FIG. 10, the receiving end device in this embodiment includes: an interface module 1001 and a control module 1002. The receiving device can be a user device or a relay device.

 The interface module 1001 is configured to transmit various signaling and data, and in particular, receive data in a downlink pilot time slot of the first type of subframe or the third type of subframe or the fourth type of subframe; The ACK or NACK is only fed back in the second type of subframe. The interface module, specifically for receiving data, includes at least downlink data on a downlink shared channel or data on a downlink control channel (PDCCH) indicating downlink half-persistent scheduling (SPS) release.

The control module 1002 is configured to generate various signaling and data, and detect the received data, and according to the detection result, instruct the interface module to feed back an ACK or a NACK only in the second type of subframe. Each of the first type of subframes or the third type of subframes or the fourth type of subframe downlink pilot time slots that are available for data transmission corresponds to one feedback subframe, and the feedback subframe is corresponding to the data. The subframe in which the ACK or NACK is located.

 Preferably, the interface module 1001 is configured to: when receiving data in the subframe n, feed back the ACK or NACK corresponding to the data only in the subframe n+k, where k is the subframe n and the preset timing relationship It is determined that the timing relationship specifies that the ACK or NACK of the feedback only occurs in the second type of subframe.

 Specifically, the interface module 1001 is specifically configured to: when the data is received in the subframe n, and n=0 or 5, send the ACK or NACK feedback corresponding to the data only in the subframe n+7; n, and when receiving the data in n=1 or 6, transmitting ACK or NACK feedback corresponding to the data only in subframe n+6; receiving the data in subframe n, and n=3 or 8 Transmitting ACK or NACK feedback corresponding to the data only in subframe n+4; when receiving the data in subframe n, and n=4 or 9, transmitting the data only in subframe n+8 The ACK or NACK feedback corresponding to the data.

 Referring to FIG. 11, the sending end device in this embodiment includes: an interface module 1101 and a control module 1102. The sender device can be a station or a relay device.

 The interface module 1101 is configured to transmit various signaling and data, in particular, to send data in downlink pilot time slots of the first type or the third type of subframe or the fourth type of subframe; An ACK or a NACK is received in the second type of subframe. The interface module 1101 is configured to include at least downlink data on a downlink shared channel or data on a downlink control channel (PDCCH) indicating downlink half-persistent scheduling (SPS) release.

The control module 1102 is configured to generate various signaling and data, and determine that the received feedback only occurs in the second type of subframe according to the subframe in which the transmitted data is located, and instruct the interface module 1101 to be only in the second class. Receive ACK or NACK in frame ₀

 Each of the first type of subframes or the third type of subframes or the fourth type of subframe downlink pilot time slots that are available for data transmission corresponds to one feedback subframe, and the feedback subframe is corresponding to the data. The subframe in which the ACK or NACK is located.

 Preferably, the interface module 1101 is specifically configured to: when transmitting data in the subframe n, receive an ACK or a NACK only in the subframe n+k, where k is determined by the subframe n and a preset timing relationship, in a timing relationship The received ACK or NACK only occurs in the second type of subframe.

 Specifically, the interface module 1101 is specifically configured to: when the data is sent in the subframe n, and n=0 or 5, receive the ACK or NACK feedback corresponding to the data only in the subframe n+7; n, and when the data is sent in n=l or 6, the ACK or NACK feedback corresponding to the data is received only in the subframe n+6; the data is sent in the subframe n, and n=3 or 8. Receiving ACK or NACK feedback corresponding to the data only in subframe n+4; when transmitting the data in subframe n, and n=4 or 9, receiving the only in subframe n+8 The ACK or NACK feedback corresponding to the data.

In the embodiment of the present invention, a new HARQ timing relationship is designed for the dynamic subframe system, and the timing relationship is used for downlink transmission and feedback, and data transmission is realized when dynamically uplink and downlink subframes are allocated. Provided by the embodiments of the present invention The HARQ timing relationship also has good backward compatibility.

 Those skilled in the art will appreciate that embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the present invention is in the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) in which computer usable program code is embodied.

 The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It will be understood that each process and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

 The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

 These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

 It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and modifications of the invention

Claims

Rights request A method for processing a downlink transmission at a receiving end, which is applied to a dynamic subframe system, wherein the dynamic subframe system is composed of at least four types of subframes, wherein the first type of subframes can only be used for downlink transmission. The second type of subframe can only be used for uplink transmission, and the third type of subframe can be dynamically configured for uplink or downlink transmission, and the third type of subframe cannot be used for both uplink and downlink transmission, and the fourth type of subframe It is a special time slot, and the fourth type of subframe includes a downlink pilot time slot DwPTS, a guard interval GP and an uplink pilot time slot UpPTS; the method includes the following steps:  Receiving, by the receiving end, data in a downlink pilot time slot of the first type of subframe or the third type of subframe or the fourth type of subframe;  After receiving the data, the receiving end feeds back the correct acknowledgement ACK or the error acknowledgement NACK only in the second type of subframe. 2. The method according to claim 1, wherein the data received by the receiving end includes at least downlink data on the downlink shared channel or data on the downlink control channel PDCCH indicating that the downlink semi-persistent scheduling SPS is released.  The method according to claim 1, wherein each of the first type of subframes or the third type of subframes or the fourth type of subframes that are available for data transmission is downlink pilot time The slot corresponds to a feedback subframe, and the feedback subframe is a subframe in which the ACK or NACK corresponding to the data is located.  The method according to claim 1, 2 or 3, wherein the step of the receiver not only feeding back an ACK or a NACK in the second type of subframe comprises: receiving when receiving data in the subframe n The terminal only feeds back the ACK or NACK corresponding to the data in the subframe n+k, where k is determined by the subframe n and a preset timing relationship, and the timing relationship specifies that the ACK or NACK of the feedback only occurs in the second type of subframe. in.  The method of claim 4, wherein when the data is received in the subframe n, the receiving end only feeds back the ACK or NACK corresponding to the data in the subframe n+k:  When the data is received in the subframe n, and n=0 or 5, the receiving end only sends the ACK or NACK feedback corresponding to the data in the subframe n+7;  When the data is received in the subframe n, and n=1 or 6, the receiving end only sends the ACK or NACK feedback corresponding to the data in the subframe n+6;  When the data is received in the subframe n, and n=3 or 8, the receiving end only sends the ACK or NACK feedback corresponding to the data in the subframe n+4;  When the data is received in subframe n, and n = 4 or 9, the receiving end transmits the ACK or NACK feedback corresponding to the data only in subframe n+8. A method for processing a downlink transmission at a transmitting end, which is applied to a dynamic subframe system, wherein the dynamic subframe system is composed of at least four types of subframes, wherein the first type of subframes can only be used for downlink transmission. The second type of subframe can only be used for uplink transmission, and the third type of subframe can be dynamically configured for uplink or downlink transmission, and the third type of subframe cannot be used for both uplink and downlink transmission, and the fourth type of subframe Is a special time slot, and the fourth type of subframe includes a downlink pilot time slot DwPTS, guard interval GP and uplink pilot time slot UpPTS; the method comprises the following steps:  Transmitting, by the sending end, data in a downlink pilot time slot of the first type of subframe or the third type of subframe or the fourth type of subframe;  The transmitting end receives the correct acknowledgement ACK or the error acknowledgement NACK only in the second type of subframe.  The method according to claim 6, wherein the data sent by the transmitting end includes at least downlink data on the downlink shared channel or data on the downlink control channel PDCCH indicating that the downlink semi-persistent scheduling SPS is released.  The method according to claim 6, wherein each of the first type of subframes or the third type of subframes or the fourth type of subframes that are available for data transmission is downlink pilot time The slot corresponds to a feedback subframe, and the feedback subframe is a subframe in which the ACK or NACK corresponding to the data is located.  The method according to claim 6, 7 or 8, wherein the step of receiving the ACK or the NACK only in the second type of subframe by the transmitting end comprises: sending when the data is transmitted in the subframe n The terminal receives the ACK or NACK feedback corresponding to the data only in the subframe n+k, where k is determined by the subframe n and a preset timing relationship, and the received ACK or NACK in the timing relationship only occurs in the second category. In the frame.  The method according to claim 9, wherein when the data is transmitted in the subframe n, the step of the sender receiving the ACK or NACK feedback corresponding to the data only in the subframe n+k includes:  When the data is transmitted in the subframe n, and n=0 or 5, the transmitting end receives the ACK or NACK feedback corresponding to the data only in the subframe n+7;  When the data is transmitted in the subframe n, and n=1 or 6, the transmitting end receives the ACK or NACK feedback corresponding to the data only in the subframe n+6;  When the data is transmitted in the subframe n, and n=3 or 8, the transmitting end receives the ACK or NACK feedback corresponding to the data only in the subframe n+4;  When the data is transmitted in subframe n, and n = 4 or 9, the transmitting end receives the ACK or NACK feedback corresponding to the data only in subframe n+8.  A receiving end device for downlink transmission, which is applied to a dynamic subframe system, wherein the dynamic subframe system is composed of at least four types of subframes, wherein the first type of subframes can only be used for downlink transmission, The second type of subframe can be used for uplink transmission only, and the third type of subframe can be dynamically configured for uplink or downlink transmission. The third type of subframe cannot be used for both uplink and downlink transmission, and the fourth type of subframe is The special time slot, the fourth type of subframe includes a downlink pilot time slot DwPTS, a guard interval GP and an uplink pilot time slot UpPTS;  An interface module, configured to receive data in a downlink pilot time slot of the first type of subframe or the third type of subframe or the fourth type of subframe; and only in the second type of subframe The feedback module correctly detects the ACK or the error response NACK. The control module is configured to detect the received data, and according to the detection result, instruct the interface module to feed back an ACK or a NACK only in the second type of subframe. 12. The receiving end device according to claim 11, wherein the interface module has data for receiving The downlink data on the downlink shared channel or the data on the downlink control channel PDCCH indicating the downlink semi-persistent scheduling SPS release is included.  The receiving end device according to claim 11, wherein each of the first type of subframes or the third type of subframes or the downlink of the fourth type of subframes that can be used for data transmission The frequency slot corresponds to one feedback subframe, and the feedback subframe is a subframe in which the ACK or NACK corresponding to the data is located.  The receiving end device according to claim 11, 12 or 13, wherein the interface module is specifically configured to: when receiving data in the subframe n, feed back the data only in the subframe n+k ACK or NACK, where k is determined by subframe n and a preset timing relationship that specifies that the ACK or NACK of the feedback occurs only in the second type of subframe.  The receiving end device according to claim 14, wherein the interface module is specifically configured to send only in the subframe n+7 when the data is received in the subframe n, and n=0 or 5. ACK or NACK feedback corresponding to the data; when receiving the data in subframe n, and n=l or 6, transmitting ACK or NACK feedback corresponding to the data only in subframe n+6; n, and when receiving the data in n=3 or 8, transmitting ACK or NACK feedback corresponding to the data only in subframe n+4; receiving the data in subframe n, and n=4 or 9 At this time, the ACK or NACK feedback corresponding to the data is transmitted only in subframe n+8.  A downlink device for transmitting a downlink device, which is applied to a dynamic subframe system, wherein the dynamic subframe system is composed of at least four types of subframes, wherein the first type of subframes can only be used for downlink transmission, The second type of subframe can be used for uplink transmission only, and the third type of subframe can be dynamically configured for uplink or downlink transmission. The third type of subframe cannot be used for both uplink and downlink transmission, and the fourth type of subframe is The special time slot, the fourth type of subframe includes a downlink pilot time slot DwPTS, a guard interval GP and an uplink pilot time slot UpPTS;  An interface module, configured to send data in a downlink pilot time slot of the first type or the third type of subframe or the fourth type of subframe; and receive an ACK only in the second type of subframe Or NACK;  And a control module, configured to determine, according to the subframe where the data is sent, that the received feedback only occurs in the second type of subframe, and instruct the interface module to receive the correct acknowledgement ACK or the error acknowledgement NACK only in the second type of subframe. .  The transmitting end device according to claim 16, wherein the interface module is configured to send at least downlink data on a downlink shared channel or a downlink control channel PDCCH indicating downlink half-persistent scheduling SPS release. data.  The transmitting end device according to claim 16, wherein each of the first type of subframes or the third type of subframes or the fourth type of subframes that are available for data transmission is downlink pilots. The time slot corresponds to one feedback subframe, and the feedback subframe is a subframe in which the ACK or NACK corresponding to the data is located. The transmitting end device according to claim 16, 17 or 18, wherein the interface module is specifically configured to: when transmitting data in the subframe n, receive the data corresponding only in the subframe n+k ACK or NACK feedback, where k is determined by subframe n and a preset timing relationship, and the received ACK or NACK in the timing relationship only occurs in the In the second type of subframe.  The transmitting end device according to claim 19, wherein the interface module is specifically configured to receive only in the subframe n+7 when the data is sent in the subframe n, and n=0 or 5 ACK or NACK feedback corresponding to the data; when the data is transmitted in subframe n, and n=l or 6, the ACK or NACK feedback corresponding to the data is received only in subframe n+6; n, and when the data is sent in n=3 or 8, the ACK or NACK feedback corresponding to the data is received only in the subframe n+4; the data is sent in the subframe n, and n=4 or 9. At this time, the ACK or NACK feedback corresponding to the data is received only in subframe n+8.