CN107528676B

CN107528676B - Method and equipment for transmitting feedback information of uplink transmission

Info

Publication number: CN107528676B
Application number: CN201610671985.XA
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: 2016-06-22
Filing date: 2016-08-15
Publication date: 2020-02-11
Anticipated expiration: 2036-08-15
Also published as: CN107528676A

Abstract

The invention discloses a method and a device for transmitting feedback information of uplink transmission, wherein the method comprises the following steps: a terminal sends a Physical Uplink Shared Channel (PUSCH) in a special subframe m, wherein m is an integer; the terminal detects a downlink control channel using a downlink control information DCI format in a subframe containing downlink transmission resources behind the special subframe m or in a subframe m + k, wherein k is a positive integer; and the terminal determines whether to retransmit the PUSCH sent in the special subframe m or not according to the downlink control channel. Therefore, a transmission scheme of the feedback information of the PUSCH transmitted in the special subframe is provided, and the PUSCH transmitted in the special subframe can normally obtain the ACK/NACK feedback information.

Description

Method and equipment for transmitting feedback information of uplink transmission

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method and a device for transmitting feedback information for uplink transmission.

Background

An existing Long Term Evolution (LTE) Time Division Duplex (TDD) system uses a frame structure (FS 2) as shown in fig. 1. In a TDD system, uplink and downlink transmissions use different subframes or different time slots on the same frequency. Each 10ms radio frame (radio frame) in FS2 is composed of two 5ms fields (half-frames), each containing 5 subframes (subframes) of 1ms length. Subframes in FS2 are divided into three categories: each special subframe comprises a Downlink transmission Time Slot (DwPTS), a Guard Period (GP) and an Uplink transmission Time Slot (UpPTS). Table 1 shows 7 uplink and downlink subframe configurations supported in FS 2.

Table 1: uplink and downlink configuration

The special subframe cutoff to version 13(Release 13, Rel-13) supports 10 configurations as shown in table 2, each configuration specifies the symbol lengths of DwPTS and UpPTS, and the length of GP can be obtained from the difference between the total number of symbols in one subframe and the symbol lengths of DwPTS and UpPTS.

TABLE 2 Special subframe configuration

In table 2, X is a value configured by higher layer signaling, and is used to additionally extend the UpPTS length, where X is currently supported by 2 or 4 symbols, which is equivalent to dividing GP into a part as UpPTS. The DwPTS may transmit a downlink pilot, downlink service data (such as a downlink shared channel), and a downlink control signaling (such as a downlink control channel), the GP does not transmit any signal, the UpPTS only transmits a random access and Sounding Reference signal (SRS for short), and cannot transmit uplink service (such as an uplink shared channel) or uplink control information (such as an uplink control channel).

In the existing LTE TDD system, a Physical Uplink Shared Channel (PUSCH) is only transmitted in an Uplink subframe, and ACK/NACK feedback Information thereof may be carried in a Physical Hybrid-ARQ Indicator Channel (PHICH, HARQ), and transmitted, or may be obtained through a Downlink Control Channel (i.e., a DCI in Uplink Control Information (DCI)) carrying an Uplink scheduling grant (UL grant), where the Downlink Control Channel includes a New Data Indicator field (NDI), and indicates whether the Downlink Control Channel is New Data or not by whether the NDI is inverted or not.

The terminal transmits PUSCH in the uplink subframe with the number of n, and the PUSCH is numbered as n + k _PHICHReceives the PHICH in the downlink subframe to obtain the ACK/NACK feedback information of the PUSCH, wherein k is _PHICHThe definitions of (A) are shown in Table 3.

TABLE 3K in TDD _PHICH(k _PHICHfor TDD)

The subframe numbers in table 3 are in units of radio frames, and the subframe number is n + k, and if n + k is greater than 9, it indicates a subframe in the next radio frame, and the following table is similar.

PHICH resource routing of a terminal in a subframe for detecting PHICH

To determine that the user has taken a particular task,

for the numbering of the PHICH group,

the orthogonal sequences within a group are numbered,

and can be determined according to the following formula:

wherein: n is _DMRSA value obtained according to demodulation reference Signal (DMRS) cyclic shift information indicated in the scheduling information of the corresponding PUSCH is as shown in table 4;

is the length of the orthogonal sequence; determining the number of PHICH groups in each subframe according to the configuration of high-layer signaling, wherein one PHICH group comprises a plurality of PHICHs which are respectively used for bearing non-PHICHAnd ACK/NACK feedback information of PUSCH, the PHICHs occupy the same resource transmission and are distinguished from each other by orthogonal sequences, and the number of PHICH groups actually contained in each subframe of TDD is Wherein m is _iFor the pre-determined coefficient corresponding to the TDD subframe numbered i, m is the predetermined coefficient corresponding to different TDD subframes in different TDD uplink and downlink configurations _iCan be 0, 1, 2, as shown in Table 5, when m _iWhen the value is 0, the PHICH resource is not packaged in the subframe; i is _{PRB_RA}A value determined according to a Physical Resource Block (PRB) index (index) of a PUSCH corresponding to the PHICH; i is _PHICHConfiguring relevant values for TDD uplink and downlink appointed by the standard, and when the TDD uplink and downlink configuration is 0 or the uplink reference TDD uplink and downlink configuration is 0, n is 4 or 9, I _PHICHOther cases I ═ 1 _PHICHAnd the value is 0, and is used for distinguishing the corresponding relation between the PHICH resource and the PUSCH in the subframe when the feedback information of the PUSCH in the two subframes is correspondingly transmitted through the PHICH in the same subframe.

Table 4:

indication field and n for indicating DMRS cyclic shift in PDCCH/EPDCCH using uplink DCI format _DMRSCorresponding relation of (Mapping between n) _DMRSand the cyclic shift for DMRS field in PDCCH/EPDCCHwithuplink DCI format)

TABLE 5 factor m in FS2 _i

For carriers which are configured to be 1-6 in TDD uplink and downlink or configured to be 1-6 in TDD uplink and downlink by using uplink reference, ACK/NACK feedback information carried by a PHICH received in a downlink subframe with the number of n corresponds to a PUSCH transmitted in a subframe n-k, wherein the definition of k is shown in a table 6; for TDD uplink and downlink allocationsSetting 0 or configuring the uplink reference to be a carrier of TDD uplink and downlink configuration 0, and receiving corresponding I in a downlink subframe with the number of n _PHICHACK/NACK feedback information carried by PHICH 0 corresponds to PUSCH transmitted in subframe n-k, corresponding I received in downlink subframe numbered n _PHICHThe ACK/NACK feedback information carried by the PHICH of 1 corresponds to the PUSCH transmitted in subframe n-6.

TABLE 6K in TDD configurations 0-6

In addition, the terminal needs to detect a downlink control channel carrying a UL grant, i.e., a downlink control channel using an uplink DCI format, in the subframe for detecting the PHICH. If the downlink control channel is detected, determining whether the downlink control channel is used for scheduling new data transmission or scheduling a previous PUSCH for retransmission according to whether the NDI indication field in the downlink control channel is inverted, for example, when the PUSCH is transmitted for the first time, the NDI in the corresponding downlink control channel is 0, if the downlink control channel with the NDI of 0 is received in a PHICH detection subframe after the PUSCH, that is, the NDI is not inverted, that is, the downlink control channel is used for scheduling the PUSCH for retransmission; if the PHICH and the downlink control channel are detected in one PHICH detection subframe at the same time, the information of the downlink control channel is used as the standard, namely whether retransmission is performed is determined according to the NDI of the downlink control channel, if retransmission is performed, the PUSCH is retransmitted according to scheduling information indicated by the downlink control channel, and if only the PHICH is received and the PHICH indicates NACK, the PUSCH is used for retransmission with the same configuration of first transmission.

With the development and change of the mobile communication service requirement, in order to realize uplink transmission in the TDD special subframe, it is proposed to define a new TDD special subframe configuration, such as 6-symbol DwPTS, 2-symbol GP, and 6-symbol UpPTS; in the new special subframe, the length of the UpPTS is increased, so that the terminal can perform uplink transmission in the UpPTS. However, there is no solution at present how to transmit the ACK/NACK feedback information of the uplink shared channel transmitted in the UpPTS.

Disclosure of Invention

The embodiment of the invention provides a method and equipment for transmitting feedback information of uplink transmission, which solve the problem that no solution exists at present how to transmit ACK/NACK feedback information of an uplink shared channel transmitted in UpPTS.

In a first aspect, a method for receiving feedback information of uplink transmission includes:

a terminal sends a Physical Uplink Shared Channel (PUSCH) in a special subframe m, wherein m is an integer;

the terminal detects a downlink control channel using a downlink control information DCI format in a subframe containing downlink transmission resources behind the special subframe m or in a subframe m + k, wherein k is a positive integer;

and the terminal determines whether to retransmit the PUSCH sent in the special subframe m or not according to the downlink control channel.

In one possible embodiment, k is defined as follows:

for a Time Division Duplex (TDD) uplink and downlink configuration 0, if m is 1 or 6, k is 4, 5, 9 or 10; or

For TDD uplink and downlink configuration 1, if m is 1 or 6, k is 3, 5, 8 or 10; or

For TDD uplink and downlink configuration 2, if m is 1 or 6, k is 2 or 7; or

For TDD uplink and downlink configuration 3, if m is 1, k is 7, 8 or 9; or

For TDD uplink and downlink configuration 4, if m is 1, k is 7 or 8; or

For TDD uplink and downlink configuration 5, if m is 1, k is 7; or

For TDD uplink and downlink configuration 6, if m is 1, k is 4, 5, 8, 9, or 10; or

For TDD uplink and downlink configuration 6, if m is 6, k is 3, 4, 5, 9, or 10.

Based on any of the above embodiments, the determining, by the terminal, whether to retransmit the PUSCH transmitted in the special subframe m according to the downlink control channel includes:

the terminal determines whether the downlink control channel corresponds to a PUSCH (physical uplink shared channel) sent in a special subframe or not according to the downlink control channel;

and after determining the PUSCH sent in the special subframe corresponding to the downlink control channel, the terminal determines whether to retransmit the PUSCH sent in the special subframe m according to an indication domain carried by the downlink control channel and used for indicating whether to retransmit.

In a possible implementation manner, the determining, by the terminal according to the downlink control channel, whether the downlink control channel corresponds to a PUSCH transmitted in a special subframe includes:

the terminal determines whether the downlink control channel corresponds to a PUSCH (physical uplink shared channel) sent in a special subframe or not according to the size of the uplink DCI format used by the downlink control channel; and/or

The terminal determines whether the downlink control channel corresponds to a PUSCH (physical uplink shared channel) sent in a special subframe or not according to a first indication domain in the downlink control channel, wherein the first indication domain is used for indicating the relevant information of the PUSCH corresponding to the downlink control channel; and/or

The terminal determines whether the downlink control channel corresponds to a PUSCH sent in a special subframe or not according to a second indication domain in the downlink control channel, wherein the second indication domain is used for indicating that the PUSCH corresponding to the downlink control channel is a PUSCH in the special subframe or a PUSCH in a common subframe; and/or

The terminal determines whether the downlink control channel corresponds to a PUSCH (physical uplink shared channel) sent in a special subframe or not according to a Radio Network Temporary Identifier (RNTI) used when the downlink control channel is scrambled; and/or

And the terminal determines whether the downlink control channel corresponds to the PUSCH sent in the special subframe or not according to the 2-bit uplink index UL index indication domain in the downlink control channel.

In a possible implementation manner, the determining, by the terminal, whether the downlink control channel corresponds to a PUSCH transmitted in a special subframe according to the size of the uplink DCI format used by the downlink control channel includes:

if the terminal detects that the downlink control channel uses the uplink DCI format with the first DCI size, the terminal determines the PUSCH sent in the special subframe corresponding to the downlink control channel; or

If the terminal detects that the downlink control channel uses an uplink DCI format with a second DCI size, the terminal determines a PUSCH (physical uplink shared channel) sent in a common subframe corresponding to the downlink control channel;

wherein the first DCI size and the second DCI size are different.

In a possible implementation manner, the first indication field carries a hybrid automatic repeat request HARQ process number of a PUSCH corresponding to the downlink control channel.

In a possible implementation manner, the determining, by the terminal, whether the downlink control channel corresponds to a PUSCH transmitted in a special subframe according to an RNTI used when the downlink control channel is scrambled includes:

if the terminal detects that the downlink control channel is scrambled by using the first RNTI, the terminal determines a PUSCH (physical uplink shared channel) sent in a special subframe corresponding to the downlink control channel; or

If the terminal detects that the downlink control channel is scrambled by using a second RNTI, the terminal determines a PUSCH (physical uplink shared channel) sent in a common subframe corresponding to the downlink control channel;

wherein the first RNTI and the second RNTI are different.

In a possible implementation manner, if the first RNTI is shared by a plurality of terminals, after the terminal determines the PUSCH transmitted in the special subframe corresponding to the downlink control channel, the method further includes:

and the terminal determines the position of an indication domain which corresponds to the terminal and is used for indicating whether to retransmit in the downlink control channel according to the index value of the terminal.

In a possible implementation manner, the subframe m + k is different from a subframe for detecting a downlink control channel of a PUSCH transmitted in a corresponding normal subframe.

Wherein k is defined as follows:

for TDD uplink and downlink configuration 1, if m is 1 or 6, k is 4 or 9; or

