User equipment and base station in communication system and method performed by same

Abstract

The invention provides user equipment (UE) and a base station in a wireless communication network and an execution method thereof, and according to one embodiment, the method executed by the UE in a wireless communication system comprises the steps of receiving downlink control information (DCI) of a scheduling physical downlink shared channel (PDSCH), receiving the PDSCH, generating hybrid automatic repeat request acknowledgement (HARQ-ACK) information of the PDSCH, and sending the HARQ-ACK information to the base station. And transmitting the HARQ-ACK information on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). Wherein under the condition that one PUCCH (Physical Uplink Control Channel) or PUSCH (Physical Uplink Shared Channel) transmits the HARQ-ACK information of the PDSCH (Physical Downlink Shared Channel) scheduled by one piece of first DCI (Downlink Control Information), the bit number of the HARQ-ACK information is determined on the basis of the PDSCH actually scheduled by the first DCI; in a case where one PUCCH or PUSCH transmits HARQ-ACK information of a plurality of PDSCHs scheduled by a first DCI, the number of bits of the HARQ-ACK information is determined on the basis of the maximum number of PDSCHs configured for the first DCI.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and more specifically, to user equipment and base stations in communication systems and methods for performing them. Background Technology

[0002] To meet the increased demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or near-5G communication systems. Therefore, 5G or near-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems".

[0003] 5G communication systems are implemented in higher frequency (millimeter wave, mmWave) bands, such as the 60GHz band, to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are discussed in 5G communication systems.

[0004] In addition, in 5G communication systems, development is underway to improve system networks based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, cooperative multipoint (CoMP), and receiver interference cancellation.

[0005] In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding and modulation (ACM), while filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) have been developed as advanced access technologies. Summary of the Invention

[0006] According to one aspect of this disclosure, a method performed by a user equipment (UE) in a wireless communication system is provided, comprising: receiving downlink control information (DCI) that schedules a physical downlink shared channel (PDSCH); receiving the PDSCH; generating hybrid automatic repeat request (HARQ-ACK) information for the PDSCH; and transmitting the HARQ-ACK information on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). Wherein, when HARQ-ACK information for one PDSCH scheduled by a first DCI is transmitted on one PUCCH or PUSCH, the number of bits in the HARQ-ACK information is determined based on the actual number of PDSCHs scheduled by the first DCI; when HARQ-ACK information for multiple PDSCHs scheduled by the first DCI is transmitted on one PUCCH or PUSCH, the number of bits in the HARQ-ACK information is determined based on the maximum number of PDSCHs configured for the first DCI.

[0007] In an exemplary implementation, the number of bits of HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: the number of bits of HARQ-ACK information is the sum of the number of bits of HARQ-ACK information of multiple PDSCHs actually scheduled by the first DCI.

[0008] In an exemplary implementation, the number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: when the codebook of the HARQ-ACK information is based on the codebook of transport block TB, the number of bits in the HARQ-ACK information is determined based on the sum of the number of TBs included in the PDSCH actually scheduled by the first DCI.

[0009] In an exemplary implementation, the number of bits of HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: when the codebook of HARQ-ACK information is based on the codebook of code block groups (CBGs), the number of bits of HARQ-ACK information is the sum of the number of bits of HARQ-ACK information of TBs included in the PDSCH actually scheduled by the first DCI. For each TB in each PDSCH: when the number of code blocks (CBs) included in the TB is greater than or equal to a preset threshold, the number of bits of HARQ-ACK information of the TB is equal to the threshold, where the threshold is the maximum number of CBGs included in each TB; and when the number of CBs included in the TB is less than the threshold, the number of bits of HARQ-ACK information of the TB is equal to the number of CBs included in the TB.

[0010] In an exemplary implementation, the number of bits of the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: when the DCI scheduling the PDSCH includes a downlink-downlink allocation index DL-DAI equal to 1, and the DCI scheduling the PUSCH does not include an uplink-downlink allocation index UL-DAI, the number of bits of the HARQ-ACK information is determined based on the PDSCH actually scheduled by the DCI.

[0011] In an exemplary implementation, the number of bits of the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: when the DCI scheduling the PDSCH includes DL-DAI equal to 1, and the DCI scheduling the PUSCH includes UL-DAI equal to 1, the number of bits of the HARQ-ACK information is determined based on the PDSCH actually scheduled by the DCI.

[0012] In an exemplary implementation, when transmitting HARQ-ACK information of a PDSCH scheduled by a first DCI on a PUCCH or PUSCH, transmitting HARQ-ACK information on the Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSCH) includes: transmitting a HARQ-ACK codebook on a PUCCH or a PUSCH, wherein a first sub-codebook in the HARQ-ACK codebook includes HARQ-ACK information of a PDSCH actually scheduled by a first DCI.

[0013] According to one aspect of this disclosure, a method performed by a base station in a wireless communication network is provided. The method includes: transmitting downlink control information (DCI) that schedules a physical downlink shared channel (PDSCH); transmitting the PDSCH; and receiving hybrid automatic repeat request acknowledgment (HARQ-ACK) information on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). Wherein, when a PUCCH or PUSCH transmits HARQ-ACK information for a PDSCH scheduled by a first DCI, the number of bits in the HARQ-ACK information is determined based on the actual number of PDSCHs scheduled by the first DCI. Where a PUCCH or PUSCH transmits HARQ-ACK information for multiple PDSCHs scheduled by the first DCI, the number of bits in the HARQ-ACK information is determined based on the maximum number of PDSCHs configured for the first DCI.

[0014] In an exemplary implementation, the number of bits of HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: the number of bits of HARQ-ACK information is the sum of the number of bits of HARQ-ACK information of multiple PDSCHs actually scheduled by the first DCI.

[0015] In an exemplary implementation, the number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: when the codebook of the HARQ-ACK information is based on the codebook of transport block TB, the number of bits in the HARQ-ACK information is determined based on the sum of the number of TBs included in the PDSCH actually scheduled by the first DCI.

[0016] In an exemplary implementation, the number of bits of HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: when the codebook of HARQ-ACK information is based on the codebook of code block groups (CBGs), the number of bits of HARQ-ACK information is the sum of the number of bits of HARQ-ACK information of TBs included in the PDSCH actually scheduled by the first DCI. For each TB in each PDSCH: when the number of code blocks (CBs) included in the TB is greater than or equal to a preset threshold, the number of bits of HARQ-ACK information of the TB is equal to the threshold, where the threshold is the maximum number of CBGs included in each TB; and when the number of CBs included in the TB is less than the threshold, the number of bits of HARQ-ACK information of the TB is equal to the number of CBs included in the TB.

[0017] In an exemplary implementation, the number of bits of the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: when the DCI scheduling the PDSCH includes a downlink-downlink allocation index DL-DAI equal to 1, and the DCI scheduling the PUSCH does not include an uplink-downlink allocation index UL-DAI, the number of bits of the HARQ-ACK information is determined based on the PDSCH actually scheduled by the DCI.

[0018] In an exemplary implementation, the number of bits of the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: when the DCI scheduling the PDSCH includes DL-DAI equal to 1, and the DCI scheduling the PUSCH includes UL-DAI equal to 1, the number of bits of the HARQ-ACK information is determined based on the PDSCH actually scheduled by the DCI.

[0019] In an exemplary implementation, when HARQ-ACK information of a PDSCH scheduled by a first DCI is transmitted on a PUCCH or PUSCH, receiving hybrid automatic repeat request acknowledgment (HARQ-ACK) information on the Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSCH) includes: receiving a HARQ-ACK codebook on a PUCCH or a PUSCH; wherein, the first sub-codebook in the HARQ-ACK codebook includes HARQ-ACK information of a PDSCH actually scheduled by a first DCI.

[0020] According to one aspect of this disclosure, a UE is provided, comprising: a transceiver configured to transmit and receive signals; and a processor coupled to the transceiver and configured to perform the methods described above performed by the UE.

[0021] According to one aspect of this disclosure, a base station is provided, comprising: a transceiver configured to transmit and receive signals; and a processor coupled to the transceiver and configured to perform the methods described above performed by the base station.

[0022] According to one aspect of this disclosure, a computer-readable storage medium is provided storing computer-executable instructions that, when executed by a processor, perform the method described above performed by a UE or a base station.

[0023] In wireless communication systems, determining the number of bits for HARQ-ACK information based on the PDSCH actually scheduled by DCI can avoid transmitting meaningless padding HARQ-ACK bits. Attached Figure Description

[0024] The above and additional aspects and advantages of this application will become clearer and more readily understood from the following description taken in conjunction with the accompanying drawings, wherein:

[0025] Figure 1 Example wireless networks according to various embodiments of this disclosure are shown;

[0026] Figure 2a and Figure 2b An example wireless transmission and reception path according to this disclosure is shown;

[0027] Figure 3a An example user equipment according to this disclosure is shown;

[0028] Figure 3b An example base station according to this disclosure is shown;

[0029] Figure 4 An exemplary HARQ-ACK according to an embodiment of this disclosure is shown;

[0030] Figure 5 This is an exemplary flowchart of a method performed by a user equipment according to an embodiment of the present disclosure;

[0031] Figure 6 An example of HARQ-ACK according to an embodiment of this disclosure is shown;

[0032] Figure 7 Another example of HARQ-ACK according to an embodiment of this disclosure is shown;

