CN103378961B

CN103378961B - A kind of data transmission method and device

Info

Publication number: CN103378961B
Application number: CN201210134655.9A
Authority: CN
Inventors: 司倩倩; 林亚男; 沈祖康
Original assignee: China Academy of Telecommunications Technology CATT
Current assignee: China Academy of Telecommunications Technology CATT; Datang Mobile Communications Equipment Co Ltd
Priority date: 2012-04-28
Filing date: 2012-04-28
Publication date: 2016-04-06
Anticipated expiration: 2032-04-28
Also published as: CN103378961A; WO2013159734A1

Abstract

The invention discloses a kind of data transmission method and device, its method comprises: determine the TDD uplink-downlink configuration used when dispatching the PUSCH of FDD up-link carrier and feed back, and the descending sub frame and/or special subframe of described TDD uplink-downlink configuration instruction are dispatched the PUSCH of FDD up-link carrier; Described PUSCH is received at FDD sub-frame of uplink; The descending sub frame and/or special subframe of described TDD uplink-downlink configuration instruction feed back described PUSCH.The present invention can be applied in TDD carrier wave and FDD up-link carrier carries out being polymerized and TDD carrier wave carries out the scene across carrier dispatching to FDD carrier wave, TDD carrier wave is to the scheduling of upstream data corresponding to FDD up-link carrier and feedback, ensure that data normal transmission, improve the stability of a system.

Description

Data transmission method and device

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a data transmission method and apparatus.

Background

Currently, LTE (long term evolution) supports three duplex modes, namely FDD (frequency division duplex), H-FDD (HalfFDD, half frequency division duplex) and TDD (time division duplex).

FDD means that uplink transmission and downlink transmission are performed on different carrier frequency bands, and allows an eNB (base station) and a UE (terminal) to perform signal reception and signal transmission simultaneously; TDD refers to that uplink transmission and downlink transmission are performed on the same carrier frequency band, allowing eNB and UE to perform signal transmission/signal reception or signal reception/signal transmission in different time periods, respectively.

In LTE and previous wireless communication systems, only one carrier is configured in one cell, and the maximum bandwidth in LTE systems is 20 MHz.

In an LTE-a (long term evolution-Advanced) system, the peak rate of the system is greatly improved compared with that of LTE, and it is required to reach 1Gbps downlink and 500Mbps uplink. The peak rate requirement cannot be achieved if only one carrier with a maximum bandwidth of 20MHz is used. Therefore, the LTE-a system needs to extend the bandwidth that can be used by the UE, and thus a CA (carrier aggregation) technology is introduced, i.e., multiple continuous or discontinuous carriers under the same eNB are aggregated together and serve the UE to provide a required rate. These aggregated carriers are also called CC (component carrier). Each cell may be a component carrier, and cells (component carriers) under different enbs cannot be aggregated. In order to ensure that the UE of the LTE system can operate under each aggregated carrier, each carrier does not exceed 20MHz at maximum. Taking 4 aggregated carriers as an example, wherein there are 4 carriers that can be aggregated under the eNB of LTE-a, the base station may perform data transmission with the UE on the 4 carriers simultaneously, so as to improve the system throughput.

In the LTE system, both the FDD mode and TDD mode are one radio frame 10ms and one subframe 1 ms. For each radio frame in the TDD mode, seven TDD Uplink and Downlink configurations are defined, specifically as shown in table 1, where D represents a DL (Downlink) subframe, U represents an UL (Uplink) subframe, and S represents a special subframe of the TDD system.

TABLE 1

(TDD uplink and downlink configuration)

In the LTE system, the eNB performs PUSCH (physical uplink shared channel) scheduling for the UE. Specifically, the method comprises the following steps:

for TDD uplink and downlink configuration 1-6 and conventional HARQ (hybrid automatic repeat request) operation, a PDCCH (physical downlink control channel) and/or PHICH (physical HARQ indicator channel) with DCI format 0 or format 4 detected by the UE in subframe n is transmitted, and PUSCH scheduling information in subframe n + l is indicated in the PDCCH and/or PHICH. The UE transmits data information on the corresponding PRB (physical resource block) in the PUSCH of subframe n + l (value l given in table 2).

For TDD uplink and downlink configuration 0 and normal HARQ operation, the UE transmits PDCCH and/or PHICH with DCI format 0 detected in subframe n, where the PUSCH scheduling information in subframe n + l is indicated. If the PDCCH has DCI format 0 and MSB (most significant bit) of the uplink index in DCI format 0 is set to 1, or the corresponding resource I in subframe n is 0 or 5_PHICHReceiving PHICH 0, the UE transmits data information on the corresponding PRB in PUSCH of subframe n + l (value l given in table 2).

For TDD uplink and downlink configuration 0 and normal HARQ operation, the UE detects PDCCH and/or PHICH transmission with DCI format 0 in subframe n. If the PDCCH has DCI format 0 and LSB of uplink index of DCI format 0 is set to 1, or corresponding resource I in subframe n-0 or 5_PHICHThe PHICH is received 1 or in subframe n 1 or 6, the PUSCH scheduling information in subframe n +7 is indicated in the PDCCH and/or PHICH, and the UE transmits data information on the corresponding PRB in the PUSCH in subframe n + 7.

For TDD uplink and downlink configuration 0, the UE detects PDCCH and/or PHICH transmission with DCI format 0 in subframe n. If the PDCCH has DCI format 0 and the MSB and LSB of the uplink index in DCI format 0 are both 1, the PDCCH and/or PHICH indicates that the PUSCH scheduling information UE in subframes n + l and n +7 transmits data information on the corresponding PRB in the PUSCH in subframes n + l (the value of l is given in table 2) and n + 7.

TABLE 2

(PUSCH scheduling timing relationship corresponding to TDD uplink and downlink configuration)

In the LTE system, a plurality of radio frames are arranged in sequence, and table 2 shows the value of i associated with PUSCH scheduling in the LTE tdd system by taking only one radio frame as an example, where n + l > 9 indicates a downlink subframe in a subsequent radio frame. For example, for an uplink and downlink configuration 0, subframe n ═ 6 corresponds to a value of l of 6.

In the LTE system, the eNB performs puschhharq feedback to the UE. Specifically, the method comprises the following steps:

in the lte fdd system, the eNB detects PUSCH transmission in the uplink subframe n-4, and feeds back the puschhharq information on the corresponding PHICH resource in the downlink subframe n.

In the lte TDD system, for TDD uplink and downlink configurations 1-6, a base station detects PUSCH transmission in an uplink subframe n-k, and feeds back puschhharq information in a corresponding PHICH resource in a downlink subframe n, where the value of k is shown in table 3.

In the LTETDD system, for TDD uplink and downlink configuration 0, the base station detects PUSCH transmission in uplink subframe n-k, corresponding to I in downlink subframe n_PHICHThe PHICH resource with 1-0 feeds back the corresponding puschh arq information, where the value of k is shown in table 3; or the base station detects PUSCH transmission in the uplink subframe n-6, corresponding to I in the downlink subframe n_PHICHThe PHICH resource with 1-1 feeds back the corresponding PUSCHHHARQ information.

TABLE 3

(PUSCHHHARQ feedback timing relation corresponding to TDD uplink and downlink configuration)

In the LTE system, a plurality of radio frames are arranged in sequence, and table 3 shows the feedback of the relative k value of puschhharq in the LTE tdd system by taking only one radio frame as an example, where n-k < 0 indicates the uplink subframe in the previous radio frame. For example, for an uplink and downlink configuration 0, the value of k for subframe n-6 is 4.

At present, there is no scheduling and feedback scheme for uplink data corresponding to a FDD uplink carrier when aggregation is performed on the TDD carrier and the FDD uplink carrier is subjected to cross-carrier scheduling by the TDD carrier.

Disclosure of Invention

The invention aims to provide a data transmission method and a data transmission device, and aims to solve the problem of realizing the scheduling and feedback of uplink data corresponding to an FDD uplink carrier when a TDD carrier and an FDD uplink carrier are aggregated and the TDD carrier performs cross-carrier scheduling on the FDD carrier.

The purpose of the invention is realized by the following technical scheme:

a method of data transmission, comprising:

determining TDD uplink and downlink configuration used for scheduling and feeding back a PUSCH of an FDD uplink carrier;

scheduling PUSCH of FDD uplink carrier on the downlink subframe and/or special subframe indicated by the TDD uplink and downlink configuration;

receiving the PUSCH on an FDD uplink subframe;

and feeding back the PUSCH on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration.

A method of data transmission, comprising:

scheduling the PUSCH of the FDD uplink carrier on the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration, and performing PUSCH transmission on the FDD uplink subframe;

receiving feedback of the PUSCH on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration;

and carrying out PUSCH retransmission processing according to the received PUSCH feedback information.

A data transmission apparatus comprising:

an uplink and downlink configuration determining module, configured to determine TDD uplink and downlink configurations used for scheduling and feeding back a PUSCH of an FDD uplink carrier;

a PUSCH scheduling module, configured to schedule a PUSCH of an FDD uplink carrier on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration;

a PUSCH receiving module, configured to receive the PUSCH on an FDD uplink subframe;

and the PUSCH feedback module is used for feeding back the PUSCH on the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration.

A data transmission apparatus comprising:

a PUSCH scheduling response module, configured to perform PUSCH transmission on an FDD uplink subframe according to the scheduling of the PUSCH of the FDD uplink carrier on the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration;

a PUSCH feedback receiving module, configured to receive feedback on the PUSCH on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration;

and the PUSCH retransmission processing module is used for carrying out PUSCH retransmission processing according to the received PUSCH feedback information.

The method and the device provided by the invention can be applied to the scene that the TDD carrier and the FDD uplink carrier are aggregated and the TDD carrier carries out cross-carrier scheduling on the FDD carrier, and the scheduling and the feedback of the TDD carrier on the uplink data corresponding to the FDD uplink carrier ensure the normal transmission of the data and improve the stability of the system.

Drawings

Fig. 1 is a flowchart of an eNB-side data transmission method according to an embodiment of the present invention;

