Patent Description:
With development and evolvement of demands on mobile communication services, multiple organizations, such as International Telecommunication Union (ITU), are beginning to research <NUM>th generation new radio access technology (<NUM> Generation New RAT (Radio Access Technology), <NUM> NR) for future mobile communication systems. In a <NUM> NR system, uplink control information (Uplink Control Information, UCI) is coded by using polar codes when a bit count of the UCI exceeds <NUM> bits. A polar encoder needs to append cyclic redundancy check (Cyclic Redundancy Check, CRC) bits to the UCI. For UCI of <NUM> bits to <NUM> bits, a quantity of polar-encoded CRC bits is <NUM>; for UCI with a bit count greater than <NUM> bits, the quantity of polar-encoded CRC bits is <NUM>. Particularly, in a case that the bit count of UCI is greater than or equal to <NUM> bits, in consideration of an encoding characteristic and a performance of polar encoder, it is necessary to further determine whether UCI segmentation is to be performed. Specifically, whether UCI is to be segmented is determined according to an encoded bit count of the UCI. For example, if the bit count of UCI is greater than or equal to <NUM> bits and the encoded bit count of UCI is greater than or equal to <NUM> bits, or if the bit count of UCI is greater than or equal to <NUM> bits, the UCI is segmented. In segmenting the UCI, original UCI bits are segmented into two group. Each group undergoes polar encoding separately, then each group has <NUM> bits of CRC appended thereto. Thus, a decision as to whether to segment the UCI influences a final CRC bit count, i.e., the CRC bit count is <NUM> bits if no segmentation is performed, and the CRC bit count is <NUM>+<NUM>=<NUM> bits if the segmentation is performed.

In NR, multiple physical uplink control channel (PUCCH) resources may be configured for transmitting multiple channel state information (CSI) reports. In case of a collision of multiple CSI reports, the CSI reports may be transmitted simultaneously on the PUCCH resources for transmitting multiple CSI reports, to avoid discarding too much CSI. According to a CSI bit count and corresponding CRC bit count, a PUCCH resource meeting a configured target code rate may be selected from the multiple PUCCH resources for transmitting multiple CSI reports.

In NR, if it is determined to transmit one or more types of UCI on a certain PUCCH resource, a minimum resource block (Resource Block, RB) count meeting a target code rate may further be determined according to a total UCI bit count and a total CRC bit count to transmit the UCI, in order to reduce PUCCH resource overhead, wherein the RB count may not exceed the quantity of RBs contained in the determined PUCCH resource.

The CRC bit count is required to determine the PUCCH resource for carrying the UCI. However, in the case that the UCI bit count is greater than or equal to <NUM> bits, there is no definite solution to UCI transmission since, absent the knowledge of the PUCCH resource, whether UCI is to be segmented cannot be determined, and then the actual CRC bit count cannot be determined.

A 3GPP draft R1-<NUM> discloses the number of CRC bits with regard to the RB selection of a PUCCH resource.

A <CIT> discloses a terminal apparatus, a base station apparatus, and a communication method capable of efficiently performing uplink transmission.

A 3GPP draft R1-<NUM> discloses For long PUCCH formats there are some remaining issues that should be resolved to complete the specifications. This contribution addresses these issues including CRC length determination when determining the PUCCH resources, UCI type supported when UCI repetition on PUCCH is applied and UCI multiplexing when multi-slot PUCCH overlaps with PUSCH.

An objective of the present invention is to provide an information transmission method, an information reception method, a terminal and a base station, as defined in accompanying claims, to solve the problem that when a bit count of UCI is greater than or equal to <NUM> bits and whether UCI is to be segmented cannot be determined, the actual CRC bit count cannot be determined, and then there is no definite solution to UCI transmission.

The embodiments of the present invention have the following beneficial effects: in the foregoing technical solutions of the embodiments of the present disclosure, it is judged whether a bit count of uplink control information (UCI) meets a predetermined bit count range; in a case that the bit count of the UCI meets the predetermined bit count range, a resource for transmitting the UCI is determined according to a reference cyclic redundancy check (CRC) bit count; the UCI is transmitted on the determined resource for transmitting the UCI, thus the problem of being difficult to determine CRC bit count, when the PUCCH resource for transmitting the UCI is determined according to the CRC bit count, is solved, and consistent understanding of UCI transmission resource between the base station and the terminal can be ensured, so that the proper UCI transmission is ensured.

To describe the technical problem to be solved, the technical solutions and the advantages of the present invention more clearly, specific embodiments are described in detail hereinafter with reference to the accompanying drawings.

As shown in <FIG>, an embodiment of the present disclosure provides an information transmission method. The method is applied to a terminal and includes step <NUM>, step <NUM> and step <NUM>.

Step <NUM>: Judging whether a bit count of uplink control information (UCI) meets a predetermined bit count range.

The predetermined bit count range is greater than or equal to a first bit count value and less than a second bit count value; or, the predetermined bit count range is greater than or equal to the first bit count value.

The first bit count value is <NUM>, and/or the second bit count value is <NUM>. In embodiments of the present disclosure, the UCI includes, but is not limited to, at least one of a hybrid automatic repeat request-acknowledgement (Hybrid Automatic Repeat Request-Acknowledgement, HARQ-ACK), channel state information (CSI) or a scheduling request (Scheduling Request, SR).

Step <NUM>: In a case that the bit count of the UCI meets the predetermined bit count range, determining a resource for transmitting the UCI according to a reference cyclic redundancy check (CRC) bit count.

The reference CRC bit count is determined through the following steps:.