[0033] Figure 8 Another example of HARQ-ACK according to an embodiment of this disclosure is shown;

[0034] Figure 9 An exemplary structure of a user equipment according to an embodiment of this disclosure is shown. Detailed Implementation

[0035] The following description, with reference to the accompanying drawings, is provided to aid in a thorough understanding of the various embodiments of this disclosure as defined by the claims and their equivalents. This description includes various specific details to aid understanding but should be considered exemplary only. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of this disclosure. Furthermore, for clarity and brevity, descriptions of well-known functions and structures may be omitted.

[0036] The terms and wording used in the following description and claims are not limited to their dictionary meanings, but are merely used by the inventors to enable a clear and consistent understanding of this disclosure. Therefore, it will be apparent to those skilled in the art that the following description of various embodiments of this disclosure is for illustrative purposes only and not for limiting the purpose of this disclosure as defined in the appended claims and their equivalents.

[0037] It should be understood that the singular forms of “one,” “an,” and “the” include plural references unless the context clearly indicates otherwise. Thus, for example, the reference to “component surface” includes one or more such surfaces.

[0038] The terms “comprising” or “may include” refer to the presence of a corresponding disclosed function, operation, or component that may be used in the various embodiments of this disclosure, rather than limiting the presence of one or more additional functions, operations, or features. Furthermore, the terms “comprising” or “having” may be interpreted as indicating certain characteristics, numbers, steps, operations, constituent elements, components, or combinations thereof, but should not be construed as excluding the possibility of the presence of one or more other characteristics, numbers, steps, operations, constituent elements, components, or combinations thereof.

[0039] The term "or" as used in the various embodiments of this disclosure includes any of the listed terms and all combinations thereof. For example, "A or B" may include A, may include B, or may include both A and B.

[0040] Unless otherwise defined, all terms used in this disclosure (including technical or scientific terms) have the same meaning as understood by one of those skilled in the art as described herein. Common terms as defined in dictionaries are to be interpreted as having a meaning consistent with the context in the relevant technical field and should not be interpreted ideally or overly formally unless expressly defined in this disclosure.

[0041] The various embodiments of this disclosure can be applied to various communication systems, such as: Global System for Mobile Communications (GSM) systems, Code Division Multiple Access (CDMA) systems, Wideband Code Division Multiple Access (WCDMA) systems, General Packet Radio Service (GPRS), Long Term Evolution (LTE) systems, Frequency Division Duplex (FDD) systems, Time Division Duplex (TDD) systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, 5th Generation (5G) systems, or New Radio (NR), etc. Furthermore, the various embodiments of this disclosure can be applied to future-oriented communication technologies.

[0042] Figure 1 An example wireless network 100 according to various embodiments of the present disclosure is shown. Figure 1 The embodiment of the wireless network 100 shown is for illustrative purposes only. Other embodiments of the wireless network 100 can be used without departing from the scope of this disclosure.

[0043] Wireless network 100 includes gNodeB (gNB) 101, gNB 102, and gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one Internet Protocol (IP) network 130 (such as the Internet, a proprietary IP network, or other data network).

[0044] Depending on the network type, other well-known terms such as "base station" or "access point" can be used instead of "gNodeB" or "gNB". For convenience, the terms "gNodeB" and "gNB" are used in this patent document to refer to network infrastructure components that provide wireless access for remote terminals. Furthermore, depending on the network type, other well-known terms such as "mobile station", "user station", "remote terminal", "wireless terminal", or "user device" can be used instead of "user equipment" or "UE". For convenience, the terms "user equipment" and "UE" are used in this patent document to refer to remote wireless devices that wirelessly access the gNB, whether the UE is a mobile device (such as a mobile phone or smartphone) or a fixed device as commonly understood (such as a desktop computer or vending machine).

[0045] gNB 102 provides wireless broadband access to network 130 to multiple first user equipments (UEs) within its coverage area 120. The multiple first UEs include: UE 111, which may be located in a small business (SB); UE 112, which may be located in an enterprise (E); UE 113, which may be located in a WiFi hotspot (HS); UE 114, which may be located in a first residence (R); UE 115, which may be located in a second residence (R); and UE 116, which may be a mobile device (M), such as a cellular phone, wireless laptop computer, wireless PDA, etc. gNB 103 provides wireless broadband access to network 130 to multiple second UEs within its coverage area 125. The multiple second UEs include UE 115 and UE 116. In some embodiments, one or more of gNBs 101-103 are capable of communicating with each other and with UEs 111-116 using 5G, LTE, LTE-A, WiMAX, or other advanced wireless communication technologies.

[0046] The dashed lines indicate the approximate extent of coverage areas 120 and 125, which are shown as approximately circular for illustrative and explanatory purposes only. It should be clearly understood that coverage areas associated with the gNB, such as coverage areas 120 and 125, can have other shapes, including irregular shapes, depending on the configuration of the gNB and variations in the radio environment associated with natural and man-made obstacles.

[0047] As described in more detail below, one or more of gNB 101, gNB 102, and gNB 103 include a 2D antenna array as described in embodiments of this disclosure. In some embodiments, one or more of gNB 101, gNB 102, and gNB 103 support codebook design and architecture for systems having 2D antenna arrays.

[0048] although Figure 1 An example of a wireless network 100 is shown, but it is possible to... Figure 1 Various modifications can be made. For example, wireless network 100 can include any number of gNBs and any number of UEs in any suitable arrangement. Furthermore, gNB 101 can communicate directly with any number of UEs and provide those UEs with wireless broadband access to network 130. Similarly, each gNB 102-103 can communicate directly with network 130 and provide UEs with direct wireless broadband access to network 130. In addition, gNBs 101, 102, and / or 103 can provide access to other or additional external networks (such as external telephone networks or other types of data networks).

[0049] Figure 2a and Figure 2b Example wireless transmit and receive paths according to this disclosure are shown. In the following description, transmit path 200 can be described as being implemented in a gNB (such as gNB 102), while receive path 250 can be described as being implemented in a UE (such as UE 116). However, it should be understood that receive path 250 can be implemented in a gNB, and transmit path 200 can be implemented in a UE. In some embodiments, receive path 250 is configured to support codebook design and structure for a system having a 2D antenna array as described in embodiments of this disclosure.

[0050] The transmit path 200 includes a channel coding and modulation block 205, a serial-to-parallel (S-to-P) block 210, an N-point inverse fast Fourier transform (IFFT) block 215, a parallel-to-serial (P-to-S) block 220, a cyclic prefix addition block 225, and an up-converter (UC) 230. The receive path 250 includes a down-converter (DC) 255, a cyclic prefix removal block 260, a serial-to-parallel (S-to-P) block 265, an N-point fast Fourier transform (FFT) block 270, a parallel-to-serial (P-to-S) block 275, and a channel decoding and demodulation block 280.

[0051] In transmit path 200, channel coding and modulation block 205 receives a set of information bits, applies coding (such as low-density parity-check (LDPC) coding), and modulates the input bits (such as using quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) to generate a sequence of frequency-domain modulated symbols. Serial-to-parallel (S-to-P) block 210 converts (e.g., demultiplexes) the serial modulated symbols into parallel data to generate N parallel symbol streams, where N is the number of IFFT / FFT points used in gNB 102 and UE 116. N-point IFFT block 215 performs IFFT operations on the N parallel symbol streams to generate a time-domain output signal. Parallel-to-serial block 220 converts (e.g., multiplexes) the parallel time-domain output symbols from N-point IFFT block 215 to generate a serial time-domain signal. Cyclic prefix addition block 225 inserts a cyclic prefix into the time-domain signal. Upconverter 230 modulates (e.g., upconverts) the output of the added cyclic prefix block 225 to an RF frequency for transmission via a wireless channel. The signal can also be filtered at the baseband before being converted to the RF frequency.

[0052] The RF signal transmitted from gNB 102 reaches UE 116 after passing through the wireless channel, and UE 116 performs the opposite operation to that at gNB 102. Downconverter 255 downconverts the received signal to the baseband frequency, and cyclic prefix removal block 260 removes the cyclic prefix to generate a serial time-domain baseband signal. Serial-to-parallel block 265 converts the time-domain baseband signal into a parallel time-domain signal. N-point FFT block 270 performs an FFT algorithm to generate N parallel frequency-domain signals. Parallel-to-serial block 275 converts the parallel frequency-domain signals into a sequence of modulated data symbols. Channel decoding and demodulation block 280 demodulates and decodes the modulated symbols to recover the original input data stream.

[0053] Each of gNBs 101-103 can implement a transmission path 200 similar to that used for transmission to UEs 111-116 in the downlink, and a reception path 250 similar to that used for reception from UEs 111-116 in the uplink. Similarly, each of UEs 111-116 can implement a transmission path 200 for transmission to gNBs 101-103 in the uplink, and a reception path 250 for reception from gNBs 101-103 in the downlink.

[0054] Figure 2a and Figure 2b Each of the components can be implemented using only hardware, or using a combination of hardware and software / firmware. As a specific example, Figure 2a and Figure 2bAt least some of the components can be implemented in software, while others can be implemented in configurable hardware or a combination of software and configurable hardware. For example, FFT block 270 and IFFT block 215 can be implemented as configurable software algorithms, wherein the value of the number of points N can be modified according to the implementation method.

