Uplink control information transmission method and device

Abstract

The present invention relates to the field of wireless communication technology, and in particular to a terminal, an access network device, a wireless communication system, and an uplink control information transmission method. In a terminal, a receiving module receives downlink scheduling information of a downlink subframe F(i, j), a preconfigured downlink subframe set M where the downlink subframe F(i, j) is located is divided into N preconfigured downlink subframe subsets, the number of bits of a hybrid automatic repeat request-acknowledgement HARQ-ACK required to be fed back for each downlink subframe in a preconfigured downlink subframe subset is a predetermined value, and the number of bits of HARQ-ACK required to be fed back for any downlink subframe in different preconfigured downlink subframe subsets is different; a processing module generates a HARQ-ACK codebook according to the reception of downlink data, and generates uplink control information after encoding; a sending module sends uplink control information, and can support the situation where the number of HARQ-ACK bits required to be fed back for downlink subframes on different aggregated carriers is different.

Description

Technical Field

[0001] The present invention relates to the field of wireless communication technology, and in particular to a terminal, access network equipment, a wireless communication system and an uplink control information transmission method. Background Art

[0002] In the Long Term Evolution (LTE) system, downlink data transmission adopts the Hybrid Automatic Repeat reQuest (HARQ) mechanism. After the user equipment (UE) receives the physical downlink shared channel (PDSCH), if the reception is correct, the UE feeds back an ACKnowledgement (ACK) on the physical uplink control channel (PUCCH). If it is incorrect, the UE feeds back a non-ACKnowledgement (NACK) on the PUCCH. ACK and NACK are collectively referred to as HARQ-ACK.

[0003] The LTE system supports carrier aggregation (CA) technology, that is, the access network equipment configures multiple carriers to one UE to increase the UE's data rate. Figure 1 As shown, the access network device uses carrier 1 and carrier 2 to perform downlink data transmission with UE1, and the base station uses carrier 1, carrier 3, and carrier 5 to perform downlink data transmission with UE2.

[0004] As shown in Table 1, in the current LTE system, there are multiple data channel transmission modes.

[0005] Table 1. Transmission mode of data channel PDSCH in LTE system

[0006]

[0007] Among them, the PDSCH scheduled in a downlink subframe under transmission modes 1, 2, 5, 6, and 7 is a single transmission block, that is, each downlink subframe corresponds to 1 HARQ-ACK bit; and the PDSCH scheduled in a downlink subframe under transmission modes 3, 4, 8, and 9 can be two transmission blocks, that is, each downlink subframe corresponds to 2 HARQ-ACK bits.

[0008] At present, in CA mode, the PDSCH transmission mode of each aggregated carrier is usually the same, so the number of HARQ-ACK bits that the UE needs to feedback for each downlink subframe on each aggregated carrier is the same. However, with the development of technology, the PDSCH transmission mode of each aggregated carrier may be different. For example, currently a maximum of 5 carriers are supported for aggregation, and in the future, 10 carriers, 20 carriers, or even up to 32 carriers may be aggregated. At this time, the PDSCH transmission mode between the aggregated carriers may be different, and the number of HARQ-ACK bits that need to be fed back for downlink subframes on different carriers is different. At present, the UE does not support the situation where the number of HARQ-ACK bits that need to be fed back for downlink subframes on different aggregated carriers is different. Summary of the invention

[0009] In view of this, an embodiment of the present invention provides a terminal, an access network device, a wireless communication system and an uplink control information transmission method, so as to support the situation where different numbers of HARQ-ACK bits required to be fed back by different aggregated carriers are different.

[0010] In a first aspect, an embodiment of the present invention provides a terminal, including:

[0011] A receiving module, configured to receive downlink scheduling information of a downlink subframe F(i, j), wherein the downlink subframe F(i, j) is a subframe in a pre-configured downlink subframe set M corresponding to an uplink subframe;

[0012] Wherein, F(i,j) represents the downlink subframe j on the carrier i configured for the terminal, i∈C, C is the set of all carriers configured for the terminal for downlink data transmission, j∈K, K is the set of downlink subframes corresponding to the uplink subframe;

[0013] The preconfigured downlink subframe set M is divided into N preconfigured downlink subframe subsets, N is an integer greater than or equal to 2, the number of bits of the hybrid automatic repeat request-acknowledgement HARQ-ACK that needs to be fed back for each downlink subframe in a preconfigured downlink subframe subset is a predetermined value, and the number of bits of the HARQ-ACK that needs to be fed back for any downlink subframe in different preconfigured downlink subframe subsets is different;

[0014] The receiving module is further used to: receive downlink data scheduled by the downlink scheduling information in the downlink subframe F(i,j);

[0015] a processing module, configured to generate a HARQ-ACK codebook according to the reception status of the downlink data received by the receiving module on the downlink subframe F(i, j) and the number of bits of the HARQ-ACK that needs to be fed back for the downlink subframe F(i, j), wherein the HARQ-ACK codebook includes at least one subcodebook, the at least one subcodebook corresponds one-to-one to at least one preconfigured downlink subframe subset, the at least one preconfigured downlink subframe subset is at least one preconfigured downlink subframe subset of the N preconfigured downlink subframe subsets, and the at least one preconfigured downlink subframe subset is a subset of downlink subframes including the downlink data scheduled by the terminal receiving the downlink scheduling information; and generate uplink control information by encoding the HARQ-ACK codebook;

[0016] A sending module is used to send the uplink control information on the uplink subframe.

[0017] In combination with the first aspect, in a first possible implementation manner, the HARQ-ACK included in the subcodebook is the HARQ-ACK of the downlink subframe scheduled in the pre-configured downlink subframe subset corresponding to the subcodebook, but does not include the HARQ-ACK of the downlink subframe that is not scheduled in the pre-configured downlink subframe subset corresponding to the subcodebook.

[0018] In combination with the first possible implementation manner of the first aspect, in a second possible implementation manner,

[0019] The receiving module is further configured to, before the processing module generates the HARQ-ACK codebook, receive first indication information corresponding to the downlink subframe F(i, j) included in each preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, wherein the first indication information is used to indicate: in a setting order, a sequence number of the downlink subframe F(i, j) in the preconfigured downlink subframe subset including the downlink subframe F(i, j) scheduled in the downlink subframe subset;

[0020] The processing module is specifically configured to generate the at least one sub-codebook in the following manner:

[0021] For a preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of HARQ-ACK bits that need to be fed back for the downlink subframe F(i, j), generate a subcodebook corresponding to the one preconfigured downlink subframe subset according to the sequence number indicated by the first indication information.

[0022] In combination with the second possible implementation manner of the first aspect, in a third possible implementation manner,

[0023] The receiving module is further used to: before the processing module generates the HARQ-ACK codebook, receive second indication information corresponding to each pre-configured downlink subframe subset in the at least one pre-configured downlink subframe subset, wherein the second indication information is used to indicate:

[0024] the total number of downlink subframes with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i,j); or

[0025] The total number of downlink subframes with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i,j) and downlink subframes before the downlink subframe with subframe number j; or

[0026] the total number of scheduled downlink subframes in the preconfigured downlink subframe subset including the downlink subframe F(i,j); or

[0027] the total number of transport blocks transmitted in the downlink subframe with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i,j); or

[0028] The total number of transport blocks transmitted in the downlink subframe with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i,j) and in the downlink subframes before the downlink subframe with subframe number j; or

[0029] a total number of transport blocks transmitted in the downlink subframes scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i, j);

[0030] The processing module is specifically used for:

[0031] For a preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of HARQ-ACK bits that need to be fed back for the downlink subframe F(i, j), generate a subcodebook corresponding to the one preconfigured downlink subframe subset according to the sequence number indicated by the first indication information and the second indication information.

[0032] In combination with the second possible implementation manner of the first aspect, in a fourth possible implementation manner,

[0033] The receiving module is further configured to: before the processing module generates the HARQ-ACK codebook, receive second indication information corresponding to the downlink subframe F(i, j) included in each pre-configured downlink subframe subset in the at least one pre-configured downlink subframe subset;

[0034] Among them, in the preconfigured downlink subframe subset including the downlink subframe F(i, j), the values ​​of the second indication information corresponding to the scheduled downlink subframes that are ranked in the last 1, 2, ..., X-1, and X in the setting order are AX-1, AX-2, ..., A1, A0 respectively, and the values ​​of the second indication information corresponding to the remaining downlink subframes are A0 respectively, and the remaining downlink subframes are the downlink subframes in the preconfigured downlink subframe subset including the downlink subframe F(i, j), except for the scheduled downlink subframes ranked in the last 1, 2, ..., X-1, X, and the AX-1, AX-2, ..., A1 and A0 are different values; or

[0035] In the preconfigured downlink subframe subset including the downlink subframe F(i, j), the values ​​of the second indication information corresponding to the scheduled downlink subframes in the preconfigured downlink subframe subset sorted in the reverse order of the setting order are respectively cyclic values ​​of {AX-1, AX-2, ..., A1, A0}; or

[0036] In the preconfigured downlink subframe subset including the downlink subframe F(i,j), the values ​​of the second indication information corresponding to the downlink subframe with subframe number j that is ranked in the last 1, 2, ..., X-1 according to the setting order, and X are respectively AX-1, AX-2, ..., A1, A0, and the values ​​of the second indication information corresponding to the remaining downlink subframes with subframe number j are respectively A0, and the remaining downlink subframes with subframe number j are the downlink subframes with subframe number j in the preconfigured downlink subframe subset including the downlink subframe F(i,j), except the downlink subframe with subframe number j that is ranked in the last 1, 2, ..., X-1, and X are scheduled, and the AX-1, AX-2, ..., A1 and A0 are different values; or

[0037] The values ​​of the second indication information corresponding to the downlink subframe with the scheduled subframe number j in the pre-configured downlink subframe subset sorted in the reverse order of the setting order are cyclic values ​​of {AX-1, AX-2, ..., A1, A0} respectively;

[0038] Wherein, X is a positive integer greater than 1;

[0039] The processing module is specifically used for:

[0040] For a preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of HARQ-ACK bits that need to be fed back for the downlink subframe F(i, j), generate a subcodebook corresponding to the one preconfigured downlink subframe subset according to the sequence number indicated by the first indication information and the second indication information.

[0041] In combination with any one of the second to fourth possible implementations of the first aspect, in a fifth possible implementation, the setting sequence includes:

[0042] The order between carriers and subframes, and the order between carriers and subframes;

[0043] The order between the carrier and the subframe includes: first the carrier and then the subframe or first the subframe and then the carrier;

[0044] The carrier order includes: carrier index from small to large, or carrier index from large to small;

[0045] The subframe sequence includes: subframe timing from front to back, or subframe timing from back to front.

[0046] In combination with the first aspect, or any one of the first to fifth possible implementations of the first aspect, in a sixth possible implementation, the at least one subcodebook is cascaded in the HARQ-ACK codebook.

[0047] In a second aspect, an embodiment of the present invention provides an access network device, including:

[0048] A sending module, configured to send downlink scheduling information of a downlink subframe F(i, j) to a terminal, and send downlink data scheduled by the downlink scheduling information to the terminal in the downlink subframe F(i, j), wherein the downlink subframe F(i, j) is a subframe in a preconfigured downlink subframe set M corresponding to an uplink subframe;

[0049] Wherein, F(i,j) represents the downlink subframe j on the carrier i configured for the terminal, i∈C, C is the set of all carriers configured for the terminal to perform downlink data transmission; j∈K, K is the set of downlink subframes corresponding to the uplink subframe;

[0050] The preconfigured downlink subframe set M is divided into N preconfigured downlink subframe subsets, N is an integer greater than or equal to 2, the number of HARQ-ACK bits required to be fed back for each downlink subframe in a preconfigured downlink subframe subset is a predetermined value, and the number of hybrid automatic repeat request-acknowledgement HARQ-ACK bits required to be fed back for any downlink subframe in different preconfigured downlink subframe subsets is different;

[0051] a receiving module, configured to receive uplink control information sent by the terminal on the first subframe and used to feed back a reception status of the downlink data scheduled by the downlink scheduling information;

[0052] a processing module, configured to decode the uplink control information to obtain a HARQ-ACK codebook, wherein the obtained HARQ-ACK codebook includes at least one subcodebook, the at least one subcodebook corresponds one-to-one to at least one preconfigured downlink subframe subset, the at least one preconfigured downlink subframe subset is at least one preconfigured downlink subframe subset of the N preconfigured downlink subframe subsets, and the at least one preconfigured downlink subframe subset is a subset of downlink subframes including downlink data scheduled by the downlink scheduling information.

[0053] In conjunction with the second aspect, in a first possible implementation manner,

[0054] The HARQ-ACK included in the subcodebook is the HARQ-ACK of the downlink subframe scheduled in the pre-configured downlink subframe subset corresponding to the subcodebook, but does not include the HARQ-ACK of the downlink subframe that is not scheduled in the pre-configured downlink subframe subset corresponding to the subcodebook.

[0055] In conjunction with the first possible implementation of the second aspect, in a second possible implementation,

[0056] The sending module is further used for: before the receiving module receives the uplink control information sent by the terminal, for each downlink subframe F(i, j) included in the at least one preconfigured downlink subframe subset, sending first indication information corresponding to the downlink subframe F(i, j) to the terminal, wherein the first indication information is used to indicate: in a set order, a sequence number of the downlink subframe F(i, j) in the preconfigured downlink subframe subset including the downlink subframe F(i, j) scheduled in the downlink subframe subset; and instructing the terminal to generate the at least one subcodebook in the following manner:

[0057] For a preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j), and the number of bits of HARQ-ACK that need to be fed back for the downlink subframe F(i, j), generate a subcodebook corresponding to the one preconfigured downlink subframe subset according to the sequence number indicated by the first indication information.

[0058] In combination with the second possible implementation manner of the second aspect, in a third possible implementation manner, the sending module is further used to: before the receiving module receives the uplink control information sent by the terminal, for each preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, send second indication information to the terminal, where the second indication information is used to indicate:

[0059] The total number of downlink subframes with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i, j); or the total number of downlink subframes with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i, j) and before the downlink subframe time with subframe number j; or the total number of downlink subframes scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i, j); or the total number of downlink subframes scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i, j); j); or the total number of transport blocks transmitted in the downlink subframe with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i, j) and the downlink subframe before the downlink subframe with subframe number j; or the total number of transport blocks transmitted in the downlink subframe scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i, j); instruct the terminal:

[0060] For a preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of HARQ-ACK bits that need to be fed back for the downlink subframe F(i, j), generate a subcodebook corresponding to the one preconfigured downlink subframe subset according to the sequence number indicated by the first indication information and the second indication information.

[0061] In combination with the second possible implementation manner of the second aspect, in a fourth possible implementation manner, the sending module is further used to: before the receiving module receives the uplink control information sent by the terminal, for each downlink subframe F(i, j) included in the at least one preconfigured downlink subframe subset, send, to the terminal, second indication information corresponding to the downlink subframe F(i, j);

[0062] Among them, in the preconfigured downlink subframe subset including the downlink subframe F(i, j), the values ​​of the second indication information corresponding to the scheduled downlink subframes that are ranked in the last 1, 2, ..., X-1, and X in the setting order are AX-1, AX-2, ..., A1, A0 respectively, and the values ​​of the second indication information corresponding to the remaining downlink subframes are A0 respectively, and the remaining downlink subframes are the downlink subframes in the preconfigured downlink subframe subset including the downlink subframe F(i, j), except for the scheduled downlink subframes ranked in the last 1, 2, ..., X-1, X, and the AX-1, AX-2, ..., A1 and A0 are different values; or

[0063] In the preconfigured downlink subframe subset including the downlink subframe F(i, j), the values ​​of the second indication information corresponding to the scheduled downlink subframes in the preconfigured downlink subframe subset sorted in the reverse order of the setting order are respectively cyclic values ​​of {AX-1, AX-2, ..., A1, A0}; or

[0064] In the preconfigured downlink subframe subset including the downlink subframe F(i,j), the values ​​of the second indication information corresponding to the downlink subframe with subframe number j that is ranked in the last 1, 2, ..., X-1 according to the setting order, and X are respectively AX-1, AX-2, ..., A1, A0, and the values ​​of the second indication information corresponding to the remaining downlink subframes with subframe number j are respectively A0, and the remaining downlink subframes with subframe number j are the downlink subframes with subframe number j in the preconfigured downlink subframe subset including the downlink subframe F(i,j), except the downlink subframe with subframe number j that is ranked in the last 1, 2, ..., X-1, and X are scheduled, and the AX-1, AX-2, ..., A1 and A0 are different values; or

[0065] The values ​​of the second indication information corresponding to the downlink subframe with the scheduled subframe number j in the pre-configured downlink subframe subset sorted in the reverse order of the setting order are cyclic values ​​of {AX-1, AX-2, ..., A1, A0} respectively;

[0066] Wherein, X is a positive integer greater than 1;

[0067] The second indication information is used to instruct the terminal: for a preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of HARQ-ACK bits that need to be fed back for the downlink subframe F(i, j), generate a subcodebook corresponding to the preconfigured downlink subframe subset according to the sequence number indicated by the first indication information and the second indication information.

[0068] In combination with any one of the second to fourth possible implementations of the second aspect, in a fifth possible implementation, the setting sequence includes:

[0069] The order between carriers and subframes, and the order between carriers and subframes;

[0070] The order between the carrier and the subframe includes: first the carrier and then the subframe or first the subframe and then the carrier;

[0071] The carrier order includes: carrier index from small to large, or carrier index from large to small;

[0072] The subframe sequence includes: subframe timing from front to back, or subframe timing from back to front.

[0073] In combination with the second aspect, or any one of the first to fifth possible implementations of the second aspect, in a sixth possible implementation, the at least one subcodebook is cascaded in the HARQ-ACK codebook.

[0074] In a third aspect, an embodiment of the present invention provides a method for sending uplink control information, including:

[0075] The terminal receives downlink scheduling information of a downlink subframe F(i, j), wherein the downlink subframe F(i, j) is a subframe in a preconfigured downlink subframe set M corresponding to the uplink subframe;

[0076] Wherein, F(i,j) represents the downlink subframe j on the carrier i configured for the terminal, i∈C, C is the set of all carriers configured for the terminal for downlink data transmission, j∈K, K is the set of downlink subframes corresponding to the uplink subframe;

[0077] The preconfigured downlink subframe set M is divided into N preconfigured downlink subframe subsets, N is an integer greater than or equal to 2, the number of bits of the hybrid automatic repeat request-acknowledgement HARQ-ACK that needs to be fed back for each downlink subframe in a preconfigured downlink subframe subset is a predetermined value, and the number of bits of the HARQ-ACK that needs to be fed back for any downlink subframe in different preconfigured downlink subframe subsets is different;

[0078] The terminal receives the downlink data scheduled by the downlink scheduling information in the downlink subframe F(i,j);

[0079] The terminal generates a HARQ-ACK codebook according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of the HARQ-ACK that needs to be fed back for the downlink subframe F(i, j), wherein the HARQ-ACK codebook includes at least one subcodebook, and the at least one subcodebook corresponds one-to-one to at least one preconfigured downlink subframe subset, and the at least one preconfigured downlink subframe subset is at least one preconfigured downlink subframe subset of the N preconfigured downlink subframe subsets, and the at least one preconfigured downlink subframe subset is a subset of downlink subframes including downlink data scheduled by the terminal receiving the downlink scheduling information;

[0080] The terminal generates uplink control information by encoding the HARQ-ACK codebook; and

[0081] The terminal sends the uplink control information in the uplink subframe.

[0082] In combination with the third aspect, in a first possible implementation manner, the HARQ-ACK included in the subcodebook is the HARQ-ACK of the downlink subframe scheduled in the pre-configured downlink subframe subset corresponding to the subcodebook, but does not include the HARQ-ACK of the downlink subframe that is not scheduled in the pre-configured downlink subframe subset corresponding to the subcodebook.

[0083] In combination with the first possible implementation manner of the third aspect, in a second possible implementation manner,

[0084] Before generating the HARQ-ACK codebook, the method further includes:

[0085] Receiving first indication information corresponding to the downlink subframe F(i, j) included in each preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, wherein the first indication information is used to indicate: in a setting order, a sequence number of the downlink subframe F(i, j) in the preconfigured downlink subframe subset including the downlink subframe F(i, j) scheduled in the downlink subframe;

[0086] The at least one sub-codebook is generated in the following manner:

[0087] For a preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, the terminal generates a subcodebook corresponding to the preconfigured downlink subframe subset according to the sequence number indicated by the first indication information, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of HARQ-ACK bits that need to be fed back for the downlink subframe F(i, j).

[0088] In conjunction with the second possible implementation manner of the third aspect, in a third possible implementation manner,

[0089] Before generating the HARQ-ACK codebook, the method further includes:

[0090] receiving second indication information corresponding to each preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, where the second indication information is used to indicate:

[0091] the total number of downlink subframes with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i,j); or

[0092] The total number of downlink subframes with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i,j) and downlink subframes before the downlink subframe with subframe number j; or