In the case that the first encoded bit count is greater than or equal to <NUM> (the second encoded bit count is surely greater than <NUM> in this case), it is determined that the reference CRC bit count is <NUM> bits, i.e., it is may be confirmed that the UCI needs to be segmented, in other words, the size of resource for transmitting the UCI is determined based on CRC of <NUM> bits; in the case that the second encoded bit count is less than <NUM> (the first encoded bit count is surely less than <NUM> in this case), it is determined that the reference CRC bit count is <NUM> bits, i.e., it is may be confirmed that the UCI does not need to be segmented, in other words, the size of resource for transmitting the UCI is determined based on CRC of <NUM> bits.

In the case that the first encoded bit count is less than <NUM> and the second encoded bit count is greater than or equal to <NUM>, it is determined that the reference CRC bit count is the predetermined CRC bit count value, in other words, the size of resource for transmitting the UCI is determined based on the predetermined based on the predetermined reference CRC bit count.

It is noted, in the embodiment of the present disclosure, the first predetermined CRC bit count is <NUM> bits, and/or, the second predetermined CRC bit count is <NUM> bits, and/or, the preset threshold value is <NUM>.

Step <NUM>: Transmitting the UCI on the determined resource for transmitting the UCI.

In the information transmission method according to the embodiments of the present disclosure, it is judged whether a bit count of uplink control information (UCI) meets a predetermined bit count range; in a case that the bit count of the UCI meets the predetermined bit count range, a resource for transmitting the UCI is determined according to a reference cyclic redundancy check (CRC) bit count; the UCI is transmitted on the determined resource for transmitting the UCI, thus the problem of being difficult to determine CRC bit count, when the PUCCH resource for transmitting the UCI is determined according to the CRC bit count, is solved, and consistent understanding of UCI transmission resource between the base station and the terminal can be ensured, so that proper UCI transmission is ensured.

Further, according to the invention, the determining a resource for transmitting the UCI according to a reference cyclic redundancy check (CRC) bit count in the step <NUM> includes at least one of following methods:.

The UCI other than the CSI part <NUM> may be one or more of HARQ-ACK, SR or CSI part <NUM>.

Further, as a second optional implementation, the determining a resource for transmitting the UCI according to a reference cyclic redundancy check (CRC) bit count in the step <NUM> includes: in a case that the UCI is transmitted on a physical uplink shared channel (PUSCH), calculating a size of a transmission resource, on the PUSCH, of the UCI according to the reference CRC bit count.

Further, after the judging whether a bit count of uplink control information (UCI) meets a predetermined bit count range, the method further includes: in a case that the bit count of the UCI does not meet the predetermined bit count range, determining the resource for transmitting the UCI according to an actual CRC bit count.

Further, before the determining a resource for transmitting the UCI according to a reference cyclic redundancy check (CRC) bit count, the method further includes: judging whether a maximum encoded bit count of UCI carried on an uplink channel for carrying UCI is greater than or equal to a preset threshold value; in a case that the maximum encoded bit count is greater than or equal to the preset threshold value, performing the step of determining the resource for transmitting the UCI according to the reference CRC bit count.

The preset threshold value is <NUM>. In the embodiment of the present disclosure, it is first judged whether a maximum encoded bit count of UCI carried on an uplink channel for carrying UCI is greater than or equal to <NUM>, if the maximum encoded bit count is greater than or equal to <NUM>, the step <NUM> is performed; otherwise, it is directly judged that the UCI does not need to be segmented, then the size of resource for transmitting the UCI is determined based on the CRC bit count corresponding to the UCI bit count range directly without having to use the reference CRC bit count.

In the information transmission method according to the embodiments of the present disclosure, it is judged whether a bit count of uplink control information (UCI) meets a predetermined bit count range; in a case that the bit count of the UCI meets the predetermined bit count range, a resource for transmitting the UCI is determined according to a reference cyclic redundancy check (CRC) bit count; the UCI is transmitted on the determined resource for transmitting the UCI, thus the problem of being difficult to determine CRC bit count, when the PUCCH resource for transmitting the UCI is determined according to the CRC bit count, is solved, and consistent understanding of a UCI transmission resource between the base station and the terminal can be ensured, so that proper UCI transmission is ensured.

As shown in <FIG>, an embodiment of the present disclosure further provides an information transmission method. The method is applied to a base station and includes step <NUM>, step <NUM> and step <NUM>.

The first bit count value is specifically <NUM>, and/or the second bit count value is <NUM>. In embodiments of the present disclosure, the UCI includes, but is not limited to, at least one of a hybrid automatic repeat request-acknowledgement (HARQ-ACK), channel state information (CSI) and a scheduling request (SR).

In the case that the first encoded bit count is less than <NUM> and the second encoded bit count is greater than or equal to <NUM>, it is determined that the reference CRC bit count is the predetermined CRC bit count value, in other words, the size of resource for transmitting the UCI is determined based on the predetermined reference CRC bit count.

Step <NUM>: Receiving the UCI on the determined resource for transmitting the UCI.

In the information transmission method according to the embodiments of the present disclosure, it is judged whether a bit count of uplink control information (UCI) meets a predetermined bit count range; in a case that the bit count of the UCI meets the predetermined bit count range, a resource for transmitting the UCI is determined according to a reference cyclic redundancy check (CRC) bit count; the UCI is received on the determined resource for transmitting the UCI, thus the problem of being difficult to determine CRC bit count, when the PUCCH resource for transmitting the UCI is determined according to the CRC bit count, is solved, and consistent understanding of a UCI transmission resource between the base station and the terminal can be ensured, so that the proper UCI transmission is ensured.