fig. 2 shows a first PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink and downlink configuration is 0;

fig. 3 shows a second PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink and downlink configuration is 0;

fig. 4 shows a first PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink/downlink configuration 1 is performed;

fig. 5 shows a second PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink/downlink configuration 1 is performed;

fig. 6 shows a first PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink/downlink configuration 2 is performed;

fig. 7 shows a second PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink/downlink configuration 2 is performed;

fig. 8 shows a third PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink/downlink configuration 2 is performed;

fig. 9 shows a first PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink/downlink configuration 3 is performed;

fig. 10 shows a second PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink/downlink configuration 3 is performed;

fig. 11 shows a third PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink/downlink configuration 3 is performed;

fig. 12 shows a fourth PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink/downlink configuration 3 is performed;

fig. 13 shows a first PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink/downlink configuration 4 is performed;

fig. 14 shows a second PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink and downlink configuration 4 is performed;

fig. 15 shows a third PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink/downlink configuration 4 is performed;

fig. 16 shows a fourth PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink/downlink configuration 4 is performed;

fig. 17 shows a first PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink/downlink configuration 5 is performed;

fig. 18 shows a second PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink/downlink configuration 5 is performed;

fig. 19 shows a third PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink/downlink configuration 5 is performed;

fig. 20 shows a first PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink/downlink configuration 6 is performed;

fig. 21 shows a second PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink/downlink configuration 6 is performed;

fig. 22 shows a third PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink/downlink configuration 6 is performed;

fig. 23 shows a fourth PUSCH feedback timing sequence and a PUSCH scheduling timing sequence according to an embodiment of the present invention when TDD uplink/downlink configuration 6 is performed;

fig. 24 is a flowchart of a UE-side data transmission method according to an embodiment of the present invention;

fig. 25 is a schematic structural diagram of an eNB-side data transmission apparatus according to an embodiment of the present invention;

fig. 26 is a schematic structural diagram of a UE-side data transmission apparatus according to an embodiment of the present invention.

Detailed Description

The invention discloses a data transmission method of an eNB side, which is implemented as shown in FIG. 1 and specifically comprises the following operations:

step 100, the eNB determines the TDD uplink and downlink configuration used for scheduling and feeding back the PUSCH of the FDD uplink carrier.

The TDD uplink and downlink configuration determined in step 100 is shown in table 1.

And step 110, the eNB schedules the PUSCH on the FDD uplink carrier on the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration.

And after the eNB side schedules the PUSCH of the UE, the UE transmits the PUSCH on the FDD uplink subframe according to the scheduling indication.

And step 120, the eNB receives the PUSCH in the FDD uplink subframe.

And step 130, the eNB feeds back the PUSCH on the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration.

In the present invention, the downlink subframe and/or the special subframe of the TDD uplink/downlink configuration indication for feeding back the PUSCH may be referred to as a feedback subframe. And if the feedback sub-frame has no PHICH resource, transmitting the retransmitted uplink scheduling signaling in the feedback sub-frame. The puschhharq feedback means that ACK/NACK (correct/error) information is fed back.

In the embodiment of the invention, the downlink subframe for scheduling the PUSCH of the FDD uplink carrier can be an FDD downlink subframe or a TDD downlink subframe. The downlink subframe for feeding back the PUSCH of the FDD uplink carrier may be an FDD downlink subframe or a TDD downlink subframe.

For the above step 130, the present invention provides the following four preferred implementations:

(A)

If the number of the FDD uplink subframe for transmitting the PUSCH is the same as the number of the uplink subframe indicated by the TDD uplink and downlink configuration, feeding back according to the feedback time sequence of the PUSCHHHARQ corresponding to the TDD uplink and downlink configuration;

and if the number of the FDD uplink subframe m for transmitting the PUSCH is the same as the number of the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration, feeding back on the downlink subframe or the special subframe indicated by the TDD uplink and downlink configuration which is the first subframe after m +3 and meets the preset condition. Wherein the predetermined condition is: and for any two FDD uplink subframes, the PUSCH feedback time corresponding to the FDD uplink subframe with the later time sequence is not earlier than the PUSCH feedback time corresponding to the FDD uplink subframe with the earlier time sequence.

In the embodiment of the present invention, the uplink subframe of the TDD uplink/downlink configuration indication with the same number as the FDD uplink subframe may be an FDD uplink subframe or a TDD uplink subframe.

In the embodiment of the present invention, the feedback timing of the puschhharq corresponding to the TDD uplink and downlink configuration is shown in table 3. Specifically, for TDD uplink and downlink configuration 0, the eNB receives PUSCH in uplink subframe n-6, and feeds back the PUSCH in downlink subframe n.

(II)

and if the number of the FDD uplink subframe m for transmitting the PUSCH is the same as the number of the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration, feeding back the PUSCH on the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration after m +3 and meeting the preset conditions according to a preset equalization principle. The equalization principle aims to ensure that the difference between the number of FDD uplink subframes corresponding to each feedback subframe is not more than 1. The description of the predetermined condition is referred to the description of the above-mentioned first preferred embodiment, and is not repeated here.

In the first and second preferred embodiments, the downlink subframe and/or the special subframe indicated by the TDD uplink/downlink configuration is used to feed back the PUSCH according to the feedback timing sequence of the puschhharq corresponding to the TDD uplink/downlink configuration. For the TDD carrier, the original PHICH resource on the TDD carrier is utilized as much as possible. In addition, in the second preferred embodiment, the number of FDD uplink subframes corresponding to the PUSCH feedback of each downlink subframe or special subframe of the TDD carrier is equalized as much as possible.

(III)

And for the PUSCH transmitted in the FDD uplink subframe m, feeding back on the downlink subframe or the special subframe indicated by the first TDD uplink and downlink configuration after m + 3.

(IV)

For the PUSCH transmitted in the FDD uplink subframe m, feedback is performed on the downlink subframe and/or the special subframe, which is after m +3 and meets the TDD uplink-downlink configuration indication of the predetermined condition, according to a predetermined equalization principle, where the description of the equalization principle refers to the description of the above-mentioned second preferred embodiment, and is not described again here. The description of the predetermined condition is referred to the description of the above-mentioned first preferred embodiment, and is not repeated here.

Since the PUSCH of the FDD uplink subframe m is fed back in the first feedback subframe after m +3, which meets the predetermined condition, is the earliest feedback time, the puschhrtt (round trip delay) can be reduced as much as possible by using the above-described preferred embodiments (third) and (fourth).

In the present invention, the specific implementation manner of the step 100 may be: according to a feedback time sequence for feeding back a PUSCH of an FDD uplink carrier and the PUSCH maximum RTT, configuring scheduling instruction information of the PUSCH on a downlink subframe and/or a special subframe indicated by TDD uplink and downlink configuration; and transmitting the scheduling instruction information on the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration.

The feedback timing for feeding back the PUSCH of the FDD uplink carrier refers to the PUSCH feedback timing determined before step 100, and for determining the PUSCH feedback timing, reference may be made to the feedback timing determined in the above four preferred embodiments of the present invention.

In the present invention, the ul index (uplink index) bits of the scheduling instruction information carried by each downlink subframe or special subframe may be configured to be the same or not completely the same. And the ULindex represents the number of FDD uplink subframes corresponding to scheduling instruction information carried in the downlink subframes or the special subframes.

If the ulidex bit numbers of the scheduling instruction information carried by each downlink subframe or special subframe are the same, the ulidex bit numbers are specifically the maximum value of the corresponding FDD uplink subframe numbers when each downlink subframe and/or special subframe carrying the scheduling instruction information feeds back the PUSCH.

If the number of ulidex bits of the scheduling instruction information carried by each downlink subframe or special subframe is not completely the same, the number of ulidex bits of the scheduling instruction information carried by each downlink subframe or special subframe is specifically the number of FDD uplink subframes corresponding to the downlink subframe or special subframe when the downlink subframe or special subframe feeds back PUSCH.

If the ULindex bit number of the scheduling instruction information carried by each downlink subframe or special subframe is the same, configuring the indicated downlink subframe and/or special subframe on the TDD uplink and downlink according to the feedback time sequence for feeding back the PUSCH of the FDD uplink carrier and the PUSCH maximum RTTThe scheduling instruction information for the PUSCH configured above may be described as: if the PUSCH of the FDD uplink subframe n-k is fed back on the downlink subframe or the special subframe n indicated by the TDD uplink and downlink configuration, the downlink subframe or the special subframe n comprises the FDD uplink subframe n + t after scheduling n +3_RTT-k and consecutive PUSCHs of x FDD uplink subframe transmissions. Preferably, starting from the FDD uplink subframe which is possibly scheduled earliest after n +3, the PUSCH transmitted by x consecutive FDD uplink subframes is scheduled by the downlink subframe or the special subframe n. Wherein, the earliest possible scheduled FDD uplink subframe needs to be ensured, and the scheduled x consecutive FDD uplink subframes include FDD uplink subframe n + t_RTT-k。t_RTTFor the maximum RTT of PUSCH, the number x of FDD uplink subframes scheduled by the downlink subframe or the special subframe n is the number of ULindex bits.

If the number of ulidex bits of the scheduling instruction information carried by each downlink subframe or special subframe is not completely the same, the scheduling instruction information of the PUSCH is configured on the downlink subframe and/or special subframe indicated by the TDD uplink and downlink configuration according to the feedback timing for feeding back the PUSCH of the FDD uplink carrier and the PUSCH maximum RTT, which can be described as follows: if the PUSCH of the FDD uplink subframe n-k is fed back on the downlink subframe or the special subframe n indicated by the TDD uplink and downlink configuration, scheduling the FDD uplink subframe n + t on the downlink subframe or the special subframe n_RTT-k transmitted PUSCH.