[0093] the total number of scheduled downlink subframes in the preconfigured downlink subframe subset including the downlink subframe F(i,j); or

[0094] the total number of transport blocks transmitted in the downlink subframe with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i,j); or

[0095] The total number of transport blocks transmitted in the downlink subframe with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i,j) and in the downlink subframes before the downlink subframe with subframe number j; or

[0096] a total number of transport blocks transmitted in the downlink subframes scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i, j);

[0097] The terminal generates, according to a reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of the HARQ-ACK that needs to be fed back for the downlink subframe F(i, j), a subcodebook corresponding to any one of the preconfigured downlink subframe subsets according to a sequence number indicated by the first indication information, including:

[0098] For a preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, the terminal generates, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of HARQ-ACK that need to be fed back for the downlink subframe F(i, j), a subcodebook corresponding to the preconfigured downlink subframe subset according to the sequence number indicated by the first indication information and the second indication information.

[0099] In combination with the second possible implementation manner of the third aspect, in a fourth possible implementation manner,

[0100] Before generating the HARQ-ACK codebook, the method further includes:

[0101] Receiving second indication information corresponding to the downlink subframe F(i, j) included in each preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset;

[0102] Among them, in the preconfigured downlink subframe subset including the downlink subframe F(i, j), the values ​​of the second indication information corresponding to the scheduled downlink subframes that are ranked in the last 1, 2, ..., X-1, and X in the setting order are AX-1, AX-2, ..., A1, A0 respectively, and the values ​​of the second indication information corresponding to the remaining downlink subframes are A0 respectively, and the remaining downlink subframes are the downlink subframes in the preconfigured downlink subframe subset including the downlink subframe F(i, j), except for the scheduled downlink subframes ranked in the last 1, 2, ..., X-1, X, and the AX-1, AX-2, ..., A1 and A0 are different values; or

[0103] In the preconfigured downlink subframe subset including the downlink subframe F(i, j), the values ​​of the second indication information corresponding to the scheduled downlink subframes in the preconfigured downlink subframe subset sorted in the reverse order of the setting order are respectively cyclic values ​​of {AX-1, AX-2, ..., A1, A0}; or

[0104] In the preconfigured downlink subframe subset including the downlink subframe F(i,j), the values ​​of the second indication information corresponding to the downlink subframe with subframe number j that is ranked in the last 1, 2, ..., X-1 according to the setting order, and X are respectively AX-1, AX-2, ..., A1, A0, and the values ​​of the second indication information corresponding to the remaining downlink subframes with subframe number j are respectively A0, and the remaining downlink subframes with subframe number j are the downlink subframes with subframe number j in the preconfigured downlink subframe subset including the downlink subframe F(i,j), except the downlink subframe with subframe number j that is ranked in the last 1, 2, ..., X-1, and X are scheduled, and the AX-1, AX-2, ..., A1 and A0 are different values; or

[0105] The values ​​of the second indication information corresponding to the downlink subframe with the scheduled subframe number j in the pre-configured downlink subframe subset sorted in the reverse order of the setting order are cyclic values ​​of {AX-1, AX-2, ..., A1, A0} respectively;

[0106] Wherein, X is a positive integer greater than 1;

[0107] The terminal generates, according to a reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of the HARQ-ACK that needs to be fed back for the downlink subframe F(i, j), a subcodebook corresponding to any one of the preconfigured downlink subframe subsets according to a sequence number indicated by the first indication information, including:

[0108] For a preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, the terminal generates, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of HARQ-ACK that need to be fed back for the downlink subframe F(i, j), a subcodebook corresponding to the preconfigured downlink subframe subset according to the sequence number indicated by the first indication information and the second indication information.

[0109] In combination with any one of the second to fourth possible implementations of the third aspect, in a fifth possible implementation, the setting order includes:

[0110] The order between carriers and subframes, and the order between carriers and subframes;

[0111] The order between the carrier and the subframe includes: first the carrier and then the subframe or first the subframe and then the carrier;

[0112] The carrier order includes: carrier index from small to large, or carrier index from large to small;

[0113] The subframe sequence includes: subframe timing from front to back, or subframe timing from back to front.

[0114] In combination with the third aspect, or any one of the first to fifth possible implementations of the third aspect, in a sixth possible implementation, the at least one subcodebook is cascaded in the HARQ-ACK codebook.

[0115] In a fourth aspect, an embodiment of the present invention provides a method for receiving uplink control information, including:

[0116] The access network device sends downlink scheduling information of a downlink subframe F(i, j) to the terminal, and sends downlink data scheduled by the downlink scheduling information to the terminal in the downlink subframe F(i, j), wherein the downlink subframe F(i, j) is a subframe in a preconfigured downlink subframe set M corresponding to the uplink subframe;

[0117] Wherein, F(i,j) represents the downlink subframe j on the carrier i configured for the terminal, i∈C, C is the set of all carriers configured for the terminal to perform downlink data transmission; j∈K, K is the set of downlink subframes corresponding to the uplink subframe;

[0118] The preconfigured downlink subframe set M is divided into N preconfigured downlink subframe subsets, N is an integer greater than or equal to 2, the number of HARQ-ACK bits required to be fed back for each downlink subframe in a preconfigured downlink subframe subset is a predetermined value, and the number of hybrid automatic repeat request-acknowledgement HARQ-ACK bits required to be fed back for any downlink subframe in different preconfigured downlink subframe subsets is different;

[0119] receiving uplink control information sent by the terminal in the first subframe and used to feed back a reception status of the downlink data scheduled by the downlink scheduling information;

[0120] The received uplink control information is decoded to obtain a HARQ-ACK codebook, wherein the obtained HARQ-ACK codebook includes at least one subcodebook, the at least one subcodebook corresponds one-to-one to at least one preconfigured downlink subframe subset, the at least one preconfigured downlink subframe subset is at least one preconfigured downlink subframe subset of the N preconfigured downlink subframe subsets, and the at least one preconfigured downlink subframe subset is a subset of downlink subframes including downlink data scheduled by the downlink scheduling information.

[0121] In conjunction with the fourth aspect, in a first possible implementation,

[0122] The HARQ-ACK included in the subcodebook is the HARQ-ACK of the downlink subframe scheduled in the pre-configured downlink subframe subset corresponding to the subcodebook, but does not include the HARQ-ACK of the downlink subframe that is not scheduled in the pre-configured downlink subframe subset corresponding to the subcodebook.

[0123] In conjunction with the first possible implementation of the fourth aspect, in a second possible implementation,

[0124] Before receiving the uplink control information sent by the terminal, the method further includes:

[0125] For each downlink subframe F(i, j) included in the at least one preconfigured downlink subframe subset, sending first indication information corresponding to the downlink subframe F(i, j) to the terminal, wherein the first indication information is used to indicate: in a setting order, a sequence number of the downlink subframe F(i, j) in the downlink subframes scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i, j);

[0126] Instructing the terminal to generate the at least one sub-codebook in the following manner:

[0127] For a preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j), and the number of bits of HARQ-ACK that need to be fed back for the downlink subframe F(i, j), generate a subcodebook corresponding to the one preconfigured downlink subframe subset according to the sequence number indicated by the first indication information.

[0128] In conjunction with the second possible implementation manner of the fourth aspect, in a third possible implementation manner, before receiving the uplink control information sent by the terminal, the method further includes:

[0129] For each preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, second indication information is sent to the terminal, where the second indication information is used to indicate:

[0130] The total number of downlink subframes with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i, j); or the total number of downlink subframes with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i, j) and before the downlink subframe time with subframe number j; or the total number of downlink subframes scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i, j); or the total number of downlink subframes scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i, j); The total number of transport blocks transmitted in the downlink subframe with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i,j); or the total number of transport blocks transmitted in the downlink subframe with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i,j) and the downlink subframe before the downlink subframe with subframe number j; or the total number of transport blocks transmitted in the downlink subframe scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i,j);

[0131] instructing the terminal: for a preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, according to a reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of HARQ-ACK that needs to be fed back for the downlink subframe F(i, j), generating a subcodebook corresponding to the one preconfigured downlink subframe subset according to the sequence number indicated by the first indication information and the second indication information.

[0132] In conjunction with the second possible implementation manner of the fourth aspect, in a fourth possible implementation manner, before receiving the uplink control information sent by the terminal, the method further includes:

[0133] For each downlink subframe F(i, j) included in the at least one preconfigured downlink subframe subset, sending second indication information corresponding to the downlink subframe F(i, j) to the terminal;

[0134] Among them, in the preconfigured downlink subframe subset including the downlink subframe F(i, j), the values ​​of the second indication information corresponding to the scheduled downlink subframes that are ranked in the last 1, 2, ..., X-1, and X in the setting order are AX-1, AX-2, ..., A1, A0 respectively, and the values ​​of the second indication information corresponding to the remaining downlink subframes are A0 respectively, and the remaining downlink subframes are the downlink subframes in the preconfigured downlink subframe subset including the downlink subframe F(i, j), except for the scheduled downlink subframes ranked in the last 1, 2, ..., X-1, X, and the AX-1, AX-2, ..., A1 and A0 are different values; or

[0135] In the preconfigured downlink subframe subset including the downlink subframe F(i, j), the values ​​of the second indication information corresponding to the scheduled downlink subframes in the preconfigured downlink subframe subset sorted in the reverse order of the setting order are respectively cyclic values ​​of {AX-1, AX-2, ..., A1, A0}; or

[0136] In the preconfigured downlink subframe subset including the downlink subframe F(i,j), the values ​​of the second indication information corresponding to the downlink subframe with subframe number j that is ranked in the last 1, 2, ..., X-1 according to the setting order, and X are respectively AX-1, AX-2, ..., A1, A0, and the values ​​of the second indication information corresponding to the remaining downlink subframes with subframe number j are respectively A0, and the remaining downlink subframes with subframe number j are the downlink subframes with subframe number j in the preconfigured downlink subframe subset including the downlink subframe F(i,j), except the downlink subframe with subframe number j that is ranked in the last 1, 2, ..., X-1, and X are scheduled, and the AX-1, AX-2, ..., A1 and A0 are different values; or

[0137] The values ​​of the second indication information corresponding to the downlink subframe with the scheduled subframe number j in the pre-configured downlink subframe subset sorted in the reverse order of the setting order are cyclic values ​​of {AX-1, AX-2, ..., A1, A0} respectively;

[0138] Wherein, X is a positive integer greater than 1;

[0139] instructing the terminal: for a preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, according to a reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of HARQ-ACK that need to be fed back for the downlink subframe F(i, j), generating a subcodebook corresponding to the one preconfigured downlink subframe subset according to the sequence number indicated by the first indication information and the second indication information.

[0140] In combination with any one of the second to fourth possible implementations of the fourth aspect, in a fifth possible implementation, the setting order includes:

[0141] The order between carriers and subframes, and the order between carriers and subframes;

[0142] The order between the carrier and the subframe includes: first the carrier and then the subframe or first the subframe and then the carrier;

[0143] The carrier order includes: carrier index from small to large, or carrier index from large to small;

[0144] The subframe sequence includes: subframe timing from front to back, or subframe timing from back to front.

[0145] In combination with the fourth aspect, or any one of the first to fifth possible implementations of the fourth aspect, in a sixth possible implementation, the at least one subcodebook is cascaded in the HARQ-ACK codebook.

[0146] In a fifth aspect, an embodiment of the present invention provides a wireless communication system, including: an access network device and a terminal,

[0147] The access network device is configured to send downlink scheduling information of a downlink subframe F(i, j) to the terminal, and send downlink data scheduled by the downlink scheduling information to the terminal in the downlink subframe F(i, j), wherein the downlink subframe F(i, j) is a subframe in a preconfigured downlink subframe set M corresponding to an uplink subframe;

[0148] Wherein, F(i,j) represents the downlink subframe j on the carrier i configured for the terminal, i∈C, C is the set of all carriers configured for the terminal to perform downlink data transmission; j∈K, K is the set of downlink subframes corresponding to the uplink subframe;

[0149] The preconfigured downlink subframe set M is divided into N preconfigured downlink subframe subsets, N is an integer greater than or equal to 2, the number of HARQ-ACK bits required to be fed back for each downlink subframe in a preconfigured downlink subframe subset is a predetermined value, and the number of hybrid automatic repeat request-acknowledgement HARQ-ACK bits required to be fed back for any downlink subframe in different preconfigured downlink subframe subsets is different;

[0150] The terminal is configured to receive downlink scheduling information of the downlink subframe F(i, j), receive downlink data scheduled by the downlink scheduling information in the downlink subframe F(i, j), generate a HARQ-ACK codebook according to a reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of the HARQ-ACK that needs to be fed back for the downlink subframe F(i, j), generate uplink control information by encoding the HARQ-ACK codebook, and send the uplink control information on the uplink subframe;

[0151] The HARQ-ACK codebook includes at least one subcodebook, the at least one subcodebook corresponds one-to-one to at least one preconfigured downlink subframe subset, the at least one preconfigured downlink subframe subset is at least one preconfigured downlink subframe subset in the N preconfigured downlink subframe subsets, and the at least one preconfigured downlink subframe subset is a subset of downlink subframes including downlink data scheduled by the terminal receiving the downlink scheduling information;

[0152] The access network device is further used to receive uplink control information sent by the terminal on the first subframe for feeding back a reception status of the downlink data scheduled by the downlink scheduling information, and decode the received uplink control information to obtain a HARQ-ACK codebook.

[0153] In an embodiment of the present invention, since the preconfigured downlink subframe set M is divided into the above-mentioned N preconfigured downlink subframe subsets, the number of HARQ-ACK bits that need to be fed back for each downlink subframe in a preconfigured downlink subframe subset is a predetermined value, and the number of HARQ-ACK bits that need to be fed back for any downlink subframe in different preconfigured downlink subframe subsets is different. In this way, when the terminal generates an ACK / NACK codebook, HARQ-ACK is fed back according to the number of HARQ-ACK bits that need to be fed back for the downlink subframe in a preconfigured downlink subframe subset. In this way, after receiving the uplink control information generated by the HARQ-ACK codebook, the access network device also parses the ACK / NACK codebook according to the number of HARQ-ACK bits that need to be fed back for the downlink subframe in the preconfigured downlink subframe subset, and provides a HARQ-ACK feedback scheme, which can support the situation where the number of HARQ-ACK bits that need to be fed back for downlink subframes on different aggregated carriers is different. BRIEF DESCRIPTION OF THE DRAWINGS

[0154] Figure 1 A schematic diagram of the data transmission method between the UE and the access network device in the current CA mode;

[0155] Figure 2A A schematic diagram of the structure of a first wireless communication system provided in Embodiment 1 of the present invention and a third wireless communication system provided in Embodiment 3 of the present invention;

[0156] Figure 2B A schematic diagram of the structure of a second wireless communication system provided in Embodiment 2 of the present invention;

[0157] Figure 3 A flowchart of data transmission between an access network device and a terminal in a first wireless communication system is provided for the first embodiment of the present invention;

[0158] Figure 4 A flowchart of data transmission between an access network device and a terminal in the second wireless communication system provided in Embodiment 2 of the present invention and the third wireless communication system provided in Embodiment 3;

[0159] Figure 5A to Figure 5D This is a schematic diagram of first indication information and second indication information in Embodiment 2 of the present invention;

[0160] Figure 6 This is a schematic diagram of a situation in which the terminal cannot determine how to fill NACK in the second embodiment of the present invention;

[0161] Figure 7A to Figure 7B This is a schematic diagram of the first indication information and the second indication information in Embodiment 3 of the present invention;

[0162] Figure 8 This is a schematic diagram of a situation in which a terminal cannot determine how to fill NACK in an embodiment of the present invention;

[0163] Fig. 9 A schematic diagram of the structure of a terminal provided in Embodiment 4 of the present invention;

[0164] Fig.10 A schematic diagram of the structure of a terminal provided in an optional implementation manner of Embodiment 4 of the present invention;

[0165] Fig.11 A schematic diagram of the structure of a terminal provided in another optional implementation manner of the fourth embodiment of the present invention;

[0166] Fig.12 A schematic diagram of the structure of an access network device provided in Embodiment 5 of the present invention;

[0167] Fig.13 A schematic diagram of the structure of an access network device provided in Embodiment 5 of the present invention in an optional implementation manner;

[0168] Fig.14 A schematic diagram of the structure of an access network device provided in Embodiment 5 of the present invention in another optional implementation manner;

[0169] Fig.15 A flowchart of a method for sending uplink control information provided by an embodiment of the present invention;

[0170] Fig.16 A flowchart of a method for receiving uplink control information provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0171] Embodiments of the present invention provide a terminal, an access network device, a wireless communication system and an uplink control information transmission method, so as to support the situation where different numbers of HARQ-ACK bits need to be fed back for downlink subframes on different aggregated carriers.

[0172] In the embodiment of the present invention, the access network device sends downlink scheduling information of a downlink subframe F(i, j) to the terminal, and sends downlink data scheduled by the downlink scheduling information, wherein the downlink subframe F(i, j) is a subframe in a preconfigured downlink subframe set M corresponding to the uplink subframe;

[0173] Wherein, F(i,j) represents the downlink subframe j on the carrier i configured for the terminal, i∈C, C is the set of all carriers configured for the terminal to perform downlink data transmission; j∈K, K is the set of downlink subframes corresponding to the above uplink subframe;

[0174] The preconfigured downlink subframe set M is divided into N preconfigured downlink subframe subsets, N is an integer greater than or equal to 2, the number of HARQ-ACK bits required to be fed back for each downlink subframe in a preconfigured downlink subframe subset is a predetermined value, and the number of HARQ-ACK bits required to be fed back for any downlink subframe in different preconfigured downlink subframe subsets is different;

[0175] The terminal receives downlink scheduling information of the downlink subframe F(i, j), and receives downlink data scheduled by the downlink scheduling information in the downlink subframe F(i, j); the terminal generates a HARQ-ACK codebook according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of the HARQ-ACK that needs to be fed back in the downlink subframe F(i, j);

[0176] The generated HARQ-ACK codebook includes at least one subcodebook, and the at least one subcodebook includes a one-to-one correspondence with at least one preconfigured downlink subframe subset, the at least one preconfigured downlink subframe subset is at least one preconfigured downlink subframe subset in N preconfigured downlink subframe subsets, and the at least one preconfigured downlink subframe subset is a subset of downlink subframes including downlink scheduling information sent by the access network device;

[0177] The terminal generates uplink control information by encoding the HARQ-ACK codebook, and sends the generated uplink control information on the uplink subframe;

[0178] The access network device receives the uplink control information sent by the terminal, and decodes the received uplink control information to obtain a HARQ-ACK codebook.

[0179] Since the preconfigured downlink subframe set M is divided into the above-mentioned N preconfigured downlink subframe subsets, the number of HARQ-ACK bits that need to be fed back for each downlink subframe in a preconfigured downlink subframe subset is a predetermined value, and the number of HARQ-ACK bits that need to be fed back for any downlink subframe in different preconfigured downlink subframe subsets is different. In this way, when the terminal generates an ACK / NACK codebook, HARQ-ACK is fed back according to the number of HARQ-ACK bits that need to be fed back for the downlink subframe in a preconfigured downlink subframe subset. In this way, after receiving the uplink control information generated by the HARQ-ACK codebook, the access network device also parses the ACK / NACK codebook according to the number of HARQ-ACK bits that need to be fed back for the downlink subframe in the preconfigured downlink subframe subset, and provides a HARQ-ACK feedback scheme, which can support the situation where the number of HARQ-ACK bits that need to be fed back for downlink subframes on different aggregated carriers is different.

[0180] In order to facilitate understanding of the embodiments of the present invention, basic concepts involved in the embodiments of the present invention are introduced below.

[0181] For ease of understanding, the LTE system is taken as an example for introduction, but this does not mean that the embodiment of the present invention is only applicable to the LTE system. In fact, any wireless communication system that provides multiple carriers for data transmission for the same terminal and has different numbers of feedback information bits corresponding to downlink subframes on different carriers can adopt the HARQ-ACK feedback scheme provided by the embodiment of the present invention.

[0182] 1. Data Transmission in LTE System

[0183] In the LTE system, downlink transmission, that is, transmission from access network equipment such as base stations to UEs, is based on the multiple access method of Orthogonal Frequency Division Multiplexing Access (OFDMA); uplink transmission, that is, transmission from UE to access network equipment, is based on the multiple access method of Single Carrier–Frequency Division Multiplexing Access (SC-FDMA).

[0184] For downlink transmission, time-frequency resources are divided into OFDM symbols in the time domain and subcarriers in the frequency domain; for uplink transmission, time-frequency resources are divided into SC-FDMA symbols in the frequency domain. In the embodiment of the present invention, OFDM symbols and SC-FDMA symbols are collectively referred to as "time domain symbols".

[0185] In the LTE system, the smallest resource granularity is called a resource element (RE), which is a time-frequency grid consisting of a time domain symbol in the time domain and a subcarrier in the frequency domain.

[0186] Generally, the basic time unit for access network device scheduling is a subframe, and a subframe includes multiple time domain symbols. Alternatively, for some scenarios requiring reduced transmission delay, the basic time unit for access network device scheduling may be one or more time domain symbols.

