CN104601303B

CN104601303B - The sending method and device and method of reseptance and device of ascending control information

Info

Publication number: CN104601303B
Application number: CN201310538441.2A
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: 2013-10-30
Filing date: 2013-11-04
Publication date: 2019-08-09
Anticipated expiration: 2033-11-04
Also published as: CN104601303A

Abstract

The invention discloses a kind of sending methods of ascending control information and device and method of reseptance and device, wherein, the sending method includes: that there are PUSCH in the case where PUSCH transmission, determined on the TDD carrier wave to be used for transmission UCI on the TDD carrier wave；UCI is generated, and passes through UCI described in the determining PUSCH transmission.By the present invention in that transmitting UCI with the PUSCH transmitted on TDD carrier wave, more efficiently information can be indicated using the domain DAI for being used to dispatch in TDD system in the PDCCH/EPDCCH of PUSCH, the rationally UCI bit number of effective control FDD and/or TDD carrier wave, efficiency of transmission is improved, avoids the problem that UCI occupies a large amount of signaling overheadss and thus bring adverse effect.

Description

Method and device for sending uplink control information, and method and device for receiving uplink control information

Technical Field

The present invention relates to the field of communications, and in particular, to a method and apparatus for transmitting Uplink Control Information (UCI), and a method and apparatus for receiving UCI.

Background

(1) Duplex system

The Long Term Evolution-advanced (Long Term Evolution-advanced, hereinafter abbreviated as LTE-a) system supports three duplex modes: full Frequency Division Duplex (FDD), Half Frequency Division Duplex (H-FDD), and Time Division Duplex (TDD). The main differences between the three duplexing modes are shown in fig. 1. FDD means that uplink and downlink transmission are performed on different carrier frequency bands, and both a base station and a terminal are allowed to receive and transmit signals at the same time, so that FDD equipment needs two sets of transceivers and duplex filters. The difference between H-FDD and FDD is that the terminal does not allow simultaneous transmission and reception of signals, i.e. the H-FDD base station is the same as the FDD base station, but the H-FDD terminal can be simplified compared to the FDD terminal, only one transceiver is reserved and the cost of the duplexer is saved. TDD is a scheme in which uplink and downlink transmissions are performed in the same carrier frequency band, and a base station/terminal transmits/receives or receives/transmits channels at different times. Both the base station and the terminal of TDD have only one transceiver.

(2) An Acknowledgement/negative Acknowledgement (ACK/NACK) feedback scheme in the existing system is as follows:

in the existing LTE-a system, a User Equipment (User Equipment, hereinafter abbreviated as UE) can use only one type of carrier (the carrier is an FDD carrier or a TDD carrier) for data transmission in one subframe. When the UE simultaneously operates on multiple carriers, only multiple FDD Carrier Aggregation (hereinafter, abbreviated CA) or multiple TDD Carrier Aggregation is supported. Therefore, ACK/NACK transmission is defined for either FDD or TDD systems.

In the LTE FDD system, the UE receives downlink data in subframe n-4, and feeds back a signaling indicating whether the data on the downlink subframe needs to be retransmitted or not, i.e., ACK/NACK, in uplink subframe n. When FDD carrier aggregation is performed, ACK/NACK information corresponding to a plurality of downlink carriers in a subframe n-4 is fed back in an uplink subframe n at the same time. When ACK/NACK is transmitted on a Physical Uplink Shared Channel (PUSCH), a Downlink Assignment Index (DAI) field is not defined in a Physical Downlink Control Channel (PDCCH) for scheduling PUSCH transmission/an Enhanced Physical Downlink Control Channel (EPDCCH), and the UE determines the number of ACK/NACK feedback bits to be transmitted on the PUSCH according to the number of aggregated carriers and a transmission mode of each carrier.

In an LTE TDD system, a UE may feed back ACK/NACK information corresponding to M downlink subframes in a same uplink subframe, and specifically, the UE feeds back ACK/NACK information of downlink data detected in a downlink subframe n-K in the uplink subframe n, where K belongs to K, M is the number of index elements K in a set K in table 1, and M of different TDD carriers and different uplink subframes may be the same or different, depending on whether TDD uplink-downlink configurations used by different TDD carriers are the same.

TABLE 1TDD Downlink related K value K: { K₀,k₁,…k_M-1}

At this time, the radio frames are arranged in sequence, that is, if the last subframe in the radio frame a is K, the first subframe in the radio frame a +1 is K +1, table 1 only gives the case of K for each uplink subframe by taking one radio frame as an example, where n-K < 0 indicates the downlink subframe in the previous radio frame.

In the TDD system, if the TDD uplink-Downlink configuration or the uplink reference TDD uplink-Downlink configuration of the carrier where the PUSCH is transmitted is configured to be other than configuration 0 (such as configurations 1, 2, 3, 4, 5, and 6), a DAI field exists in a Downlink Control Information format (hereinafter, abbreviated as DCI format) used for scheduling PDCCH/EPDCCH of the PUSCH, otherwise, the DAI field does not exist. If the current PUSCH has a corresponding PDCCH/EPDCCH and a DAI domain exists in the PDCCH/EPDCCH, an ACK/NACK feedback sequence transmitted on the PUSCH can be determined according to the indication information of the DAI domain; at the moment, the base station knows how many downlink subframes are scheduled in advance, and the number of downlink subframes fed back by the UE can be flexibly controlled through the DAI, so that the transmission efficiency is improved; if the current PUSCH has the corresponding PDCCH/EPDCCH but no DAI domain exists in the PDCCH/EPDCCH or the current PUSCH does not have the corresponding PDCCH/EPDCCH, the ACK/NACK feedback sequence transmitted on the PUSCH can be determined only according to all downlink subframe numbers for performing ACK/NACK feedback on the current uplink subframe, at the moment, as the base station possibly schedules only a small part of subframes in the subframes, the ACK/NACK also needs to be fed back for the subframe UE which is not scheduled, the transmission resources are wasted; especially when the value of M is large, if the base station actually schedules only 1 or a few subframes on the aggregated carrier, the resource waste is serious.

In addition, in the existing FDD or TDD CA system, only UCI transmission on one PUSCH is supported, and if information such as ACK/NACK, CSI, etc. exists in the current subframe and the UE aggregates multiple carriers to operate, it is necessary to select one carrier and transmit the information in the PUSCH of the selected carrier. Since ACK/NACK is transmitted on the PUSCH in a puncturing mapping manner, that is, part of data information is punctured for transmitting ACK/NACK information, too much invalid ACK/NACK feedback (i.e., feedback information generated for downlink subframes/carriers that are not scheduled) may also affect the reception of uplink data.

(3)TDD-FDD Joint Operation

In order to further improve the spectrum utilization rate to meet the continuously enhanced throughput and capacity requirements, a TDD-FDD Joint Operation is proposed. Possible implementations of TDD-FDD Joint Operation discussed so far are: TDD-FDD CA scheme, Dual Connectivity (Dual Connectivity) scheme, enhanced Dual mode (Dual mode) scheme, and the like. Regardless of the implementation manner, when the UE downlink can simultaneously work on the FDD and TDD carriers, the UE needs to simultaneously feed back UCI of the FDD and TDD carriers in one uplink subframe.

When UCI is transmitted on a PUSCH, a DAI domain does not exist in a PDCCH/EPDCCH (physical downlink control channel/physical downlink control channel) for scheduling the PUSCH defined in an FDD (frequency division duplex) system, if the UCI is transmitted on the PUSCH on an FDD carrier, the feedback bit number of ACK/NACK on the PUSCH cannot be effectively controlled, particularly for the ACK/NACK feedback information of the TDD carrier, more bits may exist as feedback information generated on a downlink subframe without scheduling information, so that the influence of the ACK/NACK on data during PUSCH transmission can be enlarged, the transmission efficiency of the ACK/NACK is also reduced, and the transmission efficiency of the system is further influenced.