For TDD uplink and downlink configuration 2, if m is 1 or 6, k is 3, 4, 5, 8, 9, or 10; or

For TDD uplink and downlink configuration 3, if m is 1, k is 4, 5, 6, or 10; or

For TDD uplink and downlink configuration 4, if m is 1, k is 3, 4, 5, 6, 9, or 10; or

For TDD uplink and downlink configuration 5, if m is 1, k is 2, 3, 4, 5, 6, 8, 9, or 10.

Further, the determining, by the terminal, whether to retransmit the PUSCH transmitted in the special subframe m according to the downlink control channel includes:

and the terminal determines whether to retransmit the PUSCH sent in the special subframe m according to an indication domain which is carried by the downlink control channel and used for indicating whether to retransmit the PUSCH.

In a possible implementation manner, the determining, by the terminal, whether the downlink control channel corresponds to a PUSCH transmitted in a special subframe according to a 2-bit uplink index ulidex indication field in the downlink control channel includes:

when the least significant bit LSB and the most significant bit MSB of the UL index are both set to 0, the terminal determines that the downlink control channel corresponds to a PUSCH transmitted in a special subframe;

and when at least one of LSB and MSB of the UL index is set to be 1, the terminal determines that the downlink control channel corresponds to PUSCH transmitted in a common uplink subframe.

In a second aspect, a method for sending feedback information of uplink transmission includes:

a base station scheduling terminal sends a Physical Uplink Shared Channel (PUSCH) in a special subframe m, wherein m is an integer;

the base station detects the PUSCH sent by the terminal in the special subframe m;

and the base station sends a downlink control channel using a Downlink Control Information (DCI) format to the terminal in a subframe containing downlink transmission resources behind the special subframe m or in a subframe m + k, wherein k is a positive integer, and the downlink control channel carries an indication domain for indicating whether the PUSCH in the special subframe m is retransmitted or not.

In one possible embodiment, k is defined as follows:

For TDD uplink and downlink configuration 1, if m is 1 or 6, k is 3, 5, 8, 10; or

For TDD uplink and downlink configuration 2, if m is 1 or 6, k is 2 or 7; or

For TDD uplink and downlink configuration 3, if m is 1, k is 7, 8 or 9; or

For TDD uplink and downlink configuration 4, if m is 1, k is 7 or 8; or

For TDD uplink and downlink configuration 5, if m is 1, k is 7; alternatively, the first and second electrodes may be,

for TDD uplink and downlink configuration 6, if m is 1, k is 4, 5, 8, 9, or 10; alternatively, the first and second electrodes may be,

for TDD uplink and downlink configuration 6, if m is 6, k is 3, 4, 5, 9, or 10.

Based on any of the above embodiments, the sending, by the base station, the downlink control channel using the uplink DCI format to the terminal includes:

the base station determines the size of an uplink DCI format used by the downlink control channel according to whether the downlink control channel corresponds to a PUSCH sent in a special subframe or not; and/or

The base station carries a first indication domain in the downlink control channel, wherein the first indication domain is used for indicating the relevant information of the PUSCH corresponding to the downlink control channel; and/or

The base station carries a second indication domain in the downlink control channel, wherein the second indication domain is used for indicating that the PUSCH corresponding to the downlink control channel is a PUSCH in a special subframe or a PUSCH in a common subframe; and/or

The base station determines a Radio Network Temporary Identifier (RNTI) used when the downlink control channel is scrambled according to whether the downlink control channel corresponds to a Physical Uplink Shared Channel (PUSCH) sent in a special subframe; and/or

And the base station determines the value of a 2-bit uplink index UL index indication domain in the downlink control channel according to whether the downlink control channel corresponds to a PUSCH sent in a special subframe.

In a possible implementation manner, the determining, by the base station, the size of the uplink DCI format used by the downlink control channel according to whether the downlink control channel corresponds to the PUSCH transmitted in the special subframe includes:

if the downlink control channel corresponds to a PUSCH sent in a special subframe, the base station determines that the downlink control channel uses an uplink DCI format with a first DCI size; or

If the downlink control channel corresponds to a PUSCH sent in a common subframe, the base station determines that the downlink control channel uses an uplink DCI format with a second DCI size;

wherein the first DCI size and the second DCI size are different.

In a possible implementation manner, the determining, by the base station, the RNTI used when the downlink control channel is scrambled according to whether the downlink control channel corresponds to the PUSCH transmitted in the special subframe includes:

if the downlink control channel corresponds to a PUSCH sent in a special subframe, the base station uses a first RNTI for scrambling when determining that the downlink control channel is scrambled; or

If the downlink control channel corresponds to a PUSCH sent in a common subframe, the base station determines that the downlink control channel uses a second RNTI when scrambling;

wherein the first RNTI and the second RNTI are different.

In a possible embodiment, if the RNTI corresponding to the special subframe is shared by a plurality of terminals, the method further includes: and the base station maps the indication domains of the terminals for indicating whether to retransmit to corresponding positions in the downlink control channel of the corresponding special subframe according to the index values of the terminals.

In one possible implementation, the subframe m + k is different from a subframe in which a downlink control channel corresponding to a PUSCH transmitted in a normal subframe is transmitted.

Wherein k is defined as follows:

for TDD uplink and downlink configuration 1, if m is 1 or 6, k is 4 or 9; or

For TDD uplink and downlink configuration 3, if m is 1, k is 4, 5, 6, or 10; or

In a possible implementation manner, the determining, by the base station, a value of a 2-bit uplink index UL index indication field in the downlink control channel according to whether the downlink control channel corresponds to a PUSCH transmitted in a special subframe includes:

if the downlink control channel corresponds to a PUSCH transmitted in a special subframe, the base station sets the LSB and the MSB of the least significant bit of the ULindex to 0;

and if the downlink control channel corresponds to a PUSCH transmitted in a common uplink subframe, the base station sets at least one of the LSB and the MSB of the ULindex to 1.

In a third aspect, a computer-readable storage medium is provided, in which executable program code is stored, the program code being adapted to implement the method of the first aspect.

In a fourth aspect, a computer-readable storage medium is provided, in which executable program code is stored, the program code being adapted to implement the method of the second aspect.

In a fifth aspect, a terminal, the terminal comprising:

the device comprises a sending module, a receiving module and a sending module, wherein the sending module is used for sending a Physical Uplink Shared Channel (PUSCH) in a special subframe m, and m is an integer;

a detection module, configured to detect a downlink control channel using a DCI format after the special subframe m or in a subframe m + k including a downlink transmission resource, where k is a positive integer;

and the determining module is used for determining whether to retransmit the PUSCH sent in the special subframe m according to the downlink control channel.

In one possible embodiment, k is defined as follows:

For TDD uplink and downlink configuration 2, if m is 1 or 6, k is 2 or 7; or

For TDD uplink and downlink configuration 3, if m is 1, k is 7, 8 or 9; or

For TDD uplink and downlink configuration 4, if m is 1, k is 7 or 8; or

For TDD uplink and downlink configuration 5, if m is 1, k is 7; or

For TDD uplink and downlink configuration 6, if m is 6, k is 3, 4, 5, 9, or 10.

Based on any of the embodiments above, the determining module is specifically configured to:

determining whether the downlink control channel corresponds to a PUSCH (physical uplink shared channel) sent in a special subframe or not according to the downlink control channel;

and after determining the PUSCH sent in the special subframe corresponding to the downlink control channel, determining whether to retransmit the PUSCH sent in the special subframe m according to an indication domain carried by the downlink control channel and used for indicating whether to retransmit.

In a possible implementation manner, the determining module is specifically configured to:

determining whether the downlink control channel corresponds to a PUSCH (physical uplink shared channel) sent in a special subframe or not according to the size of an uplink DCI (Downlink control information) format used by the downlink control channel; and/or

Determining whether the downlink control channel corresponds to a PUSCH (physical uplink shared channel) sent in a special subframe or not according to a first indication domain in the downlink control channel, wherein the first indication domain is used for indicating relevant information of the PUSCH corresponding to the downlink control channel; and/or

Determining whether the downlink control channel corresponds to a PUSCH sent in a special subframe or not according to a second indication domain in the downlink control channel, wherein the second indication domain is used for indicating that the PUSCH corresponding to the downlink control channel is a PUSCH in the special subframe or a PUSCH in a common subframe; and/or

Determining whether the downlink control channel corresponds to a PUSCH (physical uplink shared channel) sent in a special subframe or not according to a Radio Network Temporary Identifier (RNTI) used when the downlink control channel is scrambled; and/or

And determining whether the downlink control channel corresponds to a PUSCH (physical uplink shared channel) sent in a special subframe or not according to a 2-bit uplink index (UL index) indication domain in the downlink control channel.

if the detection module detects that the downlink control channel uses the uplink DCI format with the first DCI size, determining a PUSCH (physical uplink shared channel) sent in a special subframe corresponding to the downlink control channel; or if the detection module detects that the downlink control channel uses an uplink DCI format with a second DCI size, determining a PUSCH (physical uplink shared channel) sent in a common subframe corresponding to the downlink control channel; wherein the first DCI size and the second DCI size are different.

if the detection module detects that the downlink control channel is scrambled by using the first RNTI, determining a PUSCH (physical uplink shared channel) sent in a special subframe corresponding to the downlink control channel; or if the detection module detects that the downlink control channel uses a second RNTI for scrambling, determining a PUSCH sent in a common subframe corresponding to the downlink control channel; wherein the first RNTI and the second RNTI are different.

In a possible implementation manner, if the first RNTI is shared by a plurality of terminals, the determining module is further configured to:

and determining the position of an indication domain which corresponds to the terminal and is used for indicating whether to retransmit in the downlink control channel according to the index value of the terminal.

Wherein k is defined as follows:

for TDD uplink and downlink configuration 1, if m is 1 or 6, k is 4 or 9; or

For TDD uplink and downlink configuration 3, if m is 1, k is 4, 5, 6, or 10; or

Further, the determining module is specifically configured to:

and determining whether to retransmit the PUSCH sent in the special subframe m according to an indication domain carried by the downlink control channel and used for indicating whether to retransmit.

when the LSB and the MSB of the UL index are both set to be 0, determining that the downlink control channel corresponds to a PUSCH transmitted in a special subframe;

and when at least one of the LSB and the MSB of the UL index is set to be 1, determining that the downlink control channel corresponds to the PUSCH transmitted in the common uplink subframe.

In a sixth aspect, a terminal includes: a transceiver, and at least one processor connected with the transceiver, wherein:

the processor is used for reading the program in the memory and executing the following processes:

controlling the transceiver to transmit PUSCH in a special subframe m, wherein m is an integer; detecting a downlink control channel using an uplink DCI format in a subframe containing downlink transmission resources after the special subframe m or in a subframe m + k, wherein k is a positive integer; determining whether to retransmit the PUSCH sent in the special subframe m according to the downlink control channel;

the transceiver is used for receiving and transmitting data under the control of the processor.

Wherein the processor reads the program in the memory and executes the operations executed by the detecting module and the determining module in the embodiment of the fifth aspect, and the transceiver executes the operations executed by the transmitting module in the embodiment of the fifth aspect under the control of the processor.

In a seventh aspect, a base station, the base station comprising:

the scheduling module is used for scheduling the terminal to send a Physical Uplink Shared Channel (PUSCH) in a special subframe m, wherein m is an integer;

a detection module, configured to detect, in the special subframe m, a PUSCH transmitted by the terminal;

and the processing module is configured to send a downlink control channel using a DCI format to the terminal in a subframe including a downlink transmission resource after the special subframe m or in a subframe m + k, where k is a positive integer, and the downlink control channel carries an indication field for indicating whether or not the PUSCH in the special subframe m is retransmitted.

In one possible embodiment, k is defined as follows:

For TDD uplink and downlink configuration 2, if m is 1 or 6, k is 2 or 7; or

For TDD uplink and downlink configuration 3, if m is 1, k is 7, 8 or 9; or

For TDD uplink and downlink configuration 4, if m is 1, k is 7 or 8; or

for TDD uplink and downlink configuration 6, if m is 6, k is 3, 4, 5, 9, or 10.

Based on any of the embodiments above, the processing module is specifically configured to:

determining the size of an uplink DCI format used by the downlink control channel according to whether the downlink control channel corresponds to a PUSCH transmitted in a special subframe; and/or

Carrying a first indication domain in the downlink control channel, wherein the first indication domain is used for indicating the relevant information of the PUSCH corresponding to the downlink control channel; and/or

A second indication domain is carried in the downlink control channel, and the second indication domain is used for indicating that the PUSCH corresponding to the downlink control channel is a PUSCH in a special subframe or a PUSCH in a common subframe; and/or

Determining a Radio Network Temporary Identifier (RNTI) used when the downlink control channel is scrambled according to whether the downlink control channel corresponds to a Physical Uplink Shared Channel (PUSCH) sent in a special subframe; and/or

And determining the value of a 2-bit uplink index UL index indication domain in the downlink control channel according to whether the downlink control channel corresponds to a PUSCH sent in a special subframe.

In a possible implementation manner, the processing module is specifically configured to:

if the downlink control channel corresponds to a PUSCH sent in a special subframe, determining that the downlink control channel uses an uplink DCI format with a first DCI size; or if the downlink control channel corresponds to a PUSCH sent in a common subframe, determining that the downlink control channel uses an uplink DCI format with a second DCI size; wherein the first DCI size and the second DCI size are different.