[0055] Furthermore, although the description uses FFT and IFFT, this is merely illustrative and should not be construed as limiting the scope of this disclosure. Other types of transforms, such as the Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions, can be used. It should be understood that for DFT and IDFT functions, the value of variable N can be any integer (such as 1, 2, 3, 4, etc.), while for FFT and IFFT functions, the value of variable N can be any integer that is a power of 2 (such as 1, 2, 4, 8, 16, etc.).

[0056] although Figure 2a and Figure 2b An example of a wireless transmit and receive path is shown, but it is possible to modify it further. Figure 2a and Figure 2b Make various changes. For example, Figure 2a and Figure 2b The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. Furthermore, Figure 2a and Figure 2b This is intended to illustrate examples of the types of send and receive paths that can be used in a wireless network. Any other suitable architecture can be used to support wireless communication in a wireless network.

[0057] Figure 3a Example UE 116 according to this disclosure is shown. Figure 3a The embodiment of UE 116 shown is for illustrative purposes only, and Figure 1 UEs 111-115 can have the same or similar configurations. However, UEs have a wide variety of configurations, and Figure 3a This disclosure is not intended to limit the scope of any particular implementation of the UE.

[0058] UE 116 includes an antenna 301, a radio frequency (RF) transceiver 302, a transmit (TX) processing circuitry 303, a microphone 304, and a receive (RX) processing circuitry 305. UE 116 also includes a speaker 306, a controller / processor 307, an input / output (I / O) interface 308, multiple input devices 309, a display 310, and a memory 311. The memory 311 includes an operating system (OS) 312 and one or more applications 313.

[0059] RF transceiver 302 receives incoming RF signals transmitted by a gNB of wireless network 100 from antenna 301. RF transceiver 302 down-converts the incoming RF signals to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to RX processing circuitry 305, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. RX processing circuitry 305 sends the processed baseband signal to speaker 306 (e.g., for voice data) or to controller / processor 307 (e.g., for web browsing data) for further processing.

[0060] TX processing circuitry 303 receives analog or digital voice data from microphone 304, or other outgoing baseband data (such as network data, email, or interactive video game data) from controller / processor 307. TX processing circuitry 303 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate processed baseband or IF signals. RF transceiver 302 receives the processed baseband or IF signals from TX processing circuitry 303 and up-converts the baseband or IF signals into RF signals transmitted via antenna 301.

[0061] The controller / processor 307 may include one or more processors or other processing devices and execute an OS 312 stored in memory 311 to control the overall operation of the UE 116. For example, the controller / processor 307 may control the reception of forward channel signals and the transmission of reverse channel signals through the RF transceiver 302, the RX processing circuit 305, and the TX processing circuit 303 according to known principles. In some embodiments, the controller / processor 307 includes at least one microprocessor or microcontroller.

[0062] The controller / processor 307 is also capable of executing other processes and programs residing in the memory 311, such as operations for channel quality measurement and reporting for a system having a 2D antenna array as described in the embodiments of this disclosure. The controller / processor 307 is capable of moving data into or out of the memory 311 as needed for the execution of the process. In some embodiments, the controller / processor 307 is configured to execute an application 313 based on the OS 312 or in response to signals received from a gNB or operator. The controller / processor 307 is also coupled to an I / O interface IF 308, which provides the UE 116 with the ability to connect to other devices such as laptop computers and handheld computers. The I / O interface 308 is the communication path between these accessories and the controller / processor 307.

[0063] The controller / processor 307 is also coupled to input devices(s) 309 and a display 310. An operator of the UE 116 can use the input devices(s) 309 to input data into the UE 116. The display 310 may be a liquid crystal display or another display capable of displaying text and / or at least limited graphics (such as from a website). Memory 311 is coupled to the controller / processor 307. A portion of memory 311 may include random access memory (RAM), while another portion of memory 311 may include flash memory or other read-only memory (ROM).

[0064] although Figure 3a An example of UE 116 is shown, but it is possible to... Figure 3a Make various changes. For example, Figure 3a The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. As a specific example, the controller / processor 307 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Furthermore, although... Figure 3a The UE116 is shown configured as a mobile phone or smartphone, but the UE can be configured to operate as other types of mobile or fixed devices.

[0065] Figure 3b An example gNB 102 according to this disclosure is shown. Figure 3b The embodiment of gNB 102 shown is for illustrative purposes only, and Figure 1 Other gNBs can have the same or similar configurations. However, gNBs have a wide variety of configurations, and Figure 3b The scope of this disclosure is not limited to any particular implementation of the gNB. It should be noted that gNB 101 and gNB 103 can include the same or similar structures as gNB 102.

[0066] like Figure 3b As shown, gNB 102 includes multiple antennas 370a-370n, multiple RF transceivers 372a-372n, transmit (TX) processing circuitry 374, and receive (RX) processing circuitry 376. In some embodiments, one or more of the multiple antennas 370a-370n include a 2D antenna array. gNB 102 also includes a controller / processor 378, a memory 380, and a backhaul or network interface 382.

[0067] RF transceivers 372a-372n receive incoming RF signals, such as signals transmitted by the UE or other gNBs, from antennas 370a-370n. RF transceivers 372a-372n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are sent to RX processing circuitry 376, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. RX processing circuitry 376 sends the processed baseband signals to controller / processor 378 for further processing.

[0068] The TX processing circuit 374 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from the controller / processor 378. The TX processing circuit 374 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceivers 372a-372n receive the outgoing processed baseband or IF signal from the TX processing circuit 374 and up-convert the baseband or IF signal into an RF signal transmitted via antennas 370a-370n.

[0069] The controller / processor 378 may include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 378 may control the reception of forward channel signals and the transmission of reverse channel signals via RF transceivers 372a-372n, RX processing circuitry 376, and TX processing circuitry 374, according to known principles. The controller / processor 378 may also support additional functions, such as more advanced wireless communication functions. For example, the controller / processor 378 may perform a BIS process, such as by a blind interference sensing (BIS) algorithm, and decode the received signal after subtracting interference. The controller / processor 378 may support any of a wide variety of other functions in the gNB 102. In some embodiments, the controller / processor 378 includes at least one microprocessor or microcontroller.

[0070] The controller / processor 378 is also capable of executing programs and other processes, such as a basic operating system, residing in the memory 380. The controller / processor 378 is also capable of supporting channel quality measurement and reporting for systems having 2D antenna arrays as described in embodiments of this disclosure. In some embodiments, the controller / processor 378 supports communication between entities such as web RTCs. The controller / processor 378 is capable of moving data into or out of the memory 380 as needed for the execution of processes.

[0071] The controller / processor 378 is also coupled to a backhaul or network interface 382. The backhaul or network interface 382 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or over a network. The backhaul or network interface 382 is capable of supporting communication via any suitable wired or wireless connection(s). For example, when the gNB 102 is implemented as part of a cellular communication system (such as a cellular communication system supporting 5G or new radio access technologies or NR, LTE, or LTE-A), the backhaul or network interface 382 allows the gNB 102 to communicate with other gNBs via a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, the backhaul or network interface 382 allows the gNB 102 to communicate with a larger network (such as the Internet) via a wired or wireless local area network or via a wired or wireless connection. The backhaul or network interface 382 includes any suitable architecture supporting communication via a wired or wireless connection, such as an Ethernet or RF transceiver.

[0072] Memory 380 is coupled to controller / processor 378. A portion of memory 380 may include RAM, while another portion may include flash memory or other ROM. In some embodiments, multiple instructions, such as a BIS algorithm, are stored in memory. The multiple instructions are configured to cause controller / processor 378 to perform the BIS process and decode the received signal after subtracting at least one interference signal determined by the BIS algorithm.

[0073] As described in more detail below, the transmit and receive paths of the gNB 102 (implemented using RF transceivers 372a-372n, TX processing circuitry 374, and / or RX processing circuitry 376) support aggregated communication with FDD and TDD cells.

[0074] although Figure 3b An example of gNB 102 is shown, but more can be found on... Figure 3b Various modifications can be made. For example, gNB102 can include any number of... Figure 3a Each component shown. As a specific example, an access point can include multiple backhaul or network interfaces 382, ​​and a controller / processor 378 can support routing functions to route data between different network addresses. As another specific example, although shown as a single instance including TX processing circuitry 374 and a single instance including RX processing circuitry 376, the gNB 102 can include multiple instances of each (such as one for each RF transceiver).

[0075] Exemplary embodiments of this disclosure are further described below with reference to the accompanying drawings.

[0076] The text and accompanying drawings are provided by way of example only to aid the reader in understanding this disclosure. They are not intended and should not be construed as limiting the scope of this disclosure in any way. Although certain embodiments and examples have been provided, it will be apparent to those skilled in the art, based on the content disclosed herein, that changes may be made to the illustrated embodiments and examples without departing from the scope of this disclosure.

[0077] In a communication system, the transmission from the base station to the user equipment (UE) is called the downlink, and the transmission from the UE to the base station is called the uplink. The downlink corresponds to downlink transmission (also known as downlink transmission or downlink transmit), which includes at least one of downlink channel transmission and downlink signal transmission. The downlink channel includes the Physical Downlink Shared Channel (PDSCH) and the Physical Downlink Control Channel (PDCCH). Downlink signals may include, but are not limited to, downlink reference signals. The PDSCH is scheduled by the downlink control information (DCI) in the PDCCH.