Further, as an optional implementation, the determining a resource for transmitting the UCI according to a reference cyclic redundancy check (CRC) bit count in the step <NUM> includes at least one of following methods:.

The resource for UCI other than the CSI part <NUM> may be one or more of HARQ-ACK, SR and CSI part <NUM>.

Further, after the judging whether a bit count of uplink control information (UCI) meets a predetermined bit count range, the information transmission method further includes: in a case that the bit count of the UCI does not meet the predetermined bit count range, determining the resource for transmitting the UCI according to an actual CRC bit count.

Further, before the determining a resource for transmitting the UCI according to a reference cyclic redundancy check (CRC) bit count, the information transmission method further includes: judging whether a maximum encoded bit count of UCI carried on an uplink channel carrying the UCI is greater than or equal to a preset threshold value; in a case that the maximum encoded bit count is greater than or equal to the preset threshold value, performing the step of determining the resource for transmitting the UCI according to the reference CRC bit count.

In the embodiment of the present disclosure, the preset threshold value is <NUM>. It is first judged whether a maximum encoded bit count of UCI carried on an uplink channel carrying UCI is greater than or equal to <NUM>, if the maximum encoded bit count is greater than or equal to <NUM>, the step <NUM> is performed; otherwise, it is directly judged that the UCI does not need to be segmented, then the size of resource for transmitting the UCI is determined based on the CRC bit count corresponding to the UCI bit count range directly without having to use the reference CRC bit count.

In the information transmission method according to the embodiments of the present disclosure, it is judged whether a bit count of uplink control information (UCI) meets a predetermined bit count range; in a case that the bit count of the UCI meets the predetermined bit count range, a resource for transmitting the UCI is determined according to a reference cyclic redundancy check (CRC) bit count; the UCI is transmitted on the determined resource for transmitting the UCI, thus the problem of being difficult to determine CRC bit count, when the PUCCH resource for transmitting the UCI is determined according to the CRC bit count, is solved, and consistent understanding of a UCI transmission resource between the base station and the terminal can be ensured, so that the proper UCI transmission is ensured.

The information transmission method according to the present disclosure is described with respect to specific examples hereinafter.

It is assumed that UCI needs to be transmitted on a PUCCH at a time instant n, and the PUCCH resource at least has parameters such as a code rate r, an RB count <MAT> and a PUCCH symbol length; it is assumed that the PUCCH is of a format <NUM>, the PUCCH has a symbol length of <NUM> symbols, wherein a quantity of symbols carrying UCI transmission <MAT>, the PUCCH uses QPSK modulation, i.e., a corresponding modulation order Qm=<NUM>, a quantity of REs carrying UCI in each RB <MAT>, and the bit count of the UCI meets a predetermined bit count range, e.g., the bit count is a value greater than or equal to <NUM> and less than <NUM>, or the bit count is a value greater than or equal to <NUM>.

Case <NUM> (using a reference CRC directly): assuming <MAT>, r=<NUM>, assuming the UCI bit count OUCI is <NUM> bits, since it cannot be determined whether the encoded bit count of the UCI exceeds <NUM> bits prior to determination of a PUCCH resource size, it cannot be judged whether the UCI needs to be segmented, and in turn it cannot be judged whether the <NUM>-bit UCI corresponds to CRC of <NUM> bits or CRC of <NUM> bits, so a reference CRC bit count is used to determine the PUCCH resource size for transmitting the UCI, that is, assuming that the reference CRC bit count OCRC is predefined as <NUM> bits, the actual RB count <MAT> of the PUCCH is further determined based on a to-be-transmitted bit count OUCI+OCRC=<NUM> and the PUCCH code rate according to the following formula (<NUM>), wherein the <MAT> is a value not greater than <MAT>. In this case, the <MAT> RBs are <MAT> RBs starting from an initial RB of <MAT> RBs corresponding to the PUCCH resource. In other words, it is determined that merely <NUM> RBs starting from the initial RB of the <NUM> RBs are actually used for the PUCCH to transmit the <NUM>-bit UCI. During determination of the RB count of PUCCH for transmitting the UCI, the assumed reference CRC bit count does not affect the actual CRC bits determined during the actual encoding of the UCI. In other words, the actual CRC bits are always determined based on the UCI bit count range and whether UCI segmentation is performed. For example, when the UCI bit count ranges from <NUM> bits to <NUM> bits, the CRC bit count is <NUM> bits; when the UCI bit count is greater than <NUM> bits, specifically, if the UCI bit count is greater than or equal to <NUM> and the encoded bit count of UCI is greater than or equal to <NUM>, or if the UCI bit count is greater than or equal to <NUM> bits, then UCI segmentation is performed, and the CRC bit count is <NUM> bits, otherwise, UCI segmentation is not performed, and the CRC bit count is <NUM> bits. In this case, the encoded bit count of UCI carried by the <NUM> RBs is <MAT> bits, which is no more than <NUM>, thus it is determined that UCI segmentation is not required, and the actual CRC bit count for the UCI is <NUM> bits, which is consistent with the reference CRC. In this way, it is ensured that the code rate of the <NUM>-bit UCI transmitted on the PUCCH occupying <NUM> RBs does not exceed the target code rate r; <MAT> wherein if <MAT>, the transmission takes place on the <MAT> RBs, in other words, the resource is in insufficient, and all RBs included in the PUCCH need to be occupied, to reach the code rate r as close as possible.