if the downlink control channel corresponds to a PUSCH sent in a special subframe, scrambling by using a first RNTI when the downlink control channel is determined to be scrambled; or if the downlink control channel corresponds to a PUSCH sent in a common subframe, determining that a second RNTI is used when the downlink control channel is scrambled; wherein the first RNTI and the second RNTI are different.

In a possible implementation manner, if the RNTI corresponding to the special subframe is shared by a plurality of terminals, the processing module is further configured to:

and mapping the indication domains of the terminals for indicating whether to retransmit or not to corresponding positions in the downlink control channel of the corresponding special subframe according to the index values of the terminals.

Wherein k is defined as follows:

for TDD uplink and downlink configuration 1, if m is 1 or 6, k is 4 or 9; or

For TDD uplink and downlink configuration 3, if m is 1, k is 4, 5, 6, or 10; or

setting the least significant bit LSB and the most significant bit MSB of the UL index to 0 if the downlink control channel corresponds to the PUSCH transmitted in the special subframe;

and if the downlink control channel corresponds to the PUSCH transmitted in the common uplink subframe, setting at least one of the LSB and the MSB of the UL index to be 1.

In an eighth aspect, a base station comprises: a transceiver, and at least one processor connected with the transceiver, wherein:

through the transceiver, the scheduling terminal sends a Physical Uplink Shared Channel (PUSCH) in a special subframe m, wherein m is an integer; detecting a PUSCH sent by the terminal in the special subframe m; controlling the transceiver to send a downlink control channel using an uplink Downlink Control Information (DCI) format to the terminal in a subframe containing downlink transmission resources behind the special subframe m or in a subframe m + k, wherein k is a positive integer, and the downlink control channel carries an indication field for indicating whether the PUSCH in the special subframe m is retransmitted or not;

Wherein the processor reads the program in the memory and executes the operations executed by the scheduling module, the detecting module and the processing module in the embodiment of the seventh aspect.

In the method and the device provided by the embodiment of the invention, after a terminal sends a physical uplink shared channel PUSCH in a special subframe m, a downlink control channel using an uplink DCI format is detected in a subframe containing downlink transmission resources behind the special subframe m or a subframe m + k, and whether the PUSCH sent in the special subframe m is retransmitted or not is determined according to the downlink control channel, so that a transmission scheme for transmitting feedback information of the PUSCH in the special subframe is provided, and the PUSCH sent in the special subframe can normally obtain ACK/NACK feedback information.

Drawings

Fig. 1 is a schematic structural diagram of FS2 in an LTE TDD system;

fig. 2 is a schematic flowchart of a method for receiving feedback information of uplink transmission according to an embodiment of the present invention;

fig. 3 is a flowchart illustrating a method for sending feedback information of uplink transmission according to an embodiment of the present invention;

fig. 4 is a schematic diagram of a terminal according to an embodiment of the present invention;

fig. 5 is a schematic diagram of another terminal according to an embodiment of the present invention;

fig. 6 is a schematic diagram of a base station according to an embodiment of the present invention;