Aiming at the problem that how to reasonably select PUSCH to transmit UCI under the TDD-FDD Joint Operation scene, an effective solution is not provided at present.

Disclosure of Invention

Aiming at the problem that the PUSCH transmission UCI cannot be reasonably selected under the TDD-FDD Joint Operation scene in the related technology, the invention provides a method and a device for sending uplink control information, and a method and a device for receiving uplink control information, which can enable UE to reasonably send ACK/NACK feedback information under the TDD-FDD Joint Operation scene and can avoid resource waste.

The technical scheme of the invention is realized as follows:

according to an aspect of the present invention, there is provided a method for transmitting uplink control information UCI, in which UCI is transmitted when a UE is configured with at least one TDD carrier and at least one FDD carrier.

The sending method comprises the following steps: determining that one PUSCH on a TDD carrier is used for transmitting UCI under the condition that PUSCH transmission exists on the TDD carrier; generating UCI, and transmitting the UCI through the determined PUSCH.

And if the plurality of TDD carriers include a main carrier, determining the PUSCH on the main carrier as the PUSCH for transmitting the UCI.

Optionally, when there is PUSCH transmission on each of the multiple TDD carriers, selecting among the multiple TDD carriers according to a predetermined policy, and determining the PUSCH on the selected TDD carrier as a PUSCH for transmitting UCI; or,

and under the condition that PUSCH transmission exists on the plurality of TDD carriers and the plurality of TDD carriers do not comprise the main carrier, selecting the plurality of TDD carriers according to a preset strategy, and determining the PUSCH on the selected TDD carrier as the PUSCH for transmitting the UCI.

Wherein the predetermined policy may include at least one of:

selecting the TDD carrier with the largest or smallest carrier number and selecting the carrier with the appointed number.

Further, there is one of a TDD up-down configuration of at least one of the TDD carriers of the PUSCH transmission, or an uplink reference TDD up-down configuration 1, 2, 3, 4, 5, 6.

In addition, there is a corresponding PDCCH/EPDCCH for PUSCH on at least one of the TDD carriers for which PUSCH transmission exists.

The downlink control information format DCI format used by the PDCCH/EPDCCH is TDD DCI format 0/4 defined in LTE Rel-10/11.

In addition, the PDCCH/EPDCCH used to schedule PUSCH is transmitted on either a TDD carrier or an FDD carrier.

And, in case that PDCCH/EPDCCH is transmitted on a TDD carrier, the carrier on which PDCCH/EPDCCH is transmitted is the same as or different from the carrier on which PUSCH is transmitted.

And when generating the UCI, determining the UCI required to be generated according to the indication information of the DAI domain in the PDCCH/EPDCCH corresponding to the determined PUSCH.

Optionally, the indication information of the DAI field is used to indicate a scheduling condition of the TDD carrier and the FDD carrier, and/or to indicate whether ACK/NACK feedback information corresponding to the TDD carrier and/or the FDD carrier needs to be sent; or,

the indication information of the DAI domain is used for indicating and determining the information of an ACK/NACK feedback information sequence which needs to be sent in the current uplink subframe on the TDD carrier; or,

and the DAI domain is used for indicating information used for determining the number of downlink sub-frames needing ACK/NACK feedback in the current uplink sub-frame on an FDD carrier and a TDD carrier.

According to another aspect of the present invention, there is provided a method for receiving UCI in Uplink Control Information (UCI) in a case where a UE is configured with at least one TDD carrier and at least one FDD carrier.

The receiving method comprises the following steps: when the PUSCH is scheduled to be transmitted on the TDD carrier, determining that one PUSCH on the TDD carrier is used for transmitting UCI; receiving the UCI through the determined PUSCH.

When a plurality of PUSCHs are scheduled to be transmitted on a plurality of TDD carriers, if a main carrier is included in the plurality of TDD carriers, determining the PUSCH on the main carrier as a PUSCH for transmitting UCI.

In addition, optionally, when a plurality of PUSCHs are scheduled to be transmitted on a plurality of TDD carriers, selecting among the plurality of TDD carriers according to a predetermined policy, and determining a PUSCH on the selected TDD carrier as a PUSCH for transmitting UCI; or,

and under the condition that a plurality of PUSCHs are scheduled to be transmitted on a plurality of TDD carriers and the plurality of TDD carriers do not comprise the main carrier, selecting from the plurality of TDD carriers according to a preset strategy, and determining the PUSCH on the selected TDD carrier as the PUSCH for transmitting the UCI.

Wherein the predetermined policy may include at least one of:

Further, one of a TDD uplink-downlink configuration of at least one of the TDD carriers on which PUSCH transmission is scheduled, or an uplink reference TDD uplink-downlink configuration 1, 2, 3, 4, 5, 6.

In addition, there is a corresponding PDCCH/EPDCCH for PUSCH on at least one of the TDD carriers on which PUSCH transmission is scheduled.

Wherein, under the condition that the PDCCH/EPDCCH is transmitted in a TDD carrier, the carrier for transmitting the PDCCH/EPDCCH is the same as or different from the carrier for transmitting the PUSCH.

In addition, optionally, the scheduling condition of the TDD carrier and the FDD carrier is indicated through indication information of a DAI field in a PDCCH/EPDCCH for scheduling a PUSCH, and/or whether ACK/NACK feedback information corresponding to the TDD carrier and/or the FDD carrier needs to be sent is indicated; or,

the method comprises the steps of indicating and determining information of an ACK/NACK feedback information sequence which needs to be sent in a current uplink subframe on a TDD carrier wave through indication information of a DAI domain in a PDCCH/EPDCCH used for scheduling a PUSCH; or,

According to still another aspect of the present invention, there is provided a transmitting apparatus of uplink control information UCI, for transmitting UCI in a case where a UE is configured with at least one TDD carrier and at least one FDD carrier.

The transmission device includes: the device comprises a determining module, a transmitting module and a receiving module, wherein the determining module determines that one PUSCH on a TDD carrier is used for transmitting UCI under the condition that PUSCH transmission exists on the TDD carrier; and the sending module is used for generating the UCI and transmitting the UCI through the determined PUSCH.

According to another aspect of the present invention, there is provided a receiving apparatus of uplink control information UCI, for receiving UCI in a case where a UE is configured with at least one TDD carrier and at least one FDD carrier.

The receiving apparatus includes: a determining module, configured to determine that one PUSCH on a TDD carrier is used for transmitting UCI when the PUSCH is scheduled for transmission on the TDD carrier; a receiving module, configured to receive the UCI through the determined PUSCH.

The UCI is transmitted by using the PUSCH transmitted on the TDD carrier, so that DAI domain indication information in a PDCCH/EPDCCH for scheduling the PUSCH in a TDD system can be more effectively utilized, the UCI bit number of the FDD and/or TDD carrier is reasonably and effectively controlled, the transmission efficiency is improved, and the problem that the UCI occupies a large amount of signaling overhead and the adverse effect caused by the problem are avoided.

Drawings

FIG. 1 is a diagram illustrating a comparison of FDD, H-FDD and TDD transmission modes in the prior art;

fig. 2 is a flowchart of a method for transmitting uplink control information according to an embodiment of the present invention;

fig. 3 is a flowchart of a method for receiving uplink control information according to an embodiment of the present invention;