Taking the TDD uplink and downlink configuration 3 indicated TDD carrier to perform PUSCH scheduling and feedback of FDD uplink carrier as an example. When the above-described (first) preferred implementation manner is adopted, the corresponding PUSCH feedback timing and PUSCH scheduling timing are as shown in fig. 9. The two rows represent that the number of ULindex bits of the scheduling instruction information carried by each downlink subframe or special subframe is the same, and the scheduling time sequence of the PUSCH is the same; the middle two rows represent the scheduling time sequence of the PUSCH when the ULindex bit numbers of the scheduling instruction information carried by each downlink subframe or special subframe are not completely the same; the lower two rows represent feedback timing for PUSCH.

When TDD uplink and downlink configuration of a TDD carrier is 3, according to the first preferred implementation manner: when the number of the FDD uplink subframe (FDD uplink subframe 2, FDD uplink subframe 3, and FDD uplink subframe 4) for transmitting PUSCH is the same as the number of the uplink subframe indicated by the TDD uplink/downlink configuration 3, feedback is performed according to the feedback timing indicated by the uplink/downlink configuration 3 in table 3. That is, the PUSCH of the FDD uplink subframe 2 is fed back in the downlink subframe 8, the PUSCH of the FDD uplink subframe 3 is fed back in the downlink subframe 9, and the PUSCH of the FDD uplink subframe 4 is fed back in the downlink subframe 0. And if the number of the FDD uplink subframe m (m is 5,6,7, 8, 9, 0 and 1) for transmitting the PUSCH is the same as the number of the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration 3, feeding back on the downlink subframe or the special subframe indicated by the TDD uplink and downlink configuration 3 which meets the first preset condition after m + 3. That is, the PUSCH of the FDD uplink subframe 5 and the FDD uplink subframe 6 is fed back in the downlink subframe 0, the PUSCH of the FDD uplink subframe 7 is fed back in the downlink subframe 1, and the PUSCH of the FDD uplink subframe 8, the FDD uplink subframe 9, the FDD uplink subframe 0, and the FDD uplink subframe 1 is fed back in the downlink subframe 5.

According to the determined PUSCH feedback sequence, the maximum number of uplink subframes (4 uplink subframes) on an FDD uplink carrier is known to perform PUSCH feedback on a downlink subframe of a TDD carrier, and the maximum number of bits of ULindex is 4. It is also known that PUSCHTT is 11 ms. When the number of ulidex bits of the scheduling instruction information carried by each downlink subframe or special subframe is the same, the downlink subframe 5 feeds back the PUSCH of the FDD uplink subframe 8, the FDD uplink subframe 9, the FDD uplink subframe 0 and the FDD uplink subframe 1, so the downlink subframe 5 schedules the PUSCH of the FDD uplink subframe 9, the FDD uplink subframe 0, the FDD uplink subframe 1 and the FDD uplink subframe 2. Since the downlink subframe 8 feeds back the PUSCH of the FDD uplink subframe 2, the downlink subframe 8 performs PUSCH scheduling on the FDD uplink subframe 2, the FDD uplink subframe 3, the FDD uplink subframe 4, and the FDD uplink subframe 5. Similarly, the downlink subframe 9 performs PUSCH scheduling on the FDD uplink subframe 3, the FDD uplink subframe 4, the FDD uplink subframe 5, and the FDD uplink subframe 6, the downlink subframe 0 performs PUSCH scheduling on the FDD uplink subframe 4, the FDD uplink subframe 5, the FDD uplink subframe 6, and the FDD uplink subframe 7, the downlink subframe 1 performs PUSCH scheduling on the FDD uplink subframe 5, the FDD uplink subframe 6, the FDD uplink subframe 7, and the FDD uplink subframe 8, and the downlink subframe 5 performs PUSCH scheduling on the FDD uplink subframe 9, the FDD uplink subframe 0, the FDD uplink subframe 1, and the FDD uplink subframe 2. When the number of ulidex bits of the scheduling instruction information carried by each downlink subframe or special subframe is not identical, the downlink subframe 5 feeds back the PUSCH of the FDD uplink subframe 8, the FDD uplink subframe 9, the FDD uplink subframe 0 and the FDD uplink subframe 1, so that the downlink subframe 5 schedules the PUSCH of the FDD uplink subframe 9, the FDD uplink subframe 0, the FDD uplink subframe 1 and the FDD uplink subframe 2. Since the PUSCH of the FDD uplink subframe 2 is fed back in the downlink subframe 8, the PUSCH of the FDD uplink subframe 3 is scheduled in the downlink subframe 8. Since the PUSCH of the FDD uplink subframe 3 is fed back in the downlink subframe 9, the PUSCH of the FDD uplink subframe 4 is scheduled in the downlink subframe 9. Since the downlink subframe 1 feeds back the PUSCH of the FDD uplink subframe 7, the downlink subframe 1 performs PUSCH scheduling on the FDD uplink subframe 7, and similarly, the downlink subframe 0 performs PUSCH scheduling on the FDD uplink subframe 5, the FDD uplink subframe 6, and the FDD uplink subframe 7.

Taking the TDD uplink and downlink configuration 3 indicated TDD carrier to perform PUSCH scheduling and feedback of FDD uplink carrier as an example. When the second preferred implementation manner is adopted, the corresponding PUSCH feedback timing and PUSCH scheduling timing are as shown in fig. 10. The two rows represent that the number of ULindex bits of the scheduling instruction information carried by each downlink subframe or special subframe is the same, and the scheduling time sequence of the PUSCH is the same; the middle two rows represent the scheduling time sequence of the PUSCH when the ULindex bit numbers of the scheduling instruction information carried by each downlink subframe or special subframe are not completely the same; the lower two rows represent feedback timing for PUSCH.

When the TDD uplink and downlink configuration of the TDD carrier is 3, according to the second preferred implementation manner: when the FDD uplink subframe (FDD uplink subframe 2, FDD uplink subframe 3, and FDD uplink subframe 4) for transmitting PUSCH is the same as the uplink subframe number indicated by the TDD uplink/downlink configuration 3, feedback is performed according to the feedback timing indicated by the uplink/downlink configuration 3 in table 3. That is, the PUSCH of the FDD uplink subframe 2 is fed back in the downlink subframe 8, the PUSCH of the FDD uplink subframe 3 is fed back in the downlink subframe 9, and the PUSCH of the FDD uplink subframe 4 is fed back in the downlink subframe 0. And if the number of the FDD uplink subframe m (m is 5,6,7, 8, 9, 0, 1) for transmitting the PUSCH is the same as the number of the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration 3, feeding back on the downlink subframe or the special subframe indicated by the TDD uplink and downlink configuration 3 after m +3 and meeting the preset condition according to the above balancing principle. That is, the PUSCH of the FDD uplink subframe 5 is fed back in the downlink subframe 0, the PUSCH of the FDD uplink subframe 6 and the FDD uplink subframe 7 is fed back in the downlink subframe 1, the PUSCH of the FDD uplink subframe 8 and the FDD uplink subframe 9 is fed back in the downlink subframe 5, the PUSCH of the FDD uplink subframe 5 is fed back in the downlink subframe 0, and the PUSCH of the FDD uplink subframe 7 is fed back in the downlink subframe 1.

According to the determined PUSCH feedback sequence, the maximum number of 2 uplink subframes on the FDD carrier is known to perform PUSCH feedback on one downlink subframe of the TDD carrier, and the maximum number of ULindex bits is 2. It is also known that PUSCHTT is 11 ms. The corresponding PUSCH scheduling timing is shown in fig. 10.

Therefore, the PUSCH fed back by each feedback subframe is more balanced by adopting the second preferred implementation manner.

When the above-mentioned (third) and (fourth) preferred implementation manners are adopted, the corresponding PUSCH feedback timing sequence and PUSCH scheduling timing sequence may be determined by referring to the above-mentioned manners, which is not described herein again.

In the present invention, the step 110 may be further described as: and scheduling the PUSCH transmitted by the FDD uplink subframe n + L on the downlink subframe or the special subframe n indicated by the TDD uplink and downlink configuration, wherein L belongs to L. The above step 120 can also be described as: and feeding back the PUSCH transmitted by the FDD uplink subframe n-K on the downlink subframe or the special subframe n indicated by the TDD uplink and downlink configuration, wherein K belongs to K.

For a PUSCH transmitted by an FDD uplink subframe, the time sequence of a downlink subframe or a special subframe n for scheduling is earlier than the time sequence of a downlink subframe or a special subframe n for feedback.

Wherein, the number of ulidex bits of the scheduling instruction information carried in each downlink subframe or special subframe is the same:

for TDD uplink and downlink configuration 0:

if the first or third preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 2, the PUSCH scheduling timing is shown in the upper two rows of fig. 2, where n is 0 and n is 1, n is 5, and n is 6, L is {4,5,6,7}, n is 0 and n is 5, K is {7,6,5,4}, and n is 1 and n is 6, K is {4 };

or,

if the second or fourth preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 3, the PUSCH scheduling timing is shown in the upper two rows of fig. 3, and when n is 0 and n is 5, L is {4,5,6}, when n is 1 and n is 6, L is {5,6,7}, when n is 0 and n is 5, K is 7,6,5}, and when n is 1 and n is 6, K is {5,4 }.

For TDD uplink and downlink configuration 1:

if the first or third preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 4, the PUSCH scheduling timing is shown in the upper two rows of fig. 4, where n is 0 and n is 1, n is 4, n is 5, n is 6, and n is 9, L is {4,5,6}, n is 0 and n is 1, n is 5, and n is 6, K is {4}, and n is 4 and n is 9, K is {6,5,4 };

or,

if the second or fourth preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 5, the PUSCH scheduling timing is shown in the upper two rows of fig. 5, and when n is 0, n is 1, n is 5, and n is 6, L is {5,6}, n is 4, n is 9, L is 4,5, n is 0, n is 5, K is {5,4}, n is 1, n is 6, K is {4}, and n is 4, n is 9, K is 6.

For TDD uplink and downlink configuration 2:

if the first or third preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 6, the PUSCH scheduling timing is shown in the upper two rows of fig. 6, where n is 0 and n is 3, n is 4, n is 5, n is 8, and n is 9, L is {4,5,6}, n is 0 and n is 4, n is 5, and n is 9, K is {4}, and n is 3 and n is 8, K is {6,5,4 };