[0187] The specific scheduling process is that the access network device sends a control channel, such as the Physical Downlink Control Channel (PDCCH) or the Enhanced Physical Downlink Control Channel (EPDCCH). The control channel can carry the scheduling information of PDSCH or PUSCH, which includes control information such as resource allocation information and adjustment of coding mode. The UE receives the control channel in the subframe and receives the downlink data channel or sends the uplink data channel according to the scheduling information carried in the received control channel.

[0188] The LTE system supports two duplex modes: frequency division duplex (FDD) and time division duplex (TDD). For LTE systems using FDD duplex mode, referred to as FDD LTE systems, downlink transmission and uplink transmission use different carriers. For LTE systems using TDD duplex mode, referred to as TDD LTE systems, uplink transmission and downlink transmission use different times of the same carrier, specifically including downlink subframes, uplink subframes and special subframes on one carrier.

[0189] Among them, the special subframe includes three parts: Downlink Pilot Time Slot (DwPTS), Guard Period (GP) and Uplink Pilot Time Slot (UpPTS), among which GP is mainly used to compensate for the device conversion time and propagation delay from downlink to uplink. In addition, downlink data can be transmitted in DwPTS, but PUSCH cannot be transmitted in UpPTS. Therefore, from this perspective, the special subframe can be regarded as a downlink subframe.

[0190] 2. HARQ-ACK Timing Relationship

[0191] In the FDD LTE system, after the UE receives the PDSCH in subframe n-4, it will feedback HARQ-ACK in subframe n; in the TDD LTE system, the timing relationship between PDSCH reception and its corresponding HARQ-ACK feedback is shown in Table 2, where the subframe marked with a number is the uplink subframe n used to feedback HARQ-ACK, and the number indicated indicates the HARQ-ACK corresponding to the PDSCH in the downlink subframe set of nk (k belongs to K) that needs to be fed back in the uplink subframe n. For example, K={7, 6} in subframe n=2 of uplink and downlink configuration 1 indicates that the uplink subframe n=2 is used to feedback the HARQ-ACK corresponding to the PDSCH in the two downlink subframes n-7 and n-6, specifically n-7 is downlink subframe 5, and n-6 ​​is downlink subframe 6.

[0192] Table 2. Timing relationship between PDSCH and corresponding HARQ-ACK in TDD LTE system

[0193]

[0194] 3. TDD uplink and downlink configuration in LTE system

[0195] The LTE system currently supports 7 different TDD uplink and downlink configurations, where the uplink and downlink configurations are the first column in Table 2. As shown in Table 3, D represents a downlink subframe, S represents a special subframe, and U represents an uplink subframe.

[0196] Table 3. Different TDD uplink and downlink configurations in LTE system

[0197]

[0198] 4. Carrier aggregation supported by LTE system

[0199] The LTE system supports FDD CA, TDD CA and FDD+TDD CA. For TDD CA, it is divided into TDD CA with the same uplink and downlink configuration and TDD CA with different uplink and downlink configurations. In CA mode, there is one primary carrier and at least one secondary carrier, and the PUCCH carrying HARQ-ACK can be configured to be sent only on the uplink primary carrier of the UE. The current PUCCH format supports a maximum of 22 HARQ-ACK bits for transmission.

[0200] 5. Pre-configured downlink subframe set M

[0201] The preconfigured downlink subframe set M corresponds to an uplink subframe on the primary carrier in CA.

[0202] Downlink subframe F(i,j)∈M, i∈C, C is a set of all carriers configured for the terminal for downlink data transmission; j∈K, K is a set of downlink subframes corresponding to an uplink subframe according to the HARQ-ACK timing relationship, and the timing relationship can be the timing relationship between PDSCH and the corresponding HARQ-ACK in the TDD LTE system listed in Table 2.

[0203] Currently, the LTE system supports configuring up to 5 carriers for a UE for carrier aggregation. Taking the most typical TDD uplink and downlink configuration 2 as an example, the uplink subframe 2 on the uplink main carrier corresponds to or is associated with the pre-configured downlink subframe set M including subframes 4, 5, 6 and 8 on the 5 carriers, i.e., a total of 20 downlink subframes.

[0204] For simplicity of description, the special subframe is regarded as a downlink subframe. The meaning of "corresponding or associated" mentioned here can be understood as: the HARQ-ACK corresponding to the PDSCH in the above 20 downlink subframes is fed back in the above uplink subframe 2, which can be specifically determined by the timing relationship from PDSCH to HARQ-ACK in Table 2.

[0205] 6. HARQ-ACK codebook and HARQ-ACK information

[0206] On the UE side, the HARQ-ACK codebook refers to the original HARQ-ACK bit stream before channel coding, which can be sorted according to certain sorting rules; these original HARQ-ACK information bits can be a bit stream of 1 or 0, where "1" represents ACK that the downlink data is correctly received, and "0" represents NACK that the downlink data is not correctly received. The UE performs channel coding on the HARQ-ACK codebook to generate the HARQ-ACK information and sends it to the access network device; on the access network device side, the access network device receives the HARQ-ACK information sent by the UE, and obtains the HARQ-ACK codebook after channel decoding the HARQ-ACK information.

[0207] Still taking the configuration of 5 carriers for a UE for carrier aggregation and TDD uplink and downlink configuration 2 in V. Preconfigured downlink subframe set M as an example, the HARQ-ACK codebook generated by the UE can be determined by the above-mentioned preconfigured downlink subframe set M. Specifically, it can be sorted in the order of carrier first and then subframe, that is, the aforementioned sorting rule is carrier first and then subframe. For example: first arrange the HARQ-ACK bits corresponding to subframes 4, 5, 6 and 8 of carrier 1, and then arrange the HARQ-ACK bits corresponding to subframes 4, 5, 6 and 8 of carrier 2, and so on. In addition, for the position of the subframe where the UE does not receive the PDSCH scheduling, the UE needs to fill NACK processing.

[0208] 7. Scenario where the UE needs to feedback a large number of HARQ-ACK bits in an uplink subframe

[0209] As LTE technology continues to evolve, it may be necessary to support HARQ-ACK feedback with more bits in the future, which may be much larger than 22 bits.

[0210] Scene 1

[0211] A CA with a larger number of carriers, referred to as "super CA", was introduced.

[0212] For example, in CA of 10 carriers or even up to 32 carriers, taking CA of 10 carriers with TDD uplink and downlink configuration 2 as an example, a 40-bit HARQ-ACK needs to be fed back in the uplink subframe 2 on the uplink main carrier.

[0213] Scene 2

[0214] CA of 5 carriers is supported, but multiple carriers are configured as TDD uplink and downlink configuration 5. For example: the primary carrier is in uplink and downlink configuration 2, and the four secondary carriers are in uplink and downlink configuration 5, then 4+9*4=40 bits of HARQ-ACK need to be fed back in uplink subframe 2 on the uplink primary carrier.

[0215] One possible solution is to introduce a PUCCH format that supports a larger bit capacity. Considering that the number of HARQ-ACK bits that the new PUCCH format needs to support will be very large, for example, 128 HARQ-ACK bits may be supported under the configuration of 32-carrier TDD uplink and downlink configuration 2, the introduction of this new format will increase the overhead of the uplink control channel.

[0216] An optional solution of an embodiment of the present invention can be applied to the scenario where the UE needs to feedback a large number of HARQ-ACK bits in an uplink subframe, which can effectively reduce the number of HARQ-ACK bits that the UE needs to feedback.

[0217] 8. Communication standards, terminals, and access network devices applicable to the embodiments of the present invention

[0218] Among them, the communication standards of various wireless communication systems provided in the embodiments of the present invention include but are not limited to: Global System of Mobile communication (GSM), Code Division Multiple Access (CDMA) IS-95, Code Division Multiple Access (CDMA) 2000, Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Duplexing-Long Term Evolution (TDD LTE), Frequency Division Duplexing-Long Term Evolution (FDD LTE), Long Term Evolution-Advanced (LTE-advanced), Personal Handy-phone System (PHS), Wireless Fidelity (WiFi) specified in the 802.11 series of protocols, Worldwide Interoperability for Microwave Access (WCDMA), etc. Access, WiMAX), and various wireless communication systems that will evolve in the future.

[0219] As long as multiple carriers are provided for the same terminal for data transmission and different carriers have different transmission modes, resulting in a wireless communication system with different numbers of feedback information bits corresponding to different carriers, the embodiments of the present invention can be adopted to enable the terminal to correctly send HARQ-ACK information, and the access network device can accurately know the terminal's downlink data reception status based on the received HARQ-ACK information.

[0220] The terminal in the embodiment of the present invention may be a wireless terminal, which may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. The wireless terminal may communicate with one or more core networks via a wireless access network (e.g., RAN, Radio Access Network). The wireless terminal may be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal, for example, a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device, which exchanges language and / or data with the wireless access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDA, Personal Digital Assistant) and other devices. A wireless terminal may also be called a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal, an access terminal, a user terminal, a user agent, a user device, or a user equipment.

[0221] The access network device provided in the embodiment of the present invention may include a base station, or a wireless resource management device for controlling a base station, or a base station and a wireless resource management device for controlling a base station; the access network device may be a macro station or a small station, and the terminal is a terminal device that communicates with the access network device.

[0222] For example, for LTE systems such as TDD LTE, FDD LTE or LTE-A, the access network device in the wireless communication system provided by the embodiment of the present invention may be an evolved NodeB (eNodeB), and the terminal may be a UE; for a TD-SCDMA system or a WCDMA system, the access network device in the wireless communication system provided by the embodiment of the present invention may include: a NodeB and / or a Radio Network Controller (RNC), and the terminal may be a UE; for a GSM system, the access network device provided by the embodiment of the present invention may include a Base Transceiver Station (BTS) and / or a Base Station Controller (BSC); the terminal is a Mobile Station (MS); for a WiFi system, the access network device may include: an Access Point (AP) and / or an Access Controller (AC), and the terminal 202 may be a Station (STA).

[0223] IX. Other Notes

[0224] In addition, the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0225] The above introduces the basic concepts involved in the embodiments of the present invention. For ease of understanding, the embodiments of the present invention are described in detail below with reference to the accompanying drawings. For clarity of description, Table 4 lists various embodiments of the present invention.

[0226] Table 4: List of various embodiments of the present invention

[0227]

[0228] The following describes various embodiments of the present invention in detail.

[0229] [Example 1]

[0230] like Figure 2A As shown, the first wireless communication system provided by the first embodiment of the present invention includes: an access network device 201 and a terminal 202, wherein:

[0231] The access network device 201 is used to send downlink scheduling information of a downlink subframe F(i, j) to the terminal 202, and send downlink data scheduled by the downlink scheduling information on the downlink subframe F(i, j), wherein the downlink subframe F(i, j) is a subframe in a preconfigured downlink subframe set M corresponding to an uplink subframe; for example: a subframe in a preconfigured downlink subframe set M corresponding to an uplink subframe.

[0232] Wherein, F(i,j) represents the downlink subframe j on the carrier i configured for the terminal, i∈C, C is the set of all carriers configured for the terminal to perform downlink data transmission; j∈K, K is the set of downlink subframes corresponding to the above uplink subframe;

[0233] The preconfigured downlink subframe set M is divided into N preconfigured downlink subframe subsets, N is an integer greater than or equal to 2, the number of HARQ-ACK bits required to be fed back for each downlink subframe in a preconfigured downlink subframe subset is a predetermined value, and the number of HARQ-ACK bits required to be fed back for any downlink subframe in different preconfigured downlink subframe subsets is different;

[0234] The terminal 202 is configured to receive downlink scheduling information of a downlink subframe F(i, j), and receive downlink data scheduled by the downlink scheduling information in the downlink subframe F(i, j); generate a HARQ-ACK codebook according to the reception status of the downlink data received in the downlink subframe F(i, j) and the number of bits of the HARQ-ACK to be fed back in the downlink subframe F(i, j); and generate uplink control information by encoding the generated HARQ-ACK codebook, and send the generated uplink control information in the above-mentioned uplink subframe;

[0235] The HARQ-ACK codebook generated by the terminal 202 includes at least one subcodebook, and the at least one subcodebook includes a one-to-one correspondence with at least one preconfigured downlink subframe subset, and the at least one preconfigured downlink subframe subset is at least one preconfigured downlink subframe subset in N preconfigured downlink subframe subsets, and the at least one preconfigured downlink subframe subset is a subset of downlink subframes including downlink scheduling information sent by the access network device 201;

[0236] The access network device 201 is further configured to receive the uplink control information sent by the terminal 202, and decode the received uplink control information to obtain a HARQ-ACK codebook.

[0237] Next, combine Figure 3 The process of downlink scheduling, downlink data transmission, and HARQ-ACK information feedback between the access network device 201 and the terminal 202 is described. The process includes the following steps:

[0238] S301: The access network device 201 sends downlink scheduling information of a downlink subframe F(i,j) to the terminal 202;

[0239] S302: The terminal 202 receives the downlink scheduling information;

[0240] S303: the access network device 201 sends the downlink data scheduled by the downlink scheduling information sent in step S301 in the downlink subframe F(i,j);

[0241] S304: The terminal 202 receives the downlink data scheduled by the downlink scheduling information in the downlink subframe F(i, j) according to the downlink scheduling information received in step S302;

[0242] S305: The terminal 202 generates a HARQ-ACK codebook according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of HARQ-ACK bits that need to be fed back for the downlink subframe F(i, j), and generates uplink control information by encoding the generated HARQ-ACK codebook;

[0243] S306: The terminal 202 sends the generated uplink control information to the access network device 201;

[0244] S307: The access network device 201 decodes the received uplink control information to obtain a HARQ-ACK codebook; and determines the reception status of the downlink data in the downlink subframe F(i, j) scheduled in the pre-configured downlink subframe set M according to the obtained HARQ-ACK codebook.

[0245] Among them, step S301 and step S303 can be completed in one step. For example, for the LTE system, the access network device 201 sends the downlink data scheduled by the downlink scheduling information in the same downlink subframe used to send the downlink scheduling information. In this case, step S302 and step S304 can also be completed in the same step. The terminal 202 can receive the downlink data in the same downlink subframe according to the downlink scheduling information in the received downlink subframe.

[0246] In addition, in the case where downlink scheduling information is sent in downlink subframe m and the scheduling terminal receives downlink data in downlink subframe m+1, the access network device 201 may adopt the following method: Figure 3In the manner shown in , the scheduling information is sent first, and then the downlink data is sent. Accordingly, the terminal 202 also receives the downlink scheduling information first, and then receives the downlink data according to the received downlink scheduling information. Alternatively, for the case where the downlink scheduling information is sent in the downlink subframe m on the carrier 1, and the scheduling terminal receives the downlink data in the downlink subframe m on the carrier 2, it is equivalent to that the downlink scheduling information and the downlink data scheduled by the downlink scheduling information are sent and received in the downlink subframe at the same time, but the downlink scheduling information and the downlink data scheduled by the downlink scheduling information are on different carriers.

[0247] Next, Figure 3 The process and implementation scheme shown are described in detail.

[0248] 1. Step S301: Access network device 201 sends downlink scheduling information

[0249] In an embodiment of the present invention, in step S301, the access network device 201 sends downlink scheduling information of a downlink subframe F(i, j), wherein the downlink subframe F(i, j) is a subframe in a pre-configured downlink subframe set M corresponding to an uplink subframe, and F(i, j) represents a downlink subframe j on a carrier i configured for the terminal 202, i∈C, C is a set of all carriers configured for the terminal 202 for downlink data transmission, and j∈K, K is a set of downlink subframes corresponding to the above-mentioned uplink subframe.

[0250] The pre-configured downlink subframe set M may be all downlink subframes on all aggregated carriers corresponding to an uplink subframe according to the HARQ-ACK timing relationship, such as the timing relationship between the PDSCH and the corresponding HARQ-ACK defined in Table 2. That is, the terminal 202 receives downlink data of each downlink subframe in the pre-configured downlink subframe set M, and feeds back HARQ-ACK on the uplink subframe according to the defined HARQ-ACK timing relationship.

[0251] In CA mode, the terminal 202 is configured with multiple carriers by the access network device 201, for example, multiple carriers are configured through radio resource control (RRC) signaling, and the multiple carriers can be FDD carriers or TDD carriers, and each carrier includes multiple downlink subframes. For TDD carriers, the uplink and downlink configurations of different carriers can be the same or different.

[0252] Taking the terminal 202 as an example, which is configured with 10 TDD carriers of the same uplink and downlink configuration 2, according to the TDD uplink and downlink subframe configuration in Table 2 and the timing relationship between the downlink data and the uplink HARQ-ACK in Table 1, the uplink subframe 2 of the main carrier needs to feedback at most the HARQ-ACK corresponding to the downlink data channel in the downlink subframes 4, 5, 6 and 8 on the above 10 carriers.

[0253] Among them, these downlink subframes, in other words, the downlink data channels in these downlink subframes can be scheduled by independent downlink control channels respectively, or can be scheduled by a unified downlink control channel, or can be a combination of the two, such as multiple downlink control channels, each downlink control channel schedules a downlink data channel in at least one downlink subframe. In the embodiment of the present invention, independent downlink control channel scheduling is taken as an example for explanation.

[0254] The downlink subframes mentioned here include normal downlink subframes and special subframes in the TDD system. After the terminal 202 is configured with multiple carriers, the access network device 201 can send a downlink control channel to schedule the downlink data channels in the downlink subframes on these configured carriers, and then the terminal 202 needs to feedback the uplink HARQ-ACK corresponding to these downlink data channels.

[0255] Taking the terminal 202 feeding back HARQ-ACK in the uplink subframe 2 as an example, according to the timing relationship between the downlink data channel and the uplink HARQ-ACK under TDD configuration 2, the pre-configured downlink subframe set M associated with the uplink subframe 2 includes: 40 downlink subframes including subframe 4, subframe 5, subframe 6 and subframe 8 of carrier 1 to carrier 10, that is, the HARQ-ACK that the terminal 202 needs to feed back on the uplink subframe 2 of the main carrier of the carrier aggregation corresponds to the downlink data channel in the above-mentioned pre-configured downlink subframe set M.

[0256] The terminal 202 may receive a downlink control channel in the preconfigured downlink subframe set M. For example, the terminal 202 may receive a downlink control channel in each downlink subframe in the preconfigured downlink subframe set, or may receive a downlink control channel in only some of the subframes in the preconfigured downlink subframe set. Then, the terminal 202 further receives downlink data channels scheduled by these downlink control channels according to the received downlink control channels.

[0257] Generally, the downlink control channel and the downlink data channel scheduled by it are in the same subframe. Alternatively, as mentioned above, the downlink control channel and the downlink data channel scheduled by it can also be in different subframes, as long as the corresponding relationship between the downlink control channel and the downlink data channel scheduled by it can be identified, for example: the timing relationship between the two channels is pre-agreed, the access network device 201 sends the downlink control channel and the downlink data channel according to the pre-agreed timing relationship, and the terminal 202 also receives the downlink control channel and the downlink data channel according to the pre-agreed timing relationship.

[0258] Here, the downlink subframe subset where the actually scheduled downlink data channel is located in the preconfigured downlink subframe set M of the terminal 202 is called an "immediately scheduled downlink subframe set", and the immediately scheduled downlink subframe set is a subset of the preconfigured downlink subframe set M.

[0259] The downlink data channel in the above-mentioned scheduled downlink subframe may include a first downlink data channel scheduled by a downlink control channel, i.e., a dynamically scheduled downlink data channel; and may also include a second downlink data channel not scheduled by a downlink control channel, such as a downlink data channel of semi-persistent scheduling (SPS). Usually, after the SPS mechanism of a terminal is activated, the downlink data channel of the SPS does not require downlink control scheduling during the initial HARQ transmission, but directly sends the downlink data channel of the SPS at a pre-configured period, such as 20ms.

[0260] In addition, the access network device 201 can also send a separate special downlink control channel. In the LTE system, the downlink control information can be PDCCH. The special downlink control channel does not schedule the downlink data channel, but is used to indicate the termination or release of the SPS mechanism. However, the special downlink control channel also requires corresponding uplink HARQ-ACK feedback. Therefore, optionally, the subframe transmitting the special downlink control channel in the above-mentioned pre-configured downlink subframe set can also be recorded in the immediate scheduled downlink subframe set, and the terminal 202 can also feedback the corresponding HARQ-ACK to it.

[0261] 2. Step S302: Terminal 202 receives downlink scheduling information

[0262] In step S302, the terminal 202 receives the downlink scheduling information sent by the access network device 201. As mentioned above, the downlink scheduling information may include resource allocation information, adjustment of the coding mode and other control information. The terminal 202 obtains the resource information used for the allocated downlink data transmission and the modulation and coding mode of the downlink data and other information according to the received downlink scheduling information, and the terminal 202 receives the downlink data according to or based on the information.

[0263] However, due to the time-varying nature of the wireless channel, when the quality of the wireless channel is poor, the terminal 202 may not receive the downlink scheduling information. At this time, the terminal 202 cannot obtain the downlink scheduling information, and thus cannot receive downlink data according to the downlink scheduling information.