fig. 4 is a diagram of example 1 of a transmission and reception scheme of uplink control information according to an embodiment of the present invention;

fig. 5 is a diagram of example 2 of a transmission and reception scheme of uplink control information according to an embodiment of the present invention;

fig. 6 is a diagram of example 3 of a transmission and reception scheme of uplink control information according to an embodiment of the present invention;

fig. 7 is a diagram of example 4 of a transmission and reception scheme of uplink control information according to an embodiment of the present invention;

fig. 8 is a block diagram of an apparatus for transmitting uplink control information according to an embodiment of the present invention;

fig. 9 is a block diagram of an apparatus for receiving uplink control information according to an embodiment of the present invention;

fig. 10 is a block diagram of a computer capable of implementing the technical solution according to the present invention.

Detailed Description

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 only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments that can be derived by one of ordinary skill in the art from the embodiments given herein are intended to be within the scope of the present invention.

In a TDD-FDD Joint Operation scenario, an FDD carrier or a TDD carrier may both be a host carrier, a UE supporting TDD-FDD Joint Operation has the capability of accessing a legacy (legacy) FDD single-mode carrier and a legacy TDD single-mode carrier, legacy FDD UEs and FDD UEs supporting TDD-FDD Joint Operation may reside on and connect to an FDD carrier participating in TDD-FDD Joint Operation, and legacy TDD UEs and TDD UEs supporting TDD-FDD Joint Operation may reside on and connect to a TDD carrier participating in TDD-FDD Joint Operation. Since UCI of multiple carriers needs to be transmitted on one PUSCH, aggregation of multiple carriers may result in an increase in UCI signaling overhead.

In order to solve the problem that UCI signaling overhead cannot be effectively controlled in a scenario where the UE is configured with both a TDD carrier and an FDD carrier, the present invention proposes a solution, and the following describes an embodiment of the present invention in detail.

According to an embodiment of the present invention, there is provided a method for transmitting Uplink Control Information (UCI) in a case where a UE is configured with at least one TDD carrier and at least one FDD carrier.

As shown in fig. 2, a method for transmitting uplink control information according to an embodiment of the present invention includes:

step S201, under the condition that PUSCH transmission exists on a TDD carrier, determining that one PUSCH on the TDD carrier is used for transmitting UCI;

step S203, generating UCI, and transmitting the UCI through the determined PUSCH.

When selecting a carrier for transmitting UCI, one PUSCH on a TDD carrier may be determined as a PUSCH for transmitting UCI by means of various ways.

In one embodiment, in the case where there is PUSCH transmission on each of the plurality of TDD carriers, if a primary carrier is included in the plurality of TDD carriers, the PUSCH on the primary carrier may be determined as the PUSCH for transmitting UCI.

In another embodiment, whether there is PUSCH transmission on the primary carrier may not be considered, and at this time, if there is PUSCH transmission on all the multiple TDD carriers, a selection may be made among the multiple TDD carriers according to a predetermined policy, and the PUSCH on the selected TDD carrier may be determined as the PUSCH for transmitting UCI. In another embodiment, if there is PUSCH transmission on all of the plurality of TDD carriers and the plurality of TDD carriers do not include the primary carrier, selecting among the plurality of TDD carriers according to a predetermined policy, and determining PUSCH on the selected TDD carrier as PUSCH for transmitting UCI.

The predetermined policy may be for selecting the carrier according to various parameters of the carrier, for example, the predetermined policy may include at least one of: selecting the TDD carrier with the largest or smallest carrier number and selecting the carrier with the appointed number. In addition, with the aid of the above predetermined policy, the TDD carrier may also be selected according to other parameters of the carrier, for example, the carrier may be selected to use the PUSCH on the carrier for transmitting UCI according to one or a combination of carrier priority of the carrier, bandwidth of the carrier, frequency of the carrier, and relevant parameters of the PUSCH transmitted on the carrier (including transmission bandwidth and/or modulation coding level, etc.).

In addition, when determining that one PUSCH on at least one TDD carrier is used for transmitting UCI, in addition to the PUSCH of the primary carrier may be preferentially selected or selected according to a predetermined policy, the alternative TDD carrier may further satisfy at least one of the following conditions:

one of TDD uplink-downlink configurations of at least one of TDD carriers with PUSCH transmission or an uplink reference TDD uplink-downlink configuration 1, 2, 3, 4, 5, 6; the PUSCH on at least one of the TDD carriers where PUSCH transmission exists has a corresponding PDCCH/EPDCCH.

Specifically, the DCI format used for scheduling PDCCH/EPDCCH of PUSCH on a TDD carrier is TDD DCI format 0/4 defined in the lte rel-10/11 system; and/or the DCI format used for scheduling PDCCH/EPDCCH of PUSCH on the FDD carrier is FDD DCI format 0/4 defined in LTE Rel-10/11 system. In addition, the DCI format used for scheduling the PDCCH/EPDCCH on the PUSCH on the FDD carrier may also be a newly defined format, or a DCI format obtained by performing partial bit field modification or extension on an original DCI format, for example, a DAI field may be added to the original DCI format of the FDD to obtain a new DCI format.

In addition, the PDCCH/EPDCCH used for scheduling the PUSCH for transmitting the finally determined UCI may be transmitted on a TDD carrier or an FDD carrier. When the PDCCH/EPDCCH is transmitted on a TDD carrier, the carrier on which the PDCCH/EPDCCH is transmitted may be the same as the carrier on which the PUSCH is transmitted (i.e., local carrier scheduling) or different from the carrier on which the PDCCH/EPDCCH is transmitted (i.e., cross-carrier scheduling).

It can be seen that the scheme of the present invention can select one PUSCH transmitted on a TDD carrier for transmitting UCI, when one of the following conditions is satisfied: when there is a PUSCH transmission on a TDD carrier; when there is PUSCH transmission on a TDD carrier and a TDD uplink-downlink configuration of the TDD carrier or an uplink reference TDD uplink-downlink configuration of the TDD carrier configures one of configurations 1, 2, 3, 4, 5, 6; when there is PUSCH transmission on the TDD carrier, and the TDD uplink-downlink configuration or the uplink reference TDD uplink-downlink configuration of the TDD carrier configures one of 1, 2, 3, 4, 5, and 6, and the PUSCH has a corresponding PDCCH/EPDCCH.

In addition, when generating UCI, UCI to be generated may be determined according to indication information of a DAI domain in PDCCH/EPDCCH corresponding to the determined PUSCH.

In one embodiment, the indication information of the DAI field is used for indicating the scheduling condition of the TDD carrier and the FDD carrier, and/or for indicating whether ACK/NACK feedback information corresponding to the TDD carrier and/or the FDD carrier needs to be transmitted. Since the indication information of the DAI field can indicate the scheduling situation and/or whether ACK/NACK feedback information corresponding to the TDD carrier and/or the FDD carrier needs to be transmitted, the UE can determine which carriers of the ACK/NACK feedback information need to be transmitted according to the indication information of the DAI field, thereby avoiding the problem that the UE unnecessarily transmits a large amount of ACK/NACK feedback information.

For example, the DAI field may include K bits of information, 2 of the K bits of information^K2 of a state indicating FDD and/or TDD carrier respectively^KDifferent combined scheduling cases, and/or different combined ACK/NACK feedback information states indicating FDD and TDD carriers.

When indicating the scheduling case, the following may be referred to:

in the method (1), the DAI field contains at least K bits of information, and for each 1 bit of information in the at least K bits of information, 2 different states of the bit of information are used to indicate whether scheduling exists for 1 carrier corresponding to the bit of information in K carriers configured for the terminal. That is, K bits correspond to K carriers one-to-one, for example, when one bit is 0, it may indicate that there is scheduling for the corresponding carrier, and when the bit is 1, it indicates that there is no scheduling for the corresponding carrier, and vice versa.

In the mode (2), the DAI field contains at least K bits of information, and for each 1 bit of information in the at least K bits of information, 2 different states of the bit of information are used to indicate whether scheduling exists in 1 carrier group corresponding to the bit of information in predetermined K carrier groups. Specifically, K bits correspond to K carrier groups one to one, for example, when one bit is 0, it may indicate that there is scheduling in the corresponding carrier group, and when the bit is 1, it indicates that there is no scheduling in the corresponding carrier group. Each carrier group may include only a TDD carrier or an FDD carrier, or both a TDD carrier and an FDD carrier.

In the mode (3), each bit in the K-bit information of the DAI field can be 1 or 0, so that the K-bit information can be combined into 2^KDifferent states, each of which may correspond to a scheduling scenario, where there are a total of 2 for K carriers if each carrier may or may not be scheduled^KA different scheduling case, such that 2K different states obtained by K bits of information can be compared with 2^KDifferent scheduling conditions are in one-to-one correspondence, thereby indicating specific scheduling conditionsThe method is described.

Mode (4), the DAI field contains at least K bits of information, 2 of the at least K bits of information^KThe different states are respectively used for indicating whether the scheduled combination information exists in each carrier group of the preset K carrier groups. Similarly, in this scheme, each bit in the K-bit information can be 1 or 0, so that the K-bit information can be combined into 2^KDifferent states, each of which may correspond to a scheduling scenario, where there are a total of 2 for K carrier groups if all carriers in each carrier group may or may not be scheduled^KA different scheduling case, such that 2K different states obtained by K bits of information can be compared with 2^KThe different scheduling situations are in one-to-one correspondence, thereby indicating specific scheduling situations.

In indicating whether ACK/NACK feedback information needs to be transmitted for FDD carriers and/or TDD carriers, the above manner may also be referred to, except that each bit or a combination of all bits corresponds to whether scheduling exists in a carrier or a carrier group, but corresponds to whether ACK/NACK feedback information corresponding to the carrier or the carrier group needs to be transmitted.

The above K may be a natural number, and may be 1, 2, or another number, for example.

In another embodiment, the indication information of the DAI field is used to indicate information for determining an ACK/NACK feedback information sequence (including the feedback bit number of ACK/NACK and/or specific feedback information) that needs to be sent in the current uplink subframe on the TDD carrier; in general, the physical meaning of the DAI indication domain is information indicating the number of downlink subframes required to perform ACK/NACK feedback in the current uplink subframe on the TDD carrier; specifically, the information may be as shown in table 4; the information is generally used for determining the number of downlink subframes that need to perform ACK/NACK feedback in the current uplink subframe on the TDD carrier when the UE is configured to use PUCCH format 3, and determining according to which ACK/NACK mapping table a specific feedback information sequence that needs to perform ACK/NACK feedback in the current uplink subframe on the TDD carrier is generated when the UE is configured to use PUCCH format 1b with channel selection (different mapping tables also correspond to different feedback subframe numbers).

At this time, for the TDD carrier, determining the number of feedback sub-frames according to the DAI indication information, and generating ACK/NACK feedback information according to the number of the feedback sub-frames; and for the FDD carrier, determining the number of downlink subframes for performing ACK/NACK feedback on the current uplink subframe according to the feedback time sequence of the FDD carrier, and generating ACK/NACK feedback information according to the number of the subframes.

In another embodiment, the indication information of the DAI field is used to indicate information for determining the number of downlink subframes that need to perform ACK/NACK feedback in the current uplink subframe on FDD and TDD carriers; for example, the DAI field contains at least K bits of information, at least 2 of the K bits of information^KThe different states are respectively used for indicating information used for determining the number of downlink subframes needing ACK/NACK feedback in the current uplink subframe on the FDD carrier and the TDD carrier. K may be a natural number, and may be 1, 2, or another number, for example.

In addition, the UCI generated by the terminal may only include UCI of an FDD carrier, may only include UCI of a TDD carrier, and may include both UCI of an FDD carrier and UCI of a TDD carrier.

According to an embodiment of the present invention, there is also provided a method for receiving UCI in a case where a UE is configured with at least one TDD carrier and at least one FDD carrier.

As shown in fig. 3, a method for receiving UCI according to an embodiment of the present invention includes:

step S301, when the PUSCH is scheduled to be transmitted on the TDD carrier, determining that one PUSCH on the TDD carrier is used for transmitting UCI;

step S303, receiving UCI through the determined PUSCH.

When determining a carrier for transmitting UCI, one PUSCH on a TDD carrier may be determined as a PUSCH for transmitting UCI by means of various ways for subsequent reception of UCI.

When determining that one PUSCH on at least one TDD carrier is used for transmitting UCI, in addition to the PUSCH of the primary carrier being preferentially selected or selected according to a predetermined policy, the alternative TDD carrier may further satisfy at least one of the following conditions: one of TDD uplink-downlink configurations of at least one of the TDD carriers on which PUSCH transmission is scheduled, or an uplink reference TDD uplink-downlink configuration configuring 1, 2, 3, 4, 5, 6; the PUSCH on at least one of the TDD carriers on which PUSCH transmission is scheduled has a corresponding PDCCH/EPDCCH.

The downlink control information format DCI format used by the PDCCH/EPDCCH is TDD DCI format 0/4 defined in LTE Rel-10/11. Specifically, the DCI format used for scheduling PDCCH/EPDCCH of PUSCH on a TDD carrier is TDD DCI format 0/4 defined in LTE Rel-10/11 system; and/or the DCI format used for scheduling PDCCH/EPDCCH of PUSCH on the FDD carrier is FDD DCIformat 0/4 defined in LTE Rel-10/11 system. In addition, the DCI format used for scheduling the PDCCH/EPDCCH on the PUSCH on the FDD carrier may also be a newly defined format, or a DCI format obtained by performing partial bit field modification or extension on an original DCI format, for example, a DAI field may be added to the original DCI format of the FDD to obtain a new DCI format.

In addition, the PDCCH/EPDCCH used for scheduling the determined PUSCH may be transmitted on a TDD carrier or an FDD carrier. Wherein, when the PDCCH/EPDCCH is transmitted in a TDD carrier, the carrier for transmitting the PDCCH/EPDCCH is the same as or different from the carrier for transmitting the PUSCH.

It can be seen that the scheme of the present invention can determine one PUSCH transmitted on a TDD carrier as a PUSCH for transmitting UCI and receive UCI on the PUSCH when one of the following conditions is satisfied:

when the base station schedules a PUSCH transmission to the terminal on a TDD carrier; when the base station schedules PUSCH transmission to the terminal on a TDD carrier and the TDD uplink-downlink configuration of the TDD carrier or the uplink reference TDD uplink-downlink configuration configures one of 1, 2, 3, 4, 5 and 6; when the base station schedules PUSCH transmission to the terminal on a TDD carrier, and the TDD uplink-downlink configuration or the uplink reference TDD uplink-downlink configuration of the TDD carrier configures one of 1, 2, 3, 4, 5 and 6, and the PUSCH has a corresponding PDCCH/EPDCCH.

In addition, the DAI field in the PDCCH/EPDCCH for scheduling PUSCH described above may be used to indicate various information.