Case <NUM> (using reference CRC directly): assuming that <MAT>, r=<NUM>, assuming that the UCI bit count is <NUM> bits; similar to the case <NUM>, a reference CRC bit count is used to determine a size of the PUCCH resource for transmitting the UCI, to obtain an actual RB count <MAT> of the PUCCH, wherein the <MAT> is a value not greater than <MAT>. In this case, the <MAT> RBs are <MAT> RBs starting from the initial RB of the <MAT> RBs corresponding to the PUCCH resource. In other words, it is determined that merely <NUM> RBs starting from the initial RB of the <NUM> RBs are actually used for the PUCCH to transmit the <NUM>-bit UCI. During the determination of the actual CRC bit count, since the encoded bit count of UCI carried by the <NUM> RBs is <MAT> bits, which exceeds <NUM>, the UCI segmentation is required, and then the actual CRC bit count for the UCI is <NUM> bits, which is greater than the reference CRC bit count. In this case, the code rate of the <NUM>-bit UCI transmitted on the PUCCH occupying <NUM> RBs may be slightly greater than the target code rate r, e.g., <MAT>; but for this condition, the benefit of the reference CRC bit count consists in that the resource determination can always be performed according to an assumed CRC bit count, so that a simple unification can be realized by preventing the base station and the terminal from using different CRC bit counts to determine resource. When it is assumed that the reference CRC bit count is <NUM> bits, a situation in which the actual code rate for the UCI transmission is slightly greater than the target code rate might occur if the actual CRC bit count is <NUM> bits. However, considering that a frequency domain resource is allocated in units of RBs, the situation in which the actual code rate for the UCI transmission is slightly greater than the target code rate occurs infrequently, and even if the situation does occur, the actual code rate does not deviate too far from the target code rate. For example, assuming that the UCI bit count is <NUM> bits and other parameters remain unchanged, the determined <MAT> is still <NUM>, but in this case the code rate for the <NUM>-bit UCI transmitted on the <NUM> RBs does not exceed the target code rate even if it is calculated based on the CRC bit count of <NUM> bits, e.g., <MAT>. In this case, were the reference CRC bit count set to <NUM> bits, it means that the actual CRC bit count will only be less than or equal to the reference CRC bit count, it can always be guaranteed to judge whether the UCI segmentation is performed on the basis of the determination as to whether the quantity of encoded bits carried on the actual determined resource exceeds <NUM>, and the code rate of transmission of the UCI will never exceed the target code rate, however, certain PUCCH resource waste will be incurred since PUCCH is always transmitted at a code rate less than the target code rate, which means that the transmission of PUCCH always occupies resources more than what is actual needed.

Case <NUM> (determining reference CRC bits according to the encoded bits corresponding to the UCI + <NUM> bits): assuming that <MAT>, r=<NUM>, assuming that the UCI bit count is <NUM> bits, since it cannot be determined whether the encoded bit count of the UCI exceeds <NUM> bits prior to the determination of a size of a PUCCH resource, it cannot be judged whether the UCI needs to be segmented, and in turn it cannot be judged whether the <NUM>-bit UCI corresponds to CRC of <NUM> bits or CRC of <NUM> bits. Then, firstly, a minimum encoded bit count corresponding to the UCI on the condition that the target code rate is not exceeded may be calculated according to CRC of <NUM> bits, e.g., the first encoded bit rate A= (<NUM>+<NUM>) /<NUM>=<NUM>. Assuming that the PUCCH resource is large enough, it means that <NUM> UCI encoded bits are still required on the condition that the target code rate is not exceeded even if the CRC of <NUM> bits is used for the calculation, and the encoded bit count of UCI is always greater than <NUM>. In this case, according to a minimum encoded bit count corresponding to the <NUM> bits on the condition that the target code rate is not exceeded, e.g., the second encoded bit rate B= ceil ((<NUM>+<NUM>) /<NUM>) =<NUM>, wherein ceil ( ) is rounding up to an integer, it can be further judged whether B exceeds <NUM> as well. Of course, B may not be calculated, since if A is greater than <NUM>, then B is certainly greater than <NUM>. Thus, it may be determined that UCI segmentation is required, and the actual <NUM> CRC bits may be directly determined as the reference CRC bits. In this case, the quantity <MAT> of RBs on the PUCCH that are actually used for transmitting the UCI is determined according to the actual <NUM> CRC bits, then it can be calculated according to formula (<NUM>) that <MAT>, that is, the <NUM>-bit UCI can be actually transmitted by merely occupying <NUM> RBs out of <NUM> RBs corresponding to the PUCCH resource on the condition that the code rate r is not exceeded. In this case, the actual CRC bit count is consistent with the reference CRC bit count, and then the code rate of the transmission will never exceed the code rate r.

Case <NUM> (determining reference CRC bits according to the encoded bits corresponding to the UCI + <NUM> bits): assuming that <MAT>, r=<NUM>, assuming that the UCI bit count is <NUM> bits, since it cannot be determined whether the encoded bit count of the UCI exceeds <NUM> bits prior to the determination of the size of the PUCCH resource, it cannot be judged whether the UCI needs to be segmented, and in turn it cannot be judged whether the <NUM>-bit UCI corresponds to CRC of <NUM> bits or CRC of <NUM> bits. Then, firstly, a minimum encoded bit count corresponding to the UCI on the condition that the target code rate is not exceeded may be calculated according to CRC of <NUM> bits, e.g., B= (<NUM>+<NUM>) /<NUM>=<NUM>. Assuming that the PUCCH resource is large enough, it means that the corresponding encoded bit count of UCI will never exceed <NUM> on the condition that the target code rate is not exceeded even if CRC of <NUM> bits is used for the calculation, and the encoded bit count of UCI is always not greater than <NUM>. In this case, according to a minimum encoded bit count corresponding to the <NUM> bits on the condition that the target code rate is not exceeded, e.g., A= (<NUM>+<NUM>)/<NUM>=<NUM>, it can be further judged whether A exceeds <NUM>. Of course, a value of the A may not be calculated, since if B is no greater than <NUM>, then A is certainly less than <NUM>. Thus, it may be determined that UCI segmentation is not required, and the actual <NUM> CRC bits may be directly determined as the reference CRC bits. In this case, the quantity of RBs on the PUCCH that are actually used for transmitting the UCI <MAT> is determined according to the actual CRC of <NUM> bits, then it can be calculated according to formula (<NUM>) that <MAT>, that is, the <NUM>-bit UCI can be actually transmitted by merely occupying <NUM> RBs out of <NUM> RBs corresponding to the PUCCH resource on the condition that the code rate r is not exceeded. In this case, the actual CRC bit count is consistent with the reference CRC bit count, and then the transmission code rate will never exceed the code rate r.