[0264] Optionally, if the access network device 201 sends the aforementioned special downlink control channel to the terminal 202, as mentioned above, the special downlink control channel is used to indicate the termination or release of the SPS mechanism, then the terminal 202 also needs to receive the special downlink control channel.

[0265] 3. Step S303: The access network device 201 sends downlink data in the downlink subframe F(i,j).

[0266] After sending the downlink scheduling information, the access network device 201 adjusts the control information such as the coding mode according to the resource allocation information in the downlink scheduling information, and sends the downlink data on the downlink subframe F(i, j).

[0267] 4. Step S304: Terminal 202 receives downlink data.

[0268] The terminal 202 receives downlink data in the downlink subframe F(i, j) according to the downlink scheduling information received in step S302. If the terminal 202 does not receive the downlink scheduling information of the downlink subframe F(i, j) in step S302, the terminal 202 will not receive downlink data in the downlink subframe F(i, j) in step S304.

[0269] 5. Grouping of pre-configured downlink subframe set M

[0270] The preconfigured downlink subframe set M may be divided into N preconfigured downlink subframe subsets, where N is an integer greater than or equal to 2, and the number of HARQ-ACK bits that the terminal 202 needs to feed back for each downlink subframe in a preconfigured downlink subframe subset is a predetermined value.

[0271] Both the terminal 202 and the access network device 201 need to know in advance the division rule of the preconfigured downlink subframe set M, and the rule is the same for the terminal 202 and the access network device 201. The terminal 202 generates an ACK / NACK codebook according to the same division rule, and the access network device 201 also parses the ACK / NACK codebook according to the same rule, so that the access network device 201 can accurately know the reception status of the downlink data by the terminal 202. Alternatively, the access network device 201 determines the above rule and then notifies the terminal of the rule, that is, the access network device and the terminal have the same understanding of the above rule.

[0272] For example: both the terminal 202 and the access network device 201 need to know the value of N, as well as the preconfigured downlink subframe subset to which a downlink subframe in the preconfigured downlink subframe set M belongs, and know the number of HARQ-ACK bits that need to be fed back for each downlink subframe in the preconfigured downlink subframe subset. For example: both the access network device 201 and the terminal 202 can determine the number of HARQ-ACK bits that need to be fed back for a downlink subframe according to the data channel transmission mode of the downlink subframe, and determine the preconfigured downlink subframe subset to which the downlink subframe belongs. In this way, the terminal 202 correctly fills the HARQ-ACK bits according to the determined number of HARQ-ACK bits and the preconfigured downlink subframe subset to which the downlink subframe belongs, and generates a HARQ-ACK codebook, and the access network device 201 also parses the HARQ-ACK codebook according to the same rules, so that the reception status of the downlink data can be accurately known.

[0273] Still taking the example of terminal 202 feeding back HARQ-ACK in uplink subframe 2, the data channel transmission mode on each of the above 10 carriers configured with terminal 202 may be the same or different. It is assumed that two different data channel transmission modes are configured, and each PDSCH in the first data channel transmission mode is configured to correspond to one transmission block, that is, corresponds to 1 HARQ-ACK bit, and each PDSCH in the second transmission mode is configured to correspond to two transmission blocks, that is, corresponds to 2 HARQ-ACK bits.

[0274] It should be noted that, for a certain carrier, the access network device 201 can configure the terminal to adopt a transmission mode of 2 transmission blocks, that is, each downlink subframe on the carrier can transmit 2 transmission blocks, then each downlink subframe corresponds to 2 HARQ-ACK bits, and the downlink subframes on the carrier should be divided into 2 HARQ-ACK bit groups; but the access network device 201 can also configure the terminal 202 to adopt the HARQ-ACK space binding mode for the 2 transmission blocks on the downlink subframe to feedback HARQ-ACK. At this time, the 2 transmission blocks scheduled in a downlink subframe only correspond to 1 HARQ-ACK bit, that is, only when both transmission blocks are received correctly will 1 bit of ACK be fed back, otherwise 1 bit of NACK will be fed back. Since 1 downlink subframe including 2 transmission blocks corresponds to 1 HARQ-ACK bit feedback at this time, the downlink subframes on the carrier need to be divided into 1 HARQ-ACK bit group. Alternatively, the downlink subframe on the carrier is divided into another group of 1 HARQ-ACK bit, that is, the group of 1 HARQ-ACK after spatial bundling and the group of 1 HARQ-ACK corresponding to 1 transport block are two independent groups.

[0275] As mentioned above, when the UE does not receive the downlink scheduling information, since different carriers are configured with different transmission modes, the UE cannot determine the number of bits to fill the HARQ-ACK bits.

[0276] There are a variety of solutions to this problem, two of which are described below as examples.

[0277] Optional solution 1

[0278] In this solution, the above-mentioned preconfigured downlink subframe set M can be divided into N preconfigured downlink subframe subsets. Wherein, N is an integer greater than or equal to 2, and the number of bits of the hybrid automatic repeat request-acknowledgement HARQ-ACK that the terminal 202 needs to feedback for each downlink subframe in a preconfigured downlink subframe subset is a predetermined value, such as: 1 bit or 2 bits; the number of bits of the HARQ-ACK that needs to be fed back for any downlink subframe in different preconfigured downlink subframe subsets is different.

[0279] At this time, the number of pre-configured downlink subframe subsets depends on the possible values ​​of the number of HARQ-ACK bits that need to be fed back. For example: for the pre-configured downlink subframe set M, there are 2 different values ​​of the number of HARQ-ACK bits that need to be fed back, then the pre-configured downlink subframe set M can be divided into two pre-configured downlink subframe subsets; for another example: for the pre-configured downlink subframe set M, there are 3 different values ​​of the number of HARQ-ACK bits that need to be fed back, then the pre-configured downlink subframe set M can be divided into three pre-configured downlink subframe subsets. Of course, if for the pre-configured downlink subframe set M, there is only one value of the number of HARQ-ACK bits that need to be fed back, then the pre-configured downlink subframe set M does not need to be grouped.

[0280] Taking N=2 as an example, the preconfigured downlink subframe set M is divided into a first preconfigured downlink subframe subset and a second preconfigured downlink subframe subset. Therefore, since the immediate scheduled downlink subframe set is a subset of the preconfigured downlink subframe set, the immediate scheduled downlink subframe set is also divided into a first immediate scheduled downlink subframe subset and a second immediate scheduled downlink subframe subset, and the first immediate scheduled downlink subframe subset is a subset of the first preconfigured downlink subframe subset, and the second immediate scheduled downlink subframe subset is a subset of the second preconfigured downlink subframe subset.

[0281] For another example: for the preconfigured downlink subframe set M, the number of HARQ-ACK bits that need to be fed back has three different values, then the preconfigured downlink subframe set M can be divided into three preconfigured downlink subframe subsets. Of course, if for the preconfigured downlink subframe set M, the number of HARQ-ACK bits that need to be fed back has only one value, then the preconfigured downlink subframe set M does not need to be grouped.

[0282] Optional solution 2

[0283] In this solution, the preconfigured downlink subframe set M can be divided into P preconfigured downlink subframe subsets. P is an integer greater than or equal to 2, and the number of HARQ-ACK bits that the terminal 202 needs to feedback for each downlink subframe in a preconfigured downlink subframe subset is a predetermined value, such as 1 bit and 2 bits. Different from the optional solution 1, it is not necessary to limit the number of HARQ-ACK bits that need to be fed back to any downlink subframe in different preconfigured downlink subframe subsets to be different.

[0284] As long as the number of HARQ-ACK bits that need to be fed back for downlink subframes in the same pre-configured downlink subframe subset is the same, it can be ensured that the terminal 202 can correctly fill in the NACK.

[0285] At this time, the number of pre-configured downlink subframe subsets will be greater than or equal to the number of HARQ-ACK bit values ​​that need to be fed back. For example: for the pre-configured downlink subframe set M, the number of HARQ-ACK bits that need to be fed back has 2 different values, then the pre-configured downlink subframe set M can be divided into three or four equal pre-configured downlink subframe subsets, as long as the number of HARQ-ACK bits that need to be fed back for the downlink subframes in a pre-configured downlink subframe subset is the same.

[0286] This solution can be applied to the following scenarios to solve the problem of insufficient uplink subframe capacity:

[0287] Usually, the capacity of an uplink subframe is limited. In the case where the HARQ-ACK of multiple downlink subframes needs to be fed back in the same uplink subframe, the load of the uplink subframe will be relatively large. At present, in CA mode, HARQ-ACK is sent on the uplink subframe of the main carrier. Considering the limited uplink subframe capacity of the main carrier, it is possible to consider placing the HARQ-ACK of some downlink subframes on the uplink subframe of the auxiliary carrier for transmission. At this time, for the downlink subframes with the same number of HARQ-ACK bits that need to be fed back in the pre-configured downlink subframe set M, they are further subdivided into multiple pre-configured downlink subframe subsets, and some pre-configured downlink subframe subsets are placed on the uplink subframe of the auxiliary carrier for transmission, which solves the problem of insufficient uplink subframe capacity of the main carrier. Optionally, the uplink subframe of the auxiliary carrier has the same subframe number as the uplink subframe of the main carrier, so that there is no need to redefine the HARQ-ACK timing relationship.

[0288] The above two optional solutions are only examples. It can be seen from the above two solutions that when the pre-configured downlink subframe set M is divided into multiple pre-configured downlink subframe subsets, as long as the number of HARQ-ACK bits that need to be fed back for the downlink subframes in the same pre-configured downlink subframe subset is ensured to be the same, which is a predetermined value known to both the access network device 201 and the terminal 202, it can be ensured that the terminal 202 can correctly fill in the NACK and the access network device 201 can also correctly receive the HARQ-ACK.

[0289] 6. In step S305, the terminal 202 generates a HARQ-ACK codebook

[0290] The HARQ-ACK codebook generated by the terminal 202 may include the HARQ-ACK bits of all subframes in the pre-configured downlink subframe set M, or may only include the HARQ-ACK bits of all downlink subframes scheduled in the pre-configured downlink subframe set M, that is, the HARQ-ACK bits of all downlink subframes in the aforementioned immediate scheduled downlink subframe set.

[0291] The terminal 202 may determine the original HARQ-ACK information bits that need to be fed back in the uplink subframe (such as the above-mentioned uplink subframe 2) based on the reception status of the downlink data scheduled by the received downlink scheduling information. Optionally, if in step S302, the terminal 202 also receives the aforementioned special downlink control information, it may also determine the original HARQ-ACK information bits that need to be fed back in the uplink subframe (such as the above-mentioned uplink subframe 2) based on the timing relationship specified in Table 2 according to the reception status of the special downlink control channel and the number of HARQ-ACK bits that need to be fed back in the downlink subframe, and then generate a HARQ-ACK codebook.

[0292] Optionally, the HARQ-ACK codebook may correspond to the above-mentioned immediate scheduled downlink subframe set. The immediate scheduled downlink subframe set includes the downlink subframes for which the access network device 201 schedules downlink data transmission, and if the access network device 201 also sends special downlink control channels, it also includes the subframes where these special downlink control channels are located. Unless otherwise specified in the following embodiments, it is assumed that there is no such special downlink control channel, but the embodiments of the present invention can be used in the case where there are downlink data channels and special downlink control channels.

[0293] As described above, in an embodiment of the present invention, the preconfigured downlink subframe set M is divided into N preconfigured downlink subframe subsets, and the HARQ-ACK codebook generated by the terminal 202 may include at least one subcodebook, and the at least one subcodebook corresponds one-to-one to at least one preconfigured downlink subframe subset. The at least one preconfigured downlink subframe subset is at least one preconfigured downlink subframe subset in the N preconfigured downlink subframe subsets, and the at least one preconfigured downlink subframe subset is a subset of downlink subframes including the terminal receiving the downlink scheduling information.

[0294] If the HARQ-ACK codebook generated by the terminal 202 includes only the HARQ-ACK bits of all downlink subframes scheduled in the pre-configured downlink subframe set M, that is, the HARQ-ACK bits of all downlink subframes in the aforementioned immediate scheduled downlink subframe set, then when no downlink subframes are scheduled in one or more of the N pre-configured downlink subframe subsets, or when the terminal 202 does not receive the downlink scheduling information of any downlink subframe in one or more of the N pre-configured downlink subframe subsets, the terminal 202 may not include the HARQ-ACK bits corresponding to the pre-configured downlink subframe subsets for which no downlink subframes are scheduled in the generated HARQ-ACK codebook.

[0295] If the HARQ-ACK codebook generated by the terminal 202 includes HARQ-ACK bits of all subframes in the pre-configured downlink subframe set M, the terminal 202 may generate a subcodebook corresponding to each of the N pre-configured downlink subframe subsets when generating the HARQ-ACK codebook. Optionally, the terminal 202 may cascade the generated N subcodebooks to form a HARQ-ACK codebook.

[0296] If the HARQ-ACK codebook generated by the terminal 202 includes only the HARQ-ACK bits of all downlink subframes scheduled in the pre-configured downlink subframe set M, that is, the HARQ-ACK bits of all downlink subframes in the aforementioned immediate scheduled downlink subframe set, the terminal 202 may generate a subcodebook corresponding to each of the N immediate scheduled downlink subframe subsets when generating the HARQ-ACK codebook. Optionally, the terminal 202 may cascade the generated N subcodebooks to form a HARQ-ACK codebook.

[0297] As mentioned above, the terminal 202 and the access network device 201 need to know in advance the division rule of the pre-configured downlink subframe set M, and the rule is the same for the terminal 202 and the access network device 201. Here, when the terminal 202 generates the HARQ-ACK codebook in cascade, the rule adopted should also be known in advance by the terminal 202 and the access network device 201. For example, according to the number of HARQ-ACK bits that need to be fed back, the terminal 202 puts the subcodebook corresponding to the pre-configured downlink subframe subset with a small number of HARQ-ACK bits to be fed back in front during cascading, and puts the subcodebook corresponding to the pre-configured downlink subframe subset with a large number of HARQ-ACK bits to be fed back in the back. In this way, the access network device 201 also parses the HARQ-ACK codebook according to the same rule, and can accurately or HARQ-ACK bits.

[0298] 7. In step S305, the terminal 202 performs channel coding on the generated HARQ-ACK codebook to generate uplink control information.

[0299] After generating the HARQ-ACK codebook, the terminal 202 performs channel coding according to the codebook. In the embodiment of the present invention, the type of channel coding is not limited, and various channel codings such as linear block coding, convolutional coding or Turbo coding can be used. If linear block coding is used, such as Reed Muller (RM) code, it is generally not necessary to add a cyclic redundancy check (CRC) before coding; if convolutional coding or Turbo is used, CRC can be added before coding, of course, it can also be not added, and the embodiment of the present invention does not limit this.

[0300] Optionally, the terminal 202 may also adopt different encoding methods and CRC adding methods according to the codebook size, for example: when the codebook size is greater than a preset threshold, convolution coding is adopted, and CRC is added at this time; when the codebook size is less than or equal to the preset threshold, RM code is adopted, and CRC may not be added at this time.

[0301] 8. Step S306: Terminal 202 sends uplink control information to access network device 201

[0302] Taking the LTE system as an example, the terminal 202 may send the uplink control information generated in step S305 on the PUCCH or PUSCH.

[0303] After channel coding, the terminal 202 needs to map the encoded HARQ-ACK information to a physical resource before sending the uplink control information. The physical resource may be a PUCCH or PUSCH resource. Here, the PUCCH resource is used as an example to describe how the terminal 202 determines the PUCCH resource.

[0304] Optionally, the terminal 202 may determine the PUCCH resource according to the resource indication information. The terminal 202 acquires a PUCCH resource set, wherein the PUCCH resource set includes PUCCH resources of at least one PUCCH format; the terminal 202 determines the PUCCH resource from the PUCCH resource set according to the resource indication information.

[0305] Specifically, the terminal 202 may receive high-level signaling, such as RRC signaling, in advance, and obtain a PUCCH resource set configured by the access network device 201 for the terminal 202, wherein the set includes at least two PUCCH resources. The PUCCH resources included in the set may have the same format, such as: a PUCCH format (such as format 3) or a new PUCCH format (such as PUCCH format 4 based on a PUSCH channel structure) in the LTE system in the current CA mode, or may include at least two PUCCH formats, such as the above-mentioned format 3 and format 4, or at least two new formats.

[0306] Then, the terminal 202 determines the first PUCCH resource from the PUCCH resource set according to the resource indication information. The resource indication information may include a downlink control channel of a currently scheduled downlink data channel, and may specifically include bits in these control channels or other implicit state combinations, such as a newly added bit, or reuse of a current transmit power control (Transmit Power Control, TPC) field.

[0307] Optionally, different PUCCH formats may be used to carry HARQ-ACK for different codebook sizes, such as format 4 for codebook sizes above a threshold, and format 3 for codebook sizes below a threshold. Specifically, a correspondence may be established between different states of the resource indication information and different PUCCH formats, and then the PUCCH format and PUCCH resources may be determined based on the resource indication information. Alternatively, a relationship may be established among the resource indication information, the codebook size, and the PUCCH format, and then the PUCCH resources and PUCCH format may be determined based on the received resource indication information and the determined codebook size.

[0308] 9. Step S307: The access network device 201 receives the uplink control information, obtains the HARQ-ACK codebook, and determines the downlink data reception status.

[0309] After receiving the uplink control information sent by the terminal 202, the access network device 201 performs channel decoding using the same channel coding method as the terminal 202 to obtain a HARQ-ACK codebook.

[0310] If the terminal 202 combines multiple sub-codebooks into one HARQ-ACK codebook in a cascade manner when generating the HARQ-ACK codebook, the access network device 201 also parses the multiple sub-codebooks included in the HARQ-ACK codebook in the same cascade manner as the terminal 202.

[0311] Optionally, the access network device 201 determines the number of HARQ-ACK bits that need to be fed back for the downlink subframe in each pre-configured downlink subframe subset according to the pre-known division rule of the pre-configured downlink subframe set M that is the same as the terminal 202, and parses the HARQ-ACK codebook, thereby accurately knowing the HARQ-ACK of each downlink subframe fed back by the terminal 202, and further determining the reception status of the downlink data in the downlink subframe by the terminal 202.

[0312] [Example 2]

[0313] The structure of the wireless communication system provided in the second embodiment can refer to Figure 2B .

[0314] In the second embodiment, the pre-configured downlink subframe set M is not divided into subsets, and the terminal 202 only feeds back HARQ-ACK for the downlink subframes scheduled by the access network device 201, and the terminal 202 determines whether the downlink scheduling information is missed, so that the terminal 202 fills the HARQ-ACK at the missed position with NACK processing, thereby generating a HARQ-ACK codebook consistent with the understanding of the access network device 201.

[0315] Next, combine Figure 4 The process of downlink scheduling, downlink data transmission, and HARQ-ACK information feedback between the access network device 201 and the terminal 202 is described. The process includes the following steps:

[0316] S401: The access network device 201 sends downlink scheduling information and indication information of a downlink subframe F(i,j) to the terminal 202;

[0317] S402: The terminal 202 receives the downlink scheduling information and indication information;

[0318] S403: the access network device 201 sends the downlink data scheduled by the downlink scheduling information sent in step S401 in the downlink subframe F(i,j);

[0319] S404: The terminal 202 determines the downlink subframe scheduled by the access network device 201 according to the downlink scheduling information and indication information received in step S402, for example: the terminal 202 determines the downlink subframe scheduled by the received downlink scheduling information according to the received downlink scheduling information, and determines the downlink subframe scheduled by the downlink scheduling information scheduled by the access network device 201 but missed by the terminal 202 according to the indication information, thereby determining the downlink subframe actually scheduled by the access network device 201, that is, the downlink subframe immediately scheduled by the access network device 201; and receives the downlink data scheduled by the downlink scheduling information on the determined downlink subframe scheduled by the access network device 201;

[0320] S405: The terminal 202 generates a HARQ-ACK codebook according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of HARQ-ACK bits that need to be fed back on the downlink subframe F(i, j), and generates uplink control information by encoding the generated HARQ-ACK codebook;

[0321] S406: The terminal 202 sends the generated uplink control information to the access network device 201;

[0322] S407: The access network device 201 decodes the received uplink control information to obtain a HARQ-ACK codebook; and determines the reception status of the downlink data in the downlink subframe F(i, j) scheduled in the pre-configured downlink subframe set M according to the obtained HARQ-ACK codebook.

[0323] contrast Figure 4 and Figure 3 It can be seen that in Figure 4 In the steps shown, in step S401, the access network device 201 not only sends downlink scheduling information to the terminal 202, but also sends indication information. The specific implementation of the indication information is described below; in step S402, the terminal 202 not only receives the downlink scheduling information, but also receives the above indication information sent by the access network device 201;

[0324] In step S405, the terminal 202 needs to determine the downlink subframe scheduled by the access network device 201 according to the received downlink scheduling information and indication information, and generate a HARQ-ACK codebook for the determined downlink subframe scheduled by the access network device 201 according to the reception status of the downlink data and the number of HARQ-ACK bits that need to be fed back in the downlink subframe.