[0078] Uplink transmission includes at least one of uplink channel transmission and uplink signal transmission. The uplink channel includes the Physical Uplink Shared Channel (PUSCH), the Physical Uplink Control Channel (PUCCH), and the Physical Random Access Channel (PRACH). Uplink signals may include, but are not limited to, uplink reference signals. The PUSCH is scheduled by Downlink Control Information (DCI) in the PDCCH.

[0079] When multiple serving cells or multiple time slots of PDSCH are scheduled in DCI format, the number of bits in the Hybrid Automatic Retransmission Request Acknowledgement (HARQ-ACK) for each DCI-formatted PDSCH is determined by the maximum number of configured serving cells and / or the maximum number of configured time slots. Adding a NACK to the HARQ-ACK position of unscheduled PDSCHs is done to prevent discrepancies in the interpretation of the HARQ-ACK bit count between the gNB and the UE when the UE misses a DCI detection. In this case, the added NACK is unnecessary, increasing the transmission of unnecessary HARQ-ACK bits.

[0080] In this disclosure, one DCI format corresponds to one DCI, therefore, the description of "PDSCH of DCI format scheduling" can be understood as "PDSCH of DCI scheduling corresponding to the DCI format".

[0081] For example, a configured DCI format can schedule a maximum of 8 PDSCHs, but the actual number of PDSCHs scheduled by this DCI format is between 1 and 8. Taking one DCI format as an example, if the number of PDSCHs scheduled by this DCI format is 2, and the HARQ-ACK of the PDSCHs scheduled by this DCI format is transmitted in the PUCCH, and the number of HARQ-ACK bits for the PDSCHs scheduled by this DCI format is 8, then the number of HARQ-ACK bits that need to be transmitted in the PUCCH is 8. Among them, 2 bits correspond to the 2 PDSCHs actually scheduled by the DCI format, and the remaining 6 bits of HARQ-ACK are padding NACK bits. These 6 bits are unnecessary HARQ-ACK bits.

[0082] Taking two DCI formats as an example, combined Figure 4 When the number of PDSCHs scheduled by the first DCI format 401 is 2, and the number of PDSCHs scheduled by the second DCI format 402 is 4, and the HARQ-ACK bits of the PDSCHs scheduled by the first DCI format 401 and the second DCI format 402 are transmitted on the same PUCCH, then the number of HARQ-ACK bits for the PDSCHs scheduled by the first DCI format 401 is 8, and the number of HARQ-ACK bits for the PDSCHs scheduled by the second DCI format 402 is 8. In this case, the number of HARQ-ACK bits that need to be transmitted on the PUCCH is 8 + 8 = 16, of which 6 bits correspond to the 6 PDSCHs actually scheduled by the two DCI formats, and the remaining 10 bits are padding NACK bits. These 10 bits are unnecessary HARQ-ACK bits.

[0083] The scheme proposed in this disclosure can ensure that the user equipment and the base station have the same understanding of the number of HARQ-ACK bits transmitted, while avoiding the transmission of meaningless padding HARQ-ACK bits.

[0084] This disclosure discloses a method performed by a user equipment (UE) in a wireless communication system. According to one embodiment, the method includes: receiving a DCI (Distributed Controlled Interchange) of a PDSCH (Power Distribution System), receiving the PDSCH, generating HARQ-ACK information for the PDSCH, and transmitting the HARQ-ACK information on a PUCCH or PUSCH. Wherein, when HARQ-ACK information for one PDSCH scheduled by a first DCI is transmitted on one PUCCH or PUSCH, the number of bits in the HARQ-ACK information is determined based on the actual PDSCHs scheduled by the first DCI; when HARQ-ACK information for multiple PDSCHs scheduled by the first DCI is transmitted on one PUCCH or PUSCH, the number of bits in the HARQ-ACK information is determined based on the maximum number of PDSCHs configured for the first DCI. Thus, determining the number of bits in the HARQ-ACK information based on the actual PDSCHs scheduled by the DCI avoids transmitting meaningless padding HARQ-ACK bits.

[0085] Figure 5 This illustration shows a flowchart of a method executed by a user equipment in a communication system according to an embodiment of this application.

[0086] In such Figure 5 In the method 500 shown, in step 501, the DCI for scheduling PDSCH is received.

[0087] In step 502, the PDSCH is received.

[0088] In step 503, the HARQ-ACK information for PDSCH is generated.

[0089] In step 504, HARQ-ACK information is transmitted on PUCCH or PUSCH.

[0090] Here, "first DCI" is a DCI with a DCI format capable of scheduling at least one PDSCH. For example, a DCI with this DCI format can simultaneously schedule the PDSCH of at least one serving cell, or can simultaneously schedule at least one time slot PDSCH of a serving cell, or can simultaneously schedule at least one time slot PDSCH of at least one serving cell.

[0091] For example, when a PUCCH or PUSCH transmits HARQ-ACK information for a PDSCH scheduled by a first DCI, the number of bits in the HARQ-ACK information can be determined based on the PDSCH actually scheduled by the first DCI. For instance, the DCI that receives the scheduled PDSCH from the base station includes the first DCI.

[0092] When HARQ-ACK information for multiple PDSCHs scheduled by the first DCI is transmitted on a single PUCCH or PUSCH, the number of bits in the HARQ-ACK information can be determined based on the maximum number of PDSCHs configured for the first DCI.

[0093] For example, the number of bits in the HARQ-ACK information can be the number of HARQ-ACK bits in the HARQ-ACK codebook, or the number of HARQ-ACK bits in a sub-codebook within the HARQ-ACK codebook.

[0094] In some embodiments, the number of bits of the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, and may include: the number of bits of the HARQ-ACK information is the sum of the number of bits of the HARQ-ACK information of multiple PDSCHs actually scheduled by the first DCI.

[0095] For example, the number of bits in the HARQ-ACK information can be the sum of the number of bits in the HARQ-ACK information of multiple PDSCHs actually scheduled by the first DCI. If the first DCI actually schedules only one PDSCH, then the number of bits in the HARQ-ACK information is the number of bits in the HARQ-ACK information of that one PDSCH actually scheduled by the first DCI.

[0096] In some embodiments, the number of bits in the HARQ-ACK information determined based on the PDSCH actually scheduled by the first DCI may include: when the codebook of the HARQ-ACK information is based on the codebook of transport blocks (TBs), the number of bits in the HARQ-ACK information is determined based on the sum of the number of TBs included in the PDSCH actually scheduled by the first DCI. Specifically, the number of bits in the HARQ-ACK information of the PDSCH actually scheduled by the first DCI is the sum of the number of TBs included in all PDSCHs actually scheduled by the first DCI.

[0097] Optionally, when transmitting HARQ-ACK information of a PDSCH scheduled by a first DCI in a PUCCH or a PUSCH, and the codebook of the HARQ-ACK information of the PDSCH is based on a TB codebook, the number of bits of the HARQ-ACK information of the PDSCH actually scheduled by the first DCI is the sum of the number of TBs included in the PDSCH actually scheduled by the first DCI.

[0098] In some embodiments, when the codebook of HARQ-ACK information is based on a code block group (CBG), the number of bits of HARQ-ACK information is the sum of the number of bits of HARQ-ACK information of TBs included in the PDSCH actually scheduled by the first DCI. For each TB in each PDSCH: when the number of code blocks (CBs) included in the TB is greater than or equal to a preset threshold, the number of bits of HARQ-ACK information of the TB is equal to the threshold; and when the number of CBs included in the TB is less than the threshold, the number of bits of HARQ-ACK information of the TB is equal to the number of CBs included in the TB.

[0099] For example, the threshold is the maximum number of CBGs contained in each TB (maxCodeBlockGroupsPerTransportBlock).

[0100] Optionally, when transmitting HARQ-ACK information of a PDSCH scheduled by a first DCI in a PUCCH or a PUSCH, and the codebook of the HARQ-ACK information of the PDSCH is based on the codebook of CBG, the number of bits of the HARQ-ACK information of the PDSCH actually scheduled by the first DCI is the sum of the number of bits of the HARQ-ACK information of the TB included in the PDSCH actually scheduled by the first DCI.

[0101] In some embodiments, where the DCI for scheduling PDSCH includes DL-DAI equal to 1, and the DCI for scheduling PUSCH does not include UL-DAI, the number of bits of HARQ-ACK information is determined based on the PDSCH actually scheduled by that DCI.

[0102] For example, the DL DAI in this application can be a counter DAI, a total DAI, or both a counter DAI and a total DAI.

[0103] For example, the DCI of the scheduled PDSCH received by the user equipment from the base station includes a DCI in which DL-DAI equals 1. The user equipment can determine the number of bits of HARQ-ACK information based on the actual scheduled PDSCH in which the DCI in which DL-DAI equals 1.

[0104] For example, the DCI of the scheduled PDSCH received by the user equipment from the base station includes DL-DAI equal to 1, and the DCI of the scheduled PUSCH received from the base station does not include UL-DAI. The user equipment can determine the number of bits of HARQ-ACK information based on the actual scheduled PDSCH according to the DCI of DL-DAI equal to 1.