fig. 7 is a schematic diagram of another base station according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The technical solution described in the embodiments of the present invention may be used in various communication systems, such as 2G, 3G, 4G, 5G communication systems and next-generation communication systems, for example, a Global System for mobile communications (GSM), a Code Division Multiple Access (CDMA) System, a Time Division Multiple Access (TDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a Frequency Division Multiple Access (FDMA) System, an Orthogonal Frequency Division Multiple Access (OFDMA) System, an FDMA-FDMA (SC-FDMA) System, a General Packet Radio Service (Radio Service, Long Term Evolution (GPRS) System, and the like.

The embodiments of the present invention are described in connection with a terminal and/or a base station, where:

a terminal may be a wireless terminal which may be a device providing voice and/or data connectivity to a user, a handheld device having wireless connection capability, or other processing device connected to a wireless modem. Wireless terminals, which may be mobile terminals such as mobile telephones (or "cellular" telephones) and computers having mobile terminals, such as portable, pocket, hand-held, computer-included, or vehicle-mounted mobile devices, may communicate with one or more core networks via a Radio Access Network (e.g., a Radio Access Network, RAN). For example, devices such as Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs) are known. A wireless Terminal may also be referred to as a system, a Subscriber Unit (Subscriber Unit), a Subscriber Station (Subscriber Station), a Mobile Station (Mobile), a Remote Station (Remote Station), an Access Point (Access Point), a Remote Terminal (Remote Terminal), an Access Terminal (Access Terminal), a User Terminal (User Terminal), a User Agent (User Agent), a User Device (User Device), or a User Equipment (User Equipment).

A base station may refer to a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminals. The base station may be configured to interconvert received air frames and IP packets as a router between the wireless terminal and the rest of the access network, which may include an Internet Protocol (IP) network. The base station may also coordinate management of attributes for the air interface. For example, the Base Station may be a Base Transceiver Station (BTS) in GSM or CDMA, a Base Station (NodeB) in WCDMA, or an evolved Node B (NodeB or eNB or e-NodeB) in LTE, which is not limited in the embodiment of the present invention.

The embodiments of the present invention will be described in further detail with reference to the drawings attached hereto. It is to be understood that the embodiments described herein are merely illustrative and explanatory of the invention and are not restrictive thereof.

In the embodiment shown in fig. 2, a method for receiving feedback information of uplink transmission is provided, where the method includes:

s21, the terminal sends PUSCH in a special subframe m, wherein m is an integer.

Optionally, m is 1 or 6.

Optionally, the terminal sends a PUSCH in an UpPTS in the special subframe m. Of course, the terminal may also send the PUSCH in the GP in the special subframe m, and the specific location for sending the PUSCH is not limited in the embodiment of the present invention.

S22, the terminal detects a downlink control channel using an uplink DCI format in a subframe including a downlink transmission resource after the special subframe m or in a subframe m + k, where k is a positive integer.

In this step, if the HARQ of the PUSCH transmitted by the terminal employs an asynchronous mode, the terminal detects a subframe including downlink transmission resources after the special subframe m; and if the HARQ of the PUSCH sent by the terminal adopts a synchronous mode, the terminal detects in a subframe m + k.

Optionally, when the terminal detects the downlink control channel using the uplink DCI format in the subframe including the downlink transmission resource after the special subframe m, the terminal may perform detection in any subframe including the downlink resource after the special subframe m, or may perform detection in any subframe including the downlink resource within a set time after the special subframe m, for example, detect any downlink subframe and/or special subframe in 10 subframes after the special subframe m, depending on the scheduling implementation and the resource allocation condition of the base station.

And S23, the terminal determines whether to retransmit the PUSCH sent in the special subframe m according to the downlink control channel.

In the embodiment of the invention, after a terminal sends a Physical Uplink Shared Channel (PUSCH) in a special subframe m, a downlink control channel using an uplink DCI format is detected in a subframe containing downlink transmission resources behind the special subframe m or a subframe m + k, and whether the PUSCH sent in the special subframe m is retransmitted or not is determined according to the downlink control channel, so that a transmission scheme for transmitting feedback information of the PUSCH in the special subframe is provided, and the PUSCH sent in the special subframe can normally obtain ACK/NACK feedback information.

In this embodiment of the present invention, when the terminal determines whether to retransmit the PUSCH transmitted in the special subframe m according to the downlink control channel in S23, when the HARQ of the PUSCH transmitted by the terminal employs a synchronous manner and an asynchronous manner, the following processes may be employed:

Further, the terminal determines whether the downlink control channel corresponds to a PUSCH transmitted in a special subframe according to the downlink control channel, including the following five possible implementation manners:

in the mode 1, the terminal determines whether the downlink control channel corresponds to the PUSCH transmitted in the special subframe according to the size of the uplink DCI format used by the downlink control channel.

In this embodiment, the size of the uplink DCI format used for the downlink control channel corresponding to the PUSCH transmitted in the special subframe (denoted as the first DCI size) is different from the size of the uplink DCI format used for the downlink control channel corresponding to the PUSCH transmitted in the normal subframe (denoted as the second DCI size), so as to distinguish whether the detected downlink control channel corresponds to the PUSCH transmitted in the special subframe (one implementation is that for a terminal supporting PUSCH transmission in UpPTS, the uplink DCI format corresponding to UpPTS is a newly defined uplink DCI format or an uplink DCI format obtained by adding an extra bit field to an existing DCI format, and the uplink format corresponding to the normal uplink subframe is an existing uplink DCI format, where the existing uplink DCI format may be 3GPP 36.212Rel-13 or DCI format 0/4 defined in the previous release).

In this way, the terminal can distinguish whether the detected downlink control channel corresponds to the PUSCH in the special subframe or the PUSCH in the normal subframe by blindly detecting the uplink DCI formats of different sizes.

In this manner, if the terminal detects that the downlink control channel uses an uplink DCI format of a first DCI size, the terminal determines a PUSCH transmitted in a special subframe corresponding to the downlink control channel; or if the terminal detects that the downlink control channel uses the uplink DCI format with the second DCI size, the terminal determines the PUSCH sent in the common subframe corresponding to the downlink control channel.

And in the mode 2, the terminal determines whether the downlink control channel corresponds to the PUSCH transmitted in the special subframe according to a first indication field in the downlink control channel, where the first indication field is used to indicate the relevant information of the PUSCH corresponding to the downlink control channel.

Optionally, the first indication field carries an HARQ process number of a PUSCH corresponding to the downlink control channel. The HARQ process number may be a common number of the PUSCH in the UpPTS and the PUSCH in the normal subframe, or may be a number of the PUSCH in the UpPTS alone, or a number of the PUSCH in the normal subframe alone. Of course, the embodiment of the present invention does not limit the specific implementation form of the first indication field, and any information that can identify the PUSCH corresponding to the downlink control channel may be used as the first indication field.

One implementation is as follows: for a terminal supporting transmission of a PUSCH in a UpPTS, an uplink DCI format corresponding to the UpPTS is a newly defined uplink DCI format or an uplink DCI format obtained by adding an extra bit field on the basis of an existing DCI format, wherein a first indication field is used for indicating information such as a process number of the PUSCH transmitted in the UpPTS, the process number is used for identifying which information of the PUSCH transmitted in the UpPTS is, and the uplink DCI format corresponding to a common uplink subframe is the existing uplink DCI format, wherein the existing uplink DCI format may be 3GPP 36.212Rel-13 or DCI format 0/4 defined in a previous version;

the other realization mode is as follows: for a terminal supporting PUSCH transmission in the UpPTS, reusing a padding bit in an existing uplink DCI format as the first indication field, that is, at this time, for a terminal supporting PUSCH transmission in the UpPTS, the corresponding UpPTS and an uplink DCI format of an ordinary uplink subframe are the same and have the same size, and by analyzing the padding bit therein as the first indication field, it can be known whether the uplink DCI corresponds to the UpPTS or the ordinary uplink subframe and which PUSCH corresponds to the UpPTS, for example, the first indication field indicates a HARQ process number uniformly performed by the PUSCH in the UpPTS and the PUSCH in the ordinary subframe, and it is also possible to define that the first indication field is a corresponding ordinary uplink subframe with all 0, and the rest states are used for indicating which PUSCH is transmitted in the UpPTS, and certainly there may be a corresponding manner of other indications;

the other realization mode is as follows: defining an uplink DCI format A for a terminal supporting PUSCH transmission in UpPTS, wherein the uplink DCI format A can add an additional indication field on the basis of the existing uplink DCI format, for example, add an additional indication field on the basis of DCI format 0/4 as a first indication field, the indication field is only effective for the terminal supporting PUSCH transmission in UpPTS, or is a fully redefined uplink DCI format, wherein the first indication field indicates a HARQ process number uniformly performed by PUSCH in UpPTS and PUSCH in a common subframe, or one state of the first indication field indicates a corresponding common uplink subframe, and the other states are used for indicating the PUSCH transmitted in which UpPTS corresponds; a terminal supporting the transmission of the PUSCH in the UpPTS, and scheduling the PUSCH transmitted in the UpPTS and the normal uplink subframe by using the uplink DCI format a, and further defining a terminal supporting the transmission of the PUSCH in the UpPTS, where all or part of downlink DCI formats of the terminal may perform padding according to the size of the uplink DCI format a, or the uplink DCI format a performs padding according to the size of all or part of downlink DCI formats, so as to ensure that the size of the uplink DCI format a is the same as that of all or part of downlink DCI formats, and thus, the number of blind tests on the DCI by the terminal is not increased; for example: for a terminal supporting the transmission of PUSCH in UpPTS, defining its uplink DCI format based on the existing DCI format 0, adding at least a bit indication field as a first indication field on the basis of the existing DCI format 0, certainly not excluding that other indication fields may be further added, adding the uplink DCI format 0 after the indication field as the uplink DCI format 0 corresponding to the terminal supporting the transmission of PUSCH in UpPTS, in order to reduce the number of blind detections, when the size of the uplink DCI format 0 corresponding to the terminal supporting the transmission of PUSCH in UpPTS is smaller than the size of the downlink DCI format 1A, padding (i.e. padding 0 at the end of the uplink DCI format 0) to ensure that the size of the DCI format 0 corresponding to the terminal supporting the transmission of PUSCH in UpPTS is the same as the size of the corresponding downlink DCI format 1A in order to maintain the number of blind detections, when the size of downlink DCI format 1A corresponding to the terminal supporting PUSCH transmission in UpPTS is smaller than the size of uplink DCI format 0 corresponding thereto, padding is required to be performed on DCI format 1A corresponding to the terminal supporting PUSCH transmission in UpPTS to ensure that the DCI size is the same as the uplink DCI format 0 corresponding thereto, where the downlink DCI format corresponding to the terminal supporting PUSCH transmission in UpPTS, for example, DCI format 1A, does not certainly exclude other downlink DCI formats such as DCI1B/1C/1D/2/2A/2B, and may directly reuse the existing downlink DCI format, and in order to maintain the number of blind detections, downlink DCI formats 3 and 3A corresponding to the terminal supporting PUSCH transmission in UpPTS are supported, and the DCI size of the downlink DCI format 1A is the same as the size of uplink DCI format 0 and the downlink DCI format 1A corresponding to the terminal supporting PUSCH transmission in UpPTS.

And in the mode 3, the terminal determines whether the downlink control channel corresponds to the PUSCH transmitted in the special subframe according to a second indication field in the downlink control channel, wherein the second indication field is used for indicating that the PUSCH corresponding to the downlink control channel is the PUSCH in the special subframe or the PUSCH in the ordinary subframe.

In this embodiment, the second indication field may be a newly defined bit field in the downlink control channel, or may reuse a 1-bit spare bit field in an existing uplink DCI format, such as a padding bit. And reusing the 1-bit idle bit field in the existing uplink DCI format, so that the size of the uplink DCI format corresponding to the special subframe is the same as that of the uplink DCI format corresponding to the common subframe, and the number of blind tests on the uplink DCI format by the terminal can be reduced.

In this embodiment, the second indication field is represented by 1-bit information. For example, when the second indication field is "0", it indicates a PUSCH transmitted in a corresponding special subframe; when the second indication domain is '1', the PUSCH sent in the corresponding common subframe is indicated; and vice versa.

One implementation is as follows: for a terminal supporting PUSCH transmission in the UpPTS, reusing a padding bit in an existing uplink DCI format as the second indication field, that is, at this time, for a terminal supporting PUSCH transmission in the UpPTS, the corresponding UpPTS and the uplink DCI format of the ordinary uplink subframe are the same and have the same size, and by analyzing the padding bit therein as the second indication field, it is possible to know whether the uplink DCI corresponds to the UpPTS or the ordinary uplink subframe and which PUSCH corresponds to the uplink DCI, wherein the first indication field may be defined as all 0 corresponding to the ordinary uplink subframe, and the remaining states are used to indicate which PUSCH is transmitted in the UpPTS, and of course, there may be other indication corresponding manners;

the other realization mode is as follows: defining an uplink DCI format a for a terminal supporting PUSCH transmission in UpPTS, where the uplink DCI format a may add an additional indication field on the basis of an existing uplink DCI format, for example, add an additional indication field as a second indication field on the basis of DCI format 0/4, where the indication field is only valid for a terminal supporting PUSCH transmission in UpPTS, or is a fully redefined uplink DCI format, where the second indication field may be only 1 bit, one state indication corresponds to a normal uplink subframe, another state is used to indicate a corresponding UpPTS, if there are PUSCHs in multiple UpPTS, the second indication field may be more than 1 bit, one state indication corresponds to a normal uplink subframe, and the remaining states are used to indicate which UpPTS the PUSCH is transmitted, for example, expressed as a process number; a terminal supporting the transmission of the PUSCH in the UpPTS, and scheduling the PUSCH transmitted in the UpPTS and the normal uplink subframe by using the uplink DCI format a, and further defining a terminal supporting the transmission of the PUSCH in the UpPTS, where all or part of downlink DCI formats of the terminal may perform padding according to the size of the uplink DCI format a, or the uplink DCI format a performs padding according to the size of all or part of downlink DCI formats, so as to ensure that the size of the uplink DCI format a is the same as that of all or part of downlink DCI formats, and thus, the number of blind tests on the DCI by the terminal is not increased; for example: for a terminal supporting PUSCH transmission in UpPTS, an uplink DCI format is defined based on the existing DCI format 0, at least a bit indication domain is additionally added on the basis of the existing DCI format 0 to serve as a second indication domain, other indication domains are certainly not excluded, the uplink DCI format 0 after the indication domain is added serves as the uplink DCI format 0 corresponding to the terminal supporting PUSCH transmission in UpPTS, and the original DCI design ensures that the sizes of the uplink DCI format 0 and the downlink DCI format 1A are the same, so that the blind detection times are reduced; in order to maintain the original blind detection times, when the size of the uplink DCI format 0 corresponding to the terminal supporting PUSCH transmission in UpPTS is smaller than the downlink DCI format 1A, padding (i.e. filling 0 at the end) is required to be performed on the DCI format 0 corresponding to the terminal supporting PUSCH transmission in UpPTS to ensure that the DCI size is the same as the downlink DCI format 1A corresponding to the terminal, and when the size of the downlink DCI format 1A corresponding to the terminal supporting PUSCH transmission in UpPTS is smaller than the uplink DCI format 0 corresponding to the terminal supporting PUSCH transmission in UpPTS, padding is required to be performed on the downlink DCI format 1A corresponding to the terminal supporting PUSCH transmission in UpPTS to ensure that the DCI size is the same as the uplink DCI format 0 corresponding to the terminal supporting PUSCH transmission in UpPTS, wherein the downlink DCI format corresponding to the terminal supporting PUSCH transmission in UpPTS, such as DCI format 1A, and other downlink DCI formats such as DCI 1B/1C/2/2D/2B are not excluded, the existing downlink DCI format can be reused directly, and in order to maintain the number of blind tests, downlink DCI formats 3 and 3A corresponding to the terminal that transmits PUSCH in UpPTS are supported, and the DCI size of the downlink DCI formats 3 and 3A is the same as that of uplink DCI format 0 and downlink DCI format 1A corresponding to the terminal that supports PUSCH transmission in UpPTS.

Mode 4, the terminal determines whether the downlink control channel corresponds to a PUSCH transmitted in a special subframe according to a radio network Temporary Identifier (RNTI for short) used when the downlink control channel is scrambled; one implementation is that a terminal supporting PUSCH transmission in UpPTS is used to schedule that the PUSCH transmitted in UpPTS is the same as the uplink DCI format used by the PUSCH transmitted in the ordinary uplink subframe, for example, the existing uplink DCI format may be reused, or the uplink DCI format may be newly defined; of course, DCI format differences are not excluded.

In this embodiment, an RNTI (denoted as a first RNTI) used when scrambling a downlink control channel corresponding to a PUSCH transmitted in a special subframe is different from an RNTI (denoted as a second RNTI) used when scrambling a downlink control channel corresponding to a PUSCH transmitted in a normal subframe, and whether or not a detected downlink control channel corresponds to a PUSCH transmitted in a special subframe is discriminated.

In this way, the terminal may perform blind detection by using the first RNTI and the second RNTI to distinguish whether the detected downlink control channel corresponds to the PUSCH in the special subframe or the PUSCH in the normal subframe.

In this way, if the terminal detects that the downlink control channel is scrambled by using the first RNTI, the terminal determines the PUSCH transmitted in the special subframe corresponding to the downlink control channel; or if the terminal detects that the downlink control channel is scrambled by using the second RNTI, the terminal determines the PUSCH sent in the common subframe corresponding to the downlink control channel.

In this manner, optionally, if the first RNTI is shared by multiple terminals, after the terminal determines the PUSCH transmitted in the special subframe corresponding to the downlink control channel, the method further includes:

Specifically, if the first RNTI is dedicated to the terminal, at this time, the downlink control channel scrambled by the first RNTI only carries an indication field for indicating whether to retransmit the terminal that transmits PUSCH in a special subframe; if the first RNTI is shared by multiple terminals, at this time, the downlink control channel scrambled by using the first RNTI may carry indication fields of multiple terminals transmitting PUSCH in a special subframe for indicating whether to retransmit, and therefore, an index value may be configured for each terminal to identify a position of the indication field of the terminal for indicating whether to retransmit in the downlink control channel.

Mode 5: and the terminal determines whether the downlink control channel corresponds to the PUSCH sent in the special subframe or not according to the uplink index UL index indication domain in the downlink control channel.

In this embodiment, the terminal determines that the downlink control channel corresponds to a PUSCH transmitted in a special subframe when both the least Significant bit LSB (least Significant bit) and the most Significant bit MSB (most Significant bit) of the UL index are set to 0, and determines that the downlink control channel corresponds to a PUSCH transmitted in a normal uplink subframe when at least one of the LSB and the MSB of the UL index is set to 1.

For TDD uplink and downlink configuration 0, a 2-bit uplink index (UL index) field in an existing uplink DCI format may be used to determine whether a downlink control channel using the uplink DCI format corresponds to a PUSCH in a normal uplink subframe or a PUSCH in a special subframe.

Specifically, when the 2-Bit UL index is 0, that is, when both the Least Significant Bit (LSB) and the Most Significant Bit (MSB) are set to 0, it indicates that the downlink control channel corresponds to the PUSCH transmitted in the special subframe; when at least one bit of the LSB or the MSB is 1, it indicates that the downlink control channel corresponds to a PUSCH transmitted in a normal uplink subframe.

In this implementation, the time domain position of detecting the downlink control channel may be defined according to the principle of m + k, for example, for the PUSCH in the special subframe, as defined by the k value of table 7 for TDD uplink and downlink configuration 0. Alternatively, when m is 1 or 6, k is 4 or 5 or 9 or 10, and k is as shown in table 3, for PUSCH in the normal uplink subframe, when the terminal transmits PUSCH in the special subframe 1, the downlink control channel may be detected in a subframe corresponding to m + k, m is a special subframe number, it is determined whether PUSCH in the special subframe 1 is retransmitted according to NDI in the downlink control channel, for example, k is 5, the terminal detects the downlink control channel in the subframe 6, determines whether PUSCH in the special subframe 1 is retransmitted according to NDI in the downlink control channel, when the terminal transmits PUSCH in the uplink subframe 2, the downlink control channel and/or PHICH may be detected in a subframe corresponding to n + k, when a downlink control channel is detected, it may determine whether PUSCH in the special subframe 1 is retransmitted according to NDI in the downlink control channel, as shown in table 3, for n 2, k 4, the terminal detects a downlink control channel/PHICH in a subframe 6, determines whether PUSCH in an uplink subframe 2 is retransmitted according to NDI in the downlink control channel or feedback information carried in the PHICH, at this time, PUSCH in both a special subframe 1 and an uplink subframe 2 correspond to the downlink control channel detected in the subframe 6, when an uplink DCI format of the terminal corresponding to the special subframe is identical to/of the uplink DCI format of the terminal corresponding to the normal uplink subframe, the terminal detects the downlink control channel in the subframe 6 and determines whether the downlink control channel corresponds to PUSCH in the special subframe 1 or the uplink subframe 2 according to a UL index field in the downlink control channel detected in the subframe 6, that is, when LSB and MSB of UL index are both 0, determines that the downlink control channel corresponds to PUSCH in the special subframe 1 and determines whether to retransmit according to NDI, when any one of the LSB and the MSB of the ULindex is 1, it is determined that the downlink control channel corresponds to the PUSCH in the uplink subframe 2, and it is determined whether to retransmit the PUSCH according to the NDI.

Certainly, the uplink DCI may further carry an HARQ process number indication field, where the indication field may be reuse of an existing bit number in an existing uplink DCI format, and is used to indicate a PUSCH process number in a special subframe, or is used to indicate a PUSCH process number in a special subframe and a normal subframe.

Optionally, the indication field for indicating whether to retransmit is NDI.

The above modes 1 to 5 are all applicable to the HARQ of the PUSCH transmitted by the terminal, and both the asynchronous mode and the synchronous mode are adopted.

The above modes 1 to 5 may be used alone or in combination, and the embodiments of the present invention do not limit the modes.

In the embodiment of the present invention, if the terminal detects the downlink control channel using the uplink DCI format in the subframe m + k, that is, the terminal uses a synchronization scheme for the HARQ of the PUSCH transmitted by the terminal, as a possible implementation scheme, the subframe for detecting the downlink control channel corresponding to the PUSCH transmitted in the special subframe is the same as the subframe for detecting the downlink control channel corresponding to the PUSCH transmitted in the normal subframe, and the definition of k is as follows:

for TDD uplink and downlink configuration 0, if m is 1 or 6, k is 4, 5, 9 or 10; or

For TDD uplink and downlink configuration 2, if m is 1 or 6, k is 2 or 7; or

For TDD uplink and downlink configuration 3, if m is 1, k is 7, 8 or 9; or

For TDD uplink and downlink configuration 4, if m is 1, k is 7 or 8; or

For TDD uplink and downlink configuration 5, if m is 1, k is 7; or

For TDD uplink and downlink configuration 6, if m is 6, k is 3, 4, 5, 9, or 10.

Because the subframe for detecting the downlink control channel of the PUSCH transmitted in the corresponding special subframe is the same as the subframe for detecting the downlink control channel of the PUSCH transmitted in the corresponding ordinary subframe, and the definition of k enables the downlink control channel using the uplink DCI format corresponding to the special subframe and the ordinary subframe to be in the same subframe, after the terminal detects the downlink control channel using the uplink DCI format in the subframe m + k, it is necessary to determine whether the downlink control channel corresponds to the PUSCH transmitted in the special subframe first, and after determining the PUSCH transmitted in the special subframe corresponding to the downlink control channel, it is determined whether to retransmit the PUSCH transmitted in the special subframe according to an indication field carried by the downlink control channel and used for indicating whether to retransmit. Any one or a combination of the above modes 1 to 5 may be adopted when determining whether the downlink control channel corresponds to the PUSCH transmitted in the special subframe.

Based on any of the above embodiments, the determining, by the terminal in S23, whether to retransmit the PUSCH transmitted in the special subframe m according to the downlink control channel specifically includes:

1. the terminal detects in a subframe containing downlink resources after the special subframe m, and the method further includes the following two conditions:

1) if the terminal detects in any subframe containing downlink resources after the special subframe m, that is, no set time is defined, the terminal keeps the relevant information of the PUSCH transmitted in the special subframe m until receiving a downlink control channel using an uplink DCI format that can determine whether the PUSCH is retransmitted, that is, a downlink control channel using an uplink DCI format corresponding to the PUSCH transmitted in the special subframe. Further, determining whether to retransmit the PUSCH transmitted in the special subframe m according to an indication field carried in the downlink control channel and used for indicating whether to retransmit.