[0325] In step S407, the access network device 201 decodes the received uplink control information to obtain a HARQ-ACK codebook. At this time, the access network device 201 should parse the HARQ-ACK codebook according to the scheduled downlink subframe, but should not parse the HARQ-ACK codebook according to the pre-configured downlink subframe set M to obtain the reception status of the downlink data in the scheduled downlink subframe.

[0326] Among them, step S401 and step S403 can be completed in one step. For example, for the LTE system, the access network device 201 sends the downlink data scheduled by the downlink scheduling information in the same downlink subframe used to send the downlink scheduling information. In this case, step S402 and step S404 can also be completed in the same step. The terminal 202 can receive the downlink data in the same downlink subframe according to the downlink scheduling information in the received downlink subframe.

[0327] In addition, in the case where downlink scheduling information is sent in downlink subframe m and the scheduling terminal receives downlink data in downlink subframe m+1, the access network device 201 may adopt the following method: Figure 4 In the manner shown in , the scheduling information is sent first, and then the downlink data is sent. Accordingly, the terminal 202 also receives the downlink scheduling information first, and then receives the downlink data according to the received downlink scheduling information. Alternatively, for the case where the downlink scheduling information is sent in the downlink subframe m on the carrier 1, and the scheduling terminal receives the downlink data in the downlink subframe m on the carrier 2, it is equivalent to that the downlink scheduling information and the downlink data scheduled by the downlink scheduling information are sent and received in the downlink subframe at the same time, but the downlink scheduling information and the downlink data scheduled by the downlink scheduling information are on different carriers.

[0328] In addition, the indication information may be sent together with the downlink scheduling information, or may be sent separately, such as through separate signaling. One downlink subframe F(i,j) may correspond to one indication information, or multiple downlink subframes may correspond to one indication information.

[0329] In the second implementation, the HARQ-ACK codebook generated by the terminal 202 only includes the HARQ-ACK of the downlink subframe scheduled by the access network device 201, which reduces the size of the HARQ-ACK codebook. Compared with the feedback of the HARQ-ACK of all downlink subframes in the preconfigured downlink subframe set M, the occupancy of the uplink control channel, such as PUCCH, is reduced, and the data transmission efficiency is improved. When parsing the HARQ-ACK codebook, the access network device 201 only needs to parse the HARQ-ACK of the scheduled downlink subframe, which reduces the processing of the access network device 201.

[0330] The instruction information is described in detail below.

[0331] In the second embodiment, the HARQ-ACK codebook generated by the terminal 202 only includes the HARQ-ACK of the downlink subframe F(i, j) scheduled by the access network device 201, that is, generated for the aforementioned immediate scheduled downlink subframe set.

[0332] refer to Figure 5A to Figure 5D , the terminal 202 is configured with 10 carriers, and each carrier is TDD configuration 2, then the pre-configured downlink subframe set associated with the uplink subframe 2 on the uplink main carrier includes all downlink subframes 4, 5, 6 and 8 of all 10 carriers.

[0333] Assuming that in a certain scheduling scenario, the immediate scheduled downlink subframe set actually scheduled by the terminal 202 includes subframe 4 of carrier 1 to carrier 7, subframe 5 of carrier 1+carrier 3+carrier 5, subframe 6 of carrier 1 to carrier 6, and subframe 8 of carrier 1 to carrier 5, then these currently actually scheduled downlink subframes constitute the immediate scheduled downlink subframe set. It can be seen that the immediate scheduled downlink subframe set is a subset of the above-mentioned preconfigured downlink subframe set.

[0334] At this time, in the second embodiment, the HARQ-ACK codebook to be transmitted on the uplink subframe 2 on the uplink main carrier is determined by the above-mentioned immediate scheduled downlink subframe set, that is, the HARQ-ACK codebook size at this time is 21, and it is assumed here that each downlink subframe corresponds to 1 HARQ-ACK bit.

[0335] Among them, the terminal 202 can accurately identify the above-mentioned immediate scheduling downlink subframe set according to the indication information, so as to achieve the same understanding of the HARQ-ACK codebook between the access network device 201 and the terminal 202. Optionally, it can be implemented through the above-mentioned indication information. The indication information can be carried on a downlink control channel, and the downlink control information can be a downlink control channel for scheduling the downlink data channel in the above-mentioned downlink subframe, that is, a downlink control channel for sending the downlink scheduling information of the downlink subframe.

[0336] Optionally, the indication information may include: first indication information and second indication information, the first indication information may be called "downlink assignment index (DAI) index indication", and the second indication information may be called "DAI end indication".

[0337] The above two indication information can be newly added bits or reused existing bits in the current downlink control channel, or can be non-bit implicit indications, such as: scrambling code or partial state combination of certain bits; or the DAI end indication can also be carried through a separate control channel.

[0338] Taking the two-bit DAI index indication and the two-bit DAI end indication respectively included in each downlink control channel as an example, the following describes in detail how to determine the HARQ-ACK codebook determined based on the immediate scheduling downlink subframe set using the two DAI fields.

[0339] Among them, the DAI index indication can be in the order of carrier first and then subframe (of course, other orders are not excluded, as long as they are pre-defined), and the values ​​in the respective downlink control channels are accumulated in sequence. It should be noted that since there are only two bits of DAI index at present, a cyclic count is required, such as using the rule of [(X-1)mod 4]+1, that is, X=1, 5 and 9 all correspond to the value of DAI index indication 1 (for example, represented by state '00'), where X is the actual accumulated count value.

[0340] In this way, if the terminal 202 misses a part of the downlink control channels, for example, the terminal 202 continuously receives downlink control channels with DAI indexes 1 and 4, the terminal 202 can be aware of the missed detection of two downlink control channels with DAI indexes 2 and 3, respectively. In this way, when the terminal 202 determines the HARQ-ACK codebook, it can place two zero bits in the HARQ-ACK bit position associated with the downlink subframe corresponding to the above two missed downlink control channels, that is, fill NACK.

[0341] However, if only the above-mentioned DAI index indication is used, although it is possible to find that a downlink control channel is missed between two received downlink control channels, it is impossible to find the downlink control channel missed at the end. For example, assuming that the access network device 201 schedules a total of 4 downlink control channels, and the values ​​of the DAI index indication are 1, 2, 3 and 4, respectively, but the terminal 202 only receives 3 downlink control channels with DAI index indication values ​​of 1, 2 and 3, then the terminal 202 cannot find the missed detection problem of the last downlink control channel.

[0342] In order to solve the problem of missed detection of the downlink control channel at the end, optionally, a DAI end indication can be introduced. Of course, this method is not the only method to determine missed detection of the downlink control channel at the end. For example, if the UE does not determine that the downlink control information at the end is missed, the access network device 201 will not pass the CRC check, so the access network device 201 can determine that the HARQ-ACK codebook fed back by the terminal 202 is wrong. Once the access network device 201 fails the CRC check, the access network device 201 will consider that each HARQ-ACK bit in the HARQ-ACK codebook fed back by the terminal 202 is NACK, and the access network device 201 will subsequently start the physical layer retransmission scheduling. In addition, the CRC check ensures that the access network device 201 will not mistakenly detect the NACK of the terminal 202 as ACK, avoiding the occurrence of a serious error event in which the NACK is mistakenly judged as ACK, because this error event will cause physical layer packet loss, that is, the access network device 201 believes that the terminal 202 has not received the correct downlink data. Therefore, the access network device 201 will not start the physical layer retransmission, but will subsequently start the high-level retransmission, such as the radio link control (RLC, RadioLink Control) layer retransmission. This high-level retransmission will greatly reduce the system's resource utilization efficiency compared to the physical layer retransmission.

[0343] It should be noted that the above-mentioned access network device 201 combines CRC and DAI index indications to determine the method of HARQ-ACK codebook errors. Once the access network device 201 determines that the HARQ-ACK codebook is wrong, it is necessary to start the retransmission scheduling of all downlink subframes fed back by the HARQ-ACK codebook. For those downlink data of the downlink subframes that the terminal 202 receives the correct data, it is necessary to retransmit it. In a certain sense, the data transmission efficiency is still not high. Therefore, optionally, the terminal 202 can determine the missed detection of the end downlink scheduling information according to the DAI end indication described below. Compared with the method combining CRC and DAI index, this method can significantly improve the data transmission efficiency.

[0344] The following describes the optional implementation of the DAI end indication:

[0345] Optional implementation method 1

[0346] like Figure 5A As shown, the DAI end indication is used to indicate the total number of PDSCHs scheduled in the current subframe in the above-mentioned immediate scheduled downlink subframe set. In CA mode, the PDSCH scheduled in the current subframe may include: each downlink subframe with the same subframe number as the current subframe on each aggregated carrier. The modulus rule of the specific total number of DAI values ​​is consistent with the DAI index indication, that is, [(X-1)mod 4]+1.

[0347] Optional Implementation Method 2

[0348] like Figure 5B As shown, it is used to indicate the total number of PDSCHs scheduled in the current subframe and the previous subframes in the above-mentioned immediate scheduled downlink subframe set.

[0349] In addition, predictive scheduling methods can also be used, such as: Figure 5B The denominator in is changed to 1. At this time, the DAI end indication is used to indicate the total number of PDSCHs scheduled in the above-mentioned immediate scheduling downlink subframe set, but this requires the access network device 201 to make a prediction when scheduling. For example, at the moment of scheduling subframe 4, it is necessary to predict whether subframes 5, 6 and 8 need to be scheduled and the accurate number of scheduled subframes, because the total number of DAIs in these downlink control channels must be kept consistent. This predictive scheduling will bring certain implementation complexity.

[0350] For optional implementation methods one and two, it should be noted that the second indication information can be located in each downlink scheduling information for scheduling the above-mentioned downlink subframe; or, the second indication information does not need to be located in the downlink scheduling information for scheduling the above-mentioned downlink subframe, but it is only necessary to ensure that there is at least one second indication information for multiple scheduled downlink subframes with a certain subframe number, or it is only necessary to ensure that there is at least one second indication information for multiple scheduled downlink subframes in a certain instant-scheduling downlink subframe subset.

[0351] Optional implementation method three

[0352] like Figure 5C As shown, it is used to indicate the last X PDSCHs in the above-mentioned immediate scheduling downlink subframe set, for example, X=3, then the values ​​of the DAI end indication corresponding to the last 3 subframes are reversely set to 4, 3 and 2, and the values ​​of the remaining DAI end indications are 1.

[0353] Optional Implementation Method 4

[0354] like Figure 5DAs shown, it is used to indicate the last X PDSCHs scheduled in each subframe in the above-mentioned immediate scheduled downlink subframe set, for example, X=3, then the values ​​of the DAI end indications corresponding to the last 3 PDSCHs in each subframe are reversely set to 4, 3 and 2, and the values ​​of the remaining DAI end indications in the subframe are 1.

[0355] In addition, the total number indication of the DAI end indication may also include the number of special downlink control channels, where the special downlink control channel is used to indicate the resource release of semi-persistent scheduling but not used to schedule PDSCH. Moreover, the cumulative count of the DAI index indication may also include the above-mentioned special downlink control channel.

[0356] Through the above-mentioned DAI index indication and DAI end indication, the terminal 202 can accurately restore the HARQ-ACK codebook corresponding to the downlink subframe actually scheduled by the access network device 201 even when there is a certain amount of missed detection of the downlink control channel.

[0357] However, the above solutions all assume that each downlink subframe corresponds to one HARQ-ACK bit. If each carrier is configured with a different data channel transmission mode, it is likely that the number of HARQ-ACK bits corresponding to downlink subframes on different carriers will be different.

[0358] For example: LTE supports 9 data channel transmission modes as shown in Table 1, among which the PDSCH scheduled in a downlink subframe under transmission modes 1, 2, 5, 6, and 7 is a single transmission block, that is, each downlink subframe corresponds to 1 HARQ-ACK bit; and the PDSCH scheduled in a downlink subframe under transmission modes 3, 4, 8, and 9 can be two transmission blocks, that is, each downlink subframe corresponds to 2 HARQ-ACK bits.

[0359] As mentioned above, with the development of technology, in the CA mode, each carrier configured for the terminal 202 may adopt a different transmission mode. The generation of the HARQ-ACK codebook based on the immediate scheduling downlink subframe set provided in the second embodiment has a certain error risk. An example is as follows:

[0360] refer to Figure 6 , assuming that the terminal 202 is configured with 8 FDD carriers, taking one of the downlink subframes as an example, assuming that the maximum number of transmission blocks that can be scheduled in each downlink subframe configured with carriers 1 to 8 is {1, 2, 2, 2, 1, 1, 2, 1}, and the access network device 201 schedules the downlink data channels in the downlink subframes of 6 of the carriers. According to the method of Example 2, the values ​​of the DAI index indication in the corresponding downlink control channel are {1, 2, 3, 4, 1, 2}.

[0361] Assuming that the terminal 202 misses the downlink control channel in the downlink subframe on carrier 4, the terminal 202 can discover that it has missed the downlink control channel with a DAI index indication value of 4 by using the values ​​of the two preceding and succeeding DAI index indications being 3 and 1 respectively. However, the terminal 202 does not know whether the missed detection is the downlink control channel of carrier 4 or carrier 5, and the downlink subframe on carrier 4 corresponds to 2 HARQ-ACK bits, and the downlink subframe on carrier 5 corresponds to 1 HARQ-ACK bit. Therefore, the terminal 202 is not clear whether 1 zero or two zeros should be filled, which may lead to the risk of inconsistency between the HARQ-ACK codebook and the access network device 201, and ultimately lead to an error in the parsing of the HARQ-ACK codebook by the access network device 201.

[0362] In view of the fact that in the second embodiment, in the CA mode, different carriers of the terminal 202 can be configured with different data channel transmission modes, which may lead to unequal maximum numbers of transmission blocks scheduled on different downlink subframes, resulting in certain risks in the solution of determining the HARQ-ACK codebook based on the immediate scheduling downlink subframe set. Therefore, in combination with the first and second embodiments, the solution of the third embodiment is provided.

[0363] [Example 3]

[0364] Embodiment 3 provides a third wireless communication system, wherein the preconfigured downlink subframe set M is divided into N preconfigured downlink subframe subsets, and the terminal 202 determines an immediate scheduled downlink subframe subset in each preconfigured downlink subframe subset according to indication information such as that provided in Embodiment 2, and generates a HARQ-ACK codebook for the immediate scheduled downlink subframe subset.

[0365] The structure of the wireless communication system provided in the third embodiment can also be referred to Figure 2A The process of downlink scheduling, downlink data transmission and HARQ-ACK information feedback between the access network device 201 and the terminal 202 can be referred to Figure 4 .

[0366] In the third embodiment, the access network device 201 not only sends downlink scheduling information to the terminal 202 , but also sends indication information such as described in the second embodiment. In the third embodiment, the terminal 202 only feeds back HARQ-ACK for the downlink subframes scheduled by the access network device 201 .

[0367] The difference between Example 3 and Example 2 is that in Example 3, the pre-configured downlink subframe set M is divided into N pre-configured downlink subframe subsets, N is an integer greater than or equal to 2, the number of HARQ-ACK bits that need to be fed back for each downlink subframe in a pre-configured downlink subframe subset is a predetermined value, and the number of HARQ-ACK bits that need to be fed back for any downlink subframe in different pre-configured downlink subframe subsets is different.

[0368] In embodiment three, the first indication information, i.e., the DAI index indication, is for a preconfigured downlink subframe subset, and the first indication information corresponding to the downlink subframe F(i, j) in the preconfigured downlink subframe subset is used to indicate: in accordance with the setting order, the sequence number of the downlink subframe F(i, j) in the downlink subframes scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i, j), for example: the first indication information can be counted cumulatively in the downlink subframes scheduled in the preconfigured downlink subframe subset according to the above-mentioned setting order.

[0369] Accordingly, when the terminal 202 generates a HARQ-ACK codebook, the generated HARQ-ACK codebook includes at least one subcodebook, and the at least one subcodebook corresponds one-to-one to at least one preconfigured downlink subframe subset. The at least one preconfigured downlink subframe subset is at least one preconfigured downlink subframe subset of N preconfigured downlink subframe subsets, and the at least one preconfigured downlink subframe subset is a subset of the downlink subframes including the terminal 202 receiving the downlink scheduling information.

[0370] Wherein, at least one sub-codebook is generated in the following manner:

[0371] For a preconfigured downlink subframe subset in at least one preconfigured downlink subframe subset, the terminal 202 generates a subcodebook corresponding to the preconfigured downlink subframe subset according to the sequence number indicated by the first indication information, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of HARQ-ACK bits that need to be fed back for the downlink subframe F(i, j).

[0372] In the third embodiment, the indication information may include, in addition to the first indication information, second indication information, namely, a DAI end indication.

[0373] The second indication information corresponds to a preconfigured downlink subframe subset. There are multiple optional implementations of the corresponding second indication information, for example:

[0374] Optional implementation method 1

[0375] The second indication information is used to indicate: the total number of scheduled downlink subframes with a subframe number of j in the preconfigured downlink subframe subset including the downlink subframe F(i, j).

[0376] Optional Implementation Method 2

[0377] The second indication information is used to indicate: in the preconfigured downlink subframe subset including the downlink subframe F(i,j), the total number of downlink subframes scheduled with a subframe number j and before the downlink subframe with a subframe number j.

[0378] Optional implementation method three

[0379] The second indication information is used to indicate: the total number of scheduled downlink subframes in the preconfigured downlink subframe subset including the downlink subframe F(i, j).

[0380] Optional Implementation Method 4

[0381] The total number of transport blocks transmitted in the downlink subframe with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i,j).

[0382] Optional Implementation Method 5

[0383] The total number of transport blocks transmitted in the downlink subframe with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i,j) and in the downlink subframes before the downlink subframe with subframe number j.

[0384] Optional Implementation Method 6

[0385] The total number of transport blocks transmitted in the scheduled downlink subframes in the preconfigured downlink subframe subset including the downlink subframe F(i,j).

[0386] Optional Implementation Method 7

[0387] In the preconfigured downlink subframe subset including the downlink subframe F(i,j), the values ​​of the second indication information corresponding to the scheduled downlink subframes that are ranked from the bottom 1, 2, ..., X-1, and X in the setting order are AX-1, AX-2, ..., A1, A0 respectively, and the values ​​of the second indication information corresponding to the remaining downlink subframes are A0 respectively. The remaining downlink subframes are the downlink subframes in the preconfigured downlink subframe subset including the downlink subframe F(i,j), except for the scheduled downlink subframes ranked from the bottom 1, 2, ..., X-1, X, and AX-1, AX-2, ..., A1 and A0 are different values, where X is a positive integer greater than 1.

[0388] Optional Implementation Method 8

[0389] In the preconfigured downlink subframe subset including the downlink subframe F(i, j), the values ​​of the second indication information corresponding to the scheduled downlink subframes in the preconfigured downlink subframe subset sorted in the reverse order of the setting order are respectively cyclic values ​​of {AX-1, AX-2, ..., A1, A0}, where X is a positive integer greater than 1.

[0390] Optional Implementation Method Nine

[0391] In the preconfigured downlink subframe subset including the downlink subframe F(i,j), the values ​​of the second indication information corresponding to the downlink subframe with subframe number j that is ranked from the bottom 1, 2, ..., X-1 in the setting order, and X are respectively AX-1, AX-2, ..., A1, A0, and the values ​​of the second indication information corresponding to the remaining downlink subframes with subframe number j are respectively A0, and the remaining downlink subframes with subframe number j are the downlink subframes with subframe number j in the preconfigured downlink subframe subset including the downlink subframe F(i,j), except the downlink subframe with subframe number j that is ranked from the bottom 1, 2, ..., X-1, and X are scheduled, and AX-1, AX-2, ..., A1 and A0 are different values, where X is a positive integer greater than 1.

[0392] Optional Implementation Method 10

[0393] The values ​​of the second indication information corresponding to the scheduled downlink subframe with subframe number j in the preconfigured downlink subframe subset sorted in the reverse order of the setting order are cyclic values ​​of {AX-1, AX-2, ..., A1, A0}.

[0394] At this time, when generating the subcodebook corresponding to the pre-configured downlink subframe subset, the terminal 202 may generate a subcodebook corresponding to the pre-configured downlink subframe subset according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of HARQ-ACK that need to be fed back for the downlink subframe F(i, j), according to the sequence number indicated by the first indication information and the second indication information.

[0395] In the above description of the first indication information and the second indication information, the setting order involved may include: the order between carriers and subframes, and the carrier order and subframe order;

[0396] The order between the carrier and the subframe may include: the carrier first and then the subframe or the subframe first and then the carrier;

[0397] Among them, the carrier order may include: carrier index from small to large, or carrier index (index) from large to small; the subframe order includes: subframe time from front to back, or subframe time from back to front.