or,

if the second preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 7, the PUSCH scheduling timing is shown in the upper two rows of fig. 7, where n is 0 and n is 1 and n is 3 and n is 4 and n is 5 and n is 6 and n is 8 and n is 9, L is {4,5}, n is 0 and n is 1 and n is 4 and n is 5 and n is 6 and n is 9, K is {5}, and n is 3 and n is 8, K is 6,5 };

or,

if the above-described (fourth) preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 8, the PUSCH scheduling timing is shown in the upper two rows of fig. 8, where n is 0 and n is 1 and n is 3 and n is 4 and n is 5 and n is 6 and n is 8 and n is 9, L is {4,5}, n is 0 and n is 1 and n is 4 and n is 5 and n is 6 and n is 9, K is {4}, and n is 3 and n is 8, K is {5,4 };

for TDD uplink and downlink configuration 3:

if the above-mentioned first preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 9, the PUSCH scheduling timing is shown in the upper two rows of fig. 9, where n is 0 and n is 1, n is 5, n is 8, and n is 9, L is {4,5,6,7}, n is 0, K is {6,5,4}, n is 1, K is {4}, n is 5, K is {7,6,5,4}, and n is 8 and n is 9, K is {6 };

or,

if the second preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 10, the PUSCH scheduling timing is shown in the upper two rows of fig. 10, and when n is 0, L is {5,6}, when n is 1, L is {6,7}, when n is 5 and n is 6 and n is 7 and n is 8 and n is 9, L is 4,5}, when n is 0, K is {6,5}, when n is 1, K is {5,4}, when n is 5, K is 7,6}, when n is 6 and n is 7 and n is 8 and n is 9, K is {6 };

or,

if the third preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 11, the PUSCH scheduling timing is shown in the upper two rows of fig. 11, where n is 0 and n is 1 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, L is 4,5,6,7, n is 0 and n is 1 and n is 6 and n is 7 and n is 8 and n is 9, K is 4, and n is 5, K is 7, 5, 4;

or,

if the above-described (fourth) preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 12, the PUSCH scheduling timing is shown in the upper two rows of fig. 12, where n is 0, n is 1, n is 7, n is 8, and n is 9, L is {6,7}, where n is 5, L is {4,5}, where n is 6, L is 5,6}, n is 0, n is 1, n is 8, and n is 9, K is {4}, where n is 5, K is 7,6}, and n is 6, K is {6,5}, where n is 7, and K is {5,4 }.

For TDD uplink and downlink configuration 4:

if the above-mentioned first preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 13, the PUSCH scheduling timing is shown in the upper two rows of fig. 13, where n is 0 and n is 1 and n is 4 and n is 5 and n is 8 and n is 9, L is 4,5,6, n is 0 and n is 1 and n is 5, K is 4, n is 4 and n is 9, K is 6,5,4, and n is 8, K is 6;

or,

if the second preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 14, the PUSCH scheduling timing is shown in the upper two rows of fig. 14, and when n is 0 and n is 1, L is 5,6, n is 4 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, L is 4,5, n is 0, K is 5,4, n is 1, K is 4, n is 5 and n is 6 and n is 7 and n is 8, K is 6, and n is 9, K is 6;

or,

if the third preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 15, the PUSCH scheduling timing is shown in the upper two rows of fig. 15, where n is 0 and n is 1 and n is 4 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, L is {4,5,6}, n is 0 and n is 1 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, K is 4, and n is 4, K is 6,5,4 };

if the above-described (fourth) preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 16, and the PUSCH scheduling timing is shown in the upper two rows of fig. 16, or, when n is 0 and n is 1, n is 5, n is 6, n is 7, n is 8, and n is 9, L is {5,6}, when n is 4, L is 4, n is 1, n is 6, n is 7, n is 8, and n is 9, K is 4, n is 4, K is 6, and n is 5, K is 5.

For TDD uplink and downlink configuration 5:

if the above-mentioned first preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 17, the PUSCH scheduling timing is shown in the upper two rows of fig. 17, where n is 0 and n is 1 and n is 3, n is 4, n is 5, n is 8, and n is 9, L is 4,5,6, n is 0 and n is 1, n is 4, n is 5, and n is 9, K is 4, and n is 3, K is 5,4, and n is 8, K is 6,5, 4;

or,

if the second preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 18, the PUSCH scheduling timing is shown in the upper two rows of fig. 18, where n is 0 and n is 1 and n is 3 and n is 4 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, L is 4,5, n is 0 and n is 1 and n is 9, K is 5, n is 3 and n is 4 and n is 5 and n is 6 and n is 7, K is 6, and n is 8, K is 6 and 5;

or,

if the third or fourth preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 19, the PUSCH scheduling timing is shown in the upper two rows of fig. 19, where n is 0 and n is 1 and n is 3 and n is 4 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, L is 4,5, n is 0 and n is 1 and n is 4 and n is 5 and n is 6 and n is 8 and n is 9, K is 4, and n is 3, K is 5, 4;

for TDD uplink and downlink configuration 6:

if the above-mentioned first preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 20, the PUSCH scheduling timing is shown in the upper two rows of fig. 20, where n is 0, n is 1, n is 5, n is 6, and n is 9, L is {4,5,6,7}, n is 0, K is {6,5,4}, n is 1, n is 6, K is 4}, n is 5, K is 7,6,5,4}, and n is 9, K is {6 };

or,

if the second preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 21, the PUSCH scheduling timing is shown in the upper two rows of fig. 21, and when n is 0, 5, and n is 9, L is {4,5,6}, when n is 1, and n is 6, L is {5,6,7}, when n is 0, K is {6,5}, when n is 1, and n is 6, K is {5,4}, and when n is 5, K is {7,6,5}, and when n is 9, K is {6 };

or,

if the third preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 22, the PUSCH scheduling timing is shown in the upper two rows of fig. 22, n is 0, n is 1, n is 5, n is 6, and n is 9, L is {4,5,6,7}, n is 0, n is 1, and n is 6, K is {4}, n is 5, K is {7,6,5,4}, and n is 9, K is {6,5,4 };

or,

if the above-described (fourth) preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 23, the PUSCH scheduling timing is shown in the upper two rows of fig. 23, and when n is 0 and n is 6, L is {5,6}, when n is 1, L is {6,7}, when n is 5 and n is 9, L is {4,5}, when n is 0 and n is 6, K is {6,5}, when n is 1, K is {5,4}, and when n is 5 and n is 9, K is {7,6 }.

When the number of ulidex bits of the scheduling instruction information carried by each downlink subframe or special subframe is not completely the same:

for TDD uplink and downlink configuration 0:

if the first or third preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 2, the PUSCH scheduling timing is shown in the middle two rows of fig. 2, and when n is 0 and n is 5, L is {4,5,6,7}, when n is 1 and n is 6, L is {7}, when n is 0 and n is 5, K is {7,6,5,4}, and when n is 1 and n is 6, K is {4 };

or,

if the second or fourth preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 3, the PUSCH scheduling timing is shown in the upper two rows of fig. 3, and when n is 0 and n is 5, L is {4,5,6}, when n is 1 and n is 6, L is {6,7}, when n is 0 and n is 5, K is 7,6,5}, and when n is 1 and n is 6, K is {5,4 };

for TDD uplink and downlink configuration 1:

if the first or third preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 4, the PUSCH scheduling timing is shown in the middle two rows of fig. 4, when n is 0 and n is 1, n is 5, and n is 6, L is {6}, when n is 4 and n is 9, L is {4,5,6}, when n is 0 and n is 1, n is 5, and n is 6, K is {4}, and when n is 4 and n is 9, K is {6,5,4 };

or,

if the second or fourth preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 5, the PUSCH scheduling timing is shown in the upper two rows of fig. 5, when n is 0 and n is 5, L is {5,6}, when n is 1 and n is 6, L is {6}, when n is 4 and n is 9, L is 4,5}, when n is 0 and n is 5, K is {5,4}, when n is 1 and n is 6, K is {4}, and when n is 4 and n is 9, K is {6,5 };

for TDD uplink and downlink configuration 2:

if the first or third preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 6, the PUSCH scheduling timing is shown in the two rows of fig. 6, where n is 0 and n is 4, n is 5, and n is 9, L is {6}, where n is 3 and n is 8, L is {4,5,6}, where n is 0 and n is 4, n is 5, and n is 9, K is {4}, and n is 3 and n is 8, K is {6,5,4 };

or,

if the second preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 7, the PUSCH scheduling timing is shown in the middle two rows of fig. 7, where n is 0 and n is 1 and n is 4 and n is 5 and n is 6 and n is 9, L is 5, n is 3 and n is 8, L is 4,5, n is 0 and n is 1 and n is 4 and n is 5 and n is 6 and n is 9, K is 5, and n is 3 and n is 8, K is 6, 5;

or,

if the above-mentioned (fourth) preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 8, the PUSCH scheduling timing is shown in the middle two rows of fig. 8, where n is 0 and n is 1 and n is 4 and n is 5 and n is 6 and n is 9, L is 5, n is 3 and n is 8, L is 4,5, n is 0 and n is 4 and n is 5 and n is 6 and n is 9, K is 4, and n is 3 and n is 8, K is 5, 4;

for TDD uplink and downlink configuration 3:

if the above-mentioned first preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 9, the PUSCH scheduling timing is shown in the middle two rows of fig. 9, and when n is 0, L is {5,6,7}, when n is 1, L is {7}, when n is 5, L is {4,5,6,7}, when n is 8 and n is 9, L is 5}, when n is 0, K is {6,5,4}, when n is 1, K is {4}, when n is 5, K is 7,6,5,4}, when n is 8 and n is 9, K is {6 };

or,