[0105] In some embodiments, where the DCI scheduling PDSCH includes DL-DAI equal to 1 and the DCI scheduling PUSCH includes UL-DAI equal to 1, the number of bits of the HARQ-ACK information is determined based on the PDSCH actually scheduled by that DCI.

[0106] For example, the DCI of the scheduling PDSCH received by the user equipment from the base station includes DL-DAI equal to 1, and the DCI of the scheduling PUSCH received from the base station has UL DAI in the DCI format for that scheduling PDSCH. The number of bits for HARQ-ACK information can be determined based on the UL DAI and DL DAI, whether the PDSCH is actually scheduled according to the DCI. For instance, if the UL DAI in the DCI of the scheduling PUSCH received by the base station, which has the DCI format for that scheduling PDSCH, is equal to 1 and the DL DAI is equal to 1, the number of bits for HARQ-ACK information is determined based on the PDSCH actually scheduled according to the DCI.

[0107] In some embodiments, when HARQ-ACK information is transmitted in the PUCCH and the PUCCH transmits HARQ-ACK information of PDSCH scheduled in a DCI format (e.g., DCI format x_1), or when HARQ-ACK information is transmitted in the PUSCH and the PUSCH transmits HARQ-ACK information of PDSCH scheduled in a DCI format (e.g., DCI format x_1), the number of bits of the HARQ-ACK information can be determined according to the PDSCH actually scheduled in that DCI format (e.g., DCI format x_1).

[0108] For example, DCI format x_1: A DCI of DCI format x_1 can simultaneously schedule the PDSCH of at least one serving cell, a DCI of DCI format x_1 can simultaneously schedule at least one time slot PDSCH of a serving cell, or a DCI of DCI format x_1 can simultaneously schedule at least one time slot PDSCH of at least one serving cell. Here, x in DCI format x_1 can be any natural number other than 0, 1, and 2.

[0109] Optionally, the first DCI may include a first format DCI, which may be DCI format x_1.

[0110] In some embodiments, transmitting HARQ-ACK information on PUCCH or PUSCH may include transmitting a HARQ-ACK codebook on a PUCCH or a PUSCH.

[0111] Optionally, the HARQ-ACK codebook may include a first sub-codebook, which may include HARQ-ACK information for a PDSCH actually scheduled by a first DCI. For example, the first DCI may be a DCI with a first DCI format, and a first DCI may refer to a DCI with a first DCI format. The number of bits in the first sub-codebook may be determined based on the PDSCH actually scheduled by the first DCI.

[0112] Optionally, the HARQ-ACK codebook may also include a second sub-codebook. The second sub-codebook may include a codebook of HARQ-ACK information for one or more DCI-formatted DCI-scheduled PDSCHs and / or HARQ-ACK information for semi-persistently scheduled (SPS) PDSCHs.

[0113] For example, the first DCI format can be DCI format x_1, where x can be, for example, 3 or an integer greater than 3. DCI format x_1 can schedule multiple PDSCHs. The second DCI format can be a format other than DCI format x_1. For example, the second DCI format can be DCI format 0_1, 1_1, 2_1, etc., where one DCI of DCI format 0_1, 1_1, 2_1 schedules only one time slot of PDSCH of one serving cell at a time.

[0114] For example, the number of bits of HARQ-ACK information in the PDSCH of the DCI scheduling of the first DCI format can be determined according to the PDSCH actually scheduled by the DCI of the first DCI format.

[0115] For example, the number of bits of HARQ-ACK information of PDSCH and / or HARQ-ACK information of SPS PDSCH in the DCI scheduling of the second DCI format can be determined by other methods, which are not limited in this application. For example, it can be determined based on the maximum number of PDSCHs configured for the DCI of the second DCI format.

[0116] For example, if, in addition to the HARQ-ACK of the PDSCH scheduled by DCI in the first DCI format, there are also HARQ-ACK information of the PDSCH scheduled by DCI in the second DCI format and / or HARQ-ACK information of the SPS PDSCH transmitted in a PUCCH or a PUSCH, the number of bits of the HARQ-ACK information of the PDSCH scheduled by DCI in the first DCI format can be determined according to the sum of the number of bits of the HARQ-ACK information of the PDSCH actually scheduled by DCI in the first DCI format. The corresponding HARQ-ACK codebook can also be determined. This HARQ-ACK codebook is called the first sub-codebook. The codebooks for the HARQ-ACK of the PDSCH of the DCI schedule in the second DCI format and / or the HARQ-ACK of the SPS PDSCH are called the second sub-codebook. Then, the first sub-codebook and the second sub-codebook are connected together to form a HARQ-ACK codebook. The first sub-codebook can be placed before the second sub-codebook to form a HARQ-ACK codebook, or the first sub-codebook can be placed after the second sub-codebook to form a HARQ-ACK codebook.

[0117] If the HARQ-ACK information of two PDSCHs scheduled in the first DCI format (DCI format x_1) is transmitted on a PUCCH, the user equipment can determine the number of HARQ-ACK bits not based on the actual number of HARQ-ACK bits of the PDSCHs scheduled by that DCI, but for example, based on the number of HARQ-ACK bits of the maximum number of PDSCHs configured for that first DCI format. As an example, assuming the maximum number of PDSCHs that can be scheduled in a first DCI format is configured is 8, then the number of HARQ-ACK bits for two PDSCHs scheduled in the first DCI format is 16.

[0118] The specific method for determining the number of bits in the HARQ-ACK information is described below with reference to the accompanying diagram.

[0119] Example 1:

[0120] The number of at least one PDSCH actually scheduled in a DCI format can be equal to the number of serving cells actually scheduled in that DCI format. That is, only one PDSCH is scheduled for each serving cell in a DCI format. Specifically, a DCI format can be used to schedule one PDSCH in one serving cell, or to schedule multiple PDSCHs in multiple serving cells, with one PDSCH scheduled in each cell. The number of bits in the HARQ-ACK information is the sum of the number of bits in the HARQ-ACK information of all PDSCHs actually scheduled by that DCI. For example, the DCI format could be a first DCI format.

[0121] For example, such as Figure 6 As shown, a DCI schedules six PDSCHs from six serving cells. The HARQ-ACK bits in the PDSCH of the first serving cell are 1, the HARQ-ACK bits in the PDSCH of the second serving cell are 1, the HARQ-ACK bits in the PDSCH of the third serving cell are 2, the HARQ-ACK bits in the PDSCH of the fourth serving cell are 2, the HARQ-ACK bits in the PDSCH of the fifth serving cell are 1, and the HARQ-ACK bits in the PDSCH of the sixth serving cell are 2. The sum of the HARQ-ACK bits in the six PDSCHs of the six serving cells is 1+1+2+2+1+2=9. The HARQ-ACK bits in the HARQ-ACK codebook are 9. The UE transmits the 9-bit HARQ-ACK to the base station on the PUCCH.

[0122] In this way, determining the number of HARQ-ACK bits based on the actual PDSCH scheduled by the DCI can avoid adding meaningless NACK bits and prevent different understandings of the number of HARQ-ACK bits between the gNB and the UE.

[0123] The codebook for HARQ-ACK information in PDSCH can be a codebook based on TB or CBG. The number of bits in HARQ-ACK of PDSCH of the serving cell can be the number of TBs included in the PDSCH actually scheduled by DCI, or it can be the sum of the number of bits in HARQ-ACK information of the TBs included in the PDSCH actually scheduled by DCI.

[0124] When the codebook of the HARQ-ACK information of the PDSCH is based on the codebook of the transport block TB, the number of bits of the HARQ-ACK information of the PDSCH actually scheduled by the DCI is the sum of the number of TBs included in the PDSCH actually scheduled by the DCI, and the number of bits of the HARQ-ACK information of each PDSCH actually scheduled by the DCI is the number of TBs included in that PDSCH.

[0125] When the codebook of the HARQ-ACK information of the PDSCH is based on the codebook of code block groups (CBGs), the number of bits of the HARQ-ACK information of the PDSCH actually scheduled by the DCI is the sum of the number of bits of the HARQ-ACK information of the TBs included in the PDSCH actually scheduled by the DCI. The number of bits of the HARQ-ACK information of each PDSCH actually scheduled by the DCI is the sum of the number of bits of the HARQ-ACK information of the TBs included in that PDSCH. For each TB in each PDSCH: when the number of code blocks (CBs) included in the TB is greater than or equal to a preset threshold, the number of bits of the HARQ-ACK information of the TB is equal to the threshold, which is the maximum number of CBGs included in each TB; and when the number of CBs included in the TB is less than the threshold, the number of bits of the HARQ-ACK information of the TB is equal to the number of CBs included in the TB.

[0126] Optionally, the user equipment can transmit HARQ-ACK information on either PUCCH or PUSCH. When PUCCH and PUSCH overlap, the information can be transmitted via PUSCH.

[0127] According to this application, a PUCCH or a PUSCH can transmit only the HARQ-ACK information of all PDSCHs scheduled by a DCI.

[0128] Optionally, a PUCCH (or a PUSCH) can only transmit the HARQ-ACK information of all PDSCHs scheduled by the first DCI. It is impossible for two HARQ-ACKs of PDSCHs scheduled by the first DCI to be transmitted on one PUCCH. If this happens, it can be considered an error case.