[0398] Since the preconfigured downlink subframe set M is divided into N preconfigured downlink subframe subsets, and the number of HARQ-ACK bits that need to be fed back for downlink subframes in different preconfigured downlink subframe subsets is different, the number of HARQ-ACK bits that need to be fed back for downlink subframes in the same preconfigured downlink subframe subset is the same. The first indication information and the second indication information correspond to a preconfigured downlink subframe subset, rather than to the preconfigured downlink subframe set M. In this way, the terminal 202 can accurately determine which preconfigured downlink subframe subset has been missed in terms of the first indication information and, optionally, the second indication information, and the terminal 202 also knows in advance the number of HARQ-ACK bits that need to be fed back in a preconfigured downlink subframe subset, so that when it is determined that the downlink scheduling information is missed, the correct number of HARQ-ACKs can be filled.

[0399] Below, reference Fig. 7A and Figure 7B For example. The 10 carriers of the terminal 202 are divided into two groups according to the data channel transmission mode. The carriers {1, 4, 5, 7, 10} are the first group. The 20 downlink subframes 4, 5, 6 and 8 on the first group of carriers constitute the first pre-configured downlink subframe subset, wherein the PDSCH scheduled in the current data channel transmission mode in each subframe corresponds to 1 transmission block, that is, corresponds to 1 HARQ-ACK bit; the carriers {2, 3, 6, 8, 9} are the second group. The 20 downlink subframes 4, 5, 6 and 8 on the second group of carriers constitute the second pre-configured downlink subframe subset, wherein the PDSCH scheduled in the current data channel transmission mode in each subframe corresponds to 2 transmission blocks, that is, corresponds to 2 HARQ-ACK bits.

[0400] Among them, for the first pre-configured downlink subframe subset, the downlink subframes actually scheduled are subframes 4 and 6 on all first group carriers, subframe 5 on carriers 1, 4, 5 and 10, and subframe 8 on carriers 1 and 4. These subframes constitute the first immediate scheduled downlink subframe subset.

[0401] The HARQ-ACK in the first subcodebook corresponding to the first immediate scheduled subframe downlink subset is sorted in a set order, wherein, optionally, it can be in a forward order of first carrier and then subframe, which can be specifically identified by a first indication information, namely, a DAI index indication, and the DAI index indication can be located in each downlink control channel that schedules the first immediate scheduled downlink subframe subset, and if it exists in the above-mentioned special downlink control channel, it can also be located in the special downlink control channel, or if only the above-mentioned special downlink control channel exists, it only exists in these special downlink control channels. The value of the DAI index indication can be cumulatively counted in the forward order of first carrier and then subframe. The forward order mentioned here can specifically be based on the carrier index (index), which can also be called the carrier sequence number, from small to large or from large to small, and then from first to last at the time of the subframe. Other carrier sorting methods are not excluded, as long as it is a predefined order.

[0402] Here, the DAI index indication can occupy 2 bits, representing four states {00, 01, 10, 11}. If the DAI index indication is counted cumulatively in the downlink subframe scheduled in the pre-configured downlink subframe subset, the cumulative count values ​​can be {1, 2, 3, 4} respectively. If it exceeds 4, it can be counted cyclically, that is, {1, 2, 3, 4, 5 (1), 6 (2), 7 (3)...}. It can be specifically expressed by the formula: Y = [(X-1) mod 4] + 1, where X is the count value of the actual cumulative count, such as 1 to 7 mentioned above, and Y is the value after cyclic modulo, that is, corresponding to the above {1, 2, 3, 4, 1, 2, 3}. Of course, other counting methods are not excluded, such as {0, 1, 2, 3, 0, 1, 2, 3...}, etc. The above 2-bit DAI index indication is also a specific example, and the schemes of DAI index indications with other bit numbers are similar and are not excluded.

[0403] As mentioned above, the terminal 202 can determine the downlink control channel that was missed in the middle based on the DAI index indication, but cannot determine the downlink control channel that was missed at the end. At this time, the CRC before channel coding can be combined, for example: if the UE does not determine that the downlink control channel at the end is missed, the access network device 201 will not pass the CRC check, so the access network device 201 can determine that the HARQ-ACK codebook fed back by the terminal 202 is wrong, and then perform physical layer retransmission.

[0404] Optionally, in addition to sending the first indication information, the access network device 201 may also send second indication information to help the terminal determine whether the last one or several downlink control channels in the immediate scheduling downlink subframe subset or the last one or several downlink control channels in each subframe are missed.

[0405] Here, a 2-bit DAI end indication is taken as an example. Here, it is assumed that the DAI end indication is located in each downlink control channel that schedules the above-mentioned immediate scheduled downlink subframe set. Of course, it can also be located in only a part of the downlink control channels of these scheduled downlink data channels; in addition, the DAI end indication can also be in other special downlink control channels other than these downlink data channels, such as at least one such special downlink control channel will be sent in each subframe or at least one such special downlink control channel will be sent in each immediate scheduled downlink subframe subset. These extended embodiments are not excluded.

[0406] As mentioned above, there are multiple ways to set the DAI end indication, wherein the DAI end indication can be set independently for each downlink subframe, or multiple downlink subframes can correspond to the same DAI end indication.

[0407] For example: for the optional implementation method 1 in the aforementioned embodiment 3, the DAI end indication can be set independently for each subframe to indicate the number of PDSCHs scheduled in the current subframe;

[0408] For the optional implementation method 4 in the aforementioned embodiment 3, the DAI end indication can be set independently for each subframe to indicate the number of transport blocks (Transport Block, TB) scheduled in the current subframe.

[0409] refer to Fig. 7A , each subframe in the first real-time scheduled downlink subframe subset independently sets a DAI end indication, and its value represents the total number of downlink data channels scheduled in the current subframe. This total number may or may not include the downlink data channels of the above-mentioned SPS, because the downlink data channels of the SPS are not scheduled in real time but the period and specific subframe positions are determined in advance. Therefore, whether or not to include it in the above-mentioned DAI total number indication only needs to set a rule. In addition, if the above-mentioned special downlink control channel is taken into account, the value of the above-mentioned DAI total number indication also needs to include the special downlink control channel, that is, the total number of downlink data channels of the current subframe plus the total number of the above-mentioned special downlink control channels needs to be considered.

[0410] The specific value setting method of the DAI end indication can also adopt a cyclic modulo method. For example, taking the 2-bit DAI total number indication as an example (the setting method of other bit numbers is similar), the formula Y = [(X-1) mod 4] + 1 can be used, where X is the actual total number value, such as the total number of subframe 4 is 7, and Y is the value after cyclic modulo, such as the total number of subframe 4 is set to 1.

[0411] By adopting this method, the access network device 201 does not need to make advance predictions during scheduling, thus reducing scheduling complexity. For example, when the access network device 201 performs data scheduling of subframe n, the set DAI total number indication only needs to consider the total number of downlink data channels scheduled in the current subframe n, and does not need to predict the number of subframes and specific subframe positions for data scheduling in subframe n+1 when scheduling subframe n. In addition, each subframe can also accumulate the count value of the previous subframe, as shown in the following example. Figure 5B The method shown.

[0412] For another example: for the aforementioned optional implementation method seven, the DAI end indication can be set independently for each subframe, and indicates the last X-1 scheduled PDSCHs in the current subframe.

[0413] refer to Figure 7B , in the first immediate scheduled downlink subframe subset, the values ​​of the second indication information corresponding to the scheduled downlink subframes ranked in the order of 1, 2, ..., X-1, and X are AX-1, AX-2, ..., A1, A0 respectively, and the values ​​of the second indication information corresponding to the remaining downlink subframes are A0 respectively, and the remaining downlink subframes are the downlink subframes except the scheduled downlink subframes ranked in the order of 1, 2, ..., X-1, and X in the preconfigured downlink subframe subset including the downlink subframe F(i, j), AX-1, AX-2, ..., A1 and A0 are different values, wherein X is a positive integer greater than 1. Optionally, X is 2 to the power of Y, and Y is the number of bits of the DAI end indication.

[0414] For example, taking subframe 4 as an example, and the 2-bit DAI end indication, that is, X=4, the values ​​of the DAI end indication corresponding to the 1st, 2nd and 3rd subframes from the end are A3=4, A2=3 and A1=2 respectively, and the values ​​of the DAI end indication corresponding to the remaining two subframes are both A0=1.

[0415] For another example, subframe 8 only schedules two subframes, then the values ​​of the DAI end indication corresponding to the penultimate and penultimate subframes are A3 = 4 and A2 = 3, respectively. Optionally, the DAI end indication can also be used to indicate the scheduling of the penultimate X-1 PDSCH in the first immediate scheduled downlink subframe subset, and the method for selecting the value of the DAI end indication is similar to the above method.

[0416] According to the setting rules of the DAI index indication and the DAI end indication, after the first subcodebook and the second subcodebook are determined respectively, the terminal 202 cascades the two subcodebooks, for example, the first subcodebook is arranged first and then the second codebook, or the second codebook is arranged first and then the first subcodebook, to form a final HARQ-ACK codebook.

[0417] For another example, for the above optional implementation method eight, the DAI end indication is set in the reverse order of the setting order: 4, 3, 2, 1, 4, 3, 2, 1...

[0418] It should be noted that the above-mentioned sub-codebook cascading solution combines the above-mentioned multiple sub-codebooks into a final HARQ-ACK codebook, which is more robust for the consistency of the understanding of the final codebook by the terminal 202 and the access network device 201, and is specifically described as follows:

[0419] refer to Figure 8 Taking CA of 12 FDD carriers as an example, assuming that each downlink subframe on carriers 1, 3, 5, 7, 9 and 11 corresponds to 1 HARQ-ACK bit, and each downlink subframe on carriers 2, 4, 6, 8, 10 and 12 corresponds to 2 HARQ-ACK bits, then based on the above method, the 6 downlink subframes on carriers 1, 3, 5, 7, 9 and 11 constitute the above-mentioned first pre-configured downlink subframe set, and the 6 downlink subframes on carriers 2, 4, 6, 8, 10 and 12 constitute the above-mentioned second pre-configured downlink subframe set.

[0420] Assume again that the first immediate scheduled downlink subframe subset of the terminal 202 actually scheduled by the access network device 201 is downlink subframes 1, 5, 7 and 9 in the first pre-configured downlink subframe set, and the second immediate scheduled downlink subframe subset is downlink subframes 2, 4, 6 and 8 in the second pre-configured downlink subframe set, then the value of the first indication information is 1, 2, 3 and 4 respectively for downlink subframes 1, 5, 7 and 9 in the first immediate scheduled downlink subframe subset, and is 1, 2, 3 and 4 respectively for downlink subframes 2, 4, 6 and 8 in the second immediate scheduled downlink subframe subset.

[0421] Assume again that the terminal 202 misses detecting the downlink scheduling information on the downlink subframe 5 in the first immediate-scheduling downlink subframe subset.

[0422] Based on the above assumptions, if the final HARQ-ACK codebook is not composed based on the cascade of subcodebooks, but the subcodebooks are combined based on the order of the carrier index numbers from small to large, then there may still be a small probability that the terminal 202 and the access network device 201 have inconsistent understandings of the HARQ-ACK bit order in the final codebook. Of course, such a small probability of inconsistent understanding can be solved by high-level retransmission.

[0423] For the above assumptions, the terminal 202 can determine that a downlink scheduling information is missed at the middle position between 1 and 3 in the first immediate scheduling downlink subframe, but the terminal 202 cannot determine whether the missed downlink scheduling information corresponds to carrier 3 or carrier 5. If the terminal 202 combines the subcodebooks in order from small to large according to the carrier index number, there may be two possibilities, namely: the corresponding HARQ-ACK bit sorting in the codebook after the first combination corresponds to {1, 22, 3, 44, 66, 7, 88, 9}; the corresponding downlink subframe corresponding to the HARQ-ACK bit sorting in the codebook after the second combination is {1, 22, 44, 5, 66, 7, 88, 9}, where 1 represents 1 HARQ-ACK bit of carrier 1, 22 represents 2 HARQ-ACK bits of carrier 2, and so on.

[0424] Therefore, there may be a possibility that the access network device 201 and the terminal 202 have inconsistent understandings of the final codebook, but the access network device 201 can also know in advance the missed detection subframes that the terminal 202 may not be sure of for the above situation, so the access network device 201 can at least accurately obtain the HARQ-ACK bits at other positions in the HARQ-ACK codebook without causing the downlink subframes corresponding to all HARQ-ACK bits in the HARQ-ACK codebook to start physical layer retransmission; or, the access network device 201 can choose to avoid this type of scheduling method, for example, the access network device 201 tries to perform continuous downlink subframe scheduling in the above setting order.

[0425] However, if the subcodebooks based on the above grouping are directly cascaded, the problem of inconsistent understanding of the final HARQ-ACK codebook by the above terminal 202 and the access network device 201 can be eliminated. Specifically, taking the above assumption as an example, the subcodebook corresponding to 1 HARQ-ACK bit for each subframe is in front, and the subcodebook corresponding to 2 HARQ-ACK bits for each subframe is in the back. The final cascaded HARQ-ACK codebook is {1, X, 7, 9, 22, 44, 66, 88}, where X is 3 or 5, but the access network device 201 knows which subframe 3 or 5 it actually schedules the terminal 202, so the terminal 202 cannot determine whether the 1 HARQ-ACK codebook corresponds to subframe 3 or subframe 5, but the access network device 201 can determine it.

[0426] It should be noted that the above description is made using TDD LTE as an example, but the embodiment of the present invention is also applicable to other wireless communication systems such as FDD LTE. For FDD LTE, in the pre-configured downlink subframe set M associated with an uplink subframe, there is only one downlink subframe on a downlink carrier, so the implementation scheme of the FDD LTE system in the embodiment of the present invention can be regarded as a special case of the implementation scheme of the TDD LTE system.

[0427] In addition, the embodiment of the present invention is also applicable to the CA mode of the aforementioned FDD+TDD CA. In this CA mode, in the pre-configured downlink subframe set M associated with an uplink subframe, for the FDD carrier, there is only one downlink subframe, and for the TDD carrier, according to the aforementioned HARQ-ACK timing, there may be multiple downlink subframes.

[0428] [Example 4]

[0429] Fig. 9 This is a schematic diagram of the structure of a terminal provided in Embodiment 4 of the present invention. Fig. 9 As shown, the terminal includes:

[0430] The receiving module 901 is configured to receive downlink scheduling information of a downlink subframe F(i, j), wherein the downlink subframe F(i, j) is a subframe in a pre-configured downlink subframe set M corresponding to an uplink subframe;

[0431] Wherein, F(i,j) represents the downlink subframe j on the carrier i configured for the terminal, i∈C, C is the set of all carriers configured for the terminal for downlink data transmission, j∈K, K is the set of downlink subframes corresponding to the uplink subframe;

[0432] The preconfigured downlink subframe set M is divided into N preconfigured downlink subframe subsets, N is an integer greater than or equal to 2, the number of bits of the hybrid automatic repeat request-acknowledgement HARQ-ACK that needs to be fed back for each downlink subframe in a preconfigured downlink subframe subset is a predetermined value, and the number of bits of the HARQ-ACK that needs to be fed back for any downlink subframe in different preconfigured downlink subframe subsets is different;

[0433] The receiving module 901 is further configured to: receive downlink data scheduled by downlink scheduling information in a downlink subframe F(i,j);

[0434] The processing module 902 is configured to generate a HARQ-ACK codebook according to the reception status of the downlink data received by the receiving module 901 on the downlink subframe F(i, j) and the number of bits of the HARQ-ACK that needs to be fed back for the downlink subframe F(i, j), wherein the HARQ-ACK codebook includes at least one subcodebook, and the at least one subcodebook corresponds one-to-one to at least one preconfigured downlink subframe subset, and the at least one preconfigured downlink subframe subset is at least one preconfigured downlink subframe subset in N preconfigured downlink subframe subsets, and the at least one preconfigured downlink subframe subset is a subset of downlink subframes including downlink data scheduled by the terminal receiving the downlink scheduling information; and generate uplink control information by encoding the HARQ-ACK codebook;

[0435] The sending module 903 is used to send uplink control information in an uplink subframe.

[0436] Optionally, the HARQ-ACK included in the subcodebook is the HARQ-ACK of the downlink subframe scheduled in the pre-configured downlink subframe subset corresponding to the subcodebook, but does not include the HARQ-ACK of the downlink subframe that is not scheduled in the pre-configured downlink subframe subset corresponding to the subcodebook.

[0437] Optionally, the receiving module 901 is further used to, before the processing module 902 generates the HARQ-ACK codebook, receive first indication information corresponding to the downlink subframe F(i, j) included in each preconfigured downlink subframe subset in at least one preconfigured downlink subframe subset, where the first indication information is used to indicate: in a setting order, the sequence number of the downlink subframe F(i, j) scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i, j);

[0438] The processing module 902 is specifically configured to generate at least one sub-codebook in the following manner:

[0439] For a preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of HARQ-ACK that need to be fed back for the downlink subframe F(i, j), a subcodebook corresponding to the preconfigured downlink subframe subset is generated according to the sequence number indicated by the first indication information.

[0440] Optionally, the receiving module 901 is further used to: before the processing module 902 generates the HARQ-ACK codebook, receive second indication information corresponding to each preconfigured downlink subframe subset in at least one preconfigured downlink subframe subset, and the second indication information is used to indicate content that can refer to the description in the above embodiment.

[0441] The processing module 902 is specifically used for:

[0442] For a preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of HARQ-ACK that need to be fed back for the downlink subframe F(i, j), a subcodebook corresponding to the preconfigured downlink subframe subset is generated according to the sequence number indicated by the first indication information and the second indication information.

[0443] Optionally, the receiving module 901 is further used to: before the processing module 902 generates the HARQ-ACK codebook, receive second indication information corresponding to the downlink subframe F(i, j) included in each pre-configured downlink subframe subset in at least one pre-configured downlink subframe subset;

[0444] Among them, in the preconfigured downlink subframe subset including the downlink subframe F(i, j), the values ​​of the second indication information corresponding to the scheduled downlink subframes that are ranked in the last 1, 2, ..., X-1, and X in the setting order are AX-1, AX-2, ..., A1, A0 respectively, and the values ​​of the second indication information corresponding to the remaining downlink subframes are A0 respectively, and the remaining downlink subframes are the downlink subframes in the preconfigured downlink subframe subset including the downlink subframe F(i, j), except for the scheduled downlink subframes ranked in the last 1, 2, ..., X-1, X, and AX-1, AX-2, ..., A1 and A0 are different values; or

[0445] In the preconfigured downlink subframe subset including the downlink subframe F(i, j), the values ​​of the second indication information corresponding to the scheduled downlink subframes in the preconfigured downlink subframe subset sorted in the reverse order of the setting order are respectively cyclic values ​​of {AX-1, AX-2, ..., A1, A0}; or

[0446] In the preconfigured downlink subframe subset including the downlink subframe F(i,j), the values ​​of the second indication information corresponding to the downlink subframe with the subframe number j of X that is ranked last 1, 2, ..., X-1 in the setting order are AX-1, AX-2, ..., A1, A0 respectively, and the values ​​of the second indication information corresponding to the remaining downlink subframes with the subframe number j are A0 respectively, and the remaining downlink subframes with the subframe number j are the downlink subframes with the subframe number j in the preconfigured downlink subframe subset including the downlink subframe F(i,j), except the downlink subframe with the subframe number j that is ranked last 1, 2, ..., X-1 and the downlink subframe with the subframe number j of X that is scheduled, and AX-1, AX-2, ..., A1 and A0 are different values; or

[0447] The values ​​of the second indication information corresponding to the downlink subframe with the scheduled subframe number j in the preconfigured downlink subframe subset sorted in the reverse order of the setting order are cyclic values ​​of {AX-1, AX-2, ..., A1, A0} respectively;

[0448] Wherein, X is a positive integer greater than 1;

[0449] The processing module 902 is specifically used for:

[0450] For a preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of HARQ-ACK that need to be fed back for the downlink subframe F(i, j), a subcodebook corresponding to the preconfigured downlink subframe subset is generated according to the sequence number indicated by the first indication information and the second indication information.

[0451] Optionally, the setting order may refer to the above description.

[0452] Optionally, at least one subcodebook is concatenated in the HARQ-ACK codebook.

[0453] For the optional implementation scheme of dividing the pre-configured downlink subframe set M, reference may be made to the relevant description in the first embodiment.

[0454] Among them, the processing module 902 generates a sub-codebook, and composes the generated sub-codebooks into a HARQ-ACK codebook, performs channel coding to generate uplink control information, and the optional implementation method in which the sending module 903 sends the uplink control information can refer to the processing of the terminal 202 in Embodiments 1 to 3.

[0455] Among them, the receiving module 901 receives the first indication information and the second indication information, and the processing module 902 determines the optional implementation method of the downlink subframe scheduled by the access network device according to the first indication information and the second indication information, and the processing of the terminal 202 in Examples 1 to 3 can be referred to.

[0456] Other optional implementations of the terminal provided in the fourth embodiment may refer to the aforementioned terminal 202, and the repeated parts will not be repeated here.

[0457] Specifically, the processing module 902 is used to execute the processing operation executed by the terminal 202 , the receiving module 901 is used to execute the receiving operation executed by the terminal 202 , and the sending module 903 is used to execute the sending operation executed by the terminal 202 .