if the second preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 10, the PUSCH scheduling timing is shown in the upper two rows of fig. 10, and when n is 0, L is {5,6}, when n is 1, L is {6,7}, when n is 5, L is {4,5}, when n is 6 and n is 7, and when n is 8, and when n is 9, L is {5}, when n is 0, K is {6,5}, when n is 1, K is {5,4}, when n is 5, K is 7,6}, when n is 6 and n is 7, and when n is 8, and when n is 9, K is {6 };

or,

if the third preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 11, the PUSCH scheduling timing is shown in the middle two rows of fig. 11, where n is 0 and n is 1 and n is 6, and n is 7 and n is 8 and n is 9, L is 7, and n is 5, L is 4,5,6,7, n is 0 and n is 1 and n is 6, n is 7, n is 8 and n is 9, K is 4, and n is 5, K is 7,6,5, 4;

or,

if the above-described (fourth) preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 12, the PUSCH scheduling timing is shown in the middle two rows of fig. 12, and when n is 0, n is 1, n is 8, and n is 9, L is {7}, when n is 5, L is {4,5}, when n is 6, L is 5,6}, when n is 7, L is {6,7}, n is 0, n is 1, and n is 8, and n is 9, K is {4}, when n is 5, K is {7,6, when n is 6, K is 6,5}, and when n is 7, K is 5,4 };

for TDD uplink and downlink configuration 4:

if the above-mentioned first preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 13, the PUSCH scheduling timing is shown in the middle two rows of fig. 13, and when n is 0, n is 1, and n is 5, L is {6}, when n is 4, and n is 9, L is {4,5,6}, when n is 8, L is {4}, when n is 0, and n is 1, and n is 5, K is {4}, when n is 4, and n is 9, K is {6,5,4}, and when n is 8, K is {6 };

or,

if the second preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 14, the PUSCH scheduling timing is shown in the middle two rows of fig. 14, and when n is 0, L is {5,6}, when n is 1, L is {6}, when n is 4 and n is 5 and n is 6 and n is 7 and n is 8, L is 4,5}, when n is 0, K is {5,4}, when n is 1, K is 4, n is 4 and n is 6 and n is 7 and n is 8, K is {6, and when n is 9, K is 6}, and K is 6,5 };

or,

if the third preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 15, the PUSCH scheduling timing is shown in the middle two rows of fig. 15, and when n is 0 and n is 1 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, L is 6, and when n is 4, L is 4,5,6, n is 0 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, K is 4, and when n is 4, K is 6,5, 4;

or,

if the above-described (fourth) preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 16, the PUSCH scheduling timing is shown in the middle two rows of fig. 16, where n is 0, n is 1, n is 6, n is 7, n is 8, and n is 9, L is {6}, n is 4, L is {4,5}, n is 5, L is 5,6, n is 0, n is 1, n is 6, n is 7, n is 4, K is 6, and n is 5, K is {5,4 }.

For TDD uplink and downlink configuration 5:

if the above-mentioned first preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 17, the PUSCH scheduling timing is shown in the middle two rows of fig. 17, where n is 0 and n is 1, n is 4, n is 5, and n is 9, L is {4,5,6}, where n is 3, L is {5,6}, where n is 8, L is 4,5,6}, n is 0, n is 1, n is 4, n is 5, and n is 9, K is 4, n is 3, K is {5,4}, and n is 8, K is {6,5,4 };

or,

if the second preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 18, the PUSCH scheduling timing is shown in the middle two rows of fig. 18, and when n is 0, n is 1, and n is 9, L is 5, n is 3, n is 4, n is 5, n is 6, and n is 7, L is 4, n is 8, L is 4,5, n is 0, n is 1, and n is 9, K is 5, n is 3, n is 4, n is 5, n is 6, and n is 7, K is 6, and n is 8, K is 6, 5;

or,

if the third or fourth preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 19, the PUSCH scheduling timing is shown in the middle two rows of fig. 19, and when n is 0 and n is 1, n is 4, n is 5, n is 6, n is 7, n is 8, and n is 9, L is 5, when n is 3, L is 4,5, n is 0, n is 1, n is 4, n is 5, n is 6, n is 7, n is 8, and n is 9, K is 4, and when n is 3, K is 5, 4;

for TDD uplink and downlink configuration 6:

in the first preferred implementation, the PUSCH feedback timing is shown in the lower two rows of fig. 20, the PUSCH scheduling timing is shown in the middle two rows of fig. 20, and when n is 0, L is {5,6,7}, when n is 1 and n is 6, L is {7}, when n is 5, L is {4,5,6,7}, when n is 9, L is 5}, when n is 0, K is {6,5,4}, when n is 1 and n is 6, K is {4}, when n is 5, K is {7,6,5,4}, and when n is 9, K is {6 };

or,

if the second preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 21, the PUSCH scheduling timing is shown in the middle two rows of fig. 21, and when n is 0, L is {5,6}, when n is 1 and n is 6, L is {6,7}, when n is 5, L is {4,5,6}, when n is 9, L is {5}, when n is 0, K is {6,5}, when n is 1 and n is 6, K is {5,4}, when n is 5, K is 7,6,5}, and when n is 9, K is {6 };

or,

if the third preferred implementation is adopted, the PUSCH feedback timing is shown in the lower two rows of fig. 22, the PUSCH scheduling timing is shown in the middle two rows of fig. 22, and when n is 0, n is 1, and n is 6, L is {4}, when n is 5, L is {4,5,6,7}, when n is 9, L is 5,6,7}, n is 0, and n is 1, and n is 6, K is {4}, when n is 5, K is {7,6,5,4}, and when n is 9, K is {6,5,4 };

or,

In fig. 2 to 23, each cell represents one subframe, and the number below the cell represents a subframe number. For each PUSCH feedback timing diagram, the number in the grid indicates the feedback subframe number of the uplink subframe. For each PUSCH scheduling timing diagram, the number in the grid indicates the downlink subframe and/or special subframe number for performing PUSCH scheduling on the uplink subframe.

In fig. 2 to fig. 23, when the number of ulidex bits of the scheduling instruction information carried in each downlink subframe or special subframe is the same, the scheduling timing of the PUSCH is determined according to the above preferred scheduling manner, that is, starting from the FDD uplink subframe which is possibly scheduled earliest after n +3, the PUSCH transmitted by x consecutive FDD uplink subframes is scheduled by the downlink subframe or special subframe n. It should be noted that, if the PUSCH of the FDD uplink subframe n-k is fed back on the downlink subframe or the special subframe n indicated by the TDD uplink and downlink configuration, the FDD uplink subframe n + t is included after scheduling n +3 on the downlink subframe or the special subframe n_RTTPUSCH for k consecutive x FDD uplink subframe transmissions.

The invention also discloses a data transmission method at the UE side, which is implemented as shown in fig. 24, and specifically includes the following operations:

step 200, the UE determines TDD uplink and downlink configuration used by the eNB side for scheduling and feeding back the PUSCH of the FDD uplink carrier.

Specifically, the determination may be performed through the received higher layer signaling, or may be performed according to a predetermined agreement with the eNB side.

Step 210, the UE performs PUSCH transmission on the FDD uplink subframe according to the scheduling of the PUSCH of the FDD uplink carrier on the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration.

And after the UE side performs initial transmission on the PUSCH, the eNB side performs feedback on the corresponding PUSCH.

Step 220, the UE receives feedback on the PUSCH on the downlink subframe and/or the special subframe indicated by the TDD uplink/downlink configuration.

And step 230, the UE performs PUSCH retransmission processing according to the received PUSCH feedback information.

The specific implementation manner of step 230 may be: if the PUSCH feedback information is ACK information, retransmitting the corresponding PUSCH; and if the PUSCH feedback information is NACK information or retransmission scheduling signaling, retransmitting the corresponding PUSCH.

On the UE side, the timing for receiving feedback of the PUSCH is the same as on the eNB side. Specifically, reference may be made to the description of the eNB side, which is not described herein again.

In the present invention, the specific implementation manner of the step 210 may be: receiving the PUSCH scheduling instruction information on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration according to the time sequence for receiving the feedback of the PUSCH and the PUSCH maximum RTT; and carrying out PUSCH transmission on the FDD uplink subframe according to the received PUSCH scheduling instruction information.

And the time sequence of receiving the PUSCH feedback by the UE side is consistent with the PUSCH feedback time sequence of the eNB side. Therefore, the timing of receiving feedback on the PUSCH as described above refers to the PUSCH feedback timing that has been determined before step 200.

In the present invention, the step 210 can be further described as: and carrying out PUSCH transmission on the FDD uplink subframe n + L according to the scheduling of the PUSCH transmitted by the FDD uplink subframe n + L on the downlink subframe or the TDD special subframe n indicated by the TDD uplink and downlink configuration, wherein L belongs to L. The above step 210 can also be described as: and receiving feedback of PUSCH transmitted by the FDD uplink subframe n-K on the TDD downlink subframe or the special subframe n indicated by the TDD uplink and downlink configuration, wherein K belongs to K.

When the number of the ulidex bits of the scheduling instruction information carried by each downlink subframe or special subframe is the same or not completely the same, the specific values of L and K refer to the description of the eNB side, and are not described herein again.

The invention also discloses a data transmission device, the implementation structure of which is shown in fig. 25, and the specific implementation structure is as follows:

an uplink and downlink configuration determining module 1001, configured to determine TDD uplink and downlink configurations used for scheduling and feeding back a PUSCH of an FDD uplink carrier;

a PUSCH scheduling module 1002, configured to schedule a PUSCH of an FDD uplink carrier on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration;

a PUSCH receiving module 1003, configured to receive the PUSCH on an FDD uplink subframe;

a PUSCH feedback module 1004, configured to feedback the PUSCH on the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration.

The PUSCH scheduling module 1002 may specifically include: a PUSCH scheduling configuration submodule, configured to configure scheduling instruction information for the PUSCH on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration according to a feedback timing for feeding back a PUSCH of an FDD uplink carrier and a PUSCH maximum round trip time RTT; and the PUSCH scheduling and sending submodule is used for transmitting the scheduling instruction information on the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration.