2) If the terminal detects in any subframe containing downlink resources within the set time after the special subframe m, that is, the set time is defined, then:

if the terminal does not detect the downlink control channel using the uplink DCI format within a set time, or detects the downlink control channel using the uplink DCI format but the downlink control channel corresponds to the PUSCH transmitted in the normal subframe, the terminal determines that the PUSCH transmitted in the special subframe m is successfully transmitted without retransmission;

if the terminal detects a downlink control channel using an uplink DCI format within a set time and the downlink control channel corresponds to a PUSCH sent in a special subframe, the terminal determines whether to retransmit the PUSCH sent in the special subframe m according to an indication field carried in the downlink control channel and used for indicating whether to retransmit the PUSCH.

2. The terminal detects in subframe m + k, further including the case:

1) and if the terminal detects a downlink control channel using an uplink DCI format in the subframe m + k and the downlink control channel corresponds to the PUSCH sent in the special subframe, the terminal determines whether to retransmit the PUSCH sent in the special subframe m according to an indication domain carried in the downlink control channel and used for indicating whether to retransmit.

2) If the terminal does not detect the downlink control channel using the uplink DCI format in the subframe m + k, or detects the downlink control channel using the uplink DCI format but the downlink control channel corresponds to the PUSCH transmitted in the normal subframe, the terminal determines that the PUSCH transmitted in the special subframe m is successfully transmitted without retransmission.

Optionally, the indication field for indicating whether to retransmit is NDI, that is, the terminal determines whether to retransmit the PUSCH transmitted in the special subframe m according to the NDI carried in the downlink control channel.

Specifically, for dynamic scheduling, that is, each transmission has a PUSCH of a corresponding downlink control channel: if the NDI in the downlink control channel is not changed relative to the NDI corresponding to the first transmission of the PUSCH, the terminal needs to retransmit the PUSCH; and if the NDI in the downlink control channel is changed relative to the NDI corresponding to the first transmission of the PUSCH, namely the downlink control channel schedules a new PUSCH transmission, the terminal does not need to retransmit the PUSCH.

For Semi-Persistent Scheduling (SPS) PUSCH: if the NDI in the downlink control channel is 0, the downlink control channel is a downlink control channel for indicating the activation/release of downlink SPS resources, namely a scheduling command of an SPS PUSCH, and the terminal does not need to retransmit the PUSCH; and if the NDI in the downlink control channel is 1, the terminal needs to retransmit the PUSCH.

In the embodiment of the present invention, if the terminal detects the downlink control channel using the uplink DCI format in the subframe m + k, that is, a synchronization mode is adopted for the HARQ of the PUSCH transmitted by the terminal, as another possible implementation, the downlink control channel corresponding to the PUSCH transmitted in the special subframe and the downlink control channel corresponding to the PUSCH transmitted in the normal subframe may be distinguished by different subframes, that is, the subframe m + k is different from the subframe for detecting the downlink control channel corresponding to the PUSCH transmitted in the normal subframe. Wherein k is defined as follows:

1) for TDD uplink and downlink configuration 1, m is 1 or 6, and k is 4 or 9.

Specifically, for TDD uplink and downlink configuration 1, the terminal detects a downlink control channel corresponding to the PUSCH transmitted in the special subframe m in subframe m +4 or subframe m +9, that is, detects a downlink control channel corresponding to the PUSCH transmitted in the special subframe 1 or 6 in subframe 5 or subframe 0, and according to table 6, the terminal detects a downlink control channel corresponding to the PUSCH transmitted in the normal subframe in subframe 1, subframe 4, subframe 6, or subframe 9, and therefore, a subframe for detecting the downlink control channel corresponding to the PUSCH transmitted in the special subframe is different from a subframe for detecting the downlink control channel corresponding to the PUSCH transmitted in the normal subframe.

2) For TDD uplink and downlink configuration 2, m is 1 or 6, and k is 3, 4, 5, 8, 9, or 10.

Specifically, for TDD uplink and downlink configuration 2, the terminal detects a downlink control channel corresponding to the PUSCH transmitted in the special subframe m in subframe m +3, subframe m +4, subframe m +5, subframe m +8, subframe m +9, or subframe m +10, that is, detects a downlink control channel corresponding to the PUSCH transmitted in the special subframe 1 or 6 in subframe 0, subframe 1, subframe 4, subframe 5, subframe 6, or subframe 9, and detects a downlink control channel corresponding to the PUSCH transmitted in the normal subframe in subframe 3 or subframe 8 according to table 6, so that a subframe for detecting a downlink control channel corresponding to the PUSCH transmitted in the special subframe is different from a subframe for detecting a downlink control channel corresponding to the PUSCH transmitted in the normal subframe.

3) For TDD uplink and downlink configuration 3, m is 1, and k is 4, 5, 6, or 10.

Specifically, for TDD uplink and downlink configuration 3, the terminal detects a downlink control channel corresponding to the PUSCH transmitted in the special subframe m in subframe m +4, subframe m +5, subframe m +6, or subframe m +10, that is, detects a downlink control channel corresponding to the PUSCH transmitted in the special subframe 1 in subframe 1, subframe 5, subframe 6, or subframe 7, and detects a downlink control channel corresponding to the PUSCH transmitted in the normal subframe in subframe 0, subframe 8, or subframe 9 according to table 6, so that a subframe for detecting a downlink control channel corresponding to the PUSCH transmitted in the special subframe is different from a subframe for detecting a downlink control channel corresponding to the PUSCH transmitted in the normal subframe.

4) For TDD uplink and downlink configuration 4, m is 1, and k is 3, 4, 5, 6, 9, or 10.

Specifically, for TDD uplink and downlink configuration 4, the terminal detects a downlink control channel corresponding to the PUSCH transmitted in the special subframe m in subframe m +3, subframe m +4, subframe m +5, subframe m +6, subframe m +9, or subframe m +10, that is, detects a downlink control channel corresponding to the PUSCH transmitted in the special subframe 1 in subframe 0, subframe 1, subframe 4, subframe 5, subframe 6, or subframe 7, and detects a downlink control channel corresponding to the PUSCH transmitted in the normal subframe according to table 6, so that a subframe for detecting a downlink control channel corresponding to the PUSCH transmitted in the special subframe is different from a subframe for detecting a downlink control channel corresponding to the PUSCH transmitted in the normal subframe.

5) For TDD uplink and downlink configuration 5, m is 1, and k is 2, 3, 4, 5, 6, 8, 9, or 10.

Specifically, for TDD uplink and downlink configuration 5, the terminal detects a downlink control channel corresponding to the PUSCH transmitted in the special subframe m in subframe m +2, subframe m +3, subframe m +4, subframe m +5, subframe m +6, subframe m +8, subframe m +9, or subframe m +10, that is, detects a downlink control channel corresponding to the PUSCH transmitted in the special subframe 1 in subframe 0, subframe 1, subframe 3, subframe 4, subframe 5, subframe 6, subframe 7, or subframe 9, and detects a downlink control channel corresponding to the PUSCH transmitted in the normal subframe in subframe 8 according to table 6, and therefore, a subframe for detecting a downlink control channel corresponding to the PUSCH transmitted in the special subframe is different from a subframe for detecting a downlink control channel corresponding to the PUSCH transmitted in the normal subframe.

Specifically, the definition of k is shown in table 7:

TABLE 7

In table 7, the TDD uplink/downlink Configuration (TDD UL/DL Configuration) is a TDD uplink/downlink Configuration configured by referring to the TDD uplink/downlink Configuration or the system information Configuration.

Further, if the subframe m + k is different from a subframe for detecting a downlink control channel of a PUSCH transmitted in a corresponding normal subframe, the terminal determines whether to retransmit the PUSCH transmitted in the special subframe m according to the downlink control channel in S23, which includes the following two cases:

if the terminal does not detect the downlink control channel using the uplink DCI format in the subframe m + k, the terminal determines that the PUSCH transmission sent in the special subframe m is successful and does not need to be retransmitted.

If the terminal detects a downlink control channel using an uplink DCI format in the subframe m + k, the terminal determines whether to retransmit the PUSCH sent in the special subframe m according to an indication field which is carried in the downlink control channel and used for indicating whether to retransmit.

Specifically, for dynamically scheduled PUSCH: if the NDI in the downlink control channel is not changed relative to the NDI corresponding to the first transmission of the PUSCH, the terminal needs to retransmit the PUSCH; and if the NDI in the downlink control channel is changed relative to the NDI corresponding to the first transmission of the PUSCH, namely the downlink control channel schedules a new PUSCH transmission, the terminal does not need to retransmit the PUSCH.

For SPS PUSCH: if the NDI in the downlink control channel is 0, the terminal does not need to retransmit the PUSCH; and if the NDI in the downlink control channel is 1, the terminal needs to retransmit the PUSCH.

It should be noted that, at the end of the periodWhen a terminal sends a PUSCH in a common subframe n, detecting a PHICH corresponding to the PUSCH and/or a downlink control channel using an uplink DCI format in a subframe n + k; wherein k is k _PHICHIs a value predefined in the standard, as shown in table 3, for defining the PUSCH transmitted in the subframe n + k _PHICHDetecting a PHICH; further, according to the detected PHICH and/or downlink control channel, whether the PUSCH is retransmitted or not is determined by using the prior art.

Based on the same inventive concept, in the embodiment shown in fig. 3, a method for sending feedback information of uplink transmission is provided, where the method includes:

s31, the base station dispatches the terminal to send PUSCH in a special subframe m, wherein m is an integer;

s32, the base station detects the PUSCH sent by the terminal in the special subframe m;

s33, the base station sends, to the terminal, a downlink control channel using an uplink DCI format in a subframe including downlink transmission resources after the special subframe m or in a subframe m + k, where k is a positive integer, and the downlink control channel carries an indication field for indicating whether or not the PUSCH sent in the special subframe m is retransmitted.

Optionally, the indication field for indicating whether the PUSCH in the special subframe m is retransmitted is an NDI.

In the embodiment of the invention, a base station schedules a terminal to send a PUSCH in a special subframe m, and detects the PUSCH sent by the terminal in the special subframe m; and the base station sends a downlink control channel using an uplink DCI format to the terminal in a subframe containing downlink transmission resources behind the special subframe m or in a subframe m + k, wherein the downlink control channel carries an indication domain for indicating whether the PUSCH sent in the special subframe m is retransmitted or not so as to indicate whether the PUSCH sent in the special subframe m is retransmitted or not by the terminal, thereby providing a transmission scheme for transmitting the feedback information of the PUSCH in the special subframe and ensuring that the PUSCH sent in the special subframe can normally obtain ACK/NACK feedback information.

In one possible embodiment, k is defined as follows:

For TDD uplink and downlink configuration 2, if m is 1 or 6, k is 2 or 7; or

For TDD uplink and downlink configuration 3, if m is 1, k is 7, 8 or 9; or

For TDD uplink and downlink configuration 4, if m is 1, k is 7 or 8; or

for TDD uplink and downlink configuration 6, if m is 6, k is 3, 4, 5, 9, or 10.

wherein the first DCI size and the second DCI size are different.

In a possible implementation manner, the first indication field carries an HARQ process number of a PUSCH corresponding to the downlink control channel.

wherein the first RNTI and the second RNTI are different.

In a possible embodiment, if the RNTI corresponding to the special subframe is shared by a plurality of terminals, the method further includes:

and the base station maps the indication domains of the terminals for indicating whether to retransmit to corresponding positions in the downlink control channel of the corresponding special subframe according to the index values of the terminals.

In this manner, optionally, the definition of k is as follows:

for a TDD uplink and downlink configuration 1, m is 1 or 6, and k is 4 or 9; or

For TDD uplink and downlink configuration 2, m is 1 or 6, and k is 3, 4, 5, 8, 9, or 10; or

For TDD uplink and downlink configuration 3, m is 1, and k is 4, 5, 6, or 10; or

For TDD uplink and downlink configuration 4, m is 1, and k is 3, 4, 5, 6, 9, or 10; or

For TDD uplink and downlink configuration 5, m is 1, and k is 2, 3, 4, 5, 6, 8, 9, or 10.

The method provided by the embodiment of the invention is explained in detail by three specific embodiments.

Example 1: in this embodiment, taking TDD uplink and downlink configuration 1 as an example, the PUSCH transmitted in the UpPTS in the special subframe 1 or 6 assumes to use asynchronous HARQ, and carries feedback information through a downlink control channel; the downlink control channel corresponding to the PUSCH transmitted in the UpPTS includes a first indication field for indicating the HARQ process number of the PUSCH transmitted in the UpPTS, where the HARQ process number transmitted in the UpPTS in the special subframe 1 is 0, and the HARQ process number transmitted in the UpPTS in the special subframe 6 is 1. The following is a description of the implementation from the base station side and the terminal side, respectively.