[0458] Fig.10 An optional implementation of the terminal is shown, wherein the processing module 902 can be composed of Fig.10 The processor 1002 in the embodiment is implemented, and the receiving module 901 can be implemented by Fig.10 The receiver 1001 in the embodiment is implemented, and the sending module 903 can be Fig.10The transmitter 1003 in the embodiment is implemented. The bus architecture may include any number of interconnected buses and bridges, specifically various circuits of one or more processors represented by the processor 1002 and the memory represented by the memory 1004 are linked together. The bus architecture can also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The receiver 1001 and the transmitter 1003 can be implemented by a transceiver, providing a unit for communicating with various other devices on a transmission medium. For different terminals, the user interface 1005 can also be an interface that can connect externally or internally required devices, and the connected devices include but are not limited to keypads, displays, speakers, microphones, joysticks, etc.

[0459] Fig.11 Another optional implementation of the terminal is shown, wherein the processing module 902 can be composed of Fig.11 The processor 1102 in the embodiment is implemented, and the receiving module 901 can be implemented by Fig.11 The receiver 1101 in the embodiment is implemented, and the sending module 903 can be Fig.11 The transmitter 1103 in is implemented.

[0460] [Example 5]

[0461] Fig.12 This is a schematic diagram of the structure of a terminal provided in Embodiment 5 of the present invention. Fig.12 As shown, the access network equipment includes:

[0462] The sending module 1203 is configured to send downlink scheduling information of a downlink subframe F(i, j) to the terminal, and send downlink data scheduled by the downlink scheduling information to the terminal in the downlink subframe F(i, j), wherein the downlink subframe F(i, j) is a subframe in a preconfigured downlink subframe set M corresponding to the uplink subframe;

[0463] Wherein, F(i,j) represents the downlink subframe j on the carrier i configured for the terminal, i∈C, C is the set of all carriers configured for the terminal to perform downlink data transmission; j∈K, K is the set of downlink subframes corresponding to the uplink subframe;

[0464] The preconfigured downlink subframe set M is divided into N preconfigured downlink subframe subsets, N is an integer greater than or equal to 2, the number of HARQ-ACK bits required to be fed back for each downlink subframe in a preconfigured downlink subframe subset is a predetermined value, and the number of hybrid automatic repeat request-acknowledgement HARQ-ACK bits required to be fed back for any downlink subframe in different preconfigured downlink subframe subsets is different;

[0465] The receiving module 1201 is configured to receive uplink control information sent by the terminal in the first subframe for feeding back the reception status of downlink data scheduled by the downlink scheduling information;

[0466] The processing module 1202 is configured to decode the uplink control information to obtain a HARQ-ACK codebook, wherein the obtained HARQ-ACK codebook includes at least one subcodebook, the at least one subcodebook corresponds one-to-one to at least one preconfigured downlink subframe subset, the at least one preconfigured downlink subframe subset is at least one preconfigured downlink subframe subset of N preconfigured downlink subframe subsets, and the at least one preconfigured downlink subframe subset is a subset of downlink subframes containing downlink data scheduled by the downlink scheduling information.

[0467] Optionally, the HARQ-ACK included in the subcodebook is the HARQ-ACK of the downlink subframe scheduled in the pre-configured downlink subframe subset corresponding to the subcodebook, but does not include the HARQ-ACK of the downlink subframe that is not scheduled in the pre-configured downlink subframe subset corresponding to the subcodebook.

[0468] Optionally, the sending module 1203 is further used to: before the receiving module 1201 receives the uplink control information sent by the terminal, for each preconfigured downlink subframe subset included in at least one preconfigured downlink subframe subset, send first indication information corresponding to the downlink subframe F(i, j) to the terminal, where the first indication information is used to indicate: in a set order, a sequence number of the downlink subframe F(i, j) in the preconfigured downlink subframe subset including the downlink subframe F(i, j) scheduled in the downlink subframe; instruct the terminal to generate at least one subcodebook in the following manner:

[0469] For a preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j), and the number of bits of the HARQ-ACK that needs to be fed back for the downlink subframe F(i, j), a subcodebook corresponding to the preconfigured downlink subframe subset is generated according to the sequence number indicated by the first indication information.

[0470] Optionally, the sending module 1203 is further used to: before the receiving module 1201 receives the uplink control information sent by the terminal, for each preconfigured downlink subframe subset in at least one preconfigured downlink subframe subset, send second indication information to the terminal, and the second indication information is used to indicate the content of the content described in the above embodiment. Alternatively, the second indication information may indicate the terminal:

[0471] For a preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of HARQ-ACK that need to be fed back for the downlink subframe F(i, j), a subcodebook corresponding to the preconfigured downlink subframe subset is generated according to the sequence number indicated by the first indication information and the second indication information.

[0472] Optionally, the sending module 1203 is further configured to: before the receiving module 1201 receives the uplink control information sent by the terminal, for each downlink subframe F(i, j) included in at least one preconfigured downlink subframe subset, send second indication information corresponding to the downlink subframe F(i, j) to the terminal;

[0473] Among them, in the preconfigured downlink subframe subset including the downlink subframe F(i, j), the values ​​of the second indication information corresponding to the scheduled downlink subframes that are ranked in the last 1, 2, ..., X-1, and X in the setting order are AX-1, AX-2, ..., A1, A0 respectively, and the values ​​of the second indication information corresponding to the remaining downlink subframes are A0 respectively, and the remaining downlink subframes are the downlink subframes in the preconfigured downlink subframe subset including the downlink subframe F(i, j), except for the scheduled downlink subframes ranked in the last 1, 2, ..., X-1, X, and AX-1, AX-2, ..., A1 and A0 are different values; or

[0474] In the preconfigured downlink subframe subset including the downlink subframe F(i, j), the values ​​of the second indication information corresponding to the scheduled downlink subframes in the preconfigured downlink subframe subset sorted in the reverse order of the setting order are respectively cyclic values ​​of {AX-1, AX-2, ..., A1, A0}; or

[0475] In the preconfigured downlink subframe subset including the downlink subframe F(i,j), the values ​​of the second indication information corresponding to the downlink subframe with subframe number j that is ranked in the last 1, 2, ..., X-1 in the setting order, and X are respectively AX-1, AX-2, ..., A1, A0, and the values ​​of the second indication information corresponding to the remaining downlink subframes with subframe number j are respectively A0, and the remaining downlink subframes with subframe number j are the downlink subframes with subframe number j in the preconfigured downlink subframe subset including the downlink subframe F(i,j), except the downlink subframe with subframe number j that is ranked in the last 1, 2, ..., X-1, and X are scheduled, and AX-1, AX-2, ..., A1 and A0 are different values; or

[0476] The values ​​of the second indication information corresponding to the downlink subframe with the scheduled subframe number j in the preconfigured downlink subframe subset sorted in the reverse order of the setting order are cyclic values ​​of {AX-1, AX-2, ..., A1, A0} respectively;

[0477] Wherein, X is a positive integer greater than 1;

[0478] The second indication information is used to instruct the terminal: for a preconfigured downlink subframe subset in at least one preconfigured downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of HARQ-ACK bits that need to be fed back for the downlink subframe F(i, j), generate a subcodebook corresponding to the preconfigured downlink subframe subset according to the sequence number indicated by the first indication information and the second indication information.

[0479] Optionally, the setup sequence includes:

[0480] The order between carriers and subframes, and the order between carriers and subframes;

[0481] The order between the carrier and the subframe includes: first the carrier and then the subframe or first the subframe and then the carrier;

[0482] The carrier order includes: carrier index from small to large, or carrier index from large to small;

[0483] The subframe sequence includes: subframe timing from front to back, or subframe timing from back to front.

[0484] Optionally, at least one subcodebook is concatenated in the HARQ-ACK codebook.

[0485] For the optional implementation scheme of dividing the pre-configured downlink subframe set M, reference may be made to the relevant description in the first embodiment.

[0486] Among them, the processing module 1202 performs channel decoding on the received uplink control information to generate a HARQ-ACK codebook, obtains each sub-codebook, and determines the reception status of the terminal downlink data according to the HARQ-ACK codebook. Reference can be made to the processing of the access network device 201 in Embodiments 1 to 3.

[0487] The sending module 1203 sends the first indication information and the second indication information, and reference may be made to the processing of the access network device 201 in Embodiments 1 to 3.

[0488] Other optional implementations of the access network device provided in Example 5 may refer to the aforementioned access network device 201, and the repeated parts will not be repeated here.

[0489] Specifically, the processing module 1202 is used to execute the processing operation executed by the access network device 201 , the receiving module 1201 can be used to execute the receiving operation executed by the access network device 201 , and the sending module 1203 can be used to execute the sending operation executed by the access network device 201 .

[0490] Fig.13 An optional implementation of the access network device is shown, wherein the processing module 1202 can be composed of Fig.13 The processor 1302 in the embodiment is implemented, and the receiving module 1201 can be implemented by Fig.13 The receiver 1301 in the embodiment of the present invention is implemented, and the sending module 1203 can be implemented by Fig.13 The bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1302 and memory represented by memory 1304. The bus architecture may also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The receiver 1301 and the transmitter 1303 may be implemented by a transceiver, providing a unit for communicating with various other devices on a transmission medium.

[0491] Fig.14 Another optional implementation of the access network device is shown, wherein the processing module 1202 can be composed of Fig.14 The processor 1402 in the embodiment is implemented, and the receiving module 1201 can be implemented by Fig.14 The receiver 1401 in the embodiment is implemented, and the sending module 1203 can be Fig.14 The transmitter 1403 in is implemented.

[0492] [Example 6]

[0493] Fig.15 This is a flow chart of a method for sending uplink control information provided by Embodiment 6 of the present invention. Fig.15 As shown, the method comprises the following steps:

[0494] S1501: The terminal receives downlink scheduling information of a downlink subframe F(i, j), where the downlink subframe F(i, j) is a subframe in a pre-configured downlink subframe set M corresponding to the uplink subframe;

[0495] Wherein, F(i,j) represents the downlink subframe j on the carrier i configured for the terminal, i∈C, C is the set of all carriers configured for the terminal for downlink data transmission, j∈K, K is the set of downlink subframes corresponding to the uplink subframe;

[0496] The preconfigured downlink subframe set M is divided into N preconfigured downlink subframe subsets, N is an integer greater than or equal to 2, the number of bits of the hybrid automatic repeat request-acknowledgement HARQ-ACK that needs to be fed back for each downlink subframe in a preconfigured downlink subframe subset is a predetermined value, and the number of bits of the HARQ-ACK that needs to be fed back for any downlink subframe in different preconfigured downlink subframe subsets is different;

[0497] S1502: The terminal receives downlink data scheduled by downlink scheduling information in a downlink subframe F(i,j);

[0498] S1503: The terminal generates a HARQ-ACK codebook according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of the HARQ-ACK that needs to be fed back for the downlink subframe F(i, j), wherein the HARQ-ACK codebook includes at least one subcodebook, and the at least one subcodebook corresponds one-to-one to at least one preconfigured downlink subframe subset, and the at least one preconfigured downlink subframe subset is at least one preconfigured downlink subframe subset of N preconfigured downlink subframe subsets, and the at least one preconfigured downlink subframe subset is a subset of downlink subframes including downlink data scheduled by the terminal receiving the downlink scheduling information;

[0499] S1504: The terminal generates uplink control information by encoding the HARQ-ACK codebook; and

[0500] S1505: The terminal sends uplink control information in the uplink subframe.

[0501] Optionally, the HARQ-ACK included in the subcodebook is the HARQ-ACK of the downlink subframe scheduled in the pre-configured downlink subframe subset corresponding to the subcodebook, but does not include the HARQ-ACK of the downlink subframe that is not scheduled in the pre-configured downlink subframe subset corresponding to the subcodebook.

[0502] Optionally, before generating the HARQ-ACK codebook, the method further includes:

[0503] Receiving first indication information corresponding to a downlink subframe F(i, j) included in each preconfigured downlink subframe subset in at least one preconfigured downlink subframe subset, the first indication information being used to indicate: a sequence number of the downlink subframe F(i, j) in the preconfigured downlink subframe subset including the downlink subframe F(i, j) scheduled in a set order;

[0504] At least one sub-codebook is generated as follows:

[0505] For a preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, the terminal generates a subcodebook corresponding to the preconfigured downlink subframe subset according to the sequence number indicated by the first indication information, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of HARQ-ACK bits that need to be fed back for the downlink subframe F(i, j).

[0506] Optionally, before generating the HARQ-ACK codebook, the method further includes:

[0507] Second indication information corresponding to each preconfigured downlink subframe subset in at least one preconfigured downlink subframe subset is received. The content indicated by the second indication information may refer to the description in the above embodiment.

[0508] The terminal generates a subcodebook corresponding to any preconfigured downlink subframe subset according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of the HARQ-ACK that needs to be fed back for the downlink subframe F(i, j), according to the sequence number indicated by the first indication information, including:

[0509] For a preconfigured downlink subframe subset in at least one preconfigured downlink subframe subset, the terminal generates a subcodebook corresponding to the preconfigured downlink subframe subset according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of HARQ-ACK bits that need to be fed back for the downlink subframe F(i, j), according to the sequence number indicated by the first indication information and the second indication information.

[0510] Optionally, before generating the HARQ-ACK codebook, the method further includes:

[0511] Receiving second indication information corresponding to the downlink subframe F(i, j) included in each preconfigured downlink subframe subset in at least one preconfigured downlink subframe subset;

[0512] Among them, in the preconfigured downlink subframe subset including the downlink subframe F(i, j), the values ​​of the second indication information corresponding to the scheduled downlink subframes that are ranked in the last 1, 2, ..., X-1, and X in the setting order are AX-1, AX-2, ..., A1, A0 respectively, and the values ​​of the second indication information corresponding to the remaining downlink subframes are A0 respectively, and the remaining downlink subframes are the downlink subframes in the preconfigured downlink subframe subset including the downlink subframe F(i, j), except for the scheduled downlink subframes ranked in the last 1, 2, ..., X-1, X, and AX-1, AX-2, ..., A1 and A0 are different values; or

[0513] In the preconfigured downlink subframe subset including the downlink subframe F(i, j), the values ​​of the second indication information corresponding to the scheduled downlink subframes in the preconfigured downlink subframe subset sorted in the reverse order of the setting order are respectively cyclic values ​​of {AX-1, AX-2, ..., A1, A0}; or

[0514] In the preconfigured downlink subframe subset including the downlink subframe F(i,j), the values ​​of the second indication information corresponding to the downlink subframe with the subframe number j of X that is ranked last 1, 2, ..., X-1 in the setting order are AX-1, AX-2, ..., A1, A0 respectively, and the values ​​of the second indication information corresponding to the remaining downlink subframes with the subframe number j are A0 respectively, and the remaining downlink subframes with the subframe number j are the downlink subframes with the subframe number j in the preconfigured downlink subframe subset including the downlink subframe F(i,j), except the downlink subframe with the subframe number j that is ranked last 1, 2, ..., X-1 and the downlink subframe with the subframe number j of X that is scheduled, and AX-1, AX-2, ..., A1 and A0 are different values; or

[0515] The values ​​of the second indication information corresponding to the downlink subframe with the scheduled subframe number j in the preconfigured downlink subframe subset sorted in the reverse order of the setting order are cyclic values ​​of {AX-1, AX-2, ..., A1, A0} respectively;

[0516] Wherein, X is a positive integer greater than 1;

[0517] The terminal generates a subcodebook corresponding to any preconfigured downlink subframe subset according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of the HARQ-ACK that needs to be fed back for the downlink subframe F(i, j), according to the sequence number indicated by the first indication information, including:

[0518] For a preconfigured downlink subframe subset in at least one preconfigured downlink subframe subset, the terminal generates a subcodebook corresponding to the preconfigured downlink subframe subset according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of HARQ-ACK bits that need to be fed back for the downlink subframe F(i, j), according to the sequence number indicated by the first indication information and the second indication information.

[0519] Optionally, the setting order may refer to the above description.

[0520] Optionally, at least one subcodebook is concatenated in the HARQ-ACK codebook.

[0521] For the optional implementation scheme of dividing the pre-configured downlink subframe set M, reference may be made to the relevant description in the first embodiment.

[0522] Among them, the terminal generates a sub-codebook, and composes the generated sub-codebooks into a HARQ-ACK codebook, performs channel coding to generate uplink control information, and an optional implementation method of sending the uplink control information can refer to the processing of the terminal 202 in Embodiments 1 to 3.

[0523] The terminal receives the first indication information and the second indication information, and determines an optional implementation method of the downlink subframe scheduled by the access network device according to the first indication information and the second indication information. Reference may be made to the processing of the terminal 202 in Embodiments 1 to 3.

[0524] Other optional implementations of the uplink control information sending method provided in Embodiment 6 may refer to the aforementioned terminal 202, and the repeated parts will not be repeated here.

[0525] [Example 7]

[0526] Fig.16 This is a flow chart of a method for receiving uplink control information provided by Embodiment 7 of the present invention. Fig.16 As shown, the method comprises the following steps:

[0527] S1601: The access network device sends downlink scheduling information of a downlink subframe F(i, j) to the terminal, and sends downlink data scheduled by the downlink scheduling information to the terminal in the downlink subframe F(i, j), wherein the downlink subframe F(i, j) is a subframe in a preconfigured downlink subframe set M corresponding to the uplink subframe;

[0528] Wherein, F(i,j) represents the downlink subframe j on the carrier i configured for the terminal, i∈C, C is the set of all carriers configured for the terminal to perform downlink data transmission; j∈K, K is the set of downlink subframes corresponding to the uplink subframe;

[0529] The preconfigured downlink subframe set M is divided into N preconfigured downlink subframe subsets, N is an integer greater than or equal to 2, the number of HARQ-ACK bits required to be fed back for each downlink subframe in a preconfigured downlink subframe subset is a predetermined value, and the number of hybrid automatic repeat request-acknowledgement HARQ-ACK bits required to be fed back for any downlink subframe in different preconfigured downlink subframe subsets is different;

[0530] S1602: receiving uplink control information sent by the terminal in the first subframe for feeding back reception status of downlink data scheduled by the downlink scheduling information;

[0531] S1603: Decode the received uplink control information to obtain a HARQ-ACK codebook, wherein the obtained HARQ-ACK codebook includes at least one subcodebook, the at least one subcodebook corresponds one-to-one to at least one preconfigured downlink subframe subset, the at least one preconfigured downlink subframe subset is at least one preconfigured downlink subframe subset among N preconfigured downlink subframe subsets, and the at least one preconfigured downlink subframe subset is a subset of downlink subframes containing downlink data scheduled by downlink scheduling information.

[0532] Optionally, the HARQ-ACK included in the subcodebook is the HARQ-ACK of the downlink subframe scheduled in the pre-configured downlink subframe subset corresponding to the subcodebook, but does not include the HARQ-ACK of the downlink subframe that is not scheduled in the pre-configured downlink subframe subset corresponding to the subcodebook.

[0533] Optionally, before receiving the uplink control information sent by the terminal, the method further includes:

[0534] For each downlink subframe F(i, j) included in at least one preconfigured downlink subframe subset, first indication information corresponding to the downlink subframe F(i, j) is sent to the terminal, where the first indication information is used to indicate: the sequence number of the downlink subframe F(i, j) in the downlink subframes scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i, j) in the setting order;

[0535] Instruct the terminal to generate at least one sub-codebook in the following manner:

[0536] For a preconfigured downlink subframe subset in the at least one preconfigured downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j), and the number of bits of the HARQ-ACK that needs to be fed back for the downlink subframe F(i, j), a subcodebook corresponding to the preconfigured downlink subframe subset is generated according to the sequence number indicated by the first indication information.

[0537] Optionally, before receiving the uplink control information sent by the terminal, the method further includes:

[0538] For each preconfigured downlink subframe subset in at least one preconfigured downlink subframe subset, second indication information is sent to the terminal, where the second indication information is used to indicate:

[0539] The total number of downlink subframes with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i,j); or the total number of downlink subframes with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i,j) and the downlink subframes before the downlink subframe time with subframe number j; or the total number of downlink subframes scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i,j); or the total number of transport blocks transmitted in the downlink subframe with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i,j); or the total number of transport blocks transmitted in the downlink subframe with subframe number j scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i,j) and the downlink subframes before the downlink subframe time with subframe number j; or the total number of transport blocks transmitted in the downlink subframes scheduled in the preconfigured downlink subframe subset including the downlink subframe F(i,j);

[0540] Instruct the terminal: for a preconfigured downlink subframe subset in at least one preconfigured downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of HARQ-ACK that need to be fed back for the downlink subframe F(i, j), generate a subcodebook corresponding to the preconfigured downlink subframe subset according to the sequence number indicated by the first indication information and the second indication information.

[0541] Optionally, before receiving the uplink control information sent by the terminal, the method further includes:

[0542] For each downlink subframe F(i, j) included in at least one preconfigured downlink subframe subset, sending second indication information corresponding to the downlink subframe F(i, j) to the terminal;