Fig. 25 may be an eNB or an apparatus provided in an eNB. The signal processing relationship and specific operation manner between each module and each sub-module may refer to the description of the eNB side method, and are not described herein again.

The invention also discloses a data transmission device, the implementation structure of which is shown in fig. 26, and the specific implementation structure is as follows:

an uplink and downlink configuration determining module 2001, configured to determine TDD uplink and downlink configurations used for scheduling and feeding back a PUSCH of an FDD uplink carrier;

a PUSCH scheduling response module 2002, configured to perform PUSCH transmission on an FDD uplink subframe according to scheduling of a PUSCH of an FDD uplink carrier on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration;

a PUSCH feedback receiving module 2003, configured to receive feedback on the PUSCH on the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration;

and a PUSCH retransmission processing module 2004, configured to perform PUSCH retransmission processing according to the received PUSCH feedback information.

The PUSCH scheduling response module 2002 may specifically include: a PUSCH scheduling receiving submodule, configured to receive scheduling instruction information for the PUSCH on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration according to a timing for receiving feedback to the PUSCH and a PUSCH maximum RTT; and the PUSCH transmission submodule is used for carrying out PUSCH transmission on the FDD uplink subframe according to the received PUSCH scheduling instruction information.

Fig. 26 may be a UE or an apparatus provided on the UE. The signal processing relationship and specific working mode between each module and sub-module may refer to the description of the UE side method, which is not described herein again.

The data transmission method and apparatus provided by the embodiments of the present invention are suitable for a scenario in which when a TDD carrier and an FDD uplink carrier are aggregated and the TDD carrier performs cross-carrier scheduling on the FDD carrier, scheduling and feedback are performed on a PUSCH of the FDD uplink carrier; the method is also suitable for the scene that the PUSCH of the FDD uplink carrier is scheduled and fed back by the FDD downlink carrier.

The data transmission method and device provided by the embodiments of the present invention follow the following principles:

any uplink subframe on the FDD carrier corresponds to the only feedback subframe;

a feedback subframe corresponding to any uplink subframe m on the FDD carrier is a downlink subframe or a special subframe behind the subframe m +3 in the TDD uplink and downlink configuration;

and any uplink subframes m and m '(m' > m) on the FDD carrier respectively correspond to the feedback subframes n and n ', and n' is more than or equal to n.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims

1. A method of data transmission, comprising:

determining the uplink and downlink configuration of Time Division Duplex (TDD) used for scheduling and feeding back a Physical Uplink Shared Channel (PUSCH) of a Frequency Division Duplex (FDD) uplink carrier;

receiving the PUSCH on an FDD uplink subframe;

2. The method of claim 1, wherein feeding back the PUSCH on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration comprises:

if the number of the FDD uplink subframe for transmitting the PUSCH is the same as the number of the uplink subframe indicated by the TDD uplink and downlink configuration, feeding back according to the feedback time sequence of a PUSCH hybrid automatic repeat request (HARQ) corresponding to the TDD uplink and downlink configuration;

and if the number of the FDD uplink subframe m for transmitting the PUSCH is the same as the number of the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration, feeding back the PUSCH on the downlink subframe or the special subframe indicated by the TDD uplink and downlink configuration which is the first subframe after m +3 and meets the preset condition, wherein the preset condition is as follows: and for any two FDD uplink subframes, the PUSCH feedback time corresponding to the FDD uplink subframe with the later time sequence is not earlier than the PUSCH feedback time corresponding to the FDD uplink subframe with the earlier time sequence.

3. The method of claim 1, wherein feeding back the PUSCH on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration comprises:

and if the number of the FDD uplink subframe m for transmitting the PUSCH is the same as the number of the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration, feeding back the PUSCH on the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration after m +3 and meeting the preset conditions according to a preset equalization principle, wherein the equalization principle aims to ensure that the difference between the number of the FDD uplink subframes corresponding to the downlink subframes or the special subframes for feeding back the PUSCH is not more than 1, and the preset conditions are as follows: and for any two FDD uplink subframes, the PUSCH feedback time corresponding to the FDD uplink subframe with the later time sequence is not earlier than the PUSCH feedback time corresponding to the FDD uplink subframe with the earlier time sequence.

4. The method of claim 1, wherein feeding back the PUSCH on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration comprises:

and for the PUSCH transmitted in the FDD uplink subframe m, feeding back on a downlink subframe or a special subframe indicated by the first TDD uplink and downlink configuration after m + 3.

5. The method of claim 1, wherein feeding back the PUSCH on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration comprises:

for a PUSCH transmitted in an FDD uplink subframe m, feedback is performed on a downlink subframe and/or a special subframe, which is indicated by TDD uplink and downlink configuration and meets a predetermined condition, after m +3 according to a predetermined equalization principle, where the equalization principle is to make a difference between the number of the downlink subframes or the FDD uplink subframes corresponding to the special subframe, which are used for feeding back the PUSCH, not greater than 1, and the predetermined condition is: and for any two FDD uplink subframes, the PUSCH feedback time corresponding to the FDD uplink subframe with the later time sequence is not earlier than the PUSCH feedback time corresponding to the FDD uplink subframe with the earlier time sequence.

6. The method according to any one of claims 1 to 5, wherein scheduling PUSCH of FDD uplink carrier on downlink subframe and/or special subframe indicated by the TDD uplink and downlink configuration comprises:

according to a feedback time sequence for feeding back a PUSCH of an FDD uplink carrier and a PUSCH maximum round trip time RTT, configuring scheduling instruction information of the PUSCH on a downlink subframe and/or a special subframe indicated by TDD uplink and downlink configuration;

and transmitting the scheduling instruction information on the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration.

7. The method of claim 6, wherein:

if the uplink index ULindex bit number of the scheduling instruction information carried by each downlink subframe or special subframe is the same, the ULindex bit number is the maximum value of the corresponding FDD uplink subframe number when the downlink subframe and/or special subframe feeds back PUSCH;

or,

if the number of the ulidex bits of the scheduling instruction information carried by each downlink subframe or special subframe is not completely the same, the number of the ulidex bits of the scheduling instruction information carried by each downlink subframe or special subframe is the corresponding number of the FDD uplink subframes when the downlink subframe or special subframe feeds back the PUSCH.

8. The method according to claim 1, wherein the scheduling of the PUSCH of the FDD uplink carrier on the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration and the feedback of the PUSCH on the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration comprise:

scheduling a PUSCH transmitted by an FDD uplink subframe n + L on a downlink subframe or a special subframe n indicated by the TDD uplink and downlink configuration, wherein L belongs to L;

and feeding back the PUSCH transmitted by the FDD uplink subframe n-K on the downlink subframe or the special subframe n indicated by the TDD uplink and downlink configuration, wherein the K belongs to the K, and the time sequence of the downlink subframe or the special subframe n for scheduling the PUSCH transmitted by the FDD uplink subframe is earlier than that of the downlink subframe or the special subframe n for feeding back, wherein:

for TDD uplink and downlink configuration 0, when n is 0 and n is 1 and n is 5 and n is 6, L is {4,5,6,7}, when n is 0 and n is 5, K is {7,6,5,4}, when n is 1 and n is 6, K is {4 }; or, when n is 0 and n is 5, L is {4,5,6}, when n is 1 and n is 6, L is {5,6,7}, when n is 0 and n is 5, K is {7,6,5}, when n is 1 and n is 6, K is {5,4 };

or,

for TDD uplink and downlink configuration 1, when n is 0 and n is 1, n is 4, n is 5, n is 6, and n is 9, L is 4,5,6, n is 0, n is 1, n is 5, and n is 6, K is 4, n is 4, and n is 9, K is 6,5, 4; or, when n is 0 and n is 1, n is 5, and n is 6, L is {5,6}, when n is 4 and n is 9, L is {4,5}, when n is 0 and n is 5, K is {5,4}, when n is 1 and n is 6, K is {4}, when n is 4 and n is 9, K is {6,5 };

or,

for TDD uplink and downlink configuration 2, when n is 0 and n is 3 and n is 4 and n is 5 and n is 8 and n is 9, L is 4,5,6, n is 0 and n is 4 and n is 5 and n is 9, K is 4, n is 3 and n is 8, K is 6,5, 4; or, when n is 0 and n is 1 and n is 3 and n is 4 and n is 5 and n is 6 and n is 8 and n is 9, L is 4,5, n is 0 and n is 1 and n is 4 and n is 5 and n is 6 and n is 9, K is 5, and n is 3 and n is 8, K is 6, 5; or, when n is 0 and n is 1 and n is 3 and n is 4 and n is 5 and n is 6 and n is 8 and n is 9, L is 4,5, n is 0 and n is 1 and n is 4 and n is 5 and n is 6 and n is 9, K is 4, n is 3 and n is 8, K is 5, 4;

or,

for TDD uplink and downlink configuration 3, when n is 0 and n is 1 and n is 5 and n is 8 and n is 9, L is 4,5,6,7, when n is 0, K is 6,5,4, when n is 1, K is 4, when n is 5, K is 7, 5,4, when n is 9, K is 6, 4, when n is 9, K is 6; or, when n is 0, L is {5,6}, when n is 1, L is {6,7}, when n is 5 and n is 6, and n is 7, and n is 8, and n is 9, L is {4,5}, when n is 0, K is {6,5}, when n is 1, K is 5, and when n is 5, K is {7,6}, when n is 6 and n is 8, and n is 9, K is {6 }; or, when n is 0 and n is 1 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, L is 4,5,6,7, n is 0 and n is 1 and n is 6 and n is 7 and n is 8 and n is 9, K is 4, and n is 5, K is 7,6, 4; or, when n is 0, n is 1, n is 7, n is 8, and n is 9, L is 6,7, when n is 5, L is 4,5, when n is 6, L is 5,6, n is 0, n is 1, n is 8, n is 9, K is 4, when n is 5, K is 7,6, when n is 6, K is 6, and n is 7, 4;

or,