In one embodiment, the indication information of the DAI field in the PDCCH/EPDCCH for scheduling PUSCH is used to indicate the scheduling condition of the TDD carrier and the FDD carrier, and/or to indicate whether ACK/NACK feedback information corresponding to the TDD carrier and/or the FDD carrier needs to be transmitted. Since the indication information of the DAI field can indicate the scheduling situation and/or whether ACK/NACK feedback information corresponding to the TDD carrier and/or the FDD carrier needs to be transmitted, the UE can determine which carriers of the ACK/NACK feedback information need to be transmitted according to the indication information of the DAI field, thereby avoiding the problem that the UE unnecessarily transmits a large amount of ACK/NACK feedback information. The specific indication method has been described previously and will not be repeated here.

In another embodiment, the indication information of the DAI field in the PDCCH/EPDCCH for scheduling PUSCH is used to indicate information for determining an ACK/NACK feedback information sequence that needs to be transmitted in the current uplink subframe on the TDD carrier. At this time, for the TDD carrier, determining the number of feedback sub-frames according to the DAI indication information, and generating ACK/NACK feedback information according to the number of the sub-frames; and for the FDD carrier, determining the number of downlink subframes for performing ACK/NACK feedback on the current uplink subframe according to the feedback time sequence of the FDD carrier, and generating ACK/NACK feedback information according to the number of the subframes.

The technical solution of the present invention will be described below with reference to specific examples.

Example 1:

as shown in fig. 4, the UE is configured with one FDD carrier and one TDD carrier, and there is one PUSCH transmission on each of the FDD and TDD carriers in the current subframe.

In this example, since there is PUSCH on the TDD carrier, the UE will select PUSCH on the TDD carrier for transmitting UCI of the FDD carrier and the TDD carrier;

specifically, the UCI generation method is as follows:

if the selected PUSCH has the corresponding PDCCH/EPDCCH and the PDCCH/EPDCCH contains a DAI domain, determining ACK/NACK information in UCI transmitted by the UE on the PUSCH according to the indication information of the DAI domain:

(method 1): the DAI indicates scheduling conditions or ACK/NACK feedback conditions of FDD carriers and TDD carriers, taking 1-bit DAI as an example, and the specific indication manner may be shown in table 2, but is not limited to the corresponding relationship of table 2, at this time, the DAI field includes 1-bit information, when the state of the DAI bit information is 0, it indicates that both FDD and TDD carriers are not scheduled, and when the state of the DAI bit information is 1, it indicates that at least one FDD carrier and/or at least one TDD carrier is scheduled; and vice versa.

TABLE 2

In addition, the manner of indicating the scheduling conditions of the FDD carrier and the TDD carrier by the DAI can be shown in table 3, taking 2-bit DAI as an example, at this time, when the DAI domain information can indicate the following 4 different conditions:

(1) when the DAI bit information state is 00, indicating that both the FDD carrier and the TDD carrier have no scheduling or do not need to feed back ACK/NACK, not generating ACK/NACK at the moment, and not transmitting ACK/NACK in the current PUSCH;

(2) when the DAI bit information state is 01, indicating that scheduling exists only in FDD carriers or ACK/NACK (acknowledgement/negative acknowledgement) needs to be fed back, only generating ACK/NACK for each FDD carrier, and when the FDD carriers use an FDD feedback time sequence, specifically generating feedback information for the FDD carriers according to an ACK/NACK generation method which is defined by an LTE Rel-10/11FDD system and transmitted on a PUSCH (physical uplink shared channel) and transmitting the feedback information in the current PUSCH;

(3) when the DAI bit information state is 10, indicating that only TDD carriers have scheduling or need to feed back ACK/NACK, at this time, generating ACK/NACK only for each TDD carrier, and when the TDD carriers use an FDD feedback timing sequence, specifically, generating feedback information for the TDD carrier according to an ACK/NACK generation method defined by an LTE Rel-10/11FDD system and transmitted on a PUSCH, and transmitting the feedback information in a current PUSCH, and in particular, when a subframe corresponding to a current uplink subframe on the TDD carrier determined according to the FDD feedback timing sequence is uplink, not feeding back ACK/NACK for the TDD carrier; when the TDD carrier uses a TDD feedback timing sequence, feedback information (including using different PUCCH transmission schemes and adopting the same/different TDD uplink and downlink configuration conditions) may be generated for the TDD carrier according to an ACK/NACK generation method defined by the LTE Rel-10/11TDD system and transmitted on a PUSCH, and transmitted in a current PUSCH;

(4) when the DAI bit information state is 11, indicating that both FDD carriers and TDD carriers have scheduling or need to feed back ACK/NACK, respectively generating ACK/NACK for the FDD carriers and the TDD carriers according to the above mode, and cascading the ACK/NACK of each FDD carrier and each TDD carrier together according to a predetermined mode for transmission in the current PUSCH;

TABLE 3

In fact, the correspondence between the states of the DAI bit information and the indication contents shown in tables 2 and 3 may be adjusted, and a greater number of bit information may be used to correspond to a greater number of indication contents, so as to more accurately indicate the specific scheduling conditions of each FDD carrier/carrier group and/or each TDD carrier/carrier group, and/or more accurately indicate whether ACK/NACK feedback information needs to be sent to each FDD carrier/carrier group and/or each TDD carrier/carrier group.

(method 2): the DAI indication is used to determine information of an actual number of downlink subframes that need to perform ACK/NACK feedback in a current uplink subframe on a TDD carrier, and taking 2-bit DAI as an example, a specific indication manner may be shown in table 4, but is not limited to the corresponding relationship in table 4, at this time: for a TDD carrier, determining a feedback subframe number according to information indicated by the DAI, and further determining ACK/NACK according to the determined feedback subframe number, wherein the specific method is the same as the ACK/NACK generation method transmitted on the PUSCH defined in the LTE-A Rel-10/11TDD system; for an FDD carrier, determining the ACK/NACK of the FDD carrier according to the number of downlink subframes for performing ACK/NACK feedback on a current uplink subframe on the FDD carrier determined based on the ACK/NACK feedback time sequence of the FDD carrier, and if the ACK/NACK of the FDD carrier and the TDD carrier exist at the same time, cascading the FDD carrier and the TDD carrier together according to a preset mode and transmitting the FDD carrier and the TDD carrier in a current PUSCH;

TABLE 4

DAI bit information state	Indicating the content
		00	1
01	2
		10	3
11	4