1. A base station side:

1) scheduling the terminal to transmit PUSCH-1 in the UpPTS in the special subframe 1; receiving PUSCH-1 sent by a terminal in a special subframe 1, and acquiring 1-bit ACK/NACK feedback information of the PUSCH-1, wherein:

if the ACK/NACK feedback information is ACK, then: if the base station does not have new uplink data transmission to be scheduled, the downlink control channel using the uplink DCI format does not need to be sent to the terminal; if the base station needs to schedule new uplink data transmission, the NDI is inverted relative to the NDI in the downlink control channel corresponding to the first transmission of the PUSCH-1 (i.e. set to different values, for example, the NDI corresponding to the first transmission is 0, the NDI in the downlink control channel is set to 1), and the downlink control channel carrying the NDI is sent to the terminal at any subframe after the special subframe 1 containing the downlink resource or at any subframe after the special subframe 1 containing the downlink resource in a set time (for example, any downlink subframe and/or special subframe in the next 10 subframes, depending on the scheduling implementation and resource allocation situation of the base station);

if the ACK/NACK feedback information is NACK, then: the base station includes a subframe containing downlink resources in any subframe after the special subframe 1 or any subframe containing downlink resources in a set time after the special subframe 1 (for example, any downlink subframe and/or special subframe in the next 10 subframes, depending on the scheduling implementation and resource allocation situation of the base station), for example, in subframe 9, a downlink control channel using an uplink DCI format is transmitted to the terminal, and setting the NDI in the downlink control channel to the same value as the NDI in the downlink control channel corresponding to the first transmission of the PUSCH-1 (for example, if the NDI corresponding to the first transmission is 0, then the NDI in the downlink control channel is also set to 0), and indicating the PUSCH-1 sent in the special subframe 1 by the first indication field in the downlink control channel, for example, the 1-bit first indication field indicates "0" indicating HARQ process number 0 of PUSCH transmitted in UpPTS.

2) Scheduling the terminal to transmit PUSCH-2 in the UpPTS in the special subframe 6; receiving PUSCH-2 sent by a terminal in a special subframe 6, and acquiring 1-bit ACK/NACK feedback information of the PUSCH-2, wherein:

if the ACK/NACK feedback information is ACK, then: if the base station does not have new uplink data transmission to be scheduled, the downlink control channel using the uplink DCI format does not need to be sent to the terminal; if the base station needs to schedule new uplink data transmission, the NDI is inverted (i.e. set to different values, for example, the NDI corresponding to the first transmission is 0, the NDI in the downlink control channel is set to 1) relative to the NDI in the downlink control channel corresponding to the first transmission of the PUSCH-2, and the downlink control channel carrying the NDI is sent to the terminal at any subframe after the special subframe 6 containing the downlink resource or at any subframe after the special subframe 6 containing the downlink resource in a set time (for example, any downlink subframe and/or special subframe in the next 10 subframes, depending on the scheduling implementation and resource allocation situation of the base station);

if the ACK/NACK feedback information is NACK, then: the base station includes a subframe containing downlink resources in any subframe after the special subframe 6 or any subframe containing downlink resources in a set time after the special subframe 6 (for example, any downlink subframe and/or special subframe in the next 10 subframes, depending on the scheduling implementation and resource allocation situation of the base station), for example, in subframe 9, a downlink control channel using an uplink DCI format is transmitted to the terminal, and setting the NDI in the downlink control channel to the same value as the NDI in the downlink control channel corresponding to the first transmission of the PUSCH-2 (for example, if the NDI corresponding to the first transmission is 0, then the NDI in the downlink control channel is also set to 0), and indicating the PUSCH-2 sent in the special subframe 6 by the first indication field in the downlink control channel, for example, the 1-bit first indication field indicates "1", indicating HARQ process number 1 of PUSCH transmitted in UpPTS.

It should be noted that, although the feedback information of PUSCH-1 and PUSCH-2 transmitted in the UpPTS in the special subframe 1 and the special subframe 6 is obtained through the downlink control channel transmitted in the subframe 9, the terminal side may distinguish the feedback information of PUSCH-1 and PUSCH-2 because the two downlink control channels respectively indicate HARQ process numbers of PUSCH transmitted in different UpPTS.

3) The scheduling terminal transmits PUSCH-3 in the common uplink subframe 2; receiving PUSCH-3 sent by a terminal in an uplink subframe 2 and acquiringIts 1 bit ACK/NACK feedback information; according to k in Table 3 _PHICHDefining, determining that the PHICH of the PUSCH-3 is transmitted in the subframe 6, and determining the PHICH resource parameters thereof according to the minimum PRB index of the PUSCH-3 and the DMRS cyclic shift indication in the scheduling signaling

The PHICH carrying ACK/NACK feedback information of PUSCH-3 is transmitted in subframe 6 according to the parameter.

Of course, if the ACK/NACK feedback information is NACK, if the base station wants to change the resource and configuration of PUSCH-3 retransmission through dynamic scheduling, the base station may also send a downlink control channel using an uplink DCI format in subframe 6, and set the NDI in the downlink control channel to the same value as the NDI in the downlink control channel corresponding to the first transmission of PUSCH-3 (for example, the NDI corresponding to the first transmission is 0, the NDI in the downlink control channel is also set to 0).

2. A terminal side:

1) receiving scheduling information of a PUSCH-1 transmitted by a scheduling terminal in the UpPTS in the special subframe 1, and transmitting the PUSCH-1 in the UpPTS in the special subframe 1 according to the scheduling information; a downlink control channel using the uplink DCI format is detected in any one of subframes including downlink transmission resources after the special subframe 1 or subframes including downlink resources at a set time after the special subframe 1 (for example, each of the next 10 subframes and/or the special subframe).

Specifically, if the set time is specified, if the set time is not detected within the set time, the terminal determines that the base station does not send the downlink control channel indicating retransmission, that is, the terminal determines that the PUSCH-1 transmission is successful and does not need retransmission, and if the set time is not specified, the terminal needs to keep the information of the PUSCH-1 until receiving DCI capable of determining whether the PUSCH-1 is retransmitted or not for further operation; if it is detected that, for example, a downlink control channel is detected in the subframe 9, the terminal determines, according to the process number indicated by the first indication field in the downlink control channel, that the terminal corresponds to the PUSCH-1 transmitted in the UpPTS in the special subframe 1, and then determines whether retransmission is required according to whether the NDI in the downlink control channel is inverted with respect to the NDI corresponding to the first transmission of the PUSCH-1. For example, if the NDI is the same as the NDI corresponding to the first transmission, the terminal determines that retransmission is required, and retransmits the PUSCH-1 according to the scheduling information (i.e., the indicated information such as the resource and the modulation and coding level) in the downlink control channel; for another example, if the NDI is different from the NDI corresponding to the first transmission, the terminal determines that the transmission is new data, and starts to transmit new data according to the scheduling information, that is, it is determined that the PUSCH-1 transmission is successful, and no retransmission is required.

2) Receiving scheduling information of a PUSCH-2 transmitted by a scheduling terminal in the UpPTS in the special subframe 6, and transmitting the PUSCH-2 in the UpPTS in the special subframe 6 according to the scheduling information; a downlink control channel using the uplink DCI format is detected in any one of subframes including downlink transmission resources after the special subframe 6 or subframes including downlink resources at a set time after the special subframe 6 (for example, each of the next 10 subframes and/or the special subframe).

Specifically, if the set time is specified, if the set time is not detected within the set time, the terminal determines that the base station does not send the downlink control channel indicating retransmission, that is, the terminal determines that the PUSCH-2 transmission is successful and does not need retransmission, and if the set time is not specified, the terminal needs to keep the information of the PUSCH-2 until receiving DCI capable of determining whether the PUSCH-2 is retransmitted or not for further operation; if it is detected that, for example, a downlink control channel is detected in the subframe 9, the terminal determines, according to the process number indicated by the first indication field in the downlink control channel, that the terminal corresponds to the PUSCH-2 transmitted in the UpPTS in the special subframe 6, and then determines whether retransmission is required according to whether the NDI in the downlink control channel is inverted with respect to the NDI corresponding to the first transmission of the PUSCH-2. For example, if the NDI is the same as the NDI corresponding to the first transmission, the terminal determines that retransmission is required, and retransmits PUSCH-2 according to the scheduling information (i.e., the information such as the indicated resource and modulation and coding level) in the downlink control channel. For another example, if the NDI is different from the NDI corresponding to the first transmission, the terminal determines that the transmission is new data, and starts to transmit new data according to the scheduling information, that is, it is determined that the PUSCH-2 transmission is successful, and no retransmission is required.

3) Receiving scheduling information of a PUSCH-3 transmitted by a scheduling terminal in a common uplink subframe 2, and transmitting the PUSCH-3 in the uplink subframe 2 according to the scheduling information; according to k in Table 3 _PHICHDefining, determining that the PHICH of the PUSCH-3 is transmitted in the subframe 6, and determining the PHICH resource parameters thereof according to the minimum PRB index of the PUSCH-3 and the DMRS cyclic shift indication in the scheduling signaling

And detecting a PHICH carrying ACK/NACK feedback information of the PUSCH-3 in the subframe 6 according to the parameter, and determining whether to retransmit according to the feedback information in the PHICH. Specifically, the method comprises the following steps: if the ACK is received, retransmission is not needed, and if the NACK is received, the PUSCH-3 is retransmitted according to the same scheduling information transmitted for the first time.

Of course, the terminal may also detect the downlink control channel using the uplink DCI format in subframe 6, and if not, determine whether to need retransmission according to whether the NDI in the downlink control channel is inverted with respect to the NDI corresponding to the first transmission of the PUSCH-3, subject to the feedback information in the PHICH. Specifically, the method comprises the following steps: if the NDI is the same as the NDI corresponding to the first transmission, the terminal determines that retransmission is needed, and retransmits the PUSCH-3 according to scheduling information (namely information such as indicated resources, modulation coding level and the like) in the downlink control channel; and if the NDI is different from the NDI corresponding to the first transmission, the terminal determines that the new data transmission is performed, and starts to transmit the new data according to the scheduling information, namely, the PUSCH-3 transmission is judged to be successful without retransmission.

In this embodiment, if the DCI size used for the downlink control channel corresponding to the PUSCH transmitted in the UpPTS is different from the DCI size used for the downlink control channel corresponding to the PUSCH transmitted in the normal uplink subframe, the downlink control channel corresponding to the PUSCH transmitted in the UpPTS may also be transmitted in the PHICH transmission subframe corresponding to the normal uplink subframe, and at this time, the terminal may distinguish whether the downlink control channel corresponds to the PUSCH in the UpPTS or the PUSCH in the normal uplink subframe by blindly detecting the DCI with different sizes. If the DCI size used for the downlink control channel corresponding to the PUSCH transmitted in the UpPTS is the same as the DCI size used for the downlink control channel corresponding to the PUSCH transmitted in the normal uplink subframe, the base station scheduling implementation is required to avoid transmitting the downlink control channel corresponding to the PUSCH transmitted in the UpPTS and the downlink control channel corresponding to the PUSCH transmitted in the normal uplink subframe in the same subframe, or different RNTIs are needed to be used for distinguishing the downlink control channel corresponding to the PUSCH transmitted in the UpPTS from the downlink control channel corresponding to the PUSCH transmitted in the common uplink subframe by defining or configuring, or need to be distinguished by defining an indication of a second bit field corresponding to a downlink control channel of PUSCH transmitted in UpPTS and a downlink control channel of PUSCH transmitted in a normal uplink subframe, in order not to change the size of the original DCI in the normal uplink subframe, idle bit field reuse in the DCI may be used as the second bit field.

Example 2: in this embodiment, still taking TDD uplink and downlink configuration 1 as an example, the PUSCH transmitted in the UpPTS in the special subframe 1 or 6 assumes to use asynchronous HARQ, and carries the feedback information through the downlink control channel. The following is a description of the implementation from the base station side and the terminal side, respectively.

1. A base station side:

if the ACK/NACK feedback information is NACK, then: the base station sends, to the terminal, a downlink control channel using an uplink DCI format in a subframe 6 (for example, any downlink subframe and/or special subframe in the next 10 subframes depending on the scheduling implementation and resource allocation situation) in any subframe after the special subframe 1 that includes the downlink resource or any subframe after the special subframe 1 that includes the downlink resource in a set time (for example, any downlink subframe and/or special subframe in the next 10 subframes depending on the scheduling implementation and the resource allocation situation of the base station), and sets the NDI in the downlink control channel to a value that is the same as the NDI in the downlink control channel corresponding to the first transmission of the PUSCH-1, for example, if the NDI corresponding to the first transmission is 0, then the NDI in the downlink control channel is also set to 0. Further, the base station may process the downlink control channel by using any one of the following methods:

the method A comprises the following steps: transmitting the downlink control channel by using a first DCI size, wherein the first DCI size is different from the DCI size corresponding to the common uplink subframe;

the method B comprises the following steps: setting a second indication domain in the downlink control channel to be 1, indicating that the downlink control channel corresponds to the PUSCH transmitted in the UpPTS;

the method C comprises the following steps: and scrambling the downlink control channel by using a first RNTI, wherein the first RNTI is different from the RNTI corresponding to the common uplink subframe and is used for distinguishing the downlink control channel corresponding to the PUSCH in the common uplink subframe.