for TDD uplink and downlink configuration 4, where n is 0 and n is 1 and n is 4 and n is 5 and n is 8 and n is 9, L is 4,5,6, n is 0 and n is 1 and n is 5, K is 4, n is 9, K is 6, n is 8, K is 6; or, when n is 0 and n is 1, L is 5,6, n is 4 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, L is {4,5}, when n is 0, K is {5,4}, when n is 1, K is 4 and n is 5 and n is 6 and n is 7 and n is 8, K is 6 {6}, when n is 9, K is 6 }; or, when n is 0 and n is 1 and n is 4 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, L is 4,5,6, n is 0 and n is 1 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, K is 4, and K is 6,5, 4; or, when n is 0 and n is 1 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, L is 5,6, when n is 4, L is 4,5, when n is 0 and n is 1 and n is 6 and n is 7 and n is 8 and n is 9, K is 4, when n is 4, K is 6,5, when n is 4, K is 5;

or,

for TDD uplink and downlink configuration 5, where n is 0 and n is 1 and n is 3 and n is 4 and n is 5 and n is 8 and n is 9, L is {4,5,6}, n is 0 and n is 1 and n is 4 and n is 5 and n is 9, K is 4}, n is 3, K is {5,4}, and n is 8, K is {6,5,4 }; or, when n is 0 and n is 1 and n is 3 and n is 4 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, L is {4,5}, n is 0 and n is 1 and n is 9, K is 5, n is 3 and n is 4 and n is 5 and n is 6 and n is 7, K is {6}, and n is 8, K is 6 and n is 7; or, when n is 0 and n is 1 and n is 3 and n is 4 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, L is {4,5}, n is 0 and n is 1 and n is 4 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, K is {4}, and n is 3 and K is {5,4 };

or,

for TDD uplink and downlink configuration 6, when n is 0 and n is 1 and n is 5 and n is 6 and n is 9, L is 4,5,6,7, when n is 0, K is 6,5,4, when n is 1 and n is 6, K is 4, when n is 5, K is 7,6,5,4, when n is 9, K is 6; or, when n is 0, 5, and n is 9, L is 4,5,6, when n is 1, and n is 6, L is 5,6,7, n is 0, K is 6,5, n is 1, and n is 6, K is 5, when n is 1, and n is 6, K is 7,6,5, when n is 5, and K is 9, K is 6; or, when n is 0 and n is 1 and n is 5 and n is 6 and n is 9, L is 4,5,6,7, when n is 0 and n is 1 and n is 6, K is 4, when n is 5, K is 7, 5,4, when n is 9, K is 6,5, 4; alternatively, when n is 0 and n is 6, L is {5,6}, when n is 1, L is {6,7}, when n is 5 and n is 9, L is {4,5}, when n is 0 and n is 6, K is {6,5}, when n is 1, K is {5,4}, when n is 5 and n is 9, K is {7,6 }.

9. The method according to claim 1, wherein scheduling a PUSCH of an FDD uplink carrier on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration, and feeding back the PUSCH on the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration comprises:

for TDD uplink and downlink configuration 0, when n is 0 and n is 5, L is {4,5,6,7}, when n is 1 and n is 6, L is {7}, when n is 0 and n is 5, K is {7,6,5,4}, when n is 1 and n is 6, K is {4 }; or, when n is 0 and n is 5, L is {4,5,6}, when n is 1 and n is 6, L is {6,7}, when n is 0 and n is 5, K is {7,6,5}, when n is 1 and n is 6, K is {5,4 };

or,

1 is configured for TDD uplink and downlink, where n is 0 and n is 1 and n is 5 and n is 6, L is 6, n is 4 and n is 9, L is 4,5,6, n is 0 and n is 1 and n is 5 and n is 6, K is 4, n is 9, K is 6, 4; or, when n is 0 and n is 5, L is {5,6}, when n is 1 and n is 6, L is 6, when n is 4 and n is 9, L is {4,5}, when n is 0 and n is 5, K is {5,4}, when n is 1 and n is 6, K is {4}, when n is 4 and n is 9, K is {6,5 };

or,

for TDD uplink and downlink configuration 2, when n is 0 and n is 4 and n is 5 and n is 9, L is 6, n is 3 and n is 8, L is 4,5,6, n is 0 and n is 4 and n is 5 and n is 9, K is 4, n is 3, n is 8, K is 6,5, 4; or, when n is 0 and n is 1 and n is 4 and n is 5 and n is 6 and n is 9, L is 5, n is 3 and n is 8, L is 4,5, n is 0 and n is 1 and n is 4 and n is 5 and n is 9, K is 5, n is 3 and n is 8, K is 6, 5; or, when n is 0 and n is 1 and n is 4 and n is 5 and n is 6 and n is 9, L is 5, n is 3 and n is 8, L is 4,5, n is 0 and n is 1 and n is 4 and n is 5 and n is 9, K is 4, n is 3 and n is 8, K is 5, 4;

or,

for TDD uplink and downlink configuration 3, when n is 0, L is {5,6,7}, when n is 1, L is {7}, when n is 5, L is {4,5,6,7}, when n is 8 and n is 9, L is {5}, when n is 0, K is {6,5,4}, when n is 1, K is {4}, when n is 5, K is {7,6,5,4}, when n is 8 and n is 9, K is {6,5,4 }; or, when n is 0, L is {5,6}, when n is 1, L is {6,7}, when n is 5, L is {4,5}, when n is 6, n is 7, n is 8, and when n is 9, L is {5}, when n is 0, K is {6,5}, when n is 1, K is {5,4}, when n is 5, K is {7,6}, when n is 6, and when n is 7, 8, and when n is 9, K is {6 }; or, when n is 0 and n is 1 and n is 6 and n is 7 and n is 8 and n is 9, L is 7, n is 0 and n is 6 and n is 8 and n is 9, L is 4,5,6,7, n is 0 and n is 1 and n is 6 and n is 7 and n is 8 and n is 9, K is 4, n is 5, K is 7,6, 4; or, when n is 0, n is 1, n is 8, and n is 9, L is 7, when n is 5, L is 4,5, when n is 6, L is 5,6, when n is 7, L is 6,7, when n is 0, n is 1, n is 8, and n is 9, K is 4, when n is 5, K is 7,6, when n is 6, K is 6, when n is 6, K is 6,5, when n is 7, K is 5, when K is 5;

or,

for TDD uplink and downlink configuration 4, when n is 0, n is 1, and n is 5, L is 6, when n is 4, and n is 9, L is 4,5,6, when n is 8, L is 4, n is 0, n is 1, and n is 5, K is 4, n is 9, K is 6, 4, and when n is 8, K is 6,5,4, and when n is 8, K is 6; or, when n is 0, L is {5,6}, when n is 1, L is {6}, when n is 4 and n is 5, and n is 6, when n is 7, and when n is 8, L is {4}, when n is 9, L is {4,5}, when n is 0, K is 5,4}, when n is 1, K is 4, when n is 4, and n is 5, and when n is 6 and n is 8, K is 6, when n is 9, K is 6, and when n is 8, K is 6,5 }; or, when n is 0 and n is 1 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, L is 6, n is 4, L is 4,5,6, n is 0 and n is 1 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, K is 4, n is 6, n is 4, n is 6 and n is 4; or, when n is 0 and n is 1 and n is 6 and n is 7 and n is 8 and n is 9, L is 6, when n is 4, L is 4,5, when n is 5, L is 5,6, n is 0 and n is 6 and n is 7 and n is 8 and n is 9, K is 4, when n is 4, K is 6, when n is 4, K is 5, and n is 5, when n is 5, K is 5, 4;

or,

for TDD uplink and downlink configuration 5, where n is 0 and n is 1 and n is 4 and n is 5 and n is 9, where L is 4,5,6, n is 3, L is 5,6, n is 8, L is 4,5,6, n is 0 and n is 1 and n is 4 and n is 9, K is 4, n is 3, K is 5,4, K is 3, K is 5,4, and n is 8; or, when n is 0 and n is 1 and n is 9, L is 5, n is 3 and n is 4 and n is 5, n is 6 and n is 7, L is 4, n is 8, L is 4,5, n is 0 and n is 1 and n is 9, K is 5, n is 3 and n is 4 and n is 5, n is 6 and n is 7, K is 6 and n is 5, K is 6 and n is 7, K is 6 and 5; or, when n is 0 and n is 1 and n is 4 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, L is 5, when n is 3, L is 4,5, n is 0 and n is 1 and n is 4 and n is 5 and n is 6 and n is 7 and n is 8 and n is 9, K is 4, and n is 3, K is 5;

or,

in TDD uplink and downlink configuration 6, when n is 0, L is {5,6,7}, when n is 1 and n is 6, L is {7}, when n is 5, L is {4,5,6,7}, when n is 9, L is {5}, when n is 0, K is {6,5,4}, when n is 1 and n is 6, K is {4}, when n is 5, K is {7,6,5,4}, and when n is 9, K is {6 }; or, when n is 0, L is {5,6}, when n is 1 and n is 6, L is {6,7}, when n is 5, L is {4,5,6}, when n is 9, L is {5}, when n is 0, K is {6,5}, when n is 1 and n is 6, K is 5,4}, when n is 5, K is {7,6,5}, when n is 9, K is {6, 6 }; or, when n is 0 and n is 1 and n is 6, L is {4}, when n is 5, L is {4,5,6,7}, when n is 9, L is {5,6,7}, when n is 0 and n is 1 and n is 6, K is {4}, when n is 5, K is 7,6,5,4}, when n is 9, K is {6,5,4 }; alternatively, when n is 0 and n is 6, L is {5,6}, when n is 1, L is {6,7}, when n is 5 and n is 9, L is {4,5}, when n is 0 and n is 6, K is {6,5}, when n is 1, K is {5,4}, when n is 5 and n is 9, K is {7,6 }.

10. A method of data transmission, comprising:

11. The method of claim 10, wherein receiving feedback on the PUSCH on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration comprises:

if the number of the FDD uplink subframe for transmitting the PUSCH is the same as the number of the uplink subframe indicated by the TDD uplink and downlink configuration, receiving feedback to the PUSCH according to the feedback time sequence of the PUSCHHHARQ corresponding to the TDD uplink and downlink configuration;