Case <NUM> (determining reference CRC bits according to the encoded bits corresponding to the UCI + <NUM> bits and the encoded bits corresponding to the UCI + <NUM> bits): assuming that <MAT>, r=<NUM>, assuming that the UCI bit count is <NUM> bits, since it cannot be determined whether the encoded bit count of the UCI exceeds <NUM> bits prior to the determination of the size of the PUCCH resource, it cannot be judged whether the UCI needs to be segmented, and in turn it cannot be judged whether the <NUM>-bit UCI corresponds to CRC of <NUM> bits or CRC of <NUM> bits. Then, firstly, a minimum encoded bit count corresponding to the UCI on the condition that the target code rate is not exceeded may be calculated according to CRC of <NUM> bits, e.g., A=(<NUM>+<NUM>)/<NUM>=<NUM>. Assuming that the PUCCH resource is large enough, it means that the corresponding encoded bit count of UCI does not exceed <NUM> on the condition that the target code rate is not exceeded when the calculation is based on CRC of <NUM> bits. Base on this, it cannot be determined whether UCI segmentation is performed. Next, a minimum encoded bit count corresponding to the UCI on the condition that the target code rate is not exceeded may further be calculated according to CRC of <NUM> bits, e.g., B=(<NUM>+<NUM>)/<NUM>=<NUM>. Assuming that the PUCCH resource is large enough, it means that the corresponding encoded bit count of UCI exceeds <NUM> on the condition that the target code rate is not exceeded when the calculation is based on CRC of <NUM> bits, which means that in this case, it still cannot be determined whether UCI segmentation is performed. Thus, it is determined that the PUCCH resource is calculated according to the predetermined reference CRC bit count. For example, assuming that the predetermined reference CRC bit count is <NUM> bits, the quantity <MAT> of RBs on the PUCCH that are actually used for transmitting the UCI is determined according to the <NUM> CRC bits, then it can be calculated according to formula (<NUM>) that <MAT>, that is, the <NUM>-bit UCI can be actually transmitted by merely occupying <NUM> RBs out of <NUM> RBs corresponding to the PUCCH resource on the condition that the code rate r is not exceeded. In this case, the encoded bit count of UCI may be determined according to the quantity of RBs actually transmitted on the PUCCH, and then the actual CRC bits may be determined; a specific process thereof is similar to those in the case <NUM> and the case <NUM>, thus a detail description is omitted.

In the aforementioned process, the following may also be applicable: firstly, B is determined according to CRC of <NUM> bits, then it is determined that B is greater than <NUM>, and it cannot be determined whether UCI segmentation is performed; next, A is determined according to CRC of <NUM> bits, then it is determined that A is less than <NUM>, and it cannot be determined whether UCI segmentation is performed, thus it is derived that the PUCCH resource is determined according to the predetermined reference CRC bit count. In other words, both the case in which A is determined first and the case in which B is determined first are permissible. Or, in the aforementioned process, the following may also be applicable: value A and value B are determined simultaneously and then it is judged according to the ranges corresponding to the value A and value B that the PUCCH resource is determined according to the predetermined reference CRC bit count.

Case <NUM> (first judging whether the reference CRC needs to be used according to a maximum quantity of bits carried by the PUCCH): assuming that <MAT>, then according to parameters such as the quantity of RBs included in the PUCCH, it is determined that the encoded bit count of UCI that may be carried on the <MAT> RBs for the PUCCH is <MAT> bits, which is no more than <NUM>, then no matter what the original UCI bit count is, the condition for UCI segmentation will not be met since the maximum quantity of encoded bits carried by the PUCCH for carrying the UCI transmission is no more than <NUM>. Thus, the CRC bit count is the actual CRC bit count corresponding to the UCI bit count in the case that UCI segmentation is not performed, for example, when the UCI bit count ranges from <NUM> bits to <NUM> bits, the CRC bit count is <NUM> bits, and when the UCI bit count is greater than <NUM> bits, the CRC bit count is <NUM> bits. The terminal further determines the quantity <MAT> of RBs on the PUCCH that are actually used for transmitting the UCI according to the actual CRC bit count corresponding to the UCI bit count based on the sum of UCI bit count and CRC bit count and the configured code rate r. For example, assuming that the UCI bit count is <NUM> bits, CRC=<NUM> bits, and r=<NUM>, then it can be calculated according to formula (<NUM>) that <MAT>, that is, the <NUM>-bit UCI can be actually transmitted by merely occupying <NUM> RBs out of <NUM> RBs corresponding to the PUCCH resource on the condition that the code rate r is not exceeded. In this case, the actual CRC bit count is consistent with the reference CRC bit count, and then the transmission code rate will never exceed the code rate r.