2) The scheduling terminal transmits PUSCH-2 in the common uplink subframe 2; receiving PUSCH-2 sent by a terminal in an uplink subframe 2, and acquiring 1-bit ACK/NACK feedback information of the PUSCH-2; according to k in Table 3 _PHICHDefining, determining that the PHICH of the PUSCH-2 is transmitted in the subframe 6, and determining the PHICH resource parameters thereof according to the minimum PRB index of the PUSCH-2 and the DMRS cyclic shift indication in the scheduling signaling

The PHICH carrying the ACK/NACK feedback information of PUSCH-2 is transmitted in subframe 6 according to the parameter.

Of course, if the ACK/NACK feedback information is NACK, if the base station wants to change the resource and configuration of PUSCH-2 retransmission through dynamic scheduling, the base station may also send a downlink control channel using an uplink DCI format in subframe 6, and set the NDI in the downlink control channel to the same value as the NDI in the downlink control channel corresponding to the first transmission of PUSCH-2, for example, if the NDI corresponding to the first transmission is 0, then the NDI in the downlink control channel is also set to 0. Further, the base station may process the downlink control channel by using any one of the following methods:

the method comprises the following steps: transmitting the downlink control channel by using a second DCI size, wherein the second DCI size is the DCI size corresponding to the common uplink subframe;

the method 2 comprises the following steps: setting a second indication domain in the downlink control channel to be 0, indicating that the downlink control channel corresponds to a PUSCH transmitted in a common uplink subframe;

the method 3 comprises the following steps: scrambling the downlink control channel by using a second RNTI, and distinguishing the downlink control channel corresponding to the PUSCH in the UpPTS;

2. a terminal side:

1) receiving scheduling information of a PUSCH-1 transmitted by a scheduling terminal in the UpPTS in the special subframe 1, and transmitting the PUSCH-1 in the UpPTS in the special subframe 1 according to the scheduling information; a downlink control channel using the uplink DCI format is detected in any one of subframes including downlink transmission resources after the special subframe 1 or subframes including downlink resources at a set time after the special subframe 1 (for example, each of the next 10 subframes and/or the special subframe). If the set time is defined, if the downlink control channel using the uplink DCI format is not detected in the set time, the terminal judges that the base station does not send the downlink control channel indicating retransmission, namely, judges that the PUSCH-1 transmission is successful and does not need retransmission, if the set time is not agreed, the terminal needs to keep the PUSCH-1 information until receiving DCI capable of judging whether the PUSCH-1 is retransmitted or not for further operation; if a downlink control channel using the uplink DCI format is detected, for example, the downlink control channel is detected in subframe 6, the terminal performs processing by using a method corresponding to the base station side:

the method A comprises the following steps: if the detected DCI size is the first DCI size (namely the downlink control channel with the first DCI size is determined to be the downlink control channel using the first DCI size by blind detection of the first DCI size and the second DCI size), determining that the downlink control channel corresponds to the PUSCH in the UpPTS;

the method B comprises the following steps: if the second indication domain in the downlink control channel is '1', determining that the downlink control channel corresponds to the PUSCH in the UpPTS;

the method C comprises the following steps: and if the downlink control channel is scrambled by the first RNTI (namely the downlink control channel is determined to be scrambled by the first RNTI by blind detection of the first RNTI and the second RNTI), determining that the downlink control channel corresponds to the PUSCH in the UpPTS.

Further, the terminal determines whether retransmission is needed according to whether the NDI in the downlink control channel is inverted relative to the NDI corresponding to the first transmission of the PUSCH-1. For example, if the NDI is the same as the NDI corresponding to the first transmission, the terminal determines that retransmission is required, and retransmits the PUSCH-1 according to the scheduling information (i.e., the indicated information such as the resource and the modulation and coding level) in the downlink control channel; if the NDI is different from the NDI corresponding to the first transmission, the terminal determines that the transmission is new data transmission, and starts to transmit new data according to the scheduling information, that is, it is determined that the PUSCH-1 transmission is successful, and retransmission is not required.

2) Receiving scheduling information of a PUSCH-2 transmitted by a scheduling terminal in a common uplink subframe 2, and transmitting the PUSCH-2 in the uplink subframe 2 according to the scheduling information; according to k in Table 3 _PHICHDefining, determining that the PHICH of the PUSCH-2 is transmitted in the subframe 6, and determining the PHICH resource parameters thereof according to the minimum PRB index of the PUSCH-2 and the DMRS cyclic shift indication in the scheduling signaling And detecting a PHICH carrying ACK/NACK feedback information of the PUSCH-2 in a subframe 6 according to the parameter, and determining whether to retransmit according to the feedback information in the PHICH. If the ACK/NACK feedback information is ACK, the terminal determines that retransmission is not needed; and if the ACK/NACK feedback information is NACK, the terminal retransmits the PUSCH-2 according to the same scheduling information transmitted for the first time.Of course, the terminal may also detect the downlink control channel using the uplink DCI format in subframe 6, and if not, the terminal performs processing by using a method corresponding to the base station side based on the feedback information in the PHICH, and if detected:

the method comprises the following steps: determining the downlink control channel to correspond to the PUSCH in the common uplink subframe according to the detected DCI size as the second DCI size (namely, the downlink control channel is determined to be in a DCI format using the second DCI size by blind detection of the first DCI and the second DCI size);

the method 2 comprises the following steps: determining the PUSCH in the common uplink subframe corresponding to the downlink control channel according to the fact that the second indication domain in the downlink control channel is '0';

the method 3 comprises the following steps: and scrambling by adopting a second RNTI according to the downlink control channel (namely determining that the downlink control channel is scrambled by the second RNTI by blind detection of the first RNTI and the second RNTI), and determining that the downlink control channel corresponds to the PUSCH in the common uplink subframe.

Further, the terminal determines whether retransmission is needed according to whether the NDI in the downlink control channel is inverted relative to the NDI corresponding to the first transmission of the PUSCH-2. For example, if the NDI is the same as the NDI corresponding to the first transmission, the terminal determines that retransmission is required, and retransmits the PUSCH-2 according to the scheduling information (i.e., the indicated information such as the resource and the modulation and coding level) in the downlink control channel; if the NDI is different from the NDI corresponding to the first transmission, the terminal determines that the transmission is new data transmission, and starts to transmit new data according to the scheduling information, that is, it is determined that the PUSCH-2 transmission is successful, and retransmission is not required.

Example 3: still taking TDD uplink and downlink configuration 1 as an example, the PUSCH transmitted in the UpPTS in the special subframe 1 or 6 is assumed to use synchronous HARQ, and the ACK/NACK feedback information of the PUSCH transmitted in the special subframe m is obtained by detecting a downlink control channel carrying the ACK/NACK feedback information in subframe m + k, where k is assumed to be 4. The following is a description of the implementation from the base station side and the terminal side, respectively.

1. A base station side:

if the ACK/NACK feedback information is ACK, then: if the base station does not have new uplink data transmission to be scheduled, the downlink control channel using the uplink DCI format does not need to be sent to the terminal; if the base station has new uplink data transmission to be scheduled, the NDI is reversed relative to the NDI in the downlink control channel corresponding to the first transmission of the PUSCH-1 (i.e. set to different values, for example, the NDI corresponding to the first transmission is 0, the NDI in the downlink control channel is set to 1), and the downlink control channel carrying the NDI is sent to the terminal in subframe 5 (obtained according to m + k);

if the ACK/NACK feedback information is NACK, the base station sends a downlink control channel using an uplink DCI format to the terminal in subframe 5 (obtained according to m + k), and sets the NDI in the downlink control channel to the same value as the NDI in the downlink control channel corresponding to the first transmission of the PUSCH-1, for example, if the NDI corresponding to the first transmission is 0, the NDI in the downlink control channel is also set to 0.

Of course, if the ACK/NACK feedback information is NACK, if the base station wants to change the resource and configuration of PUSCH-2 retransmission through dynamic scheduling, the base station may also send a downlink control channel using an uplink DCI format in subframe 6, and set the NDI in the downlink control channel to the same value as the NDI in the downlink control channel corresponding to the first transmission of PUSCH-2, for example, if the NDI corresponding to the first transmission is 0, then the NDI in the downlink control channel is also set to 0.

It should be noted that, because the defined feedback subframes are different in position, the downlink control channels carrying the ACK/NACK feedback information and sent in the subframe 5 and the subframe 6 may be scrambled using the same DCI and the same RNTI, and the terminal may determine, by detecting the subframe of the downlink control channel, whether the PUSCH corresponding to the downlink control channel corresponds to the UpPTS or the normal uplink subframe.

2. A terminal side:

1) receiving scheduling information of a PUSCH-1 transmitted by a scheduling terminal in the UpPTS in the special subframe 1, and transmitting the PUSCH-1 in the UpPTS in the special subframe 1 according to the scheduling information; and determining to detect the downlink control channel using the uplink DCI format in the subframe 5 according to the m + k.

Specifically, if not, the terminal determines that the base station does not send the downlink control channel indicating retransmission, that is, determines that the PUSCH-1 transmission is successful and does not need retransmission;

if so, the terminal determines whether retransmission is needed according to whether the NDI in the downlink control channel is inverted relative to the NDI corresponding to the first transmission of the PUSCH-1. For example, if the NDI is the same as the NDI corresponding to the first transmission, the terminal determines that retransmission is required, and retransmits the PUSCH-1 according to the scheduling information (i.e., the indicated information such as the resource and the modulation and coding level) in the downlink control channel; for another example, if the NDI is different from the NDI corresponding to the first transmission, the terminal determines that the transmission is new data, and starts to transmit new data according to the scheduling information, that is, it is determined that the PUSCH-1 transmission is successful, and no retransmission is required.

2) Receiving scheduling information of a PUSCH-2 transmitted by a scheduling terminal in a common uplink subframe 2, and transmitting the PUSCH-2 in the uplink subframe 2 according to the scheduling information; according to k in Table 3 _PHICHDefining, determining that the PHICH of the PUSCH-2 is transmitted in the subframe 6, and determining the PHICH resource parameters thereof according to the minimum PRB index of the PUSCH-2 and the DMRS cyclic shift indication in the scheduling signaling

According to the parameterA PHICH carrying ACK/NACK feedback information of PUSCH-2 is detected in frame 6, and whether to retransmit is determined according to the ACK/NACK feedback information in the PHICH. If the ACK/NACK feedback information is ACK, the terminal channel does not need to retransmit; and if the ACK/NACK is NACK, the terminal retransmits the PUSCH-2 according to the same scheduling information transmitted for the first time.

Of course, the terminal may also detect the downlink control channel using the uplink DCI format in subframe 6; if not, taking the feedback information in the PHICH as the standard; and if so, determining whether retransmission is needed according to whether the NDI in the downlink control channel is inverted relative to the NDI corresponding to the first transmission of the PUSCH-2. For example, if the NDI is the same as the NDI corresponding to the first transmission, the terminal determines that retransmission is required, and retransmits PUSCH-2 according to the scheduling information (i.e., the indicated information such as the resource and modulation and coding level) in the downlink control channel; for another example, if the NDI is different from the NDI corresponding to the first transmission, the terminal determines that the transmission is new data, and starts to transmit new data according to the scheduling information, that is, it is determined that the PUSCH-2 transmission is successful, and no retransmission is required.

In the above embodiments, the dynamically scheduled PUSCH is taken as an example for explanation, and the method provided in the embodiments of the present invention is also applicable to the SPS PUSCH, where the only difference is that if the SPS PUSCH is used, the definition of NDI is not reversed, but 1 indicates retransmission, 0 indicates initial transmission, and the rest of the processing is the same as that of the dynamically scheduled PUSCH, and thus, no one-to-one example is described here.

In the above embodiments 1 and 2, taking the example that the PUSCH in the UpPTS uses asynchronous HARQ, the same applies to the PUSCH in the UpPTS using synchronous HARQ; if the ue is synchronous HARQ, the process is similar, and the only difference is that the subframe in which the base station side transmits the downlink control channel corresponding to the PUSCH in the UpPTS is not any subframe after the special subframe or any subframe within the set time after the special subframe, but is a fixed subframe position determined according to the subframe number of the UpPTS and the table 7, and when the terminal side detects the downlink control channel corresponding to the PUSCH in the UpPTS, the terminal side does not detect each subframe after the UpPTS or each subframe within the set time after the UpPTS, but detects the subframe number of the UpPTS and the fixed subframe position determined in the table 7.

The above method process flow may be implemented by a software program, which may be stored in a storage medium, and when the stored software program is called, the above method steps are performed.

Based on the same inventive concept, in the embodiment shown in fig. 4, there is provided a terminal, including:

a sending module 41, configured to send a physical uplink shared channel PUSCH in a special subframe m, where m is an integer;

a detecting module 42, configured to detect a downlink control channel using a DCI format after the special subframe m or in a subframe m + k including a downlink transmission resource, where k is a positive integer;

a determining module 43, configured to determine whether to retransmit the PUSCH transmitted in the special subframe m according to the downlink control channel.

In one possible embodiment, k is defined as follows:

For TDD uplink and downlink configuration 2, if m is 1 or 6, k is 2 or 7; or

For TDD uplink and downlink configuration 3, if m is 1, k is 7, 8 or 9; or

For TDD uplink and downlink configuration 4, if m is 1, k is 7 or 8; or