and if the number of an FDD uplink subframe m for transmitting the PUSCH is the same as the number of a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration, receiving feedback on the PUSCH on a first downlink subframe or special subframe, which meets a preset condition, of the TDD uplink and downlink configuration indication after m +3, wherein the preset condition is as follows: and for any two FDD uplink subframes, the PUSCH feedback time corresponding to the FDD uplink subframe with the later time sequence is not earlier than the PUSCH feedback time corresponding to the FDD uplink subframe with the earlier time sequence.

12. The method of claim 10, wherein receiving feedback on the PUSCH on a downlink subframe and/or a special subframe of a TDD carrier indicated by the TDD uplink and downlink configuration comprises:

if the number of the FDD uplink subframe for transmitting the PUSCH is the same as the number of the uplink subframe indicated by the TDD uplink and downlink configuration, receiving feedback on the PUSCH according to the feedback time sequence of the PUSCHHHARQ corresponding to the TDD uplink and downlink configuration;

and if the number of the FDD uplink subframe m for transmitting the PUSCH is the same as the number of the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration, receiving feedback on the PUSCH on the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration after m +3 and meeting the preset condition according to a preset equalization principle, wherein the equalization principle aims to ensure that the difference between the number of the FDD uplink subframes corresponding to the downlink subframes or the special subframes for feeding back the PUSCH is not more than 1, and the preset condition is that: and for any two FDD uplink subframes, the PUSCH feedback time corresponding to the FDD uplink subframe with the later time sequence is not earlier than the PUSCH feedback time corresponding to the FDD uplink subframe with the earlier time sequence.

13. The method of claim 10, wherein receiving feedback on the PUSCH on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration comprises:

and for the PUSCH transmitted in the FDD uplink subframe m, receiving feedback on the PUSCH on a downlink subframe or a special subframe indicated by the first TDD uplink and downlink configuration after m + 3.

14. The method of claim 10, wherein receiving feedback on the PUSCH on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration comprises:

for a PUSCH transmitted in an FDD uplink subframe m, receiving feedback on the PUSCH on a downlink subframe and/or a special subframe, which are/is after m +3 and meet a predetermined condition, of a TDD uplink-downlink configuration indication according to a predetermined equalization principle, where the equalization principle is to make a difference between the number of downlink subframes or FDD uplink subframes corresponding to each downlink subframe or special subframe for feeding back the PUSCH not greater than 1, where the predetermined condition is: and for any two FDD uplink subframes, the PUSCH feedback time corresponding to the FDD uplink subframe with the later time sequence is not earlier than the PUSCH feedback time corresponding to the FDD uplink subframe with the earlier time sequence.

15. The method according to any one of claims 10 to 14, wherein scheduling PUSCH of an FDD uplink carrier on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration, and performing PUSCH transmission on an FDD uplink subframe, includes:

receiving scheduling instruction information of the PUSCH on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration according to a time sequence for receiving the feedback of the PUSCH and the PUSCH maximum RTT;

and carrying out PUSCH transmission on the FDD uplink subframe according to the received scheduling instruction information.

16. The method of claim 15, wherein:

or,

if the number of the ulidex bits of the scheduling instruction information carried by each downlink subframe or special subframe is not completely the same, the number of the ulidex bits of the scheduling instruction information carried by each downlink subframe or special subframe is the number of the corresponding FDD uplink subframes when the downlink subframe or special subframe feeds back the PUSCH.

17. The method according to claim 10, wherein scheduling PUSCH for FDD uplink carrier on downlink subframe and/or special subframe indicated by the TDD uplink/downlink configuration, performing PUSCH transmission on FDD uplink subframe, and receiving feedback for PUSCH on downlink subframe and/or special subframe indicated by the TDD uplink/downlink configuration comprises:

scheduling the PUSCH transmitted by the FDD uplink subframe n + L on the TDD uplink subframe n according to the downlink subframe or the TDD special subframe n indicated by the TDD uplink and downlink configuration, and transmitting the PUSCH on the FDD uplink subframe n + L, wherein L belongs to L;

and receiving feedback of PUSCH transmitted by an FDD uplink subframe n-K on a TDD downlink subframe or a special subframe n indicated by the TDD uplink and downlink configuration, wherein K belongs to K, and the time sequence of the downlink subframe or the special subframe n for scheduling the PUSCH transmitted by the FDD uplink subframe is earlier than that of the downlink subframe or the special subframe n for feedback, wherein:

or,

18. The method according to claim 10, wherein scheduling PUSCH for FDD uplink carrier on downlink subframe and/or special subframe indicated by the TDD uplink/downlink configuration, performing PUSCH transmission on FDD uplink subframe, and receiving feedback for PUSCH on downlink subframe and/or special subframe indicated by the TDD uplink/downlink configuration comprises:

and receiving feedback of PUSCH transmitted by FDD uplink subframe n-K on TDD downlink subframe or special subframe n' indicated by TDD uplink and downlink configuration, wherein K belongs to K, and the time sequence of downlink subframe or special subframe n for scheduling PUSCH transmitted by FDD uplink subframe is earlier than that of downlink subframe or special subframe n for feedback,

or,

for TDD uplink and downlink configuration 2, when n is 0 and n is 4 and n is 5 and n is 9, L is 6, n is 3 and n is 8, L is 4,5,6, n is 0 and n is 4 and n is 5 and n is 9, K is 4, n is 3, n is 8, K is 6,5, 4; or, when n is 0 and n is 1 and n is 4 and n is 5 and n is 6 and n is 9, L is 5, n is 3 and n is 8, L is 4,5, n is 0 and n is 1 and n is 4 and n is 5 and n is 9, K is 5, n is 3 and n is 8, K is 6, 5; or, when n is 0 and n is 3 and n is 4 and n is 5 and n is 6 and n is 9, L is 5, n is 3 and n is 8, L is 4,5, n is 0 and n is 1 and n is 4 and n is 5 and n is 6 and n is 9, K is 4, n is 3 and n is 8, K is 5, 4;

or,

19. A data transmission apparatus, comprising:

20. The apparatus of claim 19, wherein the PUSCH feedback module is specifically configured to:

21. The apparatus of claim 19, wherein the PUSCH feedback module is specifically configured to:

22. The apparatus of claim 19, wherein the PUSCH feedback module is specifically configured to:

23. The apparatus of claim 19, wherein the PUSCH feedback module is specifically configured to:

24. The apparatus according to any of claims 19 to 23, wherein the PUSCH scheduling module specifically comprises:

a PUSCH scheduling configuration submodule, configured to configure scheduling instruction information for the PUSCH on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration according to a feedback timing for feeding back a PUSCH of an FDD uplink carrier and a PUSCH maximum round trip time RTT;

and the PUSCH scheduling and sending submodule is used for transmitting the scheduling instruction information on the downlink subframe and/or the special subframe indicated by the TDD uplink and downlink configuration.

25. The apparatus of claim 24, wherein:

or,

26. The apparatus of claim 19, wherein:

the PUSCH scheduling module is specifically used for scheduling the PUSCH transmitted by an FDD uplink subframe n + L on a downlink subframe or a special subframe n indicated by the TDD uplink and downlink configuration, wherein L belongs to L;

the PUSCH feedback module is specifically configured to perform feedback on a PUSCH transmitted by an FDD uplink subframe n-K on a downlink subframe or a special subframe n indicated by the TDD uplink and downlink configuration, where K belongs to K, and for a PUSCH transmitted by an FDD uplink subframe, a timing sequence of the downlink subframe or the special subframe n to be scheduled is earlier than a timing sequence of the downlink subframe or the special subframe n to be fed back, where:

or,

27. The apparatus of claim 19, wherein:

or,

28. A data transmission apparatus, comprising:

29. The apparatus of claim 28, wherein the PUSCH feedback receiving module is specifically configured to:

30. The apparatus of claim 28, wherein the PUSCH feedback receiving module is specifically configured to:

31. The apparatus of claim 28, wherein the PUSCH feedback receiving module is specifically configured to:

32. The apparatus of claim 28, wherein the PUSCH feedback receiving module is specifically configured to:

33. The apparatus according to any of claims 28-32, wherein the PUSCH scheduling response module specifically comprises:

a PUSCH scheduling receiving submodule, configured to receive scheduling instruction information for the PUSCH on a downlink subframe and/or a special subframe indicated by the TDD uplink and downlink configuration according to a timing sequence for receiving feedback for the PUSCH and a PUSCH maximum RTT;

and the PUSCH transmission submodule is used for carrying out PUSCH transmission on the FDD uplink subframe according to the received scheduling instruction information.

34. The apparatus of claim 33, wherein:

or,

35. The apparatus of claim 28, wherein:

the PUSCH scheduling response module is specifically used for carrying out PUSCH transmission on an FDD uplink subframe n + L according to the scheduling of the PUSCH transmitted by the FDD uplink subframe n + L on the downlink subframe or the TDD special subframe n indicated by the TDD uplink and downlink configuration, wherein L belongs to L;

the PUSCH feedback receiving module is specifically configured to receive, on a TDD downlink subframe or a special subframe n indicated by the TDD uplink and downlink configuration, feedback of a PUSCH transmitted by an FDD uplink subframe n-K, where K belongs to K, and for a PUSCH transmitted by an FDD uplink subframe, a timing sequence of a downlink subframe or a special subframe n for scheduling is earlier than a timing sequence of a downlink subframe or a special subframe n for feedback, where:

or,

36. The apparatus of claim 28, wherein:

the PUSCH feedback receiving module is specifically configured to receive, on a TDD downlink subframe or a special subframe n' indicated by the TDD uplink and downlink configuration, feedback of a PUSCH transmitted by an FDD uplink subframe n-K, where K belongs to K, and for a PUSCH transmitted by an FDD uplink subframe, a timing sequence of a downlink subframe or a special subframe n to be scheduled is earlier than a timing sequence of a downlink subframe or a special subframe n to be fed back,

or,