Case <NUM> (first judging whether the reference CRC needs to be used according to a maximum quantity of bits carried by the PUCCH): assuming that <MAT>, according to parameters such as the quantity of RBs included in the PUCCH, it is determined that the maximum quantity of encoded bits of UCI that may be carried on the <MAT> RBs for the PUCCH is <MAT> bits, which is greater than <NUM>, then in determining the actually transmitted RB count <MAT>, either the situation that the encoded bit count of UCI carried on the <MAT> RBs is greater than or equal to <NUM> or the situation that the encoded bit count of UCI carried on the <MAT> RBs is not more that <NUM> may occur, which is totally dependent on the value of <MAT>. Thus, it is necessary to perform the process of calculating the PUCCH resource according to the reference CRC bit count in the manners of foregoing case <NUM> to case <NUM>. A specific process thereof is similar to the foregoing, thus a detail description is omitted.

It is assumed that HARQ-ACK needs to be transmitted on a PUCCH at a time instant n, and the bit count of the HARQ-ACK meets a predetermined bit count range, e.g., the bit count is a value greater than or equal to <NUM> and less than <NUM>, or the bit count is a value greater than or equal to <NUM>.

First, the quantity of mapped resource elements (RE, Resource Element) or the quantity of modulated symbols <MAT> on the PUSCH corresponding to the HARQ-ACK is calculated according to the following formulas (<NUM>) and (<NUM>), wherein OACK is the bit count of the HARQ-ACK, LACK is the reference CRC bit count, <MAT> is a configured parameter for determining resource for the HARQ-ACK, CUL-SCH is a quantity of code blocks (CB) for carrying data (UL-SCH) on the PUSCH, Kr is the size of the rth CB, <MAT> is a modulated bandwidth of the PUSCH and is in a unit of a size of a subcarrier (SC), <MAT> is the quantity of REs for transmitting the UCI that are included in an OFDM symbol l, <MAT> is the quantity of symbols included in the PUSCH, α is a scaling factor preconfigured by a higher-layer signaling, l<NUM> is a numbering value of the first symbol on the PUSCH that does not contain a DMRS, NL represents the quantity of layers; next, the encoded bit count EUCI of UCI corresponding to the HARQ-ACK on the PUSCH is calculated according to the following formula (<NUM>), then it is determined whether UCI segmentation is required according to the encoded bit count of UCI, so as to determine whether the actual CRC bit count for the UCI is <NUM> bits or <NUM> bits. A specific process thereof is similar to those in the case <NUM> to case <NUM> of the example <NUM>.

For case <NUM> or <NUM>, <MAT> is calculated by directly using the predetermined reference CRC bit count, e.g., <NUM> bits, as LACK, and thereby the encoded bit count EUCI of UCI is obtained. The actual CRC bit count determined according to the encoded bit count of UCI may be like that in the case <NUM>, that is, the actual CRC bit count is consistent with the reference CRC bit count; or the actual CRC bit count determined according to the encoded bit count of UCI may be like that in the case <NUM>, that is, the actual CRC bit count is greater than the reference CRC bit count. In this case, when the transmission is performed according to the actual CRC bit count on the resource determined based on the reference CRC bit count, the code rate is slightly higher.

For case <NUM> or <NUM>, according to pre-judgement for results of the calculations based on <NUM> bits or <NUM> bits, LACK is directly determined to be the actual CRC bit count, so that it is ensured that the HARQ-ACK transmission resource determined based on the reference CRC bit count according to the following formulas (<NUM>) and (<NUM>) matches with actual needs.

For case <NUM>, according to the pre-judgement of the results of the calculations based on <NUM> bits or <NUM> bits, it cannot be determined whether the UCI is segmented. Thus, the process has to revert to those in case <NUM> or case <NUM>, to determine a resource according to the predetermined reference CRC bit count. The subsequent specific process is similar to those in the case <NUM> or case <NUM>, thus a detailed description thereof is omitted.

For case <NUM> or <NUM>, different from the case <NUM> or <NUM> in the example <NUM>, it is necessary to replace the process of calculating the encoded bit count of UCI based on the quantity of RBs included in the PUCCH with the upper limit of transmission resource for HARQ-ACK on the PUSCH, i.e., <MAT> in the formula (<NUM>). In other words, firstly, <MAT> is calculated according to <MAT>; next, the upper limit EUCI of the encoded bit count of HARQ-ACK transmitted on the PUSCH is calculated according to the formula (<NUM>) EUCI = NL · Q'ACK ·Qm; then it is judged whether the encoded bit count exceeds <NUM>. If the encoded bit count does not exceed <NUM>, i.e., as in the case <NUM> in the example <NUM>, it may be directly judged that the UCI segmentation is not required, and it is determined that the actual CRC bit count of <NUM> bits is used as the reference CRC bit count to calculate <MAT> and EUCI according to the following formula; if the encoded bit count exceeds <NUM>, then it cannot be judged whether UCI segmentation is required, and the process has to revert to the cases <NUM> to <NUM> for further processing, a detailed description of the specific process is omitted. <MAT><MAT>.

The information transmission method according to the embodiments of the present disclosure is used to solve the problem that the CRC bit count is unknown when the PUCCH resource for transmitting the UCI is determined according to the CRC bit count, so as to ensure consistent understanding for UCI transmission resource between the base station and the terminal, and to ensure the proper UCI transmission.

As shown in <FIG>, an embodiment not covered by the claims of the present disclosure further provides a terminal, including a transceiver <NUM>, a storage <NUM>, a processor <NUM> and a computer program stored in the storage <NUM> and configured to be executed by the processor, wherein the processor <NUM> is configured to execute the computer program to implement following steps:.