For TDD uplink and downlink configuration 5, if m is 1, k is 7; or

For TDD uplink and downlink configuration 6, if m is 6, k is 3, 4, 5, 9, or 10.

Wherein k is defined as follows:

for TDD uplink and downlink configuration 1, if m is 1 or 6, k is 4 or 9; or

For TDD uplink and downlink configuration 3, if m is 1, k is 4, 5, 6, or 10; or

Based on the same inventive concept, in the embodiment shown in fig. 5, another terminal is provided, which includes a transceiver 610 and at least one processor 600 connected to the transceiver 610, wherein:

the processor 600 is configured to read the program in the memory 620, and execute the following processes:

controlling the transceiver 610 to transmit PUSCH in a special subframe m, wherein m is an integer; detecting a downlink control channel using an uplink DCI format in a subframe containing downlink transmission resources after the special subframe m or in a subframe m + k, wherein k is a positive integer; determining whether to retransmit the PUSCH sent in the special subframe m according to the downlink control channel;

the transceiver 610 is used for receiving and transmitting data under the control of the processor 600.

Wherein in fig. 5, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 600, and various circuits of memory, represented by memory 620, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 610 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. For different user devices, the user interface 630 may also be an interface capable of interfacing with a desired device externally, including but not limited to a keypad, display, speaker, microphone, joystick, etc. The processor 600 is responsible for managing the bus architecture and general processing, and the memory 620 may store data used by the processor 600 in performing operations.

In this embodiment, the processor 600 reads the program in the memory 620 to execute the operations executed by the detection module 42 and the determination module 43 in the embodiment shown in fig. 4, and the transceiver 610 executes the operation executed by the sending module 41 in the embodiment shown in fig. 4 under the control of the processor 600, which is specifically referred to the related description in the embodiment shown in fig. 4 and is not repeated here.

Based on the same inventive concept, in the embodiment shown in fig. 6, there is provided a base station, including:

the scheduling module 61 is configured to schedule the terminal to send a physical uplink shared channel PUSCH in a special subframe m, where m is an integer;

a detecting module 62, configured to detect, in the special subframe m, a PUSCH transmitted by the terminal;

a processing module 63, configured to send a downlink control channel using an uplink downlink control information DCI format to the terminal in a subframe including a downlink transmission resource after the special subframe m or in a subframe m + k, where k is a positive integer, and the downlink control channel carries an indication field used for indicating whether or not the PUSCH in the special subframe m is retransmitted.

In one possible embodiment, k is defined as follows:

For TDD uplink and downlink configuration 2, if m is 1 or 6, k is 2 or 7; or

For TDD uplink and downlink configuration 3, if m is 1, k is 7, 8 or 9; or

For TDD uplink and downlink configuration 4, if m is 1, k is 7 or 8; or

for TDD uplink and downlink configuration 6, if m is 6, k is 3, 4, 5, 9, or 10.

Wherein k is defined as follows:

for TDD uplink and downlink configuration 1, if m is 1 or 6, k is 4 or 9; or

For TDD uplink and downlink configuration 3, if m is 1, k is 4, 5, 6, or 10; or

Based on the same inventive concept, in the embodiment shown in fig. 7, another base station is provided, which includes: a transceiver 510, and at least one processor 500 connected to the transceiver 510, wherein:

the processor 500 is configured to read the program in the memory 520 and execute the following processes:

through the transceiver 510, the scheduling terminal sends a physical uplink shared channel PUSCH in a special subframe m, where m is an integer; detecting a PUSCH sent by the terminal in the special subframe m; controlling the transceiver 510 to send a downlink control channel using an uplink downlink control information DCI format to the terminal in a subframe containing downlink transmission resources after the special subframe m or in a subframe m + k, where k is a positive integer, and the downlink control channel carries an indication field for indicating whether the PUSCH in the special subframe m is retransmitted;

the transceiver 510 is used for receiving and transmitting data under the control of the processor 500.

Where in fig. 7, the bus architecture may include any number of interconnected buses and bridges, with various circuits being linked together, particularly one or more processors represented by processor 500 and memory represented by memory 520. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 510 may be a number of elements, including a transmitter and a transceiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 500 is responsible for managing the bus architecture and general processing, and the memory 520 may store data used by the processor 500 in performing operations.

In this embodiment, the processor 500 reads the program in the memory 520, and executes the operations executed by the scheduling module 61, the detecting module 62, and the processing module 63 in the embodiment shown in fig. 6, which refer to the related descriptions in the embodiment shown in fig. 6, and are not described herein again.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.

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 for receiving feedback information of uplink transmission is characterized by comprising the following steps:

the terminal determines whether to retransmit the PUSCH sent in the special subframe m according to the downlink control channel;

the determining, by the terminal, whether to retransmit the PUSCH transmitted in the special subframe m according to the downlink control channel includes:

2. The method of claim 1, wherein k is defined as follows:

For TDD uplink and downlink configuration 2, if m is 1 or 6, k is 2 or 7; or

For TDD uplink and downlink configuration 3, if m is 1, k is 7, 8 or 9; or

For TDD uplink and downlink configuration 4, if m is 1, k is 7 or 8; or

For TDD uplink and downlink configuration 5, if m is 1, k is 7; or

For TDD uplink and downlink configuration 6, if m is 6, k is 3, 4, 5, 9, or 10.

3. The method according to claim 1, wherein the terminal determines whether the downlink control channel corresponds to a PUSCH transmitted in a special subframe according to the downlink control channel, including:

4. The method according to claim 3, wherein the terminal determines whether the downlink control channel corresponds to a PUSCH transmitted in a special subframe according to the size of the uplink DCI format used by the downlink control channel, and comprises:

wherein the first DCI size and the second DCI size are different.

5. The method according to claim 3, wherein the first indication field carries a hybrid automatic repeat request (HARQ) process number of a Physical Uplink Shared Channel (PUSCH) corresponding to the downlink control channel.

6. The method according to claim 3, wherein the terminal determines whether the downlink control channel corresponds to a PUSCH transmitted in a special subframe according to the RNTI used when the downlink control channel is scrambled, and the determining comprises:

wherein the first RNTI and the second RNTI are different.

7. The method according to claim 6, wherein if the first RNTI is shared by a plurality of terminals, after the terminal determines that the downlink control channel corresponds to a PUSCH transmitted in a special subframe, the method further comprises:

8. The method of claim 1, wherein the subframe m + k is different from a subframe for detecting a downlink control channel of a PUSCH transmitted in a corresponding normal subframe.

9. The method of claim 8, wherein k is defined as follows:

for TDD uplink and downlink configuration 1, if m is 1 or 6, k is 4 or 9; or

For TDD uplink and downlink configuration 3, if m is 1, k is 4, 5, 6, or 10; or

10. The method according to claim 8, wherein the terminal determines whether to retransmit the PUSCH transmitted in the special subframe m according to the downlink control channel, and comprises:

11. The method of claim 3, wherein the determining, by the terminal, whether the downlink control channel corresponds to a PUSCH transmitted in a special subframe according to a 2-bit uplink index (UL index) indication field in the downlink control channel comprises:

and when at least one of the LSB and the MSB of the ULindex is set to be 1, the terminal determines that the downlink control channel corresponds to the PUSCH transmitted in the common uplink subframe.

12. A method for sending feedback information of uplink transmission is characterized by comprising the following steps:

the base station sends a downlink control channel using an uplink downlink control information DCI format to the terminal in a subframe containing downlink transmission resources behind the special subframe m or in a subframe m + k, wherein k is a positive integer, and the downlink control channel carries an indication domain for indicating whether the PUSCH in the special subframe m is retransmitted or not, so that the terminal determines whether the PUSCH sent in the special subframe m is retransmitted or not according to the downlink control channel;

13. The method of claim 12, wherein k is defined as follows:

For TDD uplink and downlink configuration 2, if m is 1 or 6, k is 2 or 7; or

For TDD uplink and downlink configuration 3, if m is 1, k is 7, 8 or 9; or

For TDD uplink and downlink configuration 4, if m is 1, k is 7 or 8; or

for TDD uplink and downlink configuration 6, if m is 6, k is 3, 4, 5, 9, or 10.

14. The method according to claim 12 or 13, wherein the base station transmits a downlink control channel using an uplink DCI format to the terminal, comprising:

15. The method of claim 14, wherein the base station determines the size of the uplink DCI format used by the downlink control channel according to whether the downlink control channel corresponds to the PUSCH transmitted in the special subframe, the method comprising:

wherein the first DCI size and the second DCI size are different.

16. The method according to claim 14, wherein the first indication field carries a hybrid automatic repeat request (HARQ) process number of a Physical Uplink Shared Channel (PUSCH) corresponding to the downlink control channel.

17. The method according to claim 14, wherein the base station determines the RNTI used when the downlink control channel is scrambled according to whether the downlink control channel corresponds to the PUSCH transmitted in the special subframe, and the method includes:

wherein the first RNTI and the second RNTI are different.

18. The method of claim 14, wherein if the RNTI corresponding to the special subframe is shared by a plurality of terminals, further comprising:

19. The method of claim 12, wherein the subframe m + k is different from a subframe in which a downlink control channel corresponding to a PUSCH transmitted in a normal subframe is transmitted.

20. The method of claim 19, wherein k is defined as follows:

for TDD uplink and downlink configuration 1, if m is 1 or 6, k is 4 or 9; or

For TDD uplink and downlink configuration 3, if m is 1, k is 4, 5, 6, or 10; or

21. The method of claim 14, wherein the determining, by the base station, a value of a 2-bit uplink index (UL index) indication field in the downlink control channel according to whether the downlink control channel corresponds to a PUSCH transmitted in a special subframe comprises:

22. A terminal, characterized in that the terminal comprises:

a determining module, configured to determine whether to retransmit a PUSCH transmitted in the special subframe m according to the downlink control channel;

wherein the determining module is specifically configured to:

23. The terminal of claim 22, wherein k is defined as follows:

For TDD uplink and downlink configuration 2, if m is 1 or 6, k is 2 or 7; or

For TDD uplink and downlink configuration 3, if m is 1, k is 7, 8 or 9; or

For TDD uplink and downlink configuration 4, if m is 1, k is 7 or 8; or

For TDD uplink and downlink configuration 5, if m is 1, k is 7; or

For TDD uplink and downlink configuration 6, if m is 6, k is 3, 4, 5, 9, or 10.

24. The terminal of claim 23, wherein the determining module is specifically configured to:

25. The terminal of claim 24, wherein the determining module is specifically configured to:

26. The terminal of claim 24, wherein the first indication field carries a hybrid automatic repeat request HARQ process number of a PUSCH corresponding to the downlink control channel.

27. The terminal of claim 24, wherein the determining module is specifically configured to:

28. The terminal of claim 27, wherein if the first RNTI is shared by multiple terminals, the determining module is further configured to:

29. The terminal according to claim 22, wherein the subframe m + k is different from a subframe for detecting a downlink control channel of a PUSCH transmitted in a corresponding normal subframe.

30. The terminal of claim 29, wherein k is defined as follows:

for TDD uplink and downlink configuration 1, if m is 1 or 6, k is 4 or 9; or

For TDD uplink and downlink configuration 3, if m is 1, k is 4, 5, 6, or 10; or

31. The terminal of claim 29, wherein the determining module is specifically configured to:

32. The terminal of claim 24, wherein the determining module is specifically configured to:

and when at least one of the LSB and the MSB of the ULindex is set to be 1, determining that the downlink control channel corresponds to the PUSCH transmitted in the common uplink subframe.

33. A base station, characterized in that the base station comprises:

a processing module, configured to send, to the terminal, a downlink control channel using an uplink downlink control information DCI format in a subframe including a downlink transmission resource after the special subframe m or in a subframe m + k, where k is a positive integer, and the downlink control channel carries an indication field for indicating whether to retransmit a PUSCH in the special subframe m, so that the terminal determines whether to retransmit the PUSCH sent in the special subframe m according to the downlink control channel;

34. The base station of claim 33, wherein k is defined as follows:

For TDD uplink and downlink configuration 2, if m is 1 or 6, k is 2 or 7; or

For TDD uplink and downlink configuration 3, if m is 1, k is 7, 8 or 9; or

For TDD uplink and downlink configuration 4, if m is 1, k is 7 or 8; or

for TDD uplink and downlink configuration 6, if m is 6, k is 3, 4, 5, 9, or 10.

35. The base station according to claim 33 or 34, wherein the processing module is specifically configured to:

36. The base station of claim 35, wherein the processing module is specifically configured to:

37. The base station of claim 35, wherein the first indication field carries a hybrid automatic repeat request HARQ process number of a PUSCH corresponding to the downlink control channel.

38. The base station of claim 35, wherein the processing module is specifically configured to:

39. The base station of claim 35, wherein if the RNTI corresponding to the special subframe is shared by multiple terminals, the processing module is further configured to:

40. The base station of claim 33, wherein the subframe m + k is different from a subframe in which a downlink control channel corresponding to a PUSCH transmitted in a normal subframe is transmitted.

41. The base station of claim 40, wherein the k is defined as follows:

for TDD uplink and downlink configuration 1, if m is 1 or 6, k is 4 or 9; or

For TDD uplink and downlink configuration 3, if m is 1, k is 4, 5, 6, or 10; or

42. The base station of claim 35, wherein the processing module is specifically configured to:

if the downlink control channel corresponds to a PUSCH transmitted in a special subframe, setting the LSB and the MSB of the least significant bit of the ULindex to be 0;