[0543] Among them, in the preconfigured downlink subframe subset including the downlink subframe F(i, j), the values ​​of the second indication information corresponding to the scheduled downlink subframes that are ranked in the last 1, 2, ..., X-1, and X in the setting order are AX-1, AX-2, ..., A1, A0 respectively, and the values ​​of the second indication information corresponding to the remaining downlink subframes are A0 respectively, and the remaining downlink subframes are the downlink subframes in the preconfigured downlink subframe subset including the downlink subframe F(i, j), except for the scheduled downlink subframes ranked in the last 1, 2, ..., X-1, X, and AX-1, AX-2, ..., A1 and A0 are different values; or

[0544] In the preconfigured downlink subframe subset including the downlink subframe F(i, j), the values ​​of the second indication information corresponding to the scheduled downlink subframes in the preconfigured downlink subframe subset sorted in the reverse order of the setting order are respectively cyclic values ​​of {AX-1, AX-2, ..., A1, A0}; or

[0545] In the preconfigured downlink subframe subset including the downlink subframe F(i,j), the values ​​of the second indication information corresponding to the downlink subframe with subframe number j that is ranked in the last 1, 2, ..., X-1 in the setting order, and X are respectively AX-1, AX-2, ..., A1, A0, and the values ​​of the second indication information corresponding to the remaining downlink subframes with subframe number j are respectively A0, and the remaining downlink subframes with subframe number j are the downlink subframes with subframe number j in the preconfigured downlink subframe subset including the downlink subframe F(i,j), except the downlink subframe with subframe number j that is ranked in the last 1, 2, ..., X-1, and X are scheduled, and AX-1, AX-2, ..., A1 and A0 are different values; or

[0546] The values ​​of the second indication information corresponding to the downlink subframe with the scheduled subframe number j in the preconfigured downlink subframe subset sorted in the reverse order of the setting order are cyclic values ​​of {AX-1, AX-2, ..., A1, A0} respectively;

[0547] Wherein, X is a positive integer greater than 1;

[0548] Instruct the terminal: for a preconfigured downlink subframe subset in at least one preconfigured downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of HARQ-ACK that need to be fed back for the downlink subframe F(i, j), generate a subcodebook corresponding to the preconfigured downlink subframe subset according to the sequence number indicated by the first indication information and the second indication information.

[0549] Optionally, the setting order may refer to the above description.

[0550] Optionally, at least one subcodebook is concatenated in the HARQ-ACK codebook.

[0551] For the optional implementation scheme of dividing the pre-configured downlink subframe set M, reference may be made to the relevant description in the first embodiment.

[0552] Among them, the uplink control information received by the access network device is channel decoded to generate a HARQ-ACK codebook, each sub-codebook is obtained, and the reception status of the terminal downlink data is determined according to the HARQ-ACK codebook. Reference can be made to the processing of the access network device 201 in Embodiments 1 to 3.

[0553] The access network device sends the first indication information and the second indication information, and reference may be made to the processing of the access network device 201 in Embodiments 1 to 3.

[0554] Other optional implementations of the uplink control information receiving method provided in Embodiment 7 may refer to the aforementioned access network device 201, and the repeated parts will not be repeated here.

[0555] In summary, in the embodiment of the present invention, since the preconfigured downlink subframe set M is divided into the above-mentioned N preconfigured downlink subframe subsets, the number of HARQ-ACK bits that need to be fed back for each downlink subframe in a preconfigured downlink subframe subset is a predetermined value, and the number of HARQ-ACK bits that need to be fed back for any downlink subframe in different preconfigured downlink subframe subsets is different. In this way, when the terminal generates an ACK / NACK codebook, HARQ-ACK is fed back according to the number of HARQ-ACK bits that need to be fed back for the downlink subframe in a preconfigured downlink subframe subset. In this way, after receiving the uplink control information generated by the HARQ-ACK codebook, the access network device also parses the ACK / NACK codebook according to the number of HARQ-ACK bits that need to be fed back for the downlink subframe in the preconfigured downlink subframe subset, and provides a HARQ-ACK feedback scheme, which can support the situation where the number of HARQ-ACK bits that need to be fed back for downlink subframes on different aggregated carriers is different.

[0556] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0557] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0558] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0559] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0560] Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention.

[0561] Obviously, those skilled in the art can make various changes and modifications to the embodiments of the present invention without departing from the spirit and scope of the embodiments of the present invention. Thus, if these modifications and variations of the embodiments 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 these modifications and variations.

Claims

1. A method for sending uplink control information, characterized in that: include: receiving downlink scheduling information; receiving downlink data scheduled by the downlink scheduling information in a downlink subframe F(i,j), wherein the downlink subframe F(i,j) belongs to a downlink subframe set consisting of all downlink subframes on all aggregated carriers corresponding to an uplink subframe according to the timing relationship between a physical downlink shared channel PDSCH and a corresponding hybrid automatic repeat request-acknowledgement HARQ-ACK; the downlink subframe F(i,j) represents a downlink subframe j on carrier i configured for the terminal, i∈C, C is a set of all carriers configured for the terminal for downlink data transmission, j∈K, K is a set of downlink subframes corresponding to the uplink subframe; wherein the downlink subframe set is divided into N downlink subframe subsets, N is an integer greater than or equal to 2, wherein the number of HARQ-ACK bits required to be fed back for each downlink subframe in the same downlink subframe subset is the same, and the number of HARQ-ACK bits required to be fed back for any downlink subframe in different downlink subframe subsets is different; Generate a HARQ-ACK codebook according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of the HARQ-ACK that needs to be fed back for the downlink subframe F(i, j), wherein the HARQ-ACK codebook includes at least one subcodebook, and the at least one subcodebook corresponds one-to-one to at least one downlink subframe subset of the N downlink subframe subsets, and the at least one downlink subframe subset is a subset of downlink subframes including the downlink data received by the terminal; and and sending uplink control information including the HARQ-ACK codebook on the uplink subframe.

2. The method according to claim 1, characterized in that The HARQ-ACK included in any subcodebook of the at least one subcodebook is the HARQ-ACK of the downlink subframe scheduled in the downlink subframe subset corresponding to any subcodebook, but does not include the HARQ-ACK of the downlink subframe that is not scheduled in the downlink subframe subset corresponding to any subcodebook.

3. The method according to claim 1 or 2, characterized in that Before generating the HARQ-ACK codebook, the method further includes: Receiving first indication information corresponding to the downlink subframe F(i, j) included in each downlink subframe subset in the at least one downlink subframe subset, wherein the first indication information is used to indicate: a sequence number of the downlink subframe F(i, j) in the downlink subframe subset including the downlink subframe F(i, j) scheduled in a setting order; The at least one sub-codebook is generated in the following manner: For a downlink subframe subset in the at least one downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of HARQ-ACK that need to be fed back for the downlink subframe F(i, j), generate a subcodebook corresponding to the downlink subframe subset according to the sequence number indicated by the first indication information.

4. The method according to claim 3, characterized in that Before generating the HARQ-ACK codebook, the method further includes: receiving second indication information corresponding to each downlink subframe subset in the at least one downlink subframe subset, where the second indication information is used to indicate: in the downlink subframe subset including the downlink subframe F(i,j), the total number of downlink subframes scheduled with a subframe number j and scheduled downlink subframes before the downlink subframe time with the subframe number j; The generating, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of the HARQ-ACK that needs to be fed back for the downlink subframe F(i, j), a subcodebook corresponding to the one downlink subframe subset according to the sequence number indicated by the first indication information, includes: For a downlink subframe subset of the at least one downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of HARQ-ACK that need to be fed back for the downlink subframe F(i, j), a subcodebook corresponding to the downlink subframe subset is generated according to the sequence number indicated by the first indication information and the second indication information.

5. The method according to claim 3, characterized in that The setting sequence includes: The order between carriers and subframes, and the order between carriers and subframes; The order between the carrier and the subframe includes: first the carrier and then the subframe or first the subframe and then the carrier; The carrier order includes: carrier index from small to large, or carrier index from large to small; The subframe sequence includes: subframe timing from front to back, or subframe timing from back to front.

6. The method according to claim 1 or 2, characterized in that: The at least one subcodebook is concatenated in the HARQ-ACK codebook.

7. The method according to claim 1 or 2, characterized in that: In the HARQ-ACK codebook, the subcodebook corresponding to the downlink subframe subset for which a small number of HARQ-ACK bits need to be fed back is before the subcodebook corresponding to the downlink subframe subset for which a large number of HARQ-ACK bits need to be fed back.

8. A method for receiving uplink control information, characterized in that: include: Sending downlink scheduling information to the terminal; Sending downlink data scheduled by the downlink scheduling information to the terminal in a downlink subframe F(i, j), wherein the downlink subframe F(i, j) belongs to a downlink subframe set consisting of all downlink subframes on all aggregated carriers corresponding to an uplink subframe according to a timing relationship between a physical downlink shared channel PDSCH and a corresponding hybrid automatic repeat request-acknowledgement HARQ-ACK, F(i, j) represents a downlink subframe j on carrier i configured for the terminal, i∈C, C is a set of all carriers configured for the terminal for downlink data transmission, j∈K, K is a set of downlink subframes corresponding to the uplink subframe, the downlink subframe set is divided into N downlink subframe subsets, N is an integer greater than or equal to 2, the number of HARQ-ACK bits required to be fed back for each downlink subframe in the same downlink subframe subset is the same, and the number of HARQ-ACK bits required to be fed back for any downlink subframe in different downlink subframe subsets is different; Receiving, in the uplink subframe, uplink control information from the terminal including uplink control information for feeding back a reception status of the downlink data; The received uplink control information is decoded to obtain a HARQ-ACK codebook, wherein the HARQ-ACK codebook includes at least one subcodebook, and the at least one subcodebook corresponds one-to-one to at least one downlink subframe subset of the N downlink subframe subsets, and the at least one downlink subframe subset is a subset of downlink subframes including downlink data scheduled by the downlink scheduling information.

9. The method according to claim 8, characterized in that The HARQ-ACK included in any subcodebook in the at least one subcodebook is the HARQ-ACK of the downlink subframe scheduled in the downlink subframe subset corresponding to any subcodebook, but does not include the HARQ-ACK of the downlink subframe that is not scheduled in the downlink subframe subset corresponding to any subcodebook.

10. The method according to claim 8 or 9, characterized in that Before receiving the uplink control information sent by the terminal, the method further includes: For a downlink subframe F(i,j) included in a downlink subframe subset in the at least one downlink subframe subset, first indication information corresponding to the downlink subframe F(i,j) is sent to the terminal, wherein the first indication information is used to indicate: the sequence number of the downlink subframe F(i,j) in the downlink subframes scheduled in the downlink subframe subset including the downlink subframe F(i,j) in a set order.

11. The method according to claim 10, characterized in that The subcodebook corresponding to the one downlink subframe subset is generated according to the reception status of the downlink data received on the downlink subframe F(i, j) in the one downlink subframe subset, and the number of HARQ-ACK bits that need to be fed back for the downlink subframe F(i, j), and according to the sequence number indicated by the first indication information.

12. The method according to claim 10, characterized in that Before receiving the uplink control information sent by the terminal, the method further includes: For a downlink subframe subset in the at least one downlink subframe subset, second indication information is sent to the terminal, wherein the second indication information is used to indicate: in the downlink subframe subset including the downlink subframe F(i,j), the downlink subframe with subframe number j scheduled and the total number of scheduled downlink subframes before the downlink subframe with subframe number j.

13. The method according to claim 12, characterized in that The subcodebook corresponding to the one downlink subframe subset is generated according to the reception status of the downlink data received on the downlink subframe F(i, j) in the one downlink subframe subset and the number of HARQ-ACK bits that need to be fed back for the downlink subframe F(i, j), and according to the sequence number indicated by the first indication information and the second indication information.

14. The method according to claim 10, characterized in that The setting sequence includes: The order between carriers and subframes, and the order between carriers and subframes; The order between the carrier and the subframe includes: first the carrier and then the subframe or first the subframe and then the carrier; The carrier order includes: carrier index from small to large, or carrier index from large to small; The subframe sequence includes: subframe timing from front to back, or subframe timing from back to front.

15. The method according to claim 8 or 9, characterized in that The at least one subcodebook is concatenated in the HARQ-ACK codebook.

16. The method according to claim 8 or 9, characterized in that In the HARQ-ACK codebook, the subcodebook corresponding to the downlink subframe subset for which a small number of HARQ-ACK bits need to be fed back is before the subcodebook corresponding to the downlink subframe subset for which a large number of HARQ-ACK bits need to be fed back.

17. An uplink control information sending device in a terminal, comprising a processor, wherein the processor is used to call a program to implement the method according to any one of claims 1 to 7.

18. An uplink control information receiving device in an access network device, comprising a processor, wherein the processor is used to call a program to implement the method according to any one of claims 8 to 16.

19. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

20. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 8 to 16 is implemented.

21. A terminal, characterized in that: include: A receiver, a processor and a transmitter, wherein, The receiver is used to receive downlink scheduling information; The receiver is also used to receive downlink data scheduled by the downlink scheduling information in a downlink subframe F(i, j), wherein the downlink subframe F(i, j) belongs to a downlink subframe set consisting of all downlink subframes on all aggregated carriers corresponding to an uplink subframe according to the timing relationship between a physical downlink shared channel PDSCH and a corresponding hybrid automatic repeat request-acknowledgement HARQ-ACK; the downlink subframe F(i, j) represents a downlink subframe j on carrier i configured for the terminal, i∈C, C is a set of all carriers configured for the terminal for downlink data transmission, j∈K, K is a set of downlink subframes corresponding to the uplink subframe; wherein the downlink subframe set is divided into N downlink subframe subsets, N is an integer greater than or equal to 2, wherein the number of bits of the hybrid automatic repeat request-acknowledgement HARQ-ACK that needs to be fed back for each downlink subframe in the same downlink subframe subset is the same, and the number of bits of the HARQ-ACK that needs to be fed back for any downlink subframe in different downlink subframe subsets is different; The processor is configured to generate a HARQ-ACK codebook according to a reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of the HARQ-ACK that needs to be fed back for the downlink subframe F(i, j), wherein the HARQ-ACK codebook includes at least one subcodebook, the at least one subcodebook corresponds one-to-one to at least one downlink subframe subset of the N downlink subframe subsets, and the at least one downlink subframe subset is a subset of downlink subframes including downlink subframes in which the terminal receives downlink data; and The transmitter is configured to send uplink control information including the HARQ-ACK codebook in the uplink subframe.

22. The terminal according to claim 21, characterized in that The HARQ-ACK included in any subcodebook of the at least one subcodebook is the HARQ-ACK of the downlink subframe scheduled in the downlink subframe subset corresponding to any subcodebook, but does not include the HARQ-ACK of the downlink subframe that is not scheduled in the downlink subframe subset corresponding to any subcodebook.

23. The terminal according to claim 21 or 22, characterized in that: The receiver is further configured to receive first indication information corresponding to a downlink subframe F(i, j) included in each downlink subframe subset in the at least one downlink subframe subset, wherein the first indication information is used to indicate: a sequence number of the downlink subframe F(i, j) in the downlink subframe subset including the downlink subframe F(i, j) scheduled in a set order; The processor generates the at least one sub-codebook in the following manner: For a downlink subframe subset in the at least one downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of HARQ-ACK that need to be fed back for the downlink subframe F(i, j), generate a subcodebook corresponding to the downlink subframe subset according to the sequence number indicated by the first indication information.

24. The terminal according to claim 23, characterized in that The receiver is further configured to receive second indication information corresponding to each downlink subframe subset in the at least one downlink subframe subset, wherein the second indication information is used to indicate: in the downlink subframe subset including the downlink subframe F(i, j), the total number of downlink subframes scheduled with a subframe number j and scheduled before the downlink subframe time with the subframe number j; The processor is configured to generate a subcodebook corresponding to the one downlink subframe subset according to a reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of the HARQ-ACK that needs to be fed back by the downlink subframe F(i, j), according to a sequence number indicated by the first indication information, in the following manner: For a downlink subframe subset of the at least one downlink subframe subset, according to the reception status of the downlink data received on the downlink subframe F(i, j) and the number of bits of HARQ-ACK that need to be fed back for the downlink subframe F(i, j), a subcodebook corresponding to the downlink subframe subset is generated according to the sequence number indicated by the first indication information and the second indication information.

25. The terminal according to claim 23, characterized in that The setting sequence includes: The order between carriers and subframes, and the order between carriers and subframes; The order between the carrier and the subframe includes: first the carrier and then the subframe or first the subframe and then the carrier; The carrier order includes: carrier index from small to large, or carrier index from large to small; The subframe sequence includes: subframe timing from front to back, or subframe timing from back to front.

26. The terminal according to claim 21 or 22, characterized in that: The at least one subcodebook is concatenated in the HARQ-ACK codebook.

27. The terminal according to claim 21 or 22, characterized in that: In the HARQ-ACK codebook, the subcodebook corresponding to the downlink subframe subset for which a small number of HARQ-ACK bits need to be fed back is before the subcodebook corresponding to the downlink subframe subset for which a large number of HARQ-ACK bits need to be fed back.

28. An access network device, characterized in that: include: A receiver, a processor, and a transmitter, wherein: The transmitter is used to send downlink scheduling information to the terminal; The transmitter is further used to send the downlink data scheduled by the downlink scheduling information to the terminal in a downlink subframe F(i, j), wherein the downlink subframe F(i, j) belongs to a downlink subframe set consisting of all downlink subframes on all aggregated carriers corresponding to an uplink subframe according to the timing relationship between a physical downlink shared channel PDSCH and a corresponding hybrid automatic repeat request-acknowledgement HARQ-ACK, F(i, j) represents a downlink subframe j on carrier i configured for the terminal, i∈C, C is a set of all carriers configured for the terminal for downlink data transmission, j∈K, K is a set of downlink subframes corresponding to the uplink subframe, the downlink subframe set is divided into N downlink subframe subsets, N is an integer greater than or equal to 2, the number of bits of HARQ-ACK required to be fed back for each downlink subframe in the same downlink subframe subset is the same, and the number of bits of hybrid automatic repeat request-acknowledgement HARQ-ACK required to be fed back for any downlink subframe in different downlink subframe subsets is different; The receiver is used to receive, in the uplink subframe, uplink control information including uplink control information for feeding back a reception status of the downlink data from the terminal; The processor is configured to decode the received uplink control information to obtain a HARQ-ACK codebook, wherein the HARQ-ACK codebook includes at least one subcodebook, and the at least one subcodebook corresponds one-to-one to at least one downlink subframe subset of the N downlink subframe subsets, and the at least one downlink subframe subset is a subset of downlink subframes including downlink data scheduled by the downlink scheduling information.

29. The access network device according to claim 28, characterized in that: The HARQ-ACK included in any subcodebook in the at least one subcodebook is the HARQ-ACK of the downlink subframe scheduled in the downlink subframe subset corresponding to any subcodebook, but does not include the HARQ-ACK of the downlink subframe that is not scheduled in the downlink subframe subset corresponding to any subcodebook.

30. The access network device according to claim 28 or 29, characterized in that: The transmitter is also used to send, to the terminal, first indication information corresponding to a downlink subframe F(i,j) included in a downlink subframe subset among the at least one downlink subframe subset, wherein the first indication information is used to indicate: in a set order, the sequence number of the downlink subframe F(i,j) in the downlink subframe subset scheduled including the downlink subframe F(i,j).

31. The access network device according to claim 30, characterized in that: The subcodebook corresponding to the one downlink subframe subset is generated according to the reception status of the downlink data received on the downlink subframe F(i, j) in the one downlink subframe subset, and the number of HARQ-ACK bits that need to be fed back for the downlink subframe F(i, j), and according to the sequence number indicated by the first indication information.

32. The access network device according to claim 30, characterized in that: Before receiving the uplink control information sent by the terminal, the method further includes: For a downlink subframe subset in the at least one downlink subframe subset, second indication information is sent to the terminal, wherein the second indication information is used to indicate: in the downlink subframe subset including the downlink subframe F(i,j), the downlink subframe with subframe number j scheduled and the total number of scheduled downlink subframes before the downlink subframe with subframe number j.

33. The access network device according to claim 32, characterized in that: The subcodebook corresponding to the one downlink subframe subset is generated according to the reception status of the downlink data received on the downlink subframe F(i, j) in the one downlink subframe subset and the number of HARQ-ACK bits that need to be fed back for the downlink subframe F(i, j), and according to the sequence number indicated by the first indication information and the second indication information.

34. The access network device according to claim 30, characterized in that: The setting sequence includes: The order between carriers and subframes, and the order between carriers and subframes; The order between the carrier and the subframe includes: first the carrier and then the subframe or first the subframe and then the carrier; The carrier order includes: carrier index from small to large, or carrier index from large to small; The subframe sequence includes: subframe timing from front to back, or subframe timing from back to front.

35. The access network device according to claim 28 or 29, characterized in that: The at least one subcodebook is concatenated in the HARQ-ACK codebook.

36. The access network device according to claim 28 or 29, characterized in that: In the HARQ-ACK codebook, the subcodebook corresponding to the downlink subframe subset for which a small number of HARQ-ACK bits need to be fed back is before the subcodebook corresponding to the downlink subframe subset for which a large number of HARQ-ACK bits need to be fed back.

Images