[0129] Optionally, the DCI of the scheduling PDSCH received by the user equipment from the base station includes DL-DAI equal to 1, and the DCI of the scheduling PUSCH received from the base station does not include UL-DAI. The number of bits of HARQ-ACK information can be determined based on the actual scheduled PDSCH according to the DCI.

[0130] If the DCI of the PDSCH scheduled by the user equipment (UE) from the base station includes more than 1 DL-DAI, it means that more than one HARQ-ACK for a PDSCH scheduled in that DCI format is transmitted on a PUCCH. In this case, the UE can determine the number of HARQ-ACK bits based on the number of bits of HARQ-ACK information for the maximum number of PDSCHs configured for each DCI, rather than based on the actual number of PDSCHs scheduled by the DCI. The maximum number of PDSCHs configured for each DCI can be determined, for example, based on the maximum number of serving cells configured and / or the maximum number of time slots configured. In this embodiment, only one PDSCH is scheduled for each serving cell in a DCI format; therefore, the maximum number of PDSCHs configured for each DCI can be determined based on the maximum number of serving cells configured.

[0131] Alternatively, the DCI of the scheduled PDSCH received by the user equipment from the base station includes DL-DAI equal to 1, and the UL DAI in the DCI of the scheduled PUSCH received from the base station for the DCI format of the scheduled PDSCH is equal to 1. The DL DAI in the DCI format of the scheduled PDSCH can be replaced with UL DAI, and the number of bits of HARQ-ACK information can be determined according to the PDSCH actually scheduled by the DCI.

[0132] If the DCI of the scheduled PDSCH received by the user equipment from the base station includes a DL-DAI greater than 1, or if the UL DAI of the DCI of the scheduled PUSCH received by the user equipment from the base station is greater than 1 for the DCI format of that scheduled PDSCH, the user equipment can determine the number of HARQ-ACK bits based on the number of bits of HARQ-ACK information for the maximum number of PDSCHs configured for each DCI, rather than based on the number of bits of HARQ-ACK information for the PDSCHs actually scheduled for that DCI. The maximum number of PDSCHs configured for each DCI can be determined, for example, based on the maximum number of serving cells configured and / or the maximum number of time slots configured. In this embodiment, only one PDSCH is scheduled for each serving cell in a DCI format; therefore, the maximum number of PDSCHs configured for each DCI can be determined based on the maximum number of serving cells configured.

[0133] For example, assuming the maximum number of PDSCHs that can be scheduled in this DCI format is 8 (the maximum number of serving cells configured is 8), the first DCI format actually schedules 2 PDSCHs, the second DCI format actually schedules 4 PDSCHs, and the maximum number of HARQ-ACK bits for each PDSCH is 2, then when the HARQ-ACK bits of these two DCI format PDSCHs are transmitted on the same PUCCH, the number of HARQ-ACK bits that need to be transmitted on the PUCCH is the number of HARQ-ACK bits of 8 PDSCHs, for a total of 16 bits.

[0134] Example 2:

[0135] The number of at least one PDSCH actually scheduled in a DCI format can be equal to the number of time slots in a serving cell actually scheduled in a DCI format. That is, only one PDSCH is scheduled per time slot in a DCI format. Specifically, a DCI format can be used to schedule one PDSCH in one time slot for a serving cell, or to schedule multiple PDSCHs in multiple time slots, with one PDSCH scheduled in each time slot. The number of bits for HARQ-ACK information is the sum of the number of bits for HARQ-ACK information of all PDSCHs actually scheduled by the DCI. For example, the DCI format could be a first DCI format.

[0136] For example, such as Figure 7 As shown, a DCI schedules 6 PDSCHs across 6 time slots. The number of HARQ-ACK bits in each of the 6 time slots' PDSCHs is 1. The sum of the number of HARQ-ACK bits in the 6 PDSCHs across the 6 time slots is 1+1+1+1+1+1=6. The number of HARQ-ACK bits in the HARQ-ACK codebook is 6. The UE transmits the 6-bit HARQ-ACK to the base station on the PUCCH.

[0137] In this way, determining the number of HARQ-ACK bits based on the actual PDSCH scheduled by the DCI can avoid adding meaningless NACK bits and prevent different understandings of the number of HARQ-ACK bits between the gNB and the UE.

[0138] The codebook for the HARQ-ACK information of PDSCH can be a codebook based on TB or CBG. The number of bits for the HARQ-ACK of PDSCH can be the number of TBs included in the PDSCH actually scheduled by DCI, or it can be the sum of the number of bits for the HARQ-ACK information of the TBs included in the PDSCH actually scheduled by DCI.

[0139] When the codebook of the HARQ-ACK information of the PDSCH is based on the codebook of the transport block TB, the number of bits of the HARQ-ACK information of the PDSCH actually scheduled by the DCI is the sum of the number of TBs included in the PDSCH actually scheduled by the DCI, wherein the number of bits of the HARQ-ACK information of each PDSCH actually scheduled by the DCI is the number of TBs included in that PDSCH.

[0140] When the codebook of the HARQ-ACK information of the PDSCH is based on the codebook of code block groups (CBGs), the number of bits of the HARQ-ACK information of the PDSCH actually scheduled by the DCI is the sum of the number of bits of the HARQ-ACK information of the TBs included in the PDSCH actually scheduled by the DCI. The number of bits of the HARQ-ACK information of each PDSCH actually scheduled by the DCI is the sum of the number of bits of the HARQ-ACK information of the TBs included in the PDSCH. For each TB in each PDSCH: when the number of code blocks (CBs) included in the TB is greater than or equal to a preset threshold, the number of bits of the HARQ-ACK information of the TB is equal to the threshold, and the threshold is the maximum number of CBGs included in each TB; and when the number of CBs included in the TB is less than the threshold, the number of bits of the HARQ-ACK information of the TB is equal to the number of CBs included in the TB.

[0141] Optionally, the user equipment can transmit HARQ-ACK information on either PUCCH or PUSCH. When PUCCH and PUSCH overlap, the information can be transmitted via PUSCH.

[0142] According to this application, a PUCCH or a PUSCH can transmit only the HARQ-ACK information of all PDSCHs scheduled by a DCI.

[0143] Optionally, it can be assumed that a PUCCH (or a PUSCH) can only transmit the HARQ-ACK information of all PDSCHs scheduled by the first DCI, and there will be no situation where the HARQ-ACK of two PDSCHs scheduled by the first DCI is transmitted on one PUCCH. If this happens, it can be considered an error case.

[0144] Optionally, the DCI of the scheduling PDSCH received by the user equipment from the base station includes DL-DAI equal to 1, and the DCI of the scheduling PUSCH received from the base station does not include UL-DAI. The number of bits of HARQ-ACK information can be determined based on the actual scheduled PDSCH according to the DCI.

[0145] If the DCI of the PDSCH scheduled by the user equipment (UE) from the base station includes more than 1 DL-DAI, it means that more than one HARQ-ACK of the PDSCH scheduled in that DCI format is transmitted on a PUCCH. In this case, the UE can determine the number of HARQ-ACK bits based on the maximum number of HARQ-ACK bits configured for each DCI, rather than based on the actual number of HARQ-ACK bits of the PDSCHs scheduled by the DCI. The maximum number of PDSCHs configured for each DCI can be determined, for example, based on the maximum number of serving cells and / or the maximum number of time slots configured. In this embodiment, only one PDSCH is scheduled per time slot in a DCI format; therefore, the maximum number of PDSCHs configured for each DCI can be determined based on the maximum number of time slots configured.

[0146] Alternatively, the DCI of the scheduled PDSCH received by the user equipment from the base station includes DL-DAI equal to 1, and the UL DAI in the DCI of the scheduled PUSCH received from the base station for the DCI format of the scheduled PDSCH is equal to 1. The DL DAI in the DCI format of the scheduled PDSCH can be replaced with UL DAI, and the number of bits of HARQ-ACK information can be determined according to the PDSCH actually scheduled by the DCI.

[0147] If the DCI of the scheduled PDSCH received by the user equipment from the base station includes a DL-DAI greater than 1, or if the UL DAI of the DCI of the scheduled PUSCH received by the user equipment from the base station is greater than 1 for the DCI format of that scheduled PDSCH, the user equipment can determine the number of HARQ-ACK bits based on the maximum number configured for each DCI, rather than based on the number of HARQ-ACK bits of the PDSCH actually scheduled for that DCI. The maximum number of PDSCHs configured for each DCI can be determined, for example, based on the maximum number of serving cells and / or the maximum number of time slots configured. In this embodiment, only one PDSCH is scheduled per time slot for a DCI format; therefore, the maximum number of PDSCHs configured for each DCI can be determined based on the maximum number of time slots configured.

[0148] For example, assuming the maximum number of PDSCHs that can be scheduled in a DCI format is 8 (the maximum number of configured time slots is 8), the first DCI format actually schedules 2 PDSCHs, the second DCI format actually schedules 4 PDSCHs, and the maximum number of HARQ-ACK bits for each PDSCH is 1, then when the HARQ-ACK bits of these two DCI format PDSCHs are transmitted on the same PUCCH, the number of HARQ-ACK bits that need to be transmitted on the PUCCH is the number of HARQ-ACK bits of 8 PDSCHs, for a total of 8 bits.

[0149] Example 3:

[0150] The number of at least one PDSCH actually scheduled in a DCI format can be the sum of the number of time slots in multiple serving cells actually scheduled in a DCI format. That is, only one PDSCH is scheduled in each time slot of each serving cell in a DCI format. Specifically, the DCI format is used to schedule one PDSCH in one time slot of one serving cell, or to schedule multiple PDSCHs in multiple time slots of multiple serving cells, wherein one PDSCH is scheduled in each time slot of each serving cell. The number of bits for HARQ-ACK information is the sum of the number of bits for HARQ-ACK information of all PDSCHs actually scheduled by the DCI. For example, the DCI format can be a first DCI format.

[0151] For example, such as Figure 8 As shown, a DCI schedules 6 PDSCHs across 6 time slots for 2 serving cells. The HARQ-ACK bits for the 3 PDSCHs in the 3 time slots of the first serving cell are all 1, and the HARQ-ACK bits for the 3 PDSCHs in the 3 time slots of the second serving cell are all 2. The sum of the HARQ-ACK bits for the 6 PDSCHs across the 6 time slots is 1+1+1+2+2+2=9. The HARQ-ACK bits in the HARQ-ACK codebook are 9. The UE transmits the 9-bit HARQ-ACK to the base station on the PUCCH.

[0152] In this way, determining the number of HARQ-ACK bits based on the actual PDSCH scheduled by the DCI can avoid adding meaningless NACK bits and prevent different understandings of the number of HARQ-ACK bits between the gNB and the UE.

[0153] The codebook for the HARQ-ACK information of PDSCH can be a codebook based on TB or CBG. The number of bits for the HARQ-ACK of PDSCH can be the number of TBs included in the PDSCH actually scheduled by DCI, or it can be the sum of the number of bits for the HARQ-ACK information of the TBs included in the PDSCH actually scheduled by DCI.

[0154] When the codebook of the HARQ-ACK information of the PDSCH is based on the codebook of the transport block TB, the number of bits of the HARQ-ACK information of the PDSCH actually scheduled by the DCI is the sum of the number of TBs included in the PDSCH actually scheduled by the DCI, wherein the number of bits of the HARQ-ACK information of each PDSCH actually scheduled by the DCI is the number of TBs included in the PDSCH.

[0155] When the codebook of the HARQ-ACK information of the PDSCH is based on the codebook of code block groups (CBGs), the number of bits of the HARQ-ACK information of the PDSCH actually scheduled by the DCI is the sum of the number of bits of the HARQ-ACK information of the TBs included in the PDSCH actually scheduled by the DCI. The number of bits of the HARQ-ACK information of each PDSCH actually scheduled by the DCI is the sum of the number of bits of the HARQ-ACK information of the TBs included in the PDSCH. For each TB in each PDSCH: when the number of code blocks (CBs) included in the TB is greater than or equal to a preset threshold, the number of bits of the HARQ-ACK information of the TB is equal to the threshold, and the threshold is the maximum number of CBGs included in each TB; and when the number of CBs included in the TB is less than the threshold, the number of bits of the HARQ-ACK information of the TB is equal to the number of CBs included in the TB.

[0156] Optionally, the user equipment can transmit HARQ-ACK information on either PUCCH or PUSCH. When PUCCH and PUSCH overlap, the information can be transmitted via PUSCH.

[0157] According to this application, a PUCCH or a PUSCH can transmit only the HARQ-ACK information of all PDSCHs scheduled by a DCI.

[0158] Optionally, it can be assumed that a PUCCH (or a PUSCH) can only transmit the HARQ-ACK information of all PDSCHs scheduled by the first DCI, and there will be no situation where the HARQ-ACK of two PDSCHs scheduled by the first DCI is transmitted on one PUCCH. If this happens, it can be considered an error case.

[0159] Optionally, the DCI of the scheduling PDSCH received by the user equipment from the base station includes DL-DAI equal to 1, and the DCI of the scheduling PUSCH received from the base station does not include UL-DAI. The number of bits of HARQ-ACK information can be determined based on the actual scheduled PDSCH according to the DCI.

[0160] If the DCI of the scheduled PDSCH received by the user equipment from the base station includes more than 1 DL-DAI, it means that more than one HARQ-ACK of the PDSCH scheduled in that DCI format is transmitted on a PUCCH. In this case, the user equipment can determine the number of HARQ-ACK bits based on the maximum number of HARQ-ACK bits configured for each DCI, rather than based on the actual number of HARQ-ACK bits of the PDSCHs scheduled by the DCI. The maximum number of PDSCHs configured for each DCI can be determined, for example, based on the maximum number of serving cells and / or the maximum number of time slots configured. In this embodiment, one PDSCH is scheduled for each time slot of each serving cell in a DCI format; therefore, the maximum number of PDSCHs configured for each DCI can be determined based on the maximum number of serving cells and the maximum number of time slots configured.

[0161] Alternatively, the DCI of the scheduled PDSCH received by the user equipment from the base station includes DL-DAI equal to 1, and the UL DAI in the DCI of the scheduled PUSCH received from the base station for the DCI format of the scheduled PDSCH is equal to 1. The DL DAI in the DCI format of the scheduled PDSCH can be replaced with UL DAI, and the number of bits of HARQ-ACK information can be determined according to the PDSCH actually scheduled by the DCI.

[0162] If the DCI of the scheduled PDSCH received by the user equipment from the base station includes a DL-DAI greater than 1, or if the UL DAI of the DCI of the scheduled PUSCH received by the user equipment from the base station is greater than 1 for the DCI format of that scheduled PDSCH, the user equipment can determine the number of HARQ-ACK bits based on the maximum number of PDSCHs configured for each DCI, rather than based on the actual number of PDSCHs scheduled for that DCI. The maximum number of PDSCHs configured for each DCI can be determined, for example, based on the maximum number of serving cells configured and / or the maximum number of time slots configured. In this embodiment, one PDSCH is scheduled for each time slot of each serving cell in a DCI format scheduling; therefore, the maximum number of PDSCHs configured for each DCI can be determined based on the maximum number of serving cells configured and the maximum number of time slots configured.

[0163] For example, assuming the maximum number of serving cells configured is 4 and the maximum number of time slots configured is also 4, then the maximum number of PDSCHs that can be scheduled in this DCI format is 16. If the number of PDSCHs actually scheduled in the first DCI format is 2 and the number of PDSCHs actually scheduled in the second DCI format is 4, and the maximum number of HARQ-ACK bits for each PDSCH is 1, then when the HARQ-ACK bits of these two DCI format PDSCHs are transmitted on the same PUCCH, the number of HARQ-ACK bits that need to be transmitted on the PUCCH is the same as the number of HARQ-ACK bits for the 16 PDSCHs, for a total of 16 bits.

[0164] The methods described above in this disclosure can be performed by a UE that includes a transceiver and a processor. Figure 9 An exemplary structure of a UE according to this disclosure is shown. Figure 9 As shown, the UE includes a transceiver 910 and a processor 920 coupled to the transceiver 910. The transceiver 910 is configured to transmit and receive signals. The processor 920 is configured to perform the methods described in this disclosure. This disclosure can also be implemented as a computer storage medium. The computer storage medium stores computer-executable instructions, which, when executed by a processor, perform the methods described in this disclosure.

[0165] The UE and the method executed by the UE according to the embodiments of this disclosure have been described above. It should be understood that the base station performing the corresponding steps and the corresponding method executed by the base station are also included within the scope of this application.

[0166] According to an exemplary embodiment, a method performed by a base station in a wireless communication system may include:

[0167] The system transmits Downlink Control Information (DCI) on the Physical Downlink Shared Channel (PDSCH), transmits PDSCH, and receives Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) information on the Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSCH). Specifically, when a PUCCH or PUSCH transmits HARQ-ACK information for one PDSCH scheduled by the first DCI, the number of bits in the HARQ-ACK information is determined based on the actual number of PDSCHs scheduled by the first DCI. When a PUCCH or PUSCH transmits HARQ-ACK information for multiple PDSCHs scheduled by the first DCI, the number of bits in the HARQ-ACK information is determined based on the maximum number of PDSCHs configured for the first DCI.

[0168] In an exemplary implementation, the number of bits of HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: the number of bits of HARQ-ACK information is the sum of the number of bits of HARQ-ACK information of multiple PDSCHs actually scheduled by the first DCI.

[0169] In an exemplary implementation, the number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: when the codebook of the HARQ-ACK information is based on the codebook of transport block TB, the number of bits in the HARQ-ACK information is determined based on the sum of the number of TBs included in the PDSCH actually scheduled by the first DCI.

[0170] In an exemplary implementation, when the codebook of HARQ-ACK information is based on a codebook of code block groups (CBGs), the number of bits of HARQ-ACK information is the sum of the number of bits of HARQ-ACK information of TBs included in the PDSCH actually scheduled by the first DCI. For each TB in each PDSCH: when the number of code blocks (CBs) included in the TB is greater than or equal to a preset threshold, the number of bits of HARQ-ACK information of the TB is equal to the threshold, where the threshold is the maximum number of CBGs included in each TB; and when the number of CBs included in the TB is less than the threshold, the number of bits of HARQ-ACK information of the TB is equal to the number of CBs included in the TB.

[0171] In an exemplary implementation, when the DCI for scheduling PDSCH includes a downlink-downlink allocation index DL-DAI equal to 1, and the DCI for scheduling PUSCH does not include an uplink-downlink allocation index UL-DAI, the number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the DCI.