In <FIG>, a bus architecture may include any number of interconnected buses and bridges, and connects various circuits including one or more processors represented by the processor <NUM> and a storage represented by the storage <NUM>. The bus architecture may also connect various other circuits such as peripherals, voltage regulators and power management circuits, which are well known in the art. Therefore, a detailed description thereof is omitted herein. A bus interface provides an interface. The transceiver <NUM> may be multiple elements, i.e., including a transmitter and a receiver, to provide a unit for communication with various other apparatuses on a transmission medium. For different UEs, the user interface <NUM> may be an interface capable of connecting externally or internally to a required device. The connected device includes, but is not limited to: a keypad, a display, a speaker, a microphone, a joystick or the like.

The processor <NUM> is responsible for supervising the bus architecture and normal operation and the storage <NUM> may store data being used by the processor <NUM> during operation.

Optionally, the processor <NUM> is further configured to read the computer program in the storage <NUM> to implement the following step:
in a case that the bit count of the UCI does not meet the predetermined bit count range, determining the resource for transmitting the UCI according to an actual CRC bit count.

Optionally, the predetermined bit count range is greater than or equal to a first bit count value and less than a second bit count value; or, the predetermined bit count range is greater than or equal to the first bit count value.

Optionally, the first bit count value is <NUM>, and/or the second bit count value is <NUM>.

Optionally, the processor <NUM> is further configured to read the computer program in the storage <NUM> to implement the following steps:.

Optionally, the first predetermined CRC bit count is <NUM> bits, and/or, the second predetermined CRC bit count is <NUM> bits, and/or, the preset threshold value is <NUM>.

Optionally, the processor <NUM> is further configured to read the computer program in the storage <NUM> to implement at least one of following methods:.

Optionally, the processor <NUM> is further configured to read the computer program in the storage <NUM> to implement the following step:
in a case that the UCI is transmitted on a physical uplink shared channel (PUSCH), calculating a size of a transmission resource on the PUSCH for the UCI according to a reference CRC bit count.

Optionally, the UCI includes at least one of a hybrid automatic repeat request-acknowledgement (HARQ-ACK), channel state information (CSI) and a scheduling request (SR).

In some embodiments not covered by the claims of the present disclosure, a computer readable storage medium storing therein a computer program is provided. The computer program is configured to be executed by a processor to implement the following steps:.

The computer program is configured to be executed by a processor to realize all implementations of the embodiment of the information transmission method applied to the terminal side. To avoid repetition, a detail description is omitted herein.

As shown in <FIG>, an embodiment of the present disclosure further provides a terminal. The terminal includes:.

The terminal according to the embodiment of the present disclosure further includes: a third determination module configured to, in a case that the bit count of the UCI does not meet the predetermined bit count range, determine the resource for transmitting the UCI according to an actual CRC bit count.

In the terminal according to the embodiment of the present disclosure, the predetermined bit count range is greater than or equal to a first bit count value and less than a second bit count value; or, the predetermined bit count range is greater than or equal to the first bit count value.

In the terminal according to the embodiment of the present disclosure, the first bit count value is <NUM>, and/or the second bit count value is <NUM>.

In the terminal according to the embodiment of the present disclosure, the first determination module is configured to:.

In the terminal according to the embodiment of the present disclosure, the first predetermined CRC bit count is <NUM> bits, and/or, the second predetermined CRC bit count is <NUM> bits, and/or, the preset threshold value is <NUM>.

In the terminal according to the embodiment of the present disclosure, the first determination module is configured to implement at least one of following methods:.

In the terminal according to the embodiment of the present disclosure, the first determination module is configured to, in a case that the UCI is transmitted on a physical uplink shared channel (PUSCH), calculate a size of a transmission resource on the PUSCH of the UCI according to a reference CRC bit count.

The terminal according to the embodiment of the present disclosure further includes:.

In the terminal according to the embodiment of the present disclosure, the UCI includes at least one of a hybrid automatic repeat request-acknowledgement (HARQ-ACK), channel state information (CSI) and a scheduling request (SR).

In the terminal according to the embodiment of the present disclosure, it is judged whether a bit count of uplink control information (UCI) meets a predetermined bit count range; in a case that the bit count of the UCI meets the predetermined bit count range, a resource for transmitting the UCI is determined according to a reference cyclic redundancy check (CRC) bit count; the UCI is transmitted on the determined resource for transmitting the UCI, thus the problem of being difficult to determine CRC bit count, when the PUCCH resource for transmitting the UCI is determined according to the CRC bit count, is solved, and consistent understanding of UCI transmission resource between the base station and the terminal can be ensured, so that the proper UCI transmission is ensured.

As shown in <FIG>, an embodiment not covered by the claims of the present disclosure further provides a base station, including a storage <NUM>, a processor <NUM>, a transceiver <NUM>, a bus interface and a computer program stored in the storage <NUM> and configured to be executable by the processor <NUM>, wherein the processor <NUM> is configured to read the computer program in the storage <NUM> to implement following steps:.

In <FIG>, a bus architecture may include any number of interconnected buses and bridges, and connects various circuits including one or more processors represented by the processor <NUM> and a storage represented by the storage <NUM>. The bus architecture may also connect various other circuits such as peripherals, voltage regulators and power management circuits, which are well known in the art. Therefore, a detailed description thereof is omitted herein. A bus interface provides an interface. The transceiver <NUM> may be multiple elements, i.e., including a transmitter and a receiver, to provide a unit for communication with various other apparatuses on a transmission medium. The processor <NUM> is responsible for supervising the bus architecture and normal operation and the storage <NUM> may store the data being used by the processor <NUM> during operation.