(method 3): the DAI indicates information for determining the number of actual downlink subframes that need to perform ACK/NACK feedback in the current uplink subframe on FDD and TDD carriers, and taking 2-bit DAI as an example, the specific indication mode may be as shown in table 4, but is not limited to the corresponding indication mode of table 4Relationship, assume that the information indicated by DAI in Table 4 isAt this time: for each FDD and TDD carrier, a feedback subframe number may be determined according to the information indicated by the DAI, and further an ACK/NACK may be determined according to the feedback subframe number, where a specific method is similar to an ACK/NACK generation method for transmission on a PUSCH defined in the LTE-a Rel-10/11TDD system, for example: when the UE is configured to employ PUCCH format 3 scheme on PUCCH: when all the carriers in the FDD and TDD carriers meet the condition that the number M of downlink subframes for performing ACK/NACK feedback in the current uplink subframe on the carrier determined according to the ACK/NACK feedback time sequence relation of each carrier does not exceed 4, for each FDD and TDD carrier, the number M of the downlink subframes for performing ACK/NACK feedback in the current uplink subframe on the carrier determined according to the ACK/NACK feedback time sequence relation of the carrier c can be used_cAndthe minimum value of the carrier is used as the number of downlink subframes actually needing ACK/NACK feedback in the current subframe of the carrier, namelyAccording to whichThe downlink subframe number indicated by the value generates ACK/NACK feedback information for the carrier; at least one carrier exists in all carriers in FDD and TDD carriers, when the number M of downlink sub-frames corresponding to ACK/NACK feedback in the current uplink sub-frame on the carrier determined according to the ACK/NACK feedback time sequence relation of the carrier exceeds 4, for each FDD and TDD carrier, determining the number of downlink sub-frames on each carrierWherein, U_cM corresponding to ACK/NACK feedback in uplink subframe n on each carrier c_cPDSCH received in a downlink subframe set and PDCCH/EPDC indicating downlink semi-persistent scheduling (SPS) resource releaseTotal number of CH, U being U of all carriers_cMaximum value of (d); when the UE is configured on the PUCCH using PUCCH format 1b with channel selection scheme, the ACK/NACK feedback information may also be generated in a manner defined in the case where M of all subframes in PUCCH format 3 does not exceed 4, or according to the methodDetermines the ACK/NACK feedback information sequence of the corresponding FDD carrier and TDD carrier transmitted by the UE on the PUSCH (i.e. according to the value ofDetermining a corresponding ACK/NACK mapping table according to the value, and generating ACK/ANCK feedback information according to the mapping table); in particular, the above process may further include, when receivingAnd when the UE does not receive the PDSCH and the PDCCH for indicating the release of the downlink SPS resources in the downlink subframe which carries out ACK/NACK feedback in the current uplink subframe, the UE determines that the ACK/NACK is not fed back on the PUSCH in the current uplink subframe. In the above process, if there are ACK/NACK of FDD and TDD carriers at the same time, they are concatenated together in a predetermined manner and transmitted in the current PUSCH;

in addition, taking 1-bit DAI as an example, 2 different states of 1-bit DAI are respectively used for indicating information for determining the number of downlink subframes needing ACK/NACK feedback in the current uplink subframe on FDD and TDD carriers asThe specific indication manner may be shown in table 5, but is not limited to the corresponding relationship of table 5; for each FDD carrier and each TDD carrier, the carrier determined according to the ACK/NACK feedback timing relation of the carrier c may correspond to the number M of downlink subframes for ACK/NACK feedback in the current uplink subframe_cAndthe most important ofThe small value is used as the number of downlink subframes needing ACK/NACK feedback in the current subframe of the actual carrierNamely, it isAccording toThe downlink subframe number indicated by the value generates ACK/NACK feedback information for the carrier; the ACK/NACK generation scheme is also applicable to a case where the UE is configured to use PUCCH format 3 on PUCCH or configured to use PUCCH format 1b with channel selection;

TABLE 5

In addition, taking 1-bit DAI as an example, 2 different states of 1-bit DAI are respectively used for indicating information for determining the number of downlink subframes needing ACK/NACK feedback in the current uplink subframe on FDD and TDD carriers asThe specific indication manner may be shown in table 6, but is not limited to the corresponding relationship of table 6; for each FDD carrier and each TDD carrier whenThen, the number M of downlink sub-frames corresponding to ACK/NACK feedback in the current uplink sub-frame on the carrier determined according to the ACK/NACK feedback time sequence relation of the carrier c can be determined_cAndthe minimum value of the carrier is used as the number of downlink subframes actually needing ACK/NACK feedback in the current subframe of the carrier, namelyAccording to whichThe downlink sub-frame number shown by the value generates ACK/NACK feedback information for the carrier wave whenAnd then, determining not to send ACK/NACK feedback information to the FDD and TDD carriers. The ACK/NACK generation method is also applicable to a case where the UE is configured to adopt PUCCH format 3 on PUCCH or configured to adopt PUCCH format 1b with channel selection;

TABLE 6

In addition, if the selected PUSCH does not have a corresponding PDCCH/EPDCCH, or a corresponding PDCCH/EPDCCH exists and the PDCCH/EPDCCH does not include a DAI domain, that is, there is no DAI domain in these two cases, and the UE cannot obtain DAI indication information, then determining ACK/NACK of the FDD carrier according to the downlink subframe number for performing ACK/NACK feedback on the current uplink subframe on the FDD carrier determined based on the ACK/NACK feedback timing of the FDD carrier, and determining ACK/NACK of the TDD carrier according to the downlink subframe number for performing ACK/NACK feedback on the current uplink subframe on the TDD carrier determined based on the ACK/NACK feedback timing of the TDD carrier, and concatenating the ACK/NACK of the FDD carrier and the TDD carrier together in a predetermined manner for transmission in the current PUSCH;

in addition, if the UCI that the UE needs to transmit in the current uplink subframe further includes periodic CSI information, the periodic CSI is generated for the FDD carrier and the TDD carrier according to the feedback period and the related configuration parameters of the periodic CSI of the FDD carrier and the TDD carrier, respectively, and if a plurality of carriers (including the FDD carrier and/or the TDD carrier) have periodic CSI at the same time, the carriers are concatenated together in a predetermined manner and transmitted in the current PUSCH.

Example 2:

as shown in fig. 5, the UE is configured with 2 FDD carriers and 2 TDD carriers; there is one PUSCH transmission on each carrier in the current subframe. It is assumed that the predetermined policy for determining the PUSCH is to determine the PUSCH of the TDD carrier with the smallest carrier number as the PUSCH for transmitting UCI.

At this time, due to the existence of PUSCH on multiple TDD carriers, PUSCH on the TDD carrier with the smallest carrier number is selected according to the carrier number, that is, PUSCH on TDD carrier 1 (with the smallest TDD carrier number) is selected by the UE for transmitting UCI of the FDD carrier and the TDD carrier. The specific UCI generation method is the same as example 1, and is not described herein again;

example 3:

as shown in fig. 6, the UE is configured with one FDD carrier and 2 TDD carriers and TDD carriers; there is a PUSCH transmission on each of FDD and TDD carriers in the current subframe, and the uplink and downlink configuration of TDD carrier 1 or the reference uplink and downlink configuration configures 0, and the uplink and downlink configuration of TDD carrier 2 or the reference uplink and downlink configuration configures one of configurations 1, 2, 3, 4, 5, and 6.

At this time, since there is PUSCH on the TDD carrier, and the uplink and downlink configuration of the TDD carrier 2 or the reference uplink and downlink configuration configures one of 1, 2, 3, 4, 5, and 6 (that is, when there is corresponding PDCCH/EPDCCH on the PUSCH on the carrier, there is a DAI domain in the PDCCH/EPDCCH), the UE may select PUSCH on the TDD carrier 2 for transmitting UCI of the FDD carrier and the TDD carrier;

since the uplink and downlink configuration of the selected TDD carrier or the reference uplink and downlink configuration is configured with one of configurations 1, 2, 3, 4, 5, and 6, therefore:

when the selected PUSCH has a corresponding PDCCH/EPDCCH, and a DAI domain always exists in the PDCCH/EPDCCH, the specific ACK/NACK generation method is the same as that of the case where the DAI domain exists in example 1, and is not described herein again;

when the selected PUSCH does not have the corresponding PDCCH/EPDCCH, the DAI domain cannot be obtained, and the specific ACK/NACK generation method is the same as that in example 1 without the DAI domain, which is not described herein again.

In addition, if the UCI that the UE needs to transmit in the current uplink subframe further includes periodic CSI information, the specific generation method is the same as that described in example 1, and is not repeated here.

Example 4:

as shown in fig. 7, the UE is configured with 2 FDD carriers and 2 TDD carriers; there is a PUSCH transmission on each carrier in the current subframe, and the uplink and downlink configuration of TDD carrier 1 and carrier 2 or the reference uplink and downlink configuration configures one of 1, 2, 3, 4, 5, 6, and there is no corresponding PDCCH/EPDCCH (i.e. semi-persistent scheduling PUSCH) for the PUSCH on TDD carrier 1, and there is a corresponding PDCCH/EPDCCH for the PUSCH on TDD carrier 2.

At this time, since there is PUSCH on the TDD carrier, and the uplink and downlink configuration of the TDD carrier 2 or the reference uplink and downlink configuration configures one of 1, 2, 3, 4, 5, and 6, and there is corresponding PDCCH/EPDCCH on the PUSCH on the TDD carrier 2 (i.e. there is corresponding PDCCH/EPDCCH on the PUSCH on the carrier and there is a DAI domain in the PDCCH/EPDCCH), the UE may select the PUSCH on the TDD carrier 2 for transmitting UCI of the FDD carrier and the TDD carrier.

Since the selected PUSCH always has a corresponding PDCCH/EPDCCH and a DAI domain always exists in the PDCCH/EPDCCH, the specific ACK/NACK generation method is the same as that in example 1, which is not described herein again;

if the UCI that the UE needs to transmit in the current uplink subframe further includes periodic CSI information, the specific generation method is the same as the method described in example 1, and details are not repeated here.

In addition, in the above-mentioned examples, only the case that the primary carrier of the terminal is the TDD carrier is exemplified in some embodiments, actually, the technical solution of the present invention is not only applicable to the case that the TDD carrier is the primary carrier, but also applicable to the case that the FDD carrier is the primary carrier, and also applicable to a mode that UCI of FDD and TDD is transmitted on only one PUSCH; in addition, the present invention does not limit the carrier wave for transmitting the ACK/NACK feedback information, and actually, the scheme of the present invention is applicable to the way that the ACK/NACK can be transmitted on different PUSCHs respectively (for example, UCI of an FDD carrier is transmitted in one PUSCH of an FDD carrier, UCI of a TDD carrier is transmitted in one PUSCH of a TDD carrier).

According to an embodiment of the present invention, there is also provided a device for sending uplink control information UCI, configured to send UC when the UE is configured with at least one TDD carrier and at least one FDD carrier.

As shown in fig. 8, a transmitting apparatus according to an embodiment of the present invention includes:

a determining module 81, configured to determine that one PUSCH on a TDD carrier is used for transmitting UCI when there is PUSCH transmission on the TDD carrier;

and a transmitting module 82, configured to generate UCI and transmit the UCI through the determined PUSCH.

According to an embodiment of the present invention, there is also provided a device for receiving UCI, where the UE is configured with at least one TDD carrier and at least one FDD carrier.

As shown in fig. 9, a receiving apparatus according to an embodiment of the present invention includes:

a determining module 91, configured to determine, when PUSCH transmission on a TDD carrier is scheduled, that one PUSCH on the TDD carrier is used for transmitting UCI;

a receiving module 92, configured to receive UCI through the determined PUSCH.

The apparatuses shown in fig. 8 and 9 may also refer to the manner described above to determine the PUSCH for transmitting UCI, and indicate the scheduling condition of the carrier/carrier group through the DAI field, or whether the corresponding ACK/NACK feedback information needs to be fed back, and the specific procedures thereof have been described and will not be repeated here.

In summary, with the above technical solution of the present invention, the PUSCH transmitted on the TDD carrier is used to transmit the UCI, so that the DAI domain indication information in the PDCCH/EPDCCH used for scheduling the PUSCH in the TDD system can be more effectively utilized, the UCI bit number of the FDD and/or TDD carrier can be reasonably and effectively controlled, the transmission efficiency can be improved, and the problem that the UCI occupies a large amount of signaling overhead and adverse effects caused by the problem can be avoided.

While the principles of the invention have been described in connection with specific embodiments thereof, it should be noted that it will be understood by those skilled in the art that all or any of the steps or elements of the method and apparatus of the invention may be implemented in any computing device (including processors, storage media, etc.) or network of computing devices, in hardware, firmware, software, or any combination thereof, which may be implemented by those skilled in the art using their basic programming skills after reading the description of the invention.

Thus, the objects of the invention may also be achieved by running a program or a set of programs on any computing device. The computing device may be a general purpose device as is well known. The object of the invention is thus also achieved solely by providing a program product comprising program code for implementing the method or the apparatus. That is, such a program product also constitutes the present invention, and a storage medium storing such a program product also constitutes the present invention. It is to be understood that the storage medium may be any known storage medium or any storage medium developed in the future.

According to another embodiment of the present invention, there is also provided a storage medium (which may be ROM, RAM, a hard disk, a removable memory, etc.), having embedded therein a computer program for UCI transmission in a case where a UE is configured with at least one TDD carrier and at least one FDD carrier, the computer program having code segments configured to perform the following steps: determining that one PUSCH on a TDD carrier is used for transmitting UCI under the condition that PUSCH transmission exists on the TDD carrier; generating UCI, and transmitting the UCI through the determined PUSCH.

According to another embodiment of the present invention, there is also provided a storage medium (which may be ROM, RAM, a hard disk, a removable memory, etc.), having embedded therein a computer program for UCI reception in case that a UE is configured with at least one TDD carrier and at least one FDD carrier, the computer program having code segments configured to perform the following steps: when the PUSCH is scheduled to be transmitted on the TDD carrier, determining that one PUSCH on the TDD carrier is used for transmitting UCI; receiving the UCI through the determined PUSCH.

According to another embodiment of the present invention, there is also provided a computer program having a code segment configured to perform the following UCI transmission steps in case that a UE is configured with at least one TDD carrier and at least one FDD carrier: determining that one PUSCH on a TDD carrier is used for transmitting UCI under the condition that PUSCH transmission exists on the TDD carrier; generating UCI, and transmitting the UCI through the determined PUSCH.

According to another embodiment of the present invention, there is also provided a computer program having a code segment configured to perform the following UCI receiving steps in case that a UE is configured with at least one TDD carrier and at least one FDD carrier: when the PUSCH is scheduled to be transmitted on the TDD carrier, determining that one PUSCH on the TDD carrier is used for transmitting UCI; receiving the UCI through the determined PUSCH.

In the case where the embodiment of the present invention is implemented by software and/or firmware, a program constituting the software is installed from a storage medium or a network to a computer having a dedicated hardware structure, such as a general-purpose computer 1000 shown in fig. 10, which is capable of executing various functions and the like when various programs are installed.

In fig. 10, a central processing module (CPU)1001 executes various processes in accordance with a program stored in a Read Only Memory (ROM)1002 or a program loaded from a storage section 1008 to a Random Access Memory (RAM) 1003. The RAM 1003 also stores data necessary when the CPU 1001 executes various processes and the like, as necessary. The CPU 1001, ROM 1002, and RAM 1003 are connected to each other via a bus 1004. An input/output interface 1005 is also connected to the bus 1004.

The following components are connected to the input/output interface 1005: an input section 1006 including a keyboard, a mouse, and the like; an output section 1007 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker and the like; a storage portion 1008 including a hard disk and the like; and a communication section 1009 including a network interface card such as a LAN card, a modem, and the like. The communication section 1009 performs communication processing via a network such as the internet.

A driver 1010 is also connected to the input/output interface 1005 as necessary. A removable medium 1011 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1010 as needed, so that a computer program read out therefrom is installed into the storage portion 1008 as needed.