[0172] In an exemplary implementation, when the DCI scheduling PDSCH includes DL-DAI equal to 1 and the DCI scheduling PUSCH includes UL-DAI equal to 1, the number of bits of the HARQ-ACK information is determined based on the PDSCH actually scheduled by the DCI.

[0173] In an exemplary implementation, receiving hybrid automatic repeat request acknowledgment (HARQ-ACK) information on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) includes: receiving a HARQ-ACK codebook on a PUCCH or a PUSCH; wherein a first sub-codebook in the HARQ-ACK codebook includes HARQ-ACK information for a first DCI-scheduled PDSCH.

[0174] Furthermore, other technical features related to the base station in the implementation described for the UE are also applicable to the base station according to this disclosure.

[0175] The various illustrative logic blocks, modules, and circuits described in this disclosure may be implemented or performed using a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternative embodiments, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

[0176] The steps of the methods or algorithms described in this disclosure may be embodied directly in hardware, in a software module executed by a processor, or in a combination of both. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor such that the processor can read and write information to / from the storage medium. In an alternative, the storage medium may be integrated into the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user equipment terminal. In an alternative, the processor and storage medium may reside as discrete components in the user equipment terminal.

[0177] In one or more exemplary designs, the functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media, the latter including any medium that facilitates the transfer of a computer program from one location to another. Storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0178] The description set forth herein, taken in conjunction with the accompanying drawings, describes exemplary methods and apparatuses and does not represent all examples that can be implemented or that fall within the scope of the claims. As used herein, the term "exemplary" means "serving as an example, instance, or illustration," and not "preferred" or "superior to other examples." The detailed description includes specific details intended to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, well-known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0179] Although this specification contains details of various specific implementations, these should not be construed as limiting any invention or the scope of the claims, but rather as descriptions of specific features of particular embodiments of a particular invention. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually in multiple embodiments or in any suitable sub-combination. Furthermore, although features may be described above as functioning in certain combinations, and even initially claimed as such, in some cases one or more features from a claimed combination may be removed from that combination, and the claimed combination may be for sub-combinations or variations thereof.

[0180] It should be understood that the specific order or hierarchy of steps in the methods of this disclosure is an illustration of an exemplary process. Based on design preferences, it is understood that the specific order or hierarchy of steps in the method can be rearranged to achieve the functions and effects disclosed in this disclosure. The appended method claims present the elements of various steps in an exemplary order and are not intended to limit one to the specific order or hierarchy presented, unless otherwise specifically stated. Furthermore, although elements may be described or claimed in the singular, the plural is also contemplated unless a limitation on the singular is explicitly stated. Therefore, this disclosure is not limited to the examples shown, and any means for performing the functions described herein are included in various aspects of this disclosure. Furthermore, the symbol “ / ” used in this application should be understood as “and / or”.

[0181] The text and accompanying drawings are provided by way of example only to aid the reader in understanding this disclosure. They are not intended and should not be construed as limiting the scope of this disclosure in any way. Although certain embodiments and examples have been provided, it will be apparent to those skilled in the art, based on the content disclosed herein, that changes may be made to the illustrated embodiments and examples without departing from the scope of this disclosure.

Claims

1. A method performed by a user equipment (UE) in a wireless communication network, the method comprising: Receive and schedule downlink control information (DCI) for the Physical Downlink Shared Channel (PDSCH); Receive the PDSCH; Generate the hybrid automatic repeat request response (HARQ-ACK) information for the PDSCH; The HARQ-ACK information is transmitted on the Physical Uplink Control Channel PUCCH or the Physical Uplink Shared Channel PUSCH. In the case where a PUCCH or PUSCH transmits HARQ-ACK information for a PDSCH scheduled by a first DCI, the number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI. When HARQ-ACK information for multiple PDSCHs scheduled by the first DCI is transmitted on a single PUCCH or PUSCH, the number of bits in the HARQ-ACK information is determined based on the maximum number of PDSCHs configured for the first DCI.

2. The method of claim 1, wherein, The number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: the number of bits in the HARQ-ACK information is the sum of the number of bits in the HARQ-ACK information of multiple PDSCHs actually scheduled by the first DCI.

3. The method of claim 1, wherein, The number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: when the codebook of the HARQ-ACK information is based on the codebook of transport block TB, the number of bits in the HARQ-ACK information is determined based on the sum of the number of TBs included in the PDSCH actually scheduled by the first DCI.

4. The method according to claim 1, wherein, The number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: When the codebook for the HARQ-ACK information is based on the codebook of code block group CBG, the number of bits in the HARQ-ACK information is the sum of the number of bits in the HARQ-ACK information of the TBs included in the PDSCH actually scheduled by the first DCI, for each TB in each PDSCH: When the number of code blocks (CBs) included in the TB is greater than or equal to a preset threshold, the number of bits of the HARQ-ACK information in the TB is equal to the threshold, where the threshold is the maximum number of CBGs contained in each TB; and When the number of CBs included in the TB is less than the threshold, the number of bits of the HARQ-ACK information of the TB is equal to the number of CBs included in the TB.

5. The method according to claim 1, wherein, The number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: When the DCI for scheduling the PDSCH includes a downlink-downlink allocation index DL-DAI equal to 1, and the DCI for scheduling the PUSCH does not include an uplink-downlink allocation index UL-DAI, the number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the DCI.

6. The method according to claim 1, wherein, The number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: When the DCI for scheduling the PDSCH includes DL-DAI equal to 1, and the DCI for scheduling the PUSCH includes UL-DAI equal to 1, the number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the DCI.

7. The method according to claim 1, wherein, In the case of transmitting HARQ-ACK information for a first DCI-scheduled PDSCH on a PUCCH or PUSCH, transmitting the HARQ-ACK information on the Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSCH) includes: HARQ-ACK codebook is transmitted on one of the PUCCHs or one of the PUSCHs, wherein the first sub-codebook in the HARQ-ACK codebook includes the HARQ-ACK information of a PDSCH actually scheduled by the first DCI.

8. A method performed by a base station in a wireless communication network, the method comprising: Send downlink control information (DCI) to schedule the physical downlink shared channel (PDSCH); Send the PDSCH; Receive the hybrid automatic repeat request response (HARQ-ACK) information on the physical uplink control channel (PUCCH) or the physical uplink shared channel (PUSCH); In the case where a PUCCH or PUSCH transmits HARQ-ACK information for a PDSCH scheduled by a first DCI, the number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI. When HARQ-ACK information for multiple PDSCHs scheduled by the first DCI is transmitted on a single PUCCH or PUSCH, the number of bits in the HARQ-ACK information is determined based on the maximum number of PDSCHs configured for the first DCI.

9. The method according to claim 8, wherein, The number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: the number of bits in the HARQ-ACK information is the sum of the number of bits in the HARQ-ACK information of multiple PDSCHs actually scheduled by the first DCI.

10. The method according to claim 8, wherein, The number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: When the codebook of the HARQ-ACK information is based on the codebook of transport block TB, the number of bits of the HARQ-ACK information is determined based on the sum of the number of TBs included in the PDSCH actually scheduled by the first DCI.

11. The method according to claim 8, wherein, The number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: When the codebook for the HARQ-ACK information is based on the codebook of code block group CBG, the number of bits in the HARQ-ACK information is the sum of the number of bits in the HARQ-ACK information of the TBs included in the PDSCH actually scheduled by the first DCI, for each TB in each PDSCH: When the number of code blocks (CBs) included in the TB is greater than or equal to a preset threshold, the number of bits of the HARQ-ACK information in the TB is equal to the threshold, where the threshold is the maximum number of CBGs contained in each TB; and When the number of CBs included in the TB is less than the threshold, the number of bits of the HARQ-ACK information of the TB is equal to the number of CBs included in the TB.

12. The method according to claim 8, wherein, The number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: When the DCI for scheduling the PDSCH includes a downlink-downlink allocation index DL-DAI equal to 1, and the DCI for scheduling the PUSCH does not include an uplink-downlink allocation index UL-DAI, the number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the DCI.

13. The method according to claim 8, wherein, The number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the first DCI, including: When the DCI for scheduling the PDSCH includes DL-DAI equal to 1, and the DCI for scheduling the PUSCH includes UL-DAI equal to 1, the number of bits in the HARQ-ACK information is determined based on the PDSCH actually scheduled by the DCI.

14. The method according to claim 8, wherein, In the case where a HARQ-ACK message for a first DCI-scheduled PDSCH is transmitted on a PUCCH or PUSCH, receiving the hybrid automatic repeat request acknowledgment (HARQ-ACK) message on the Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSCH) includes: HARQ-ACK codebook is received on one of the PUCCHs or one of the PUSCHs; wherein, the first sub-codebook in the HARQ-ACK codebook includes the HARQ-ACK information of a PDSCH actually scheduled by the first DCI.

15. A user equipment (UE), comprising: A transceiver is configured to send and receive signals; and A processor, coupled to the transceiver, and configured to perform the method according to any one of claims 1 to 7.

16. A base station, comprising: A transceiver is configured to send and receive signals; and A processor, coupled to the transceiver, and configured to perform the method described in any one of claims 8 to 14.

17. A computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, perform the method of any one of claims 1 to 14.

Images