Optionally, the processor <NUM> is configured to execute the computer program to further implement the following step:
in a case that the bit count of the UCI does not meet the predetermined bit count range, determining the resource for transmitting the UCI according to an actual CRC bit count.

Optionally, the processor <NUM> is configured to execute the computer program to further implement the following steps:.

Optionally, the processor <NUM> is configured to execute the computer program to further implement at least one of following methods:.

Optionally, the processor <NUM> is configured to execute the computer program to further implement the following step:
in a case that the UCI is transmitted on a physical uplink shared channel (PUSCH), calculating a size of a transmission resource on the PUSCH for UCI according to a reference CRC bit count.

In some embodiments not covered by the claims of the present disclosure, a computer readable storage medium storing therein a computer program is further provided. The computer program is configured to be executed by a processor to implement the following steps:.

The computer program is configured to be executed by a processor to realize all implementations of the embodiment of the information transmission method applied to the base station side. To avoid repetition, a detail description is omitted herein.

As shown in <FIG>, an embodiment of the present disclosure further provides a base station. The base station includes:.

The base station according to the embodiment of the present disclosure further includes: a fourth determination module, configured to, in a case that the bit count of the UCI does not meet the predetermined bit count range, determine the resource for transmitting the UCI according to an actual CRC bit count.

In the base station according to the embodiment of the present disclosure, the predetermined bit count range is greater than or equal to a first bit count value and less than a second bit count value; or, the predetermined bit count range is greater than or equal to the first bit count value.

In the base station according to the embodiment of the present disclosure, the first bit count value is <NUM>, and/or the second bit count value is <NUM>.

In the base station according to the embodiment of the present disclosure, the second determination module is configured to:.

In the base station according to the embodiment of the present disclosure, the first predetermined CRC bit count is <NUM> bits, and/or, the second predetermined CRC bit count is <NUM> bits, and/or, the preset threshold value is <NUM>.

In the base station according to the embodiment of the present disclosure, the second determination module is configured to implement at least one of following methods:.

In the base station according to the embodiment of the present disclosure, the second determination module is configured to, in a case that the UCI is transmitted on a physical uplink shared channel (PUSCH), calculate a size of a transmission resource on the PUSCH for the UCI according to a reference CRC bit count.

The base station according to the embodiment of the present disclosure further includes:.

In the base station according to the embodiment of the present disclosure, the UCI includes at least one of a hybrid automatic repeat request-acknowledgement (HARQ-ACK), channel state information (CSI) and a scheduling request (SR).

In the base station according to the embodiment of the present disclosure, it is judged whether a bit count of uplink control information (UCI) meets a predetermined bit count range; in a case that the bit count of the UCI meets the predetermined bit count range, a resource for transmitting the UCI is determined according to a reference cyclic redundancy check (CRC) bit count; the UCI is received on the determined resource for transmitting the UCI, thus the problem of being difficult to determine CRC bit count, when the PUCCH resource for transmitting the UCI is determined according to the CRC bit count, is solved, and consistent understanding of UCI transmission resource between the base station and the base station can be ensured, so that the proper UCI transmission is ensured.

In various embodiments of the present disclosure, it is understood, numbering values of various processes are not intended to imply an execution sequence of the processes. The execution sequence of the processes should be determined in accordance with the functions and inherent logic thereof, and by no means constitutes any limitation as to the implementation of the embodiments of the present disclosure.

An embodiment not covered by the claims of the present disclosure further provides a computer readable storage medium storing therein a computer program. The computer program is configured to be executed by a processor to implement various processes of the method embodiments of the present disclosure, and may achieve the same technical effects. To avoid repetition, a detail description is omitted herein. The computer readable storage medium may be transitory or non-transitory, such as a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optic disc.

It is noted that terms "include," "have," or any variations thereof in the present disclosure are intended to cover a non-exclusive inclusion, such that a process, a method, an article, or a device that includes a list of elements not only includes the list of elements, but also may include other elements not expressly listed or include elements inherent in the process, the method, the article, or the device. Without further restriction, an element preceded by "includes or including" does not preclude existence of additional identical elements in the process, the method, the article, or the device including the element.

Claim 1:
An information transmission method, performed by a terminal, comprising:
judging (<NUM>) whether a bit count of uplink control information, UCI, meets a predetermined bit count range;
in a case that the bit count of the UCI meets the predetermined bit count range, determining (<NUM>) a resource for transmitting the UCI according to a reference cyclic redundancy check, CRC, bit count;
transmitting (<NUM>) the UCI on the determined resource for transmitting the UCI,
characterized in that,
the reference CRC bit count is selected from one of a predetermined CRC bit count, a first predetermined CRC bit count, and a second predetermined CRC bit count, and
the determining (<NUM>) a resource for transmitting the UCI according to a reference CRC bit count comprises at least one of following <NUM>)-<NUM>):
<NUM>): in a case that the UCI is channel state information, CSI, and multiple Physical Uplink Control Channel, PUCCH, resources for transmitting multiple CSIs are configured, selecting one PUCCH resource for transmitting the CSI from the multiple PUCCH resources for transmitting the multiple CSIs according to the reference CRC bit count;
<NUM>): in a case that the UCI comprises a CSI part <NUM>, determining a resource for transmitting the CSI part <NUM> and a resource for transmitting UCI other than the CSI part <NUM> among a determined PUCCH resource according to the reference CRC bit count;
<NUM>): in a case that the UCI is transmitted on a physical uplink shared channel, PUSCH, calculating a size of a transmission resource, on the PUSCH, of the UCI according to the reference CRC bit count.