In the case where the above-described series of processes is realized by software, a program constituting the software is installed from a network such as the internet or a storage medium such as the removable medium 1011.

It should be understood by those skilled in the art that such a storage medium is not limited to the removable medium 1011 shown in fig. 10, in which the program is stored, distributed separately from the apparatus to provide the program to the user. Examples of the removable medium 1011 include a magnetic disk (including a floppy disk (registered trademark)), an optical disk (including a compact disc read only memory (CD-ROM) and a Digital Versatile Disc (DVD)), a magneto-optical disk (including a Mini Disk (MD) (registered trademark)), and a semiconductor memory. Alternatively, the storage medium may be the ROM 1002, a hard disk included in the storage section 1008, or the like, in which programs are stored and which are distributed to users together with the apparatus including them.

It is further noted that in the apparatus and method of the present invention, it is apparent that each component or step can be decomposed and/or recombined. These decompositions and/or recombinations are to be regarded as equivalents of the present invention. Also, the steps of executing the series of processes described above may naturally be executed chronologically in the order described, but need not necessarily be executed chronologically. Some steps may be performed in parallel or independently of each other.

Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention as defined by the appended claims. Furthermore, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

Claims

1. A method for transmitting Uplink Control Information (UCI) when a UE is configured with at least one TDD carrier and at least one FDD carrier, the method comprising:

determining that one PUSCH on the TDD carrier is used for transmitting UCI under the condition that PUSCH transmission exists on the TDD carrier;

generating UCI, and transmitting the UCI through the determined PUSCH.

2. The transmission method according to claim 1, wherein in case there is a PUSCH transmission on each of a plurality of TDD carriers, if a primary carrier is included in the plurality of TDD carriers, the PUSCH on the primary carrier is determined as the PUSCH for transmitting UCI.

3. The transmission method of claim 1,

under the condition that PUSCH transmission exists on a plurality of TDD carriers, selecting from the plurality of TDD carriers according to a preset strategy, and determining the PUSCH on the selected TDD carrier as a PUSCH for transmitting UCI; or,

and under the condition that PUSCH transmission exists on a plurality of TDD carriers and the plurality of TDD carriers do not comprise the main carrier, selecting from the plurality of TDD carriers according to a preset strategy, and determining the PUSCH on the selected TDD carrier as the PUSCH for transmitting the UCI.

4. The transmission method of claim 3, wherein the predetermined policy comprises at least one of:

5. The transmitting method according to claim 1, wherein the TDD uplink-downlink configuration of at least one of the TDD carriers with PUSCH transmission or the uplink reference TDD uplink-downlink configuration is one of configurations 1, 2, 3, 4, 5, and 6.

6. The transmission method of claim 1, wherein there is a corresponding PDCCH/EPDCCH for PUSCH on at least one of the TDD carriers with PUSCH transmission.

7. The transmission method of claim 6, wherein a downlink control information format (DCI format) used by the PDCCH/EPDCCH is a TDD DCI format 0/4 defined in LTE Rel-10/11.

8. The transmission method of claim 1, wherein the PDCCH/EPDCCH used for scheduling the PUSCH is transmitted on a TDD carrier or an FDD carrier.

9. The transmitting method of claim 8, wherein in the case that the PDCCH/EPDCCH is transmitted on a TDD carrier, the carrier on which the PDCCH/EPDCCH is transmitted is the same as or different from the carrier on which the PUSCH is transmitted.

10. The transmission method as claimed in claim 1, wherein when generating the UCI, the UCI to be generated is determined according to the determined indication information of the DAI field in the PDCCH/EPDCCH corresponding to the PUSCH.

11. The transmission method of claim 10,

the indication information of the DAI domain is used for indicating the scheduling condition of the TDD carrier and the FDD carrier and/or indicating whether ACK/NACK feedback information corresponding to the TDD carrier and/or the FDD carrier needs to be sent; or,

the indication information of the DAI domain is used for indicating and determining information of an ACK/NACK feedback information sequence which needs to be sent in a current uplink subframe on the TDD carrier; or,

12. A method for receiving uplink control information, UCI, when a UE is configured with at least one TDD carrier and at least one FDD carrier, the method comprising:

when PUSCH transmission on a TDD carrier is scheduled, determining that one PUSCH on the TDD carrier is used for transmitting UCI;

receiving the UCI through the determined PUSCH.

13. The receiving method according to claim 12, wherein when a plurality of PUSCHs are scheduled for transmission on a plurality of TDD carriers, if a primary carrier is included in the plurality of TDD carriers, a PUSCH on the primary carrier is determined as a PUSCH for transmitting UCI.

14. The receiving method according to claim 12, wherein when a plurality of PUSCHs are scheduled for transmission on a plurality of TDD carriers, then selecting among the plurality of TDD carriers according to a predetermined policy, determining a PUSCH on the selected TDD carrier as a PUSCH for transmitting UCI; or,

under the condition that a plurality of PUSCHs are scheduled to be transmitted on a plurality of TDD carriers and the plurality of TDD carriers do not comprise a main carrier, selecting from the plurality of TDD carriers according to a preset strategy, and determining the PUSCH on the selected TDD carrier as the PUSCH for transmitting UCI.

15. The receiving method according to claim 14, characterized in that the predetermined strategy comprises at least one of:

16. The receiving method according to claim 12, wherein the TDD uplink-downlink configuration or the uplink reference TDD uplink-downlink configuration of at least one of the TDD carriers with scheduled PUSCH transmission is one of configurations 1, 2, 3, 4, 5, 6.

17. The receiving method of claim 12, wherein there is a corresponding PDCCH/EPDCCH for PUSCH on at least one of the TDD carriers on which PUSCH transmission is scheduled.

18. The receiving method of claim 17, wherein a downlink control information format DCI format used by the PDCCH/EPDCCH is a TDD DCI format 0/4 defined in LTE Rel-10/11.

19. The receiving method according to claim 12, wherein the PDCCH/EPDCCH used for scheduling the PUSCH is transmitted on a TDD carrier or an FDD carrier.

20. The receiving method according to claim 19, wherein in case the PDCCH/EPDCCH is transmitted on a TDD carrier, the carrier on which the PDCCH/EPDCCH is transmitted is the same or different from the carrier on which the PUSCH is transmitted.

21. The receiving method according to claim 12, wherein the scheduling condition of the TDD carrier and the FDD carrier is indicated by indication information of a DAI field in a PDCCH/EPDCCH for scheduling a PUSCH, and/or the ACK/NACK feedback information corresponding to the TDD carrier and/or the FDD carrier needs to be sent is indicated; or,

indicating and determining information of an ACK/NACK feedback information sequence which needs to be sent in a current uplink subframe on the TDD carrier wave through indicating information of a DAI domain in a PDCCH/EPDCCH for scheduling a PUSCH; or,

22. An apparatus for transmitting uplink control information, UCI, when a UE is configured with at least one TDD carrier and at least one FDD carrier, the apparatus comprising:

a determining module, configured to determine that one PUSCH on the TDD carrier is used for transmitting UCI, when there is a PUSCH transmission on the TDD carrier;

and the sending module is used for generating UCI and transmitting the UCI through the determined PUSCH.

23. An apparatus for receiving Uplink Control Information (UCI), where the UCI is received when a UE is configured with at least one TDD carrier and at least one FDD carrier, the apparatus comprising:

a determining module, configured to determine that one PUSCH on a TDD carrier is used for transmitting UCI when a PUSCH is scheduled for transmission on the TDD carrier;

a receiving module, configured to receive the UCI through the determined PUSCH.