CN115883027A - Method and apparatus for hybrid automatic repeat request-acknowledgement retransmission - Google Patents

Abstract

Methods and apparatus for hybrid automatic repeat request-acknowledgement (HARQ-ACK) retransmission are provided. The method comprises the following steps: receiving configuration information related to HARQ-ACK retransmission from a base station; and retransmitting the HARQ-ACK information which is cancelled on the first physical uplink control channel PUCCH based on the configuration information. The invention avoids the retransmission of the downlink data by retransmitting the HARQ-ACK information, thereby saving transmission resources.

Description

Method and apparatus for hybrid automatic repeat request-acknowledgement retransmission

Technical Field

The present disclosure relates generally to the field of wireless communications, and more particularly, to a method and apparatus for hybrid automatic repeat request-acknowledgement (HARQ-ACK) retransmission.

Background

In order to meet the increasing demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi-5G communication systems. Accordingly, the 5G or quasi-5G communication system is also referred to as a "super 4G network" or a "post-LTE system".

The 5G communication system is implemented in a higher frequency (millimeter wave) band, for example, a 60GHz band, to achieve a higher data rate. In order to reduce propagation loss of radio waves and increase transmission distance, beamforming, massive Multiple Input Multiple Output (MIMO), full-dimensional MIMO (FD-MIMO), array antenna, analog beamforming, massive antenna technology are discussed in the 5G communication system.

Further, in the 5G communication system, development of improvement of a system network is ongoing based on advanced small cells, cloud Radio Access Network (RAN), ultra dense network, device-to-device (D2D) communication, wireless backhaul, mobile network, cooperative communication, coordinated multipoint (CoMP), reception side interference cancellation, and the like.

In 5G systems, hybrid FSK and QAM modulation (FQAM) and Sliding Window Superposition Coding (SWSC) have been developed as Advanced Coding Modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and Sparse Code Multiple Access (SCMA) as advanced access techniques.

Disclosure of Invention

In accordance with at least one embodiment of the present disclosure, a method for hybrid automatic repeat request-acknowledgement (HARQ-ACK) retransmission performed by a terminal is provided. The method comprises the following steps: receiving configuration information related to HARQ-ACK retransmission from a base station; and retransmitting the HARQ-ACK information, which is cancelled on a first Physical Uplink Control Channel (PUCCH), based on the configuration information.

According to at least one embodiment of the present disclosure, a method for HARQ-ACK retransmission performed by a base station is provided. The method comprises the following steps:

in some embodiments, for example, the configuration information related to HARQ-ACK retransmission includes a Downlink Control Information (DCI) format indicating whether retransmission of HARQ-ACK information on the second PUCCH is triggered.

In some embodiments, for example, the DCI format includes at least one of a first offset indicator to indicate a time unit interval of the first PUCCH and a second PUCCH to retransmit HARQ-ACK information or a second offset indicator to indicate a time unit interval of the first PUCCH and a Physical Downlink Control Channel (PDCCH) carrying the DCI format.

In some embodiments, for example, at least one of a plurality of fields in the DCI format is used for at least one of the first offset indicator or the second offset indicator, the plurality of fields including a Frequency Domain Resource Allocation (FDRA), a Modulation and Coding Scheme (MCS), a HARQ process number, or an antenna port.

In some embodiments, for example, the DCI format is a group-common DCI format for indicating whether to trigger retransmission of HARQ-ACK information for each terminal in a group of terminals including the terminal.

In some embodiments, for example, a Cyclic Redundancy Check (CRC) of the DCI format is scrambled by at least one of a cell radio network temporary identity (C-RNTI), a configuration schedule (CS-RNTI), a Modulation and Coding Scheme (MCS) -C-RNTI, a multicast (G) -RNTI, or a multicast configuration schedule (G-CS) -RNTI.

In some embodiments, for example, the terminal does not expect more than one DCI format to trigger retransmission of HARQ-ACK information in the second PUCCH.

In some embodiments, for example, the DCI format triggers only retransmission of HARQ-ACK information as an initial transmission.

In some embodiments, for example, the retransmission of the HARQ-ACK information is not multiplexed with other HARQ-ACK information to the second PUCCH.

In some embodiments, for example, the second PUCCH that the terminal does not expect for retransmission of HARQ-ACK information is earlier than or equal to the first PUCCH.

In some embodiments, for example, retransmitting HARQ-ACK information based on configuration information comprises: and when the DCI format indication triggers retransmission of the HARQ-ACK information on the second PUCCH, performing retransmission of the HARQ-ACK information on the second PUCCH.

In some embodiments, for example, when there are multiple DCI formats received with the same PDCCH monitoring occasion indicating that HARQ-ACK is transmitted on the same PUCCH, the terminal does not expect configuration information related to HARQ-ACK retransmission among the multiple DCI formats to be different.

In some embodiments, for example, when a DCI format is received at a first PDCCH monitoring occasion and the DCI format triggers retransmission of HARQ-ACK information in a second PUCCH, another DCI format that does not trigger retransmission of HARQ-ACK information in the second PUCCH is not expected to be received at the second PDCCH monitoring occasion.

In some embodiments, for example, when the HARQ-ACK information is retransmitted HARQ-ACK information and the DCI format is used to trigger retransmission of the retransmitted HARQ-ACK information, a time unit interval between a first PUCCH used for retransmission of the HARQ-ACK information and a second PUCCH used for retransmission of the HARQ-ACK information is not expected to be greater than or equal to a maximum time unit interval.

In some embodiments, for example, retransmitting the HARQ-ACK information based on the configuration information includes determining a HARQ-ACK codebook including the HARQ-ACK information and transmitting the HARQ-ACK codebook.

In some examples, determining the HARQ-ACK codebook including the HARQ-ACK information includes at least one of:

determining a HARQ-ACK codebook of the HARQ-ACK information based on a set of timing values K1 for indicating timing of HARQ feedback and a time unit interval between the first PUCCH and a second PUCCH for retransmitting the HARQ-ACK information; or

The HARQ-ACK codebook for the HARQ-ACK information triggering retransmission is placed after or before a type-1 HARQ-ACK codebook in a second PUCCH indicated by a second DCI format for transmission if the HARQ-ACK codebook for the HARQ-ACK information triggering retransmission only includes HARQ-ACK information for a semi-persistent scheduling SPS Physical Downlink Shared Channel (PDSCH); or

The HARQ-ACK information for at least one of the one or more SPS PDSCHs that satisfies a predefined condition is placed for transmission after or before the type-1 HARQ-ACK codebook in the second PUCCH indicated by the second DCI format if the HARQ-ACK codebook for the HARQ-ACK information for which retransmission is triggered includes only HARQ-ACK information for the one or more SPS PDSCHs, wherein the predefined condition includes that the at least one SPS PDSCH is not included in any of the one or more downlink time units indicated by the set of corresponding timing values K1 for the second PUCCH.

In some examples, determining the HARQ-ACK codebook including the HARQ-ACK information includes:

and jointly counting or respectively counting Downlink Assignment Indexes (DAIs) of DCI formats triggering retransmission of the HARQ-ACK information and DAIs of DCI formats corresponding to downlink transmission associated with the HARQ-ACK information, and determining an HARQ codebook of the HARQ-ACK information based on the jointly counted DAIs or the respectively counted DAIs.

In some embodiments, for example, when the terminal is configured with a dynamic HARQ-ACK codebook, the HARQ-ACK codebook not generating the dynamically scheduled downlink transmission is determined based on at least one of:

a value indicated by a DAI field included in the DCI format is a preset value;

the terminal does not receive any DCI format scheduling HARQ-ACK information and transmits the HARQ-ACK information in a time unit where a second PUCCH for retransmitting the HARQ-ACK information is located; or

The terminal does not receive any DCI format scheduling HARQ-ACK which does not include the HARQ-ACK information for retransmission and transmits the HARQ-ACK in the time unit where the second PUCCH for retransmitting the HARQ-ACK information is located.

In some embodiments, the DAI of the HARQ-ACK information that triggered the retransmission is indicated, for example, by a DAI field in the DCI format.

In some embodiments, for example, a counting downlink assignment index (C-DAI) in a DCI format that is a downlink DCI format that triggers HARQ-ACK retransmission is counted separately from the DAI associated with the retransmitted HARQ-ACK information.

In some embodiments, the DAI of the HARQ-ACK information that triggered the retransmission is indicated, for example, by a total downlink assignment index (T-DAI) field in a DCI format that is a downlink DCI format.

In some embodiments, for example, if a DCI format triggering HARQ-ACK retransmission schedules transport block TB-based PDSCH reception, the DAI of the HARQ-ACK sub-codebook corresponding to TB-based PDSCH reception is determined based on the DAI field in the DCI format.

In some embodiments, for example, if the DCI format triggering HARQ-ACK retransmission schedules PDSCH reception based on a code block group CBG, the DAI of the HARQ-ACK sub-codebook corresponding to the CBG-based PDSCH reception is determined based on the DAI field in the DCI format.

According to some embodiments of the present disclosure, there is also provided a terminal. The terminal includes: a transceiver configured to transmit and receive a signal; and a controller coupled with the transceiver and configured to perform one or more operations of the above-described method performed by the terminal.

According to some embodiments of the present disclosure, there is also provided a base station. The base station includes: a transceiver configured to transmit and receive a signal; and a controller coupled with the transceiver and configured to perform one or more of the operations of the method described above as being performed by the base station.

There is also provided, in accordance with some embodiments of the present disclosure, a computer-readable storage medium, having one or more computer programs stored thereon, where the one or more computer programs, when executed by one or more processors, can implement any of the above-described methods.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings of the embodiments of the present disclosure will be briefly described below. It is to be expressly understood that the drawings described below are directed to only some embodiments of the disclosure and are not intended as a definition of the limits of the disclosure. In the drawings:

fig. 1 illustrates a schematic diagram of an example wireless network, in accordance with some embodiments of the present disclosure;

fig. 2A and 2B illustrate example wireless transmit and receive paths, according to some embodiments of the present disclosure;

fig. 3A illustrates an example User Equipment (UE) in accordance with some embodiments of the present disclosure;

fig. 3B illustrates an example gNB in accordance with some embodiments of the present disclosure;

figure 4 illustrates a block diagram of a second transceiving node, in accordance with some embodiments of the present disclosure;

fig. 5 illustrates a flow diagram of a method performed by a UE in accordance with some disclosed embodiments;

6A-6C illustrate some examples of uplink transmission timing according to some embodiments of the present disclosure;

fig. 7 illustrates an example of a first offset indicator (offset 1) according to some embodiments of the present disclosure;

fig. 8 illustrates an example of a second offset indicator (offset 2) according to some embodiments of the present disclosure;

9A-9F illustrate examples of dynamic HARQ-ACK codebook DAI counts according to some disclosed embodiments;

fig. 10 illustrates a flow diagram of a method performed by a terminal in accordance with some embodiments of the present disclosure;

figure 11 illustrates a block diagram of a first transceiving node, in accordance with some embodiments of the present disclosure;

figure 12 illustrates a block diagram of a first transceiving node, in accordance with some embodiments of the present disclosure; and

fig. 13 illustrates a flow chart of a method performed by a base station in accordance with some embodiments of the present disclosure.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present disclosure more apparent, the technical solutions of the embodiments of the present disclosure will be described clearly and completely with reference to the drawings of the embodiments of the present disclosure. It is to be understood that the described embodiments are only a few embodiments of the present disclosure, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the described embodiments of the disclosure without any inventive step, are within the scope of protection of the disclosure.

Before proceeding with the description of the specific embodiments below, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term "couple" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms "transmit," "receive," and "communicate," as well as derivatives thereof, encompass both direct and indirect communication. The terms "include" and "comprise," as well as derivatives thereof, mean inclusion without limitation. The term "or" is inclusive, meaning and/or. The phrase "associated with,. And its derivatives are intended to include, be included within, be connected to, be interconnected with, contain, be contained within, be connected to or be connected with, be coupled to or be coupled with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or be bound with, have,. Properties, have,. Relationships, or have relationships to. The term "controller" means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware, or in a combination of hardware and software and/or firmware. The functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. At least one of the phrases "when used with a list of items means that different combinations of one or more of the listed items may be used and only one item in the list may be required. For example, "at least one of a, B, and C" includes any one of the following combinations: A. b, C, A and B, A and C, B and C, and A, B and C. For example, "at least one of a, B, or C" includes any one of the following combinations: A. b, C, A and B, A and C, B and C, and A and B and C.

Furthermore, the various functions described below may be implemented or supported by one or more computer programs, each computer program formed from computer readable program code and embodied in a computer readable medium. The terms "application" and "program" refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in suitable computer-readable program code. The phrase "computer readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer readable medium" includes any type of medium capable of being accessed by a computer, such as Read-Only Memory (ROM), random Access Memory (RAM), a hard disk drive, a Compact Disc (CD), a Digital Video Disc (DVD), or any other type of Memory. A "non-transitory" computer-readable medium excludes wired, wireless, optical, or other communication links that transmit transitory electrical or other signals. Non-transitory computer-readable media include media that can permanently store data and media that can store and later rewrite data, such as a rewritable optical disk or an erasable memory device.

The terminology used herein to describe embodiments of the invention is not intended to limit and/or define the scope of the invention. For example, unless defined otherwise, technical or scientific terms used herein shall have the ordinary meaning as understood by those of ordinary skill in the art to which this invention belongs.

It should be understood that the use of "first," "second," and similar terms in the present disclosure are not intended to indicate any order, quantity, or importance, but rather are used to distinguish one element from another. The singular forms "a," "an," or "the" and similar referents do not denote a limitation of quantity, but rather denote the presence of at least one, unless the context clearly dictates otherwise.

As used herein, any reference to "one example" or "an example," "one embodiment," or "an embodiment" means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase "in one embodiment" or "in an example" in various places in the specification are not necessarily all referring to the same embodiment.

As used herein, a "portion of a thing" means "at least some of the thing" and thus may mean less than all of the thing or all of the thing. Thus, a "portion of a thing" includes the entire thing as a special case, i.e., the entire thing is an example of a portion of the thing.

As used herein, the term "set" means one or more. Thus, a collection of items may be a single item or a collection of two or more items.

In the present disclosure, in order to determine whether a specific condition is satisfied, expressions such as "greater than" or "less than" are used as examples, and expressions such as "greater than or equal to" or "less than or equal to" are also applicable and are not excluded. For example, a condition defined by "greater than or equal to" can be replaced with "greater than" or vice versa, a condition defined by "less than or equal to" can be replaced with "less than" or vice versa, and so forth.

It will be further understood that the terms "comprises" or "comprising," and the like, mean that the element or item identified as preceding the term, includes the element or item identified as following the term, and equivalents thereof, without excluding other elements or items. The terms "connected" or "coupled" and the like are not restricted to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "upper", "lower", "left", "right", and the like are used only to indicate relative positional relationships, and when the absolute position of the object being described is changed, the relative positional relationships may also be changed accordingly.

The various embodiments discussed below are illustrative only of the principles of the present disclosure in this patent document and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged wireless communication system. For example, although the following detailed description of embodiments of the present disclosure will be directed to LTE and 5G communication systems, those skilled in the art will appreciate that the primary gist of the present disclosure is also applicable, with slight modifications, to other communication systems having similar technical background and channel format without substantially departing from the scope of the present disclosure. The technical solution of the embodiment of the present application may be applied to various communication systems, for example, the communication system may include a global system for mobile communications (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a General Packet Radio Service (GPRS), a long term evolution (long term evolution) system, an LTE frequency division duplex (frequency division duplex, FDD) system, an LTE time division duplex (time division duplex, TDD), a universal mobile communication system (universal mobile communication system, UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) system, a fifth generation radio communication system (NR, 5), and the like. In addition, the technical scheme of the embodiment of the application can be applied to future-oriented communication technology. In addition, the technical scheme of the embodiment of the application can be applied to future-oriented communication technology.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that the same reference numerals in different figures will be used to refer to the same elements that have been described.

Fig. 1-3B below describe various embodiments implemented in a wireless communication system using Orthogonal Frequency Division Multiplexing (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA) communication techniques. The descriptions of fig. 1-3B are not meant to imply physical or architectural implications for the manner in which different embodiments may be implemented. The different embodiments of the present disclosure may be implemented in any suitably arranged communication system.

Fig. 1 illustrates an example wireless network 100 in accordance with some embodiments of the present disclosure. The embodiment of the wireless network 100 shown in fig. 1 is for illustration only. Other embodiments of wireless network 100 can be used without departing from the scope of this disclosure.

Wireless network 100 includes a gNodeB (gNB) 101, a gNB 102, and a gNB 103.gNB 101 communicates with gNB 102 and gNB 103. The 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.

Depending on the network type, other well-known terms can be used instead of "gnnodeb" or "gNB", such as "base station" or "access point". 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. Also, other well-known terms, such as "mobile station", "subscriber station", "remote terminal", "wireless terminal", or "user equipment", can be used instead of "user equipment" or "UE", depending on the network type. For example, the terms "terminal," "user equipment," and "UE" may be used in this patent document to refer to a remote wireless device that wirelessly accesses a gNB, whether the UE is a mobile device (such as a mobile phone or smartphone) or what is commonly considered a stationary device (such as a desktop computer or vending machine).

gNB 102 provides wireless broadband access to network 130 for a first plurality of User Equipments (UEs) within coverage area 120 of gNB 102. The first plurality of UEs comprises: a UE 111, which may be located in a Small Enterprise (SB); a UE 112, which may be located in an enterprise (E); UE 113, which may be located in a WiFi Hotspot (HS); a UE 114, which may be located in a first residence (R); a UE 115, which may be located in a second residence (R); the UE 116, may be a mobile device (M), such as a cellular phone, wireless laptop, wireless PDA, or the like. gNB 103 provides wireless broadband access to network 130 for a second plurality of UEs within coverage area 125 of gNB 103. The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more of the gNBs 101-103 can communicate with each other and with UEs 111-116 using 5G, long Term Evolution (LTE), LTE-A, wiMAX, or other advanced wireless communication technology.

The dashed lines illustrate the approximate extent of coverage areas 120 and 125, which are shown as approximately circular for purposes of illustration and explanation 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 artificial obstructions.

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 the present disclosure. In some embodiments, one or more of gNB 101, gNB 102, and gNB 103 support codebook design and structure for systems with 2D antenna arrays.

Although fig. 1 shows one example of a wireless network 100, various changes can be made to fig. 1. For example, wireless network 100 can include any number of gnbs and any number of UEs in any suitable arrangement. Also, the gNB 101 can communicate directly with any number of UEs and provide those UEs with wireless broadband access to the network 130. Similarly, each of gnbs 102-103 can communicate directly with network 130 and provide UEs direct wireless broadband access to network 130. Further, the 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.

Fig. 2A and 2B illustrate example wireless transmit and receive paths, according to some embodiments of the present disclosure. 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 the receive path 250 can be implemented in the gNB and the transmit path 200 can be implemented in the UE. In some embodiments, receive path 250 is configured to support codebook design and structure for systems with 2D antenna arrays as described in embodiments of the present disclosure.

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, an add cyclic prefix block 225, and an up-converter (UC) 230. Receive path 250 includes a down-converter (DC) 255, a remove cyclic prefix 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 decode and demodulation block 280.

In transmit path 200, a 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 with Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM), to generate a sequence of frequency domain modulation symbols. A serial-to-parallel (S-to-P) block 210 converts (such as demultiplexes) the serial modulation symbols into parallel data in order to generate N parallel symbol streams, where N is the number of IFFT/FFT points used in the gNB 102 and the 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 (such as multiplexes) the parallel time-domain output symbols from N-point IFFT block 215 to generate a serial time-domain signal. Add cyclic prefix block 225 inserts a cyclic prefix into the time domain signal. Upconverter 230 modulates (such as upconverts) the output of add cyclic prefix block 225 to an RF frequency for transmission over a wireless channel. The signal can also be filtered at baseband before being converted to RF frequency.

The RF signal transmitted from the gNB 102 reaches the UE 116 after passing through the radio channel, and the reverse operation to that at the gNB 102 is performed at the UE 116. Downconverter 255 downconverts the received signal to baseband frequency and remove cyclic prefix 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 to parallel time-domain signals. An 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 to a sequence of modulated data symbols. Channel decode and demodulation block 280 demodulates and decodes the modulated symbols to recover the original input data stream.

Each of the gnbs 101-103 may implement a transmit path 200 similar to transmitting to the UEs 111-116 in the downlink and may implement a receive path 250 similar to receiving from the UEs 111-116 in the uplink. Similarly, each of UEs 111-116 may implement a transmit path 200 for transmitting in the uplink to gnbs 101-103 and may implement a receive path 250 for receiving in the downlink from gnbs 101-103.

Each of the components in fig. 2A and 2B can be implemented using hardware only, or using a combination of hardware and software/firmware. As a particular example, at least some of the components in fig. 2A and 2B may be implemented in software, while other components may be implemented in configurable hardware or a mixture of software and configurable hardware. For example, FFT block 270 and IFFT block 215 may be implemented as configurable software algorithms, where the value of the number of points N may be modified depending on the implementation.

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

Although fig. 2A and 2B show examples of wireless transmission and reception paths, various changes may be made to fig. 2A and 2B. For example, the various components in fig. 2A and 2B can be combined, further subdivided, or omitted, and additional components can be added according to particular needs. Also, fig. 2A and 2B are intended to illustrate examples of the types of transmit and receive paths that can be used in a wireless network. Any other suitable architecture can be used to support wireless communications in a wireless network.

Fig. 3A illustrates an example UE 116 in accordance with some embodiments of the present disclosure. The embodiment of UE 116 shown in fig. 3A is for illustration only, and UEs 111-115 of fig. 1 can have the same or similar configurations. However, UEs have a wide variety of configurations, and fig. 3A does not limit the scope of the disclosure to any particular implementation of a UE.

The UE 116 includes an antenna 305, a Radio Frequency (RF) transceiver 310, transmit (TX) processing circuitry 315, a microphone 320, and Receive (RX) processing circuitry 325. The UE 116 also includes a speaker 330, a processor/controller 340, an input/output (I/O) interface 345, input device(s) 350, a display 355, and a memory 360. Memory 360 includes an Operating System (OS) 361 and one or more applications 362.

RF transceiver 310 receives incoming RF signals from antenna 305 that are transmitted by the gNB of wireless network 100. The RF transceiver 310 down-converts an incoming RF signal to generate an Intermediate Frequency (IF) or baseband signal. The IF or baseband signal is sent to RX processing circuitry 325, where RX processing circuitry 325 generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. RX processing circuit 325 sends the processed baseband signals to speaker 330 (such as for voice data) or to processor/controller 340 (such as for web browsing data) for further processing.

TX processing circuitry 315 receives analog or digital voice data from microphone 320 or other outgoing baseband data (such as network data, e-mail, or interactive video game data) from processor/controller 340. TX processing circuitry 315 encodes, multiplexes, and/or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceiver 310 receives the outgoing processed baseband or IF signal from TX processing circuitry 315 and upconverts the baseband or IF signal to an RF signal, which is transmitted via antenna 305.

The processor/controller 340 can include one or more processors or other processing devices and executes the OS 361 stored in the memory 360 in order to control overall operation of the UE 116. For example, processor/controller 340 may be capable of controlling the reception of forward channel signals and the transmission of reverse channel signals by RF transceiver 310, RX processing circuitry 325, and TX processing circuitry 315 in accordance with well-known principles. In some embodiments, processor/controller 340 includes at least one microprocessor or microcontroller.

The processor/controller 340 is also capable of executing other processes and programs resident in the memory 360, such as operations for channel quality measurement and reporting for systems having 2D antenna arrays as described in embodiments of the present disclosure. Processor/controller 340 is capable of moving data into and out of memory 360 as needed to perform a process. In some embodiments, processor/controller 340 is configured to execute applications 362 based on OS 361 or in response to signals received from the gNB or the operator. The processor/controller 340 is also coupled to an I/O interface 345, where the I/O interface 345 provides the UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. I/O interface 345 is the communication path between these accessories and processor/controller 340.

The processor/controller 340 is also coupled to input device(s) 350 and a display 355. The operator of the UE 116 can input data into the UE 116 using the input device(s) 350. Display 355 may be a liquid crystal display or other display capable of presenting text and/or at least limited graphics (such as from a website). A memory 360 is coupled to the processor/controller 340. A portion of memory 360 can include Random Access Memory (RAM) while another portion of memory 360 can include flash memory or other Read Only Memory (ROM).

Although fig. 3A shows one example of the UE 116, various changes can be made to fig. 3A. For example, the various components in FIG. 3A can be combined, further subdivided, or omitted, and additional components can be added according to particular needs. As a particular example, the processor/controller 340 can be divided into multiple processors, such as one or more Central Processing Units (CPUs) and one or more Graphics Processing Units (GPUs). Also, while fig. 3A shows the UE 116 configured as a mobile phone or smart phone, the UE can be configured to operate as other types of mobile or fixed devices.

Fig. 3B illustrates an example gNB 102, according to some embodiments of the present disclosure. The embodiment of the gNB 102 shown in fig. 3B is for illustration only, and the other gnbs of fig. 1 can have the same or similar configuration. However, the gNB has a wide variety of configurations, and fig. 3B does not limit the scope of the disclosure to any particular implementation of the gNB. Note that gNB 101 and gNB 103 can include the same or similar structure as gNB 102.

As shown in fig. 3B, the gNB 102 includes a plurality of antennas 370a-370n, a plurality of RF transceivers 372a-372n, transmit (TX) processing circuitry 374, and Receive (RX) processing circuitry 376. In some embodiments, one or more of the plurality of antennas 370a-370n comprises a 2D antenna array. The gNB 102 also includes a controller/processor 378, a memory 380, and a backhaul or network interface 382.

The RF transceivers 372a-372n receive incoming RF signals, such as signals transmitted by UEs or other gnbs, from the antennas 370a-370 n. RF transceivers 372a-372n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signal is sent to RX processing circuitry 376, where RX processing circuitry 376 generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. The RX processing circuit 376 sends the processed baseband signals to the controller/processor 378 for further processing.

TX processing circuitry 374 receives analog or digital data (such as voice data, network data, e-mail, or interactive video game data) from controller/processor 378. TX processing circuitry 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 signals from TX processing circuitry 374 and upconvert the baseband or IF signals into RF signals, which are transmitted via antennas 370a-370 n.

Controller/processor 378 can include one or more processors or other processing devices that control the overall operation of gNB 102. For example, the controller/processor 378 can control the reception of forward channel signals and the transmission of reverse channel signals through the RF transceivers 372a-372n, RX processing circuitry 376, and TX processing circuitry 374 according to well-known principles. The controller/processor 378 can also support additional functions, such as higher-level wireless communication functions. For example, the controller/processor 378 can perform a Blind Interference Sensing (BIS) process, such as by performing a BIS algorithm, and decode the received signal with the interference signal subtracted. Controller/processor 378 may support any of a wide variety of other functions in the gNB 102. In some embodiments, controller/processor 378 includes at least one microprocessor or microcontroller.

Controller/processor 378 is also capable of executing programs and other processes resident in memory 380, such as a base OS. Controller/processor 378 can also support channel quality measurement and reporting for systems with 2D antenna arrays as described in embodiments of the present disclosure. In some embodiments, controller/processor 378 supports communication between entities such as a web RTC. Controller/processor 378 can move data into and out of memory 380 as needed to perform a process.

Controller/processor 378 is also coupled to a backhaul or network interface 382. Backhaul or network interface 382 allows gNB 102 to communicate with other devices or systems over a backhaul connection or over a network. Backhaul or network interface 382 can support 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 one supporting 5G or new radio access technologies or NR, LTE or LTE-a), the backhaul or network interface 382 can allow the gNB 102 to communicate with other gnbs over wired or wireless backhaul connections. When gNB 102 is implemented as an access point, backhaul or network interface 382 can allow gNB 102 to communicate with a larger network (such as the internet) through a wired or wireless local area network or through a wired or wireless connection. Backhaul or network interface 382 includes any suitable structure that supports communication over a wired or wireless connection, such as an ethernet or RF transceiver.

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

As described in more detail below, the transmit and receive paths of 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.

Although fig. 3B shows one example of a gNB 102, various changes may be made to fig. 3B. For example, the gNB 102 can include any number of each of the components shown in fig. 3A. As a particular example, the access point can include a number of backhauls or network interfaces 382 and the controller/processor 378 can support routing functions to route data between different network addresses. As another particular example, although shown as including a single instance of TX processing circuitry 374 and a single instance of RX processing circuitry 376, gNB 102 can include multiple instances of each (such as one for each RF transceiver).

As will be understood by those skilled in the art, the term "terminal" as used herein includes both wireless signal receiver devices, which include only wireless signal receiver devices without transmission capability, and receiving and transmitting hardware devices, which include hardware devices capable of receiving and transmitting bi-directional communications over a bi-directional communications link. Such a device may include: a cellular or other communication device having a single line display or a multi-line display or a cellular or other communication device without a multi-line display; a PCS (personal communications System), which may combine voice, data processing, facsimile and/or data communications capabilities; a PDA (personal digital assistant) which may include a radio frequency receiver, pager, internet/intranet access, web browser, notepad, calendar and/or GPS (global positioning system) receiver; a conventional laptop and/or palmtop computer or other appliance having and/or including a radio frequency receiver. As used herein, a "terminal" or "terminal device" may be portable, transportable, installed in a vehicle (aeronautical, maritime, and/or land-based), or situated and/or configured to operate locally and/or in a distributed fashion at any other location(s) on earth and/or in space. As used herein, a "terminal" and a "terminal device" may also be a communication terminal, a web terminal, and a music/video playing terminal, such as a PDA, an MID (mobile internet device) and/or a mobile phone with music/video playing function, and may also be a smart tv, a set-top box, and the like.

Exemplary embodiments of the present disclosure are further described below in conjunction with the appended drawings.

With the rapid development of the information industry, especially the growing demand from the mobile internet and internet of things (IoT), the future mobile communication technology is challenged with unprecedented challenges. As reported by the International Telecommunications Union (ITU) in ITU-R M. [ imt. Beyond 2020.Traffic ], it is expected that by 2020, the mobile traffic will increase nearly 1000 times and the number of UE connections will also exceed 170 billion compared to 2010 (4G era), and the number of connected devices will be more dramatic as the vast number of IoT devices gradually permeates into the mobile communication network. To address this unprecedented challenge, the communications industry and academia have developed extensive fifth generation mobile communications technology (5G) research to target the 2020. Future 5G frameworks and overall goals are currently discussed in ITU's report ITU-R M. [ imt.vision ], where the 5G demand landscape, application scenarios and various important performance indicators are specified. For the new requirements in 5G, ITU's report ITU-R M [ imt. Use TECHNOLOGY trend trees ] provides information related to the technical trend of 5G, and aims to solve the significant problems of significant improvement of system throughput, consistency of user experience, and extensibility to support IoT, delay, energy efficiency, cost, network flexibility, support of emerging services, flexible spectrum utilization, and the like. In 3GPP (3 rd Generation Partnership Project), the first phase of work for 5G has been ongoing. To support more flexible scheduling, the 3GPP decides to support variable Hybrid Automatic Repeat request-Acknowledgement (HARQ-ACK) feedback latency in 5G. In an existing Long Term Evolution (LTE) system, an uplink transmission Time of receiving HARQ-ACK from downlink data is fixed, for example, in a Frequency Division Duplex (FDD) system, a Time delay is 4 subframes, and in a Time Division Duplex (TDD) system, an HARQ-ACK feedback Time delay is determined for a corresponding downlink subframe according to uplink and downlink configuration. In a 5G system, whether FDD or TDD, the uplink time unit for which HARQ-ACK can be fed back is variable for a certain downlink time unit (e.g., downlink timeslot or downlink mini-timeslot). For example, the HARQ-ACK feedback delay may be dynamically indicated through physical layer signaling, or different HARQ-ACK delays may be determined according to different services or user capabilities and other factors.

The 3GPP defines three major directions of 5G application scenarios — eMBB (enhanced mobile broadband), mtc (massive machine-type communication), URLLC (ultra-reliable and low-latency communication). The eMBB scene aims to further improve the data transmission rate on the basis of the existing mobile broadband service scene so as to improve the user experience, and thus the extremely communication experience between people is pursued. mtc and URLLC are application scenarios such as internet of things, but the respective emphasis points are different: mMTC is mainly information interaction between people and objects, and URLLC mainly embodies the communication requirements between the objects.

In 5G, HARQ-ACK information may be cancelled for various reasons. In order to avoid downlink data retransmission, the HARQ-ACK information which is not sent may be retransmitted. In this case, it needs to be considered how to indicate retransmission of HARQ-ACK information. In addition, a HARQ-ACK codebook considering how to generate retransmitted HARQ-ACK information is required.

In order to solve at least the above technical problems, embodiments of the present disclosure provide a method performed by a terminal, a method performed by a base station, and a non-transitory computer-readable storage medium in a wireless communication system. Hereinafter, various embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

In the embodiments of the present disclosure, for convenience of description, a first transceiving node and a second transceiving node are defined. For example, the first transceiving node may be a base station and the second transceiving node may be a UE. In the following examples, the first transceiving node is illustrated by taking a base station as an example (but not limited to), and the second transceiving node is illustrated by taking a UE as an example (but not limited to).

Exemplary embodiments of the present disclosure are further described below in conjunction with the appended drawings.

The text and drawings are provided as examples only to assist the reader in understanding the disclosure. They are not intended, nor should they be construed, as limiting the scope of the disclosure in any way. While certain embodiments and examples have been provided, it will be apparent to those skilled in the art, based on the disclosure herein, that changes can be made in the embodiments and examples shown without departing from the scope of the disclosure.

Fig. 4 shows a block diagram of a second transceiving node according to an embodiment of the present disclosure.

Referring to fig. 4, a second transceiving node 400 may comprise a transceiver 401 and a controller 402.

The transceiver 401 may be configured to receive first data and/or first control signaling from a first transceiving node and to transmit second data and/or second control signaling to the first transceiving node at a determined time unit.

The controller 402 may be an application specific integrated circuit or at least one processor. The controller 402 may be configured to control the overall operation of the second transceiving node, and to control the second transceiving node to implement the methods set forth in embodiments of the present disclosure. For example, the controller 402 may be configured to determine second data and/or second control signaling and a time unit for transmitting the second data and/or second control signaling based on the first data and/or first control signaling, and to control the transceiver 401 to transmit the second data and/or second control signaling to the first transceiving node at the determined time unit.

In some implementations, the controller 402 may be configured to perform one or more of the operations of the methods of the various embodiments described below. For example, the controller 402 may be configured to perform one or more of the operations of the method 500 to be described later in connection with fig. 5, the method 1000 to be described in connection with fig. 10.

In some embodiments, the first data may be data transmitted by the first transceiving node to the second transceiving node. In the following examples, the first data is exemplified by (but not limited to) Downlink data carried by a PDSCH (Physical Downlink Shared Channel).

In some embodiments, the second data may be data transmitted by the second transceiving node to the first transceiving node. In the following examples, the second data is exemplified by (but not limited to) Uplink data carried by a PUSCH (Physical Uplink Shared Channel).

In some embodiments, the first control signalling may be control signalling sent by the first transceiving node to the second transceiving node. In the following examples, the first control signaling is illustrated by taking the downlink control signaling as an example (but not limited to). The Downlink Control signaling may be DCI (Downlink Control information) carried by a PDCCH (Physical Downlink Control Channel) and/or Control signaling carried by a PDSCH (Physical Downlink Shared Channel). For example, the DCI may be UE specific DCI, the DCI may also be common DCI, the common DCI may be DCI common to some UEs, for example, group common DCI, and the common DCI may also be DCI common to all UEs. The DCI may be an uplink DCI (e.g., a DCI scheduling a PUSCH) and/or a downlink DCI (e.g., a DCI scheduling a PDSCH).

In some embodiments, the second control signalling may be control signalling sent by the second transceiving node to the first transceiving node. In the following example, the second control signaling is illustrated by taking the uplink control signaling as an example (but not limited to). The Uplink Control signaling may be UCI (Uplink Control Information) carried through a PUCCH (Physical Uplink Control Channel) and/or Control signaling carried through PUSCH (Physical Uplink Shared Channel). The type of UCI may include one or more of the following: HARQ-ACK Information, SR (Scheduling Request), LRR (Link Recovery Request), CSI (channel State Information), or CG (Configured grant) UCI. In an embodiment of the present disclosure, when UCI is carried by PUCCH, UCI may be used interchangeably with PUCCH.

In some embodiments, the PUCCH carrying the SR may be a PUCCH carrying a positive SR (positive SR) and/or a negative SR (negative SR). The SR may be a positive SR and/or a negative SR.

In some embodiments, the CSI may also be Part 1CSI (first-Part CSI) and/or Part 2CSI (second-Part CSI).

In some embodiments, the first time unit is a time unit in which the first transceiving node transmits the first data and/or the first control signaling. In the following examples, the first time unit is illustrated by taking the following line time unit as an example (but not limited to).

In some embodiments, the second time unit is a time unit in which the second transceiving node transmits the second data and/or the second control signaling. In the following example, the second time unit is illustrated by taking the upper line time unit as an example (but not limited to).

In some embodiments, the first time unit and the second time unit may be one or more slots (slots), one or more sub-slots (sub-slots), one or more OFDM (Orthogonal Frequency Division Multiplexing) symbols, or one or more subframes (subframes).

Herein, depending on the network type, the term "base station" or "BS" may refer to any component (or collection of components) configured to provide wireless access to the network, such as a Transmission Point (TP), a Transmission and Reception Point (TRP), an enhanced base station (eNodeB or eNB), a 5G base station (gNB), a macrocell, a femtocell, a WiFi Access Point (AP), or other wirelessly enabled device. The base station may provide wireless access according to one or more wireless communication protocols, e.g., 5G 3GPP new radio interface/access (NR), long Term Evolution (LTE), LTE-advanced (LTE-A), high Speed Packet Access (HSPA), wi-Fi 802.11a/b/g/n/ac, etc.

In describing the wireless communication system and in the present disclosure described below, higher layer signaling or higher layer signals are signal transfer methods for transferring information from a base station to a terminal through a downlink data channel of a physical layer or transferring information from a terminal to a base station through an uplink data channel of a physical layer, and examples of the signal transfer methods may include signal transfer methods for transferring information through Radio Resource Control (RRC) signaling, packet Data Convergence Protocol (PDCP) signaling, or Medium Access Control (MAC) control element (MAC control element).

Fig. 5 shows a flow diagram of a method performed by a UE in accordance with an embodiment of the present disclosure.

Referring to fig. 5, in step S510, the UE may receive downlink data (e.g., downlink data carried by the PDSCH) and/or downlink control signaling from the base station. For example, the UE may receive downlink data and/or downlink control signaling from the base station based on predefined rules and/or already received configuration parameters.

In step S520, the UE determines uplink data and/or uplink control signaling and an uplink time unit according to the downlink data and/or downlink control signaling.

In step S530, the UE transmits uplink data and/or uplink control signaling to the base station in uplink time unit.

In some embodiments, acknowledgement/negative acknowledgement (ACK/NACK) for downlink transmissions may be performed by HARQ-ACK.

In some embodiments, the downlink control signaling may include DCI carried over a PDCCH and/or control signaling carried over a PDSCH. For example, the DCI may be used to schedule transmission of a PUSCH or reception of a PDSCH. Some examples of uplink transmission timing will be described below with reference to fig. 6A-6C.

In one example, the UE receives DCI and receives PDSCH according to time domain resources indicated in the DCI. For example, the parameter K0 may be used to indicate a time interval between a DCI-scheduled PDSCH and a DCI-carrying PDCCH, and the unit of K0 may be a time slot. For example, fig. 6A gives an example of K0= 1. In the example shown in fig. 6A, the time interval from the DCI scheduled PDSCH to the PDCCH carrying the DCI is 1 slot. In an embodiment of the present disclosure, "the UE receives the DCI" may mean "the UE detects the DCI".

In another example, the UE receives DCI and transmits PUSCH according to time domain resources indicated in the DCI. For example, a time interval between a PUSCH for DCI scheduling and a PDCCH carrying DCI may be represented using a parameter K2, and a unit of K2 may be a slot. For example, fig. 6B gives an example of K2= 1. In the example shown in fig. 6B, the time interval between the PUSCH scheduled by the DCI and the PDCCH carrying the DCI is 1 slot. K2 may also represent a time interval of a PDCCH activating a CG (configured grant) PUSCH and a CG PUSCH first activated. In examples of the present disclosure, the PUSCH may be a dynamically scheduled (e.g., DCI scheduled) PUSCH (e.g., may be referred to as DG (dynamic grant) PUSCH in embodiments of the present disclosure) and/or a PUSCH that is not DCI scheduled (e.g., CG PUSCH), if not specifically stated.

In yet another example, the UE receives the PDSCH and may transmit HARQ-ACK information for the PDSCH reception on the PUCCH in the uplink time unit. For example, a timing parameter (also referred to as a timing value) K1 (e.g., 3GPP parameter dl-DataToUL-ACK) may be used to indicate a time interval between a PUCCH for transmitting HARQ-ACK information received by a PDSCH and the PDSCH, and a unit of K1 may be an uplink time unit such as a slot or a sub-slot. In the case where the unit of K1 is a slot, the time interval is a slot offset value of the PUCCH for feeding back HARQ-ACK information received by the PDSCH and the PDSCH, and K1 may be referred to as a slot timing value. For example, fig. 6A gives an example of K1= 3. In the example shown in fig. 6A, the PUCCH for transmitting HARQ-ACK information received by the PDSCH is 3 slots apart from the PDSCH. It should be noted that, in the embodiment of the disclosure, the timing parameter K1 may be the same as the timing parameter K ₁ Used interchangeably, the timing parameter K0 may be the same as the timing parameter K ₀ Used interchangeably, the timing parameter K2 may be the same as the timing parameter K ₂ Are used interchangeably.

The PDSCH may be a DCI scheduled PDSCH and/or an SPS PDSCH. After the SPS PDSCH is activated by the DCI, the UE may periodically receive the SPS PDSCH. In examples of the present disclosure, the SPS PDSCH may be equivalent to a PDSCH without DCI/PDCCH scheduling. After the SPS PDSCH is released (deactivated), the UE no longer receives the SPS PDSCH.

The HARQ-ACK in embodiments of the present disclosure may be a HARQ-ACK received for an SPS PDSCH (e.g., a HARQ-ACK without DCI indication) and/or a HARQ-ACK indicated by one DCI format (e.g., a HARQ-ACK received for a PDSCH scheduled by one DCI format).

In yet another example, the UE receives DCI (e.g., DCI indicating SPS (Semi-Persistent Scheduling) PDSCH release (deactivation)), and may transmit HARQ-ACK information of the DCI on a PUCCH of an uplink time unit. For example, a time interval between a PUCCH for transmitting HARQ-ACK information of DCI and the DCI may be represented using a timing parameter K1, and the unit of K1 may be an uplink time unit such as a slot or a sub-slot. For example, fig. 6C gives an example of K1= 3. In the example of fig. 6C, the time interval between the PUCCH for transmitting HARQ-ACK information of DCI and the DCI is 3 slots. For example, the parameter K1 may be used to indicate the time interval between PDCCH reception carrying DCI indicating SPS PDSCH release (deactivation) and PUCCH whose HARQ-ACK is fed back.

In some embodiments, in step S520, the UE may report (or send (signal/transmit)) the UE capability to the base station or indicate the UE capability. For example, the UE reports (or sends) the UE capability to the base station by sending a PUSCH. In this case, the PUSCH transmitted by the UE includes UE capability information.

In some embodiments, the base station may configure the UE with higher layer signaling based on the UE capabilities previously received from the UE (e.g., in step S510 of a previous downlink-uplink transmission procedure). For example, the base station configures higher layer signaling for the UE by sending PDSCH. In this case, the PDSCH transmitted by the base station includes higher layer signaling configured for the UE. It should be noted that the higher layer signaling is higher layer signaling compared to physical layer signaling, for example, the higher layer signaling may include RRC signaling and/or MAC CE.

In some embodiments, the downlink channel (downlink resource) may include a PDCCH and/or a PDSCH. The uplink channel (uplink resource) may include PUCCH and/or PUSCH.

In some embodiments, the UE may be configured with two levels of priority for uplink transmissions. For example, the UE may be configured to multiplex UCI of different priorities by higher layer signaling (e.g., by 3GPP parameter UCI-muxwithdiffferentpriority); otherwise (e.g., if the UE is not configured to multiplex UCI of different priorities), the UE prioritizes PUCCH and/or PUSCH of different priorities (prioritization). For example, the two levels of priority may include a first priority and a second priority that are different from each other. In one example, the first priority may be higher than the second priority, i.e., the first priority is a higher priority and the second priority is a lower priority. In another example, the first priority may be lower than the second priority. However, embodiments of the present disclosure are not limited thereto, e.g., the UE may be configured with more than two levels of priority. For convenience, in the embodiments of the present disclosure, the description is made in consideration of the first priority being higher than the second priority. It should be noted that all embodiments of the present disclosure are applicable to the case that the first priority may be higher than the second priority; all embodiments of the present disclosure are applicable to situations where the first priority may be lower than the second priority; all embodiments of the disclosure are applicable to the case where the first priority may be equal to the second priority.

In some examples, multiplexing multiple uplink transmissions (e.g., PUCCH and/or PUSCH) with overlap in the time domain may be to multiplex UCI information in the PUCCH into one PUCCH or PUSCH.

In some examples, prioritizing, by the UE, two uplink transmissions (e.g., PUCCH and/or PUSCH) that overlap in the time domain may include the UE sending a higher priority uplink transmission (e.g., PUCCH or PUSCH) and the UE not sending a lower priority uplink transmission (PUCCH or PUSCH).

In some embodiments, the UE may be configured for sub-slot (subslot) based PUCCH transmission. For example, a sub-slot length parameter (which may also be referred to as a parameter related to a sub-slot length in the embodiment of the present disclosure) of each of the first PUCCH configuration parameter and the second PUCCH configuration parameter (e.g., a parameter subslotlengthporpucch in 3 GPP) may be 7 OFDM symbols, or 6 OFDM symbols, or 2 OFDM symbols. The sub-slot configuration length parameters in different PUCCH configuration parameters may be configured separately. If the sub-slot length parameter is not configured in one PUCCH configuration parameter, the scheduling time unit of the PUCCH configuration parameter is defaulted to be one slot. If a sub-slot length parameter is configured in one PUCCH configuration parameter, the scheduling time unit of this PUCCH configuration parameter is L (L is the configured sub-slot configuration length) OFDM symbols.

The mechanism of the PUCCH transmission based on the slot and the PUCCH transmission based on the sub-slot is basically the same, and in the present disclosure, a PUCCH opportunity (occast) unit may be represented by a slot (slot); for example, if the UE is configured with subslots, the slot that is a PUCCH occasion unit may be replaced with a subslot. For example, it may be specified by the protocol that if the UE is configured with a sub-slot length parameter (e.g., 3GPP parameter subslotlengthporpucch), unless otherwise specified, the number of symbols contained in the slot of the PUCCH transmission is indicated by the sub-slot length parameter.

For example, if the UE is configured with a sub-slot length parameter, and the sub-slot n is the last uplink sub-slot that overlaps with PDSCH reception or PDCCH reception (e.g., indicating SPS PDSCH release, and/or indicating secondary cell dormancy, and/or triggering type-3 HARQ-ACK codebook reporting without scheduling PDSCH reception), HARQ-ACK information for that PDSCH reception or PDCCH reception is sent in uplink sub-slot n + K, where K is determined by a timing parameter K1 (with respect to the definition of timing parameter K1, it may refer to the previous description). For another example, if the UE is not configured with the sub-slot length parameter, and the time slot n is the last uplink time slot overlapped with the downlink time slot where the PDSCH reception or the PDCCH reception is located, the HARQ-ACK information received by the PDSCH reception or the PDCCH is sent in the uplink time slot n + K, where K is determined by the timing parameter K1.

In the embodiments of the present disclosure, unicast may refer to a manner in which a network communicates with one UE, and multicast/broadcast may refer to a manner in which a network communicates with a plurality of UEs. For example, the unicast PDSCH may be one PDSCH received by one UE, and the scrambling of the PDSCH may be based on a Radio Network Temporary Identifier (RNTI) unique to the UE, such as a cell-RNTI (C-RNTI). The multicast/broadcast PDSCH may be one PDSCH received simultaneously by more than one UE, and the scrambling of the multicast/broadcast PDSCH may be based on an RNTI common to the group of UEs. For example, the RNTI common to the scrambled UE group for the multicast/broadcast PDSCH may include an RNTI (referred to as a G-RNTI in embodiments of the present disclosure) scrambled for a dynamically scheduled multicast/broadcast transmission (e.g., PDSCH) or an RNTI (referred to as a G-CS-RNTI in embodiments of the present disclosure) scrambled for a multicast/broadcast SPS transmission (e.g., SPS PDSCH). The G-CS-RNTI and the G-RNTI can be different RNTIs or the same RNTI. The UCI of the unicast PDSCH may include HARQ-ACK information, SR, or CSI of the unicast PDSCH. UCI of multicast (groupcast or multicast)/broadcast PDSCH may include HARQ-ACK information of multicast/broadcast PDSCH. In an embodiment of the present disclosure, "multicast/broadcast" may refer to at least one of multicast or broadcast.

In some embodiments, the HARQ-ACK codebook may include HARQ-ACK information for one or more PDSCHs and/or DCIs. If the HARQ-ACK information of one or more PDSCHs and/or DCIs is transmitted in the same uplink time unit, the UE may generate a HARQ-ACK codebook according to a predefined rule. For example, if one PDSCH is successfully decoded, the HARQ-ACK information of this PDSCH is positive ACK. For example, a positive ACK may be represented by 1 in the HARQ-ACK codebook. If one PDSCH is not successfully decoded, the HARQ-ACK information of this PDSCH is Negative ACK (Negative ACK). For example, NACK may be represented by 0 in the HARQ-ACK codebook. For example, the UE may generate the HARQ-ACK codebook according to a pseudo-code specified by a protocol. In one example, if the UE receives a DCI format indicating SPS PDSCH release (deactivation), the UE transmits HARQ-ACK information (ACK) for the DCI format. In another example, if the UE receives a DCI format indicating that a secondary cell is dormant, the UE transmits HARQ-ACK information (ACK) for the DCI format. In yet another example, if the UE receives a DCI format indicating transmission of HARQ-ACK information for all HARQ-ACK processes for all configured serving cells (e.g., type-3 HARQ-ACK codebook (Type-3 HARQ-ACK codebook) in 3 GPP), the UE transmits HARQ-ACK information for all HARQ-ACK processes for all configured serving cells. To reduce the size of the type-3 HARQ-ACK codebook, in the enhanced type-3 HARQ-ACK codebook, the UE may transmit HARQ-ACK information for a specific HARQ-ACK process of a specific serving cell based on the indication of the DCI. In yet another example, if the UE receives a DCI format, wherein the DCI format schedules a PDSCH, the UE transmits HARQ-ACK information for the PDSCH. In yet another example, the UE receives the SPS PDSCH, and the UE transmits HARQ-ACK information for the SPS PDSCH. In yet another example, if the UE is configured by higher layer signaling to receive the SPS PDSCH, the UE transmits HARQ-ACK information for the SPS PDSCH. Receiving the SPS PDSCH configured by higher layer signaling may be cancelled by other signaling. In yet another example, the UE does not receive the SPS PDSCH if at least one uplink symbol (e.g., OFDM symbol) in the semi-static frame structure in which the UE is configured by higher layer signaling overlaps a symbol of the SPS PDSCH. In yet another example, if the UE is configured by higher layer signaling to receive the SPS PDSCH according to a predefined rule, the UE transmits HARQ-ACK information for the SPS PDSCH. It should be noted that, in the embodiments of the present disclosure, the overlapping of "a" and "B" may mean that "a" and "B" at least partially overlap. That is, the overlapping of "a" and "B" includes the case where "a" and "B" completely overlap.

In some embodiments, the UE may generate HARQ-ACK information according to a rule that yields an SPS PDSCH HARQ-ACK codebook if the HARQ-ACK information transmitted for the same uplink time unit does not include HARQ-ACK information for any DCI format, does not include dynamically scheduled PDSCH (e.g., PDSCH scheduled by DCI format) and/or DCI HARQ-ACK information, or the HARQ-ACK information transmitted for the same uplink time unit includes only HARQ-ACK information for one or more SPS PDSCHs.

In some embodiments, if the HARQ-ACK information transmitted for the same uplink time unit includes DCI format HARQ-ACK information, and/or a dynamically scheduled PDSCH (e.g., a PDSCH scheduled by a DCI format), the UE may generate the HARQ-ACK information according to a rule that produces the dynamically scheduled PDSCH and/or DCI format HARQ-ACK codebook. For example, the UE may determine to generate a semi-static HARQ-ACK Codebook (e.g., type-1 HARQ-ACK Codebook (Type-1 HARQ-ACK Codebook) in 3 GPP) or a dynamic HARQ-ACK Codebook (e.g., type-2 HARQ-ACK Codebook (Type-2 HARQ-ACK Codebook) in 3 GPP) according to the PDSCH HARQ-ACK Codebook configuration parameters (e.g., parameter PDSCH-HARQ-ACK-Codebook in 3 GPP).

In some embodiments, if the HARQ-ACK information transmitted for the same uplink time unit includes only HARQ-ACK information for an SPS PDSCH (e.g., a PDSCH not scheduled by a DCI format), the UE may generate a HARQ-ACK codebook according to a rule that yields the HARQ-ACK codebook for the SPS PDSCH (e.g., a pseudo code of a codebook that generates HARQ-ACK for the SPS PDSCH as defined in 3 GPP).

In some embodiments, the dynamic HARQ-ACK codebook and/or the enhanced dynamic HARQ-ACK codebook may determine the size and ordering of the HARQ-ACK codebook according to the allocation index. For example, the allocation Index may be DAI (Downlink Assignment Index). In the following embodiments, the allocation index is described as DAI as an example. However, embodiments of the present disclosure are not so limited, and any other suitable allocation index may be employed.

In some embodiments, the DAI field includes at least one of a first DAI and a second DAI.

In some examples, the first DAI may be a C-DAI (Counter-DAI). The first DAI may indicate a cumulative count of at least one of a DCI for a scheduled PDSCH, or a DCI for SPS PDSCH release (deactivation), or a DCI for secondary cell dormancy. For example, the cumulative count may be a cumulative count to the current serving cell and/or the current time unit. For example, C-DAI may refer to: the cumulative number of { serving cell, time unit } pairs scheduled by the PDCCH until the current time unit within the time window (which may also include the number of PDCCHs (e.g., PDCCH indicating SPS release, and/or PDCCH indicating secondary cell dormancy); or the cumulative number of PDCCHs until the current time unit; or the cumulative number of PDSCH transmissions until the current time unit; or the cumulative number of { serving cell, time unit } pairs for which there is PDSCH transmission related to the PDCCH (e.g., scheduled by the PDCCH) and/or for which there is a PDCCH (e.g., a PDCCH indicating SPS release, and/or a PDCCH indicating secondary cell dormancy) until the current serving cell and/or current time unit; or the cumulative number of PDSCHs and/or PDCCHs (e.g., PDCCHs indicating SPS release, and/or PDCCHs indicating secondary cell dormancy) for which the corresponding PDCCH exists, which have been scheduled by the base station, to the current serving cell and/or the current time unit; or the cumulative number of PDSCHs scheduled by the base station to the current serving cell and/or the current time unit (the PDSCH is the PDSCH with the corresponding PDCCH); or the cumulative number of time units with PDSCH transmission scheduled by the base station to the current serving cell and/or the current time unit (the PDSCH is the PDSCH with the corresponding PDCCH). The ordering of bits in the HARQ-ACK codebook corresponding to at least one of PDSCH reception, DCI indicating SPS PDSCH release (deactivation), or DCI indicating secondary cell dormancy may be determined by receiving the time including the first DAI and the first DAI information. The first DAI may be included in a downlink DCI format.

In some examples, the second DAI may be a T-DAI (Total-DAI, total DAI). The second DAI may indicate a total count of at least one of all PDSCH receptions, DCI indicating SPS PDSCH release (deactivation), or DCI indicating secondary cell dormancy. For example, the total count may be the total count of all serving cells to the current time unit. For example, T-DAI may refer to: a total number of { serving cell, time unit } pairs scheduled by the PDCCH until the current time unit within the time window (the number of PDCCHs to indicate SPS release may also be included); or the total number of PDSCH transmissions until the current time unit; or a total number of { serving cell, time unit } pairs for which there is a PDSCH transmission related to the PDCCH (e.g., scheduled by the PDCCH) and/or for which there is a PDCCH (e.g., a PDCCH indicating SPS release, and/or a PDCCH indicating secondary cell dormancy) by the current serving cell and/or current time unit; or the total number of PDSCHs and/or PDCCHs (e.g., PDCCHs indicating SPS release, and/or PDCCHs indicating secondary cell dormancy) for which the corresponding PDCCH exists that have been scheduled by the base station by the current serving cell and/or current time unit; or the total number of PDSCHs scheduled by the base station to the current serving cell and/or the current time unit (the PDSCHs are the PDSCHs with the corresponding PDCCH); or the total number of time units in which there is PDSCH transmission scheduled by the base station to the current serving cell and/or the current time unit (e.g., the PDSCH is the PDSCH in which the corresponding PDCCH exists). The second DAI may be included in the downlink DCI format and/or the uplink DCI format. The second DAI included in the uplink DCI format is also referred to as an UL DAI.

In the following example, the first DAI is illustrated as being C-DAI and the second DAI is T-DAI, but not limited thereto.

Tables 1 and 2 show the DAI wordSegment and V _T-DAI，m Or V _{C-DAI，c，m} Or

The corresponding relationship of (1). The number of bits of the C-DAI and T-DAI is limited.

For example, in the case where the C-DAI or T-DAI is expressed with 2 bits, the value of the C-DAI or T-DAI in the DCI may be determined by the formula in Table 1. V _T-DAI，m Or

V is the value of T-DAI in DCI received at PDCCH listening opportunity (MO) m _{C-DAI，c，m} Is the value of C-DAI in DCI for serving cell C received at PDCCH listening occasion m. V _T-DAI，m And V _{C-DAI，c，m} Is related to the number of bits of the DAI field in the DCI. MSB is the Most Significant Bit (Most Significant Bit), and LSB is the Least Significant Bit (Least Significant Bit).

[ Table 1]

For example, if C-DAI or T-DAI is 1, 5 or 9, as shown in Table 1, each is indicated by "00" in the DAI field, and V is expressed by the formula in Table 1 _T-DAI，m Or V _{C-DAI，c，m} The value of (d) is represented as "1". Y may represent a value of DAI (a value of DAI before conversion by a formula in a table) corresponding to the number of DCIs actually transmitted by the base station.

For example, in the case where C-DAI or T-DAI in DCI is 1 bit, a value greater than 2 may be represented by the formula in Table 2.

[ Table 2]

It should be noted that, unless the context clearly dictates otherwise, all or one or more of the methods, steps or operations described by the embodiments of the present disclosure may be configured and/or indicated by protocol provisions and/or higher layer signaling. The dynamic signaling may be PDCCH and/or DCI format. For example, for SPS PDSCH and/or CG PUSCH, the indication may be dynamically indicated in its activation DCI/DCI format/PDCCH. All or one or more of the described methods, steps and operations may be optional. For example, if a certain parameter (e.g., parameter X) is configured, the UE performs a certain mode (e.g., mode a), otherwise (if the parameter, e.g., parameter X, is not configured), the UE performs another mode (e.g., mode B).

It should be noted that PCell (primary Cell) or PSCell (primary secondary Cell) in the embodiments of the present disclosure may be used interchangeably with Cell (Cell) having PUCCH.

It should be noted that the method for the downlink in the embodiment of the present disclosure may also be applied to the uplink, and the method for the uplink may also be applied to the downlink. For example, PDSCH may be replaced with PUSCH, SPS PDSCH with CG PUSCH, and downlink symbol may be replaced with uplink symbol, so that the method for downlink may be applied to uplink.

It should be noted that the method applied to scheduling multiple PDSCH/PUSCH in the embodiment of the present disclosure may also be applied to PDSCH/PUSCH repeated transmission. For example, one PDSCH/PUSCH of a plurality of PDSCH/PUSCH may be replaced with one of a plurality of repeated PDSCH/PUSCH transmissions.

It should be noted that in the method of the present disclosure, the number of times that the repeated transmission is configured and/or indicated may be understood as the repeated transmission is greater than 1. For example, a PUCCH that is "configured and/or indicated for repeated transmission" may be replaced with a "PUCCH that is repeatedly transmitted on more than one slot/sub-slot. Not configured and/or indicating that the repeated transmission may be understood as a number of repeated transmissions equal to 1. E.g. PUC "not configured and/or indicating repeated transmissionCH "may be replaced with" PUCCH transmission with repetition transmission number of 1". For example, the UE may be configured with a parameter related to the number of PUCCH repetition transmissions

When the parameter is->

Greater than 1, it may mean that the UE is configured with PUCCH repeat transmissions and the UE may be ≧ H>

Repeat PUCCH transmissions over a time unit (e.g., slot); when the parameter is equal to 1, it may mean that the UE is not configured with PUCCH repetition transmission. For example, a repeatedly transmitted PUCCH may contain only one type of UCI. If the PUCCH is configured with repetition transmission, in the embodiments of the present disclosure, one of multiple repetition transmissions of the PUCCH may be regarded as one PUCCH (or PUCCH resource), or all of the repetition transmissions of the PUCCH may be regarded as one PUCCH (or PUCCH resource), or a specific one of the multiple repetition transmissions of the PUCCH may be regarded as one PUCCH (or PUCCH resource).

It should be noted that, in the method of the present disclosure, one PDCCH and/or DCI format schedules multiple PDSCH/PUSCHs, which may be multiple PDSCH/PUSCHs of the same serving cell and/or multiple PDSCH/PUSCHs of different serving cells.

It should be noted that the various aspects described in this disclosure can be combined in any order. In one combination, a mode may be performed one or more times.

It should be noted that the steps in the method of the present disclosure may be performed in any order.

It should be noted that, in the method of the present disclosure, "canceling transmission" may be canceling transmission of the entire uplink channel and/or canceling transmission of a part of the uplink channel.

It should be noted that in the method of the present disclosure, the "small to large order" (e.g., ascending order) may be replaced by the "large to small order" (e.g., descending order), and/or the "large to small order" (e.g., descending order) may be replaced by the "small to large order" (e.g., ascending order).

In the method of the present disclosure, the PUCCH/PUSCH carrying a may be understood as only the PUCCH/PUSCH carrying a, and may also be understood as at least the PUCCH/PUSCH carrying a.

It should be noted that "time slot" in the embodiments of the present disclosure may be replaced by "sub-time slot" or "time unit".

It should be noted that "at least one" in the embodiments of the present disclosure may be understood as "one" or "a plurality". In the case of "a plurality", any permutation and combination of the listed items is possible. For example, at least one of "a", "B", "C" may be: "A", "B", "C", "AB", "BA", "ABC", "CBA", "ABCA", "ABCCB", etc.

In some cases, the PUCCH and/or PUSCH carrying HARQ-ACK information may be de-transmitted, or the base station may not receive and/or successfully decode the HARQ-ACK information. For example, if a PUCCH carrying HARQ-ACK information of an SPS PDSCH and/or a scheduling-free PUSCH carrying HARQ-ACK information (e.g., a Configured granted PUSCH (CG-PUSCH)) overlaps with a set of downlink symbols and/or flexible (flex) symbols indicated by higher layer signaling (e.g., a parameter tdd-UL-DL-configuration common or a parameter tdd-UL-DL-configuration determined) and/or DCI (e.g., a dynamic Slot Format Indicator (SFI) included therein) as downlink symbols and/or flexible (flex) symbols, the UE does not transmit and/or cancels transmission of HARQ-ACK of this SPS PDSCH. For another example, PUCCH and/or PUSCH carrying lower priority HARQ-ACKs are cancelled by higher priority uplink transmissions. However, the reason why the HARQ-ACK information that is not transmitted and/or is cancelled is present is not limited thereto. Additionally, in embodiments of the present disclosure, the expression "not send. Furthermore, in some embodiments of the present disclosure, the term "transmitting" may be used interchangeably with the term "sending".

In some embodiments, HARQ-ACK information (HARQ-ACK codebook) carried by one PUCCH (or in one slot) may be indicated by DCI format (downlink DCI format and/or uplink DCI format) for retransmission on another PUCCH (or slot) and/or PUSCH. For example, a time unit interval (e.g., slot interval) or a time unit offset (e.g., slot offset) of one PUCCH (or slot) carrying retransmitted HARQ-ACK information (HARQ-ACK codebook) and a PUCCH (or slot) for retransmitting the HARQ-ACK information (HARQ-ACK codebook) may be indicated in one downlink DCI format, which is denoted by a first offset indicator (or, simply, a first offset) or offset1 in the embodiments of the present disclosure. As shown in fig. 7, the PUCCH carrying the HARQ-ACK information (HARQ-ACK codebook) to be retransmitted is PUCCH #1 (or PUCCH #1 is a PUCCH in which the HARQ-ACK information is not transmitted or cancelled; for example, the HARQ-ACK information on PUCCH #1 may be the initial HARQ-ACK information or the retransmitted HARQ-ACK information), and the slot carrying the retransmitted HARQ-ACK information (HARQ-ACK codebook) has slot number 0 (slot # 0). The PUCCH carrying the retransmission of the HARQ-ACK information (HARQ-ACK codebook) is PUCCH #2, and the slot carrying the retransmission of the HARQ-ACK information (HARQ-ACK codebook) has slot number 2 (slot # 2). In this case, offset1 denotes a time unit interval (2 in this example) of PUCCH #2 to PUCCH #1 or a time unit interval (2 in this example) of PUCCH #1 to PUCCH # 2.

For another example, a time unit interval (e.g., slot interval) or a time unit offset (e.g., slot offset) of a PUCCH (or slot) carrying HARQ-ACK information to be retransmitted (HARQ-ACK codebook) and a PDCCH (or slot) carrying DCI which indicates (or triggers) retransmission of the HARQ-ACK information may be indicated in one downlink DCI format, and in an embodiment of the present disclosure, indicated by a second offset indicator (or, simply, referred to as a second offset) or offset2. As shown in fig. 8, the PUCCH carrying the retransmitted HARQ-ACK information (HARQ-ACK codebook) is PUCCH #1 (or PUCCH #1 is PUCCH in which the HARQ-ACK information is not transmitted or cancelled; for example, the HARQ-ACK information on PUCCH #1 may be originally transmitted HARQ-ACK information or retransmitted HARQ-ACK information), and the slot carrying the retransmitted HARQ-ACK information (HARQ-ACK codebook) is slot 0. The time slot of the PDCCH carrying the DCI for indicating the retransmission of the HARQ-ACK information is time slot 1.Offset2 denotes a time unit interval from PDCCH to PUCCH #1 (1 in this example) or a time unit interval from PUCCH #1 to PDCCH (1 in this example).

In some cases, the SCS of PDCCH and PUCCH may not be the same, or PUCCH is configured with sub-slots, and one PDCCH or slot of one PDCCH may overlap with slots of more than one PUCCH, where explicit reference points for Offset1 and/or Offset2 are needed. For example, a PDCCH end position (or symbol) or a PDCCH end position (or symbol) of a slot of a PDCCH in which the PDCCH is located may be used as a reference point.

For example, with reference to a slot of a PUCCH transmission on a primary cell, for a type-1 or type-2 HARQ-ACK codebook, a UE that transmits or will transmit a first HARQ-ACK codebook in slot m (e.g., the first HARQ-ACK codebook may be carried by a PUCCH or a PUSCH) may indicate that a PUCCH carrying the first HARQ-ACK codebook is transmitted in slot n + k by a DCI format carried by a PDCCH of slot n by an end position (e.g., an end symbol) (e.g., the DCI format does not schedule PDSCH to receive and/or does not indicate specific HARQ-ACK information (e.g., the specific HARQ-ACK information may be initially transmitted HARQ-ACK information, the specific HARQ-ACK information may be non-retransmitted HARQ-ACK information, and the specific HARQ-ACK information may be feedback of the initially transmitted HARQ-ACK information in a non-first HARQ-ACK codebook), where n + k may be after slot m.

In some embodiments, if the PUCCH carrying HARQ-ACK retransmission of mode-1 overlaps the PUSCH scheduled by one DCI format in the time domain, the HARQ-ACK information may be multiplexed onto the PUSCH for transmission. The PDCCH triggering HARQ-ACK retransmission of mode-1 may be specified by the protocol to be no later or earlier than the PDCCH scheduling the PUSCH. With regard to the definition of "HARQ-ACK retransmission for mode-1", reference may be made to embodiments described later.

In some embodiments, at least one of the following ways MN 1-MN 2 may be employed to generate the HARQ-ACK codebook. For example, a UE that transmits or will transmit a first HARQ-ACK codebook in slot m (e.g., which may be carried by the first PUCCH or the first PUSCH) may indicate by an end position (symbol) that a second PUCCH carrying the first HARQ-ACK codebook is transmitted in slot n + k in a DCI format carried by a PDCCH of slot n, with reference to a slot of a PUCCH transmission on the primary cell; if the UE multiplexes HARQ-ACK of the second PUCCH to the second PUSCH, the HARQ-ACK codebook may be generated in at least one of the following manners MN 1-MN 2.

Mode MN1

In the method MN1, the first HARQ-ACK codebook in the second PUSCH may be transmitted in slot m or will be transmitted. That is, the DAI information of the first HARQ-ACK codebook is not indicated in the DCI format scheduling the second PUSCH. In the mode MN1, the first HARQ-ACK codebook transmitted or to be transmitted in the slot m is determined as the first HARQ-ACK codebook in the second PUSCH.

The method is simple to implement, and can reduce the implementation complexity of the UE and the base station.

Mode MN2

In the scheme MN2, the first HARQ-ACK codebook in the second PUSCH may be determined according to the first UL DAI field in the DCI format scheduling the second PUSCH. The first UL DAI field may be a UL DAI that specifically indicates the first HARQ-ACK codebook, which may be protocol-specified and/or higher layer signaling configuration. Alternatively, the first UL DAI field may be a UL DAI field indicating a first HARQ-ACK codebook and a second HARQ-ACK codebook, wherein the second HARQ-ACK codebook is a non-retransmitted HARQ-ACK codebook carried in the second PUCCH. That is, the UE may reuse the existing UL DAI field to indicate the total DAI for the first HARQ-ACK codebook.

The method can improve the reliability of the transmission of the HARQ-ACK codebook, and avoid the inconsistency of the base station and the UE in the understanding of the HARQ-ACK codebook caused by the missed detection of the PDCCH.

It should be noted that the method can be applied to the same physical layer priority. The method can be applied to a dynamic HARQ-ACK codebook and/or a semi-static HARQ-ACK codebook.

In the embodiment of the present disclosure, the above-described HARQ-ACK retransmission may be referred to as a mode-1 HARQ-ACK retransmission for convenience of description. However, this is merely an example, and any suitable nomenclature may be employed. For example, the HARQ-ACK retransmission for mode-1 may simply be referred to as a "HARQ-ACK retransmission".

In some embodiments, the configuration may be via protocol provisioning and/or higher layer signaling: the UE is instructed to trigger HARQ-ACK retransmission of mode-1 on one PUCCH by receiving the downlink DCI format. The UE does not expect the K1 field in the DCI format to indicate a value of one non-numeric value (or non-available) (e.g., -1). The DCI format only indicates that the retransmission of the HARQ-ACK information is sent on the PUCCH and does not indicate that other HARQ-ACK information is sent on the PUCCH. For example, the DCI format does not schedule PDSCH and/or does not indicate SPS PDSCH release (deactivation) and/or does not indicate secondary cell dormancy and/or does not indicate Type-3 HARQ-ACK codebook transmission in 3 GPP. The UE expects to provide the HARQ-ACK information after N _1 symbols of the last symbol of the PDCCH carrying the DCI format. For example, N _1 may be determined by receiving a DCI format indicating SPS PDSCH release (deactivation) to a timing relationship defined by 3GPP that needs to be satisfied for feeding back HARQ-ACK information of the DCI format. The UE may also report whether the DCI format that triggers the HARQ-ACK retransmission of mode-1 is supported by capability reporting while scheduling the PDSCH and/or indicating SPS PDSCH release (deactivation) and/or indicating secondary cell dormancy and/or indicating Type-3 HARQ-ACK codebook transmission in 3 GPP. The method is simple to realize and does not need to be multiplexed with other HARQ-ACK scheduled by the DCI format. In addition, UE implementation complexity may be reduced by reusing existing implementations.

In some embodiments, the configuration may be by protocol specification and/or higher layer signaling: at least one of the one or more fields in the DCI format is reserved (reserved), and/or at least one of the one or more fields is not included in the DCI format, and/or the DCI format reuses at least one of the one or more fields to indicate offset1 and/or offset2. The one or more fields include, for example:

frequency Domain Resource Allocation (FDRA)

Modulation and Coding Scheme (MCS)

HARQ Process Number (HPN)

- (multiple antenna port)

For example, the MCS field and/or the FDRA field may be reused to indicate offset1 and/or offset2. The two fields have a larger number of bits, which can increase the flexibility of indication.

By reusing the existing fields in the DCI format, the method can reduce the size of the DCI format, thereby improving the spectrum efficiency. In addition, the method can also reduce the complexity of UE implementation.

In some embodiments, the configuration may be via protocol provisioning and/or higher layer signaling: HARQ-ACK information (or HARQ-ACK codebook) retransmission for one or more UEs is triggered by a group common (DCI) format. For example, whether to retransmit HARQ-ACK, and/or offset1, and/or offset2, and/or PUCCH Resource Indicator (PRI), and/or Transmit Power Control (TPC) indication may be indicated to the UEs in one group, respectively. The method can reduce DCI overhead and improve spectrum efficiency.

In some embodiments, whether HARQ-ACK retransmission and offset1 and/or offset2 are indicated by a new field in the DCI format. HARQ-ACK retransmission and offset1 and/or offset2 may be indicated by different fields, respectively, or HARQ-ACK retransmission and offset1 and/or offset2 may be indicated by one field in combination. For example, one codeword is used to indicate that no HARQ-ACK retransmission is triggered, and the other codewords are used to indicate different values of offset1 and/or offset2 corresponding to the triggering of HARQ-ACK retransmission. In one specific example, where a 2-bit joint indication is used, for example, "00" may indicate that no HARQ-ACK retransmission is triggered, "01", "10", "11" may indicate three values of offset1 and/or offset2, respectively, and that the DCI triggered a HARQ-ACK retransmission. When 2 bits are used to indicate different fields, respectively, the 2 bits can indicate only two values of offset1 and/or offset2 at most. In contrast, the method of joint indication can improve the scheduling flexibility when the number of indication bits is the same. For example, if the number of possible values of different offset1 and/or offset2 is K, it can be used

One bit comes inAnd (4) indicating row association. The method can improve the flexibility of scheduling.

In some embodiments, the UE may support multiple HARQ-ACK retransmission methods. For example, the UE may be configured with an enhanced dynamic HARQ-ACK Codebook (e.g., the UE is configured with the 3GPP parameter pdsch-HARQ-ACK-Codebook-r16; this parameter may be configured as enhanced dynamic). As another example, the UE may be configured for HARQ-ACK retransmission for mode-1 as described above. The UE implementation complexity increases if multiple retransmission modes are supported simultaneously. Furthermore, the protocol also needs to specify how the UE needs to generate the HARQ-ACK codebook when triggered simultaneously. It may be specified by the protocol that the UE does not expect to be configured with the enhanced dynamic HARQ-ACK codebook and HARQ-ACK retransmission for mode-1 at the same time. It may be specified by the protocol that the UE does not expect HARQ-ACK retransmissions for type-3 HARQ-ACK codebooks (including enhanced type-3 HARQ-ACK codebooks) and mode-1 in 3GPP to be configured and/or triggered simultaneously. The method is simple to implement, and can reduce the implementation complexity of the base station and the UE.

In some embodiments, the DCI format triggering HARQ-ACK retransmission of mode-1 and/or the DCI format triggering type-3 HARQ-ACK codebook in 3GPP (including enhanced type-3 HARQ-ACK codebook) may be scrambled by at least one of the following RNTIs, possibly via protocol provisions and/or higher layer signaling configurations:

-C-RNTI

-CS-RNTI

-MCS-C-RNTI

-G-RNTI

-G-CS-RNTI

the method provides various RNTIs which can be scrambled, and the scheduling flexibility can be increased.

In some embodiments, the DCI format triggering HARQ-ACK retransmission of mode-1 may or may not schedule the PDSCH, which may be specified by a protocol and/or higher layer signaling configuration. Whether the DCI format schedules the PDSCH may be determined by, for example, the FDRA field in the DCI format. For example, the DCI format may trigger HARQ-ACK retransmission for mode-1 without scheduling PDSCH when at least one of the following conditions is met, as specified by the protocol:

-the UE detects that one DCI format indication triggers a mode-1 HARQ-ACK retransmission;

-the DCI format is scrambled by a C-RNTI or MCS-C-RNTI or G-RNTI;

higher layer parameter resourceAllocation is configured as resourceAllocationType0 (i.e. resourceAllocation = resourceAllocationType 0) and the bits in the FDRA field in the DCI format are all 0;

the higher layer parameter resourcealocation is configured as resourceAllocationType1 (i.e. resourceAllocation = resourceAllocationType 1) and the bits in the FDRA field in the DCI format are all 1;

higher layer parameter resourceAllocation is configured as dynamic switch (i.e. resourceAllocation = dynamic switch) and the bits in the FDRA field in the DCI format are all 0 or 1.

The method can reduce the size of the DCI format, thereby improving the spectrum efficiency.

In some embodiments, only one DCI format may be allowed to trigger the HARQ-ACK retransmission of mode-1 to be sent in one PUCCH, either by protocol specification and/or higher layer signaling configuration. For example, the UE does not expect to receive more than one DCI format to trigger a retransmission of HARQ-ACK information (HARQ-ACK codebook) of the same (or different) PUCCH bearer (or slot) on another PUCCH (or slot) and/or PUSCH (e.g., HARQ-ACK retransmission of mode-1). The method is simple to implement, avoids multiplexing a plurality of HARQ-ACK codebooks on one PUCCH for transmission, and can reduce the implementation complexity of the base station and the UE.

In some embodiments, only DCI formats may be allowed to trigger retransmission of initially transmitted HARQ-ACK information (HARQ-ACK codebook) (e.g., HARQ-ACK retransmission for mode-1) via protocol specification and/or higher layer signaling configuration. For example, the UE does not expect to receive HARQ-ACK information (HARQ-ACK codebook) for DCI format triggered retransmissions to retransmit on another PUCCH (or slot) and/or PUSCH (e.g., HARQ-ACK retransmission for mode-1). For example, the UE does not expect to receive a PUCCH (or slot) carrying HARQ-ACK information (HARQ-ACK codebook) for a DCI format trigger retransmission to be retransmitted on another PUCCH (or slot) and/or PUSCH (e.g., HARQ-ACK retransmission for mode-1). The method is simple to implement, and can reduce the implementation complexity of the base station and the UE. The method avoids the HARQ-ACK codebook triggering retransmission, can improve the consistency of the base station and the UE in understanding the HARQ-ACK codebook, and improves the reliability of HARQ-ACK transmission.

In some embodiments, retransmissions of HARQ-ACK (e.g., HARQ-ACK retransmissions for mode-1) may not be allowed to be multiplexed with other HARQ-ACK information (e.g., HARQ-ACK information for dynamically scheduled PDSCH and/or HARQ-ACK information for SPS PDSCH) to one PUCCH by protocol provisions and/or higher layer signaling configurations. For example, the UE does not expect to receive one DCI format trigger retransmission of HARQ-ACK information (HARQ-ACK codebook) multiplexed to the same PUCCH with other HARQ-ACK information. For another example, the UE does not expect to receive retransmission of one DCI format trigger HARQ-ACK information (HARQ-ACK codebook) multiplexed on the same PUCCH with HARQ-ACK information scheduled by another DCI format and/or HARQ-ACK information of SPS PDSCH. The method is simple to implement, avoids multiplexing a plurality of HARQ-ACK codebooks on one PUCCH for transmission, and can reduce the implementation complexity of the base station and the UE.

In some embodiments, the PUCCH (or slot) carrying the retransmission of the HARQ-ACK (e.g., HARQ-ACK retransmission for mode-1) may not be allowed to be earlier than (and/or equal to) the PUCCH (or slot) carrying the initial transmission of the HARQ-ACK, via protocol provisions and/or higher layer signaling configurations. For example, the PUCCH (or slot) that the UE does not expect to receive one DCI format to trigger a retransmission carrying HARQ-ACK information (HARQ-ACK codebook) is earlier than (and/or equal to) the PUCCH (or slot) carrying the initial transmission of the HARQ-ACK. For another example, the UE does not expect to receive a starting (or ending) symbol (or position) of a PUCCH that one DCI format triggers a retransmission carrying HARQ-ACK information (HARQ-ACK codebook) earlier than (and/or equal to) a starting (or ending) symbol (or position) of an initially transmitted PUCCH carrying that HARQ-ACK. For another example, if offset1 indicates a time interval from the PUCCH carrying the retransmitted HARQ-ACK to the PUCCH carrying the originally transmitted HARQ-ACK, then offset1 may be configured to have a positive integer (or a non-negative integer). For another example, if offset1 indicates a time interval from the PUCCH carrying the initially transmitted HARQ-ACK to the PUCCH carrying the retransmitted HARQ-ACK, offset1 may be configured to have a negative integer and/or 0. The method can avoid the problem of Out of Order (OOO) scheduling and reduce the complexity of UE implementation. If the protocol allows the PUCCH (or slot) carrying the retransmission of the HARQ-ACK (e.g., HARQ-ACK retransmission for mode-1) to be earlier than (and/or equal to) the PUCCH (or slot) carrying the initial transmission of the HARQ-ACK. The PUCCH carrying the retransmission of HARQ-ACK (e.g., HARQ-ACK retransmission for mode-1) also satisfies the constraints of OOO scheduling. That is, the transmission time of the HARQ-ACK of the PDSCH scheduled first cannot be later than the transmission time of the HARQ-ACK of the PDSCH scheduled later.

In some embodiments, more than one DCI format may be allowed to trigger the transmission of a retransmission of HARQ-ACK information (HARQ-ACK codebook) in one PUCCH (e.g., HARQ-ACK retransmission of mode-1) for the same PUCCH bearer (or slot) through protocol specification and/or higher layer signaling configuration. For example, when the UE receives at least one DCI format triggering a retransmission (e.g., HARQ-ACK retransmission of mode-1) that sends HARQ-ACK information (HARQ-ACK codebook) in one PUCCH, the UE sends the retransmission of HARQ-ACK in that PUCCH. For another example, the HARQ-ACK retransmission indications of mode-1 indicating that HARQ-ACK is transmitted in the same PUCCH are not the same, but the UE does not expect to receive in the same PDCCH MO. That is, all DCI indicates that mode-1 HARQ-ACK retransmission is triggered or all DCI indicates that mode-1 HARQ-ACK retransmission is not triggered. For another example, when the UE receives one DCI format in the first PDCCH MO triggering a retransmission (e.g., a mode-1 HARQ-ACK retransmission) that transmits HARQ-ACK information (HARQ-ACK codebook) in one PUCCH, the UE does not expect to receive one DCI format in the second PDCCH MO not triggering a retransmission that transmits the HARQ-ACK information (HARQ-ACK codebook) in the PUCCH. The method defines the behavior of the UE, ensures the consistency of the UE and the base station for the trigger understanding, and improves the reliability of the HARQ-ACK transmission.

In some embodiments, the DCI format may be allowed to trigger retransmission of the retransmitted HARQ-ACK information (HARQ-ACK codebook) (e.g., HARQ-ACK retransmission for mode-1) via protocol specification and/or higher layer signaling configuration. In this case, the maximum time interval Kmax from the PUCCH carrying the HARQ-ACK retransmission to the PUCCH carrying the HARQ-ACK initial transmission may be configured through higher layer signaling. For example, the UE does not expect to receive one DCI format to trigger a retransmission of one HARQ-ACK, where the time interval from the PUCCH carrying the HARQ-ACK retransmission (e.g., the HARQ-ACK retransmission may be a retransmission of one HARQ-ACK retransmission) to the PUCCH carrying the HARQ-ACK initial transmission exceeds Kmax. The method defines the behavior of the UE, ensures the consistency of the UE and the base station for the trigger understanding, and improves the reliability of the HARQ-ACK transmission.

In some embodiments, the retransmission of HARQ-ACK (e.g., HARQ-ACK retransmission for mode-1) may be allowed to be multiplexed with other HARQ-ACK information (e.g., HARQ-ACK information for dynamically scheduled PDSCH and/or HARQ-ACK information for SPS PDSCH) to one PUCCH by protocol provisioning and/or higher layer signaling configuration. The HARQ-ACK information primarily transmitted in the PUCCH can form a first HARQ-ACK sub-codebook, and the HARQ-ACK information retransmitted in the PUCCH can form a second HARQ-ACK sub-codebook. And the HARQ-ACK codebook transmitted on the PUCCH consists of a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. The first HARQ-ACK sub-codebook may be located before or after the second HARQ-ACK sub-codebook. The method defines the behavior of the UE, ensures the consistency of the UE and the base station for the trigger understanding, and improves the reliability of the HARQ-ACK transmission.

In some embodiments, more than one DCI format may be allowed to trigger the transmission of a retransmission of different HARQ-ACK information (HARQ-ACK codebook) for different PUCCH bearers (or in a slot) in the same PUCCH (e.g., HARQ-ACK retransmission for mode-1), either by protocol specification and/or higher layer signaling configuration. The initial HARQ-ACK information sent on the same PUCCH may form a first HARQ-ACK sub-codebook, and the retransmission HARQ-ACK information sent on the same PUCCH may form a second HARQ-ACK sub-codebook. And the HARQ-ACK codebook transmitted on the same PUCCH consists of a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. The first HARQ-ACK sub-codebook may be located before or after the second HARQ-ACK sub-codebook. The second HARQ-ACK sub-codebook may be composed of one or more HARQ-ACK sub-codebooks. Each HARQ-ACK sub-codebook corresponds to one initial transmission HARQ-ACK codebook carried by one PUCCH (or in a time slot), and HARQ-ACK retransmission of the initial transmission HARQ-ACK codebook is sent on the same PUCCH. The HARQ-ACK sub-codebooks may be ordered in chronological order. The method defines the behavior of the UE, ensures the consistency of the UE and the base station for the trigger understanding, and improves the reliability of the HARQ-ACK transmission.

The UE may be configured with a semi-static HARQ-ACK codebook or a dynamic HARQ-ACK codebook. In this case, how to determine the HARQ-ACK codebook of the HARQ-ACK information triggering the retransmission is a matter to be considered.

In some embodiments, the UE is configured with a semi-static HARQ-ACK codebook. Currently, a semi-static HARQ-ACK codebook (type-1 HARQ-ACK codebook) in 3GPP may determine downlink timeslots included in the HARQ-ACK codebook according to possible values of the timing value K1. The possible values of K1 may be a union of sets of K1 that may be indicated by available downlink DCI formats. For example, if the set of K1 is {1,2,3,4}, then the HARQ-ACK codebook at slot n needs to include HARQ-ACK information for the possible PDSCHs in slots n-4, n-3, n-2, and n-1. If the slot interval offset1 of PUCCH #2 to PUCCH #1 is equal to 2 in fig. 7, the type-1 HARQ-ACK codebook in PUCCH #2 cannot completely include the type-1 HARQ-ACK codebook in PUCCH # 1. To solve this problem, one of the following two ways may be adopted. In one mode, the type-1 HARQ-ACK codebooks corresponding to the PUCCH #1 and the PUCCH #2 are spliced into a new HARQ-ACK codebook. Referring to fig. 7, since slot #1 and slot #2 are both included in the type-1 HARQ-ACK codebook corresponding to PUCCH #1 and PUCCH #2, redundant bits are included in the HARQ-ACK codebook. In another way, the set of K1 is expanded, and the expanded set of K1 may include a value indicating a downlink slot corresponding to a type-1 HARQ-ACK codebook that is triggered to retransmit and a value indicating a downlink slot corresponding to a type-1 HARQ-ACK codebook in a PUCCH indicated by a DCI format (which may be the DCI format that triggers retransmission or another DCI format). For example, the set of K1 is expanded to {1,2,3,4,5,6} in this example. An example extension method may include adding offset1 (e.g., 2) to elements in a set of K1 (e.g., {1,2,3,4 }) respectively to obtain a set (e.g., {3,4,5,6 }) and then taking the union of the set (e.g., {3,4,5,6 }) with the set of original K1 (e.g., {1,2,3,4 }) to obtain a set of extended K1. And the UE generates a type-1 HARQ-ACK codebook according to the expanded K1 set. The method can reduce the bit number of the HARQ-ACK, improve the reliability of the HARQ-ACK transmission and improve the spectrum efficiency of the system.

In some embodiments, the UE is configured with a semi-static HARQ-ACK codebook. If the HARQ-ACK codebook that triggered the retransmission includes only HARQ-ACK information for the SPS PDSCH, the HARQ-ACK codebook may be placed after (or before) the type-1 HARQ-ACK codebook in the indicated PUCCH. Alternatively, if the HARQ-ACK codebook for which retransmission is triggered only includes HARQ-ACK information for the SPS PDSCH, the HARQ-ACK information for the SPS PDSCH that satisfies the predefined condition corresponding to the HARQ-ACK codebook may be placed after (or before) the type-1 HARQ-ACK codebook in the indicated PUCCH. The predefined condition may be that the SPS PDSCH is not included in any of the downlink slot(s) indicated by the K1 set to which the PUCCH corresponds. The method can reduce the bit number of the HARQ-ACK, improve the reliability of the HARQ-ACK transmission and improve the spectrum efficiency of the system.

In some embodiments, the UE is configured with a dynamic HARQ-ACK codebook. The joint count of DAIs in the downlink DCI format triggering HARQ-ACK retransmission and DAIs associated with retransmitted HARQ-ACK information may be indicated by protocol specification and/or higher layer signaling configuration. For example, as shown in fig. 9A, HARQ-ACK information in which 1 PDSCH is scheduled for each of DCI #1 and DCI #2 is fed back to PUCCH #1, and the C-DAI counts are 1 and 2, respectively. DCI #3 triggers retransmission of HARQ-ACK information carried by PUCCH #1 in PUCCH # 2.DCI #3 schedules one PDSCH, and the C-DAI count is 3. The UE generates HARQ-ACK codebook according to the DAIs of DCI #1, DCI #2, and DCI #3, for example, according to the method of type-2 HARQ-ACK codebook on PUCCH in 3 GPP. In this example, one PDSCH corresponds to 1-bit HARQ-ACK information, and the number of HARQ-ACK codebook bits is 3 bits. If the UE does not receive DCI #2, the UE may find the missed detection of DCI #2 according to DCI # 3. The method can improve the reliability of the HARQ-ACK codebook.

In some embodiments, the UE is configured with a dynamic HARQ-ACK codebook. The joint count of DAIs in the downlink DCI format that trigger HARQ-ACK retransmission and DAIs associated with retransmitted HARQ-ACK may be indicated by protocol specification and/or higher layer signaling configuration. For example, as shown in fig. 9B, HARQ information in which 1 PDSCH is scheduled in DCI #1 and DCI #2 is fed back to PUCCH #1, and the C-DAI counts are 1 and 2, respectively. DCI #3 triggers retransmission of HARQ-ACK carried by PUCCH #1 in PUCCH # 2.DCI #3 does not schedule PDSCH and/or DCI #3 does not indicate other HARQ-ACK (e.g., SPS release or secondary cell dormant); the C-DAI count in DCI #3 is 2, and/or the T-DAI count in DCI #3 is 2. And the UE generates an HARQ-ACK codebook according to the DAIs of the DCI #1, the DCI #2 and the DCI # 3. The UE generates a HARQ-ACK codebook according to a method of a type-2 HARQ-ACK codebook on a PUSCH in 3GPP, wherein C-DAI and/or T-DAI in DCI #3 can replace UL DAI. In this example, one PDSCH corresponds to 1-bit HARQ-ACK information, and the number of HARQ-ACK codebook bits is 2 bits. If the UE does not receive DCI #2, the UE may find the missed detection of DCI #2 according to DCI # 3. The method can improve the reliability of the HARQ-ACK codebook.

In some embodiments, the UE is configured with a dynamic HARQ-ACK codebook. The respective counts of the DAIs in the downlink DCI format triggering HARQ-ACK retransmission and the DAIs associated with the retransmitted HARQ-ACK may be indicated by protocol specification and/or higher layer signaling configuration. For example, as shown in fig. 9C, HARQ information in which 1 PDSCH is scheduled in each of DCI #1 and DCI #2 is fed back to PUCCH #1, and the C-DAI counts are 1 and 2, respectively. DCI #4 triggers retransmission of HARQ-ACK carried by PUCCH #1 in PUCCH # 2. HARQ information in which 1 PDSCH is scheduled in DCI #3 and DCI #4 is fed back in PUCCH #2, and the C-DAI counts are 1 and 2, respectively. And the UE generates a retransmission HARQ-ACK sub-codebook according to DCI #1 and DCI #2, and generates an initial transmission HARQ-ACK sub-codebook according to DCI #1 and DCI # 2. For example, the HARQ-ACK sub-codebook is generated according to a method of a type-2 HARQ-ACK codebook on a PUCCH in 3 GPP. The HARQ-ACK codebook consists of a retransmitted HARQ-ACK sub-codebook and an initially transmitted HARQ-ACK sub-codebook. If the UE does not receive DCI #3, the UE may find the missed detection of DCI #3 according to DCI # 4. The method can improve the reliability of the HARQ-ACK codebook.

In some embodiments, the UE is configured with a dynamic HARQ-ACK codebook. The respective counts of the DAIs in the downlink DCI format triggering HARQ-ACK retransmission and the DAIs associated with the retransmitted HARQ-ACK may be indicated by protocol specification and/or higher layer signaling configuration. For example, as shown in fig. 9D, HARQ information in which 1 PDSCH is scheduled in each of DCI #1 and DCI #2 is fed back to PUCCH #1, and the C-DAI counts are 1 and 2, respectively. DCI #4 triggers retransmission of HARQ-ACK carried by PUCCH #1 in PUCCH # 2. The DCI #3 schedules HARQ information of 1 PDSCH to be fed back in PUCCH #2, and the C-DAI count is 1.DCI #4 does not schedule PDSCH and/or DCI #4 does not indicate other HARQ-ACK (e.g., SPS release or secondary cell dormant), the C-DAI count is 1 in DCI #4, and/or the T-DAI count is 1 in DCI # 4. And the UE generates a retransmission HARQ-ACK sub-codebook according to the DCI #1 and the DCI #2, and generates a primary transmission HARQ-ACK sub-codebook according to the DCI #3 and the DCI # 4. For example, the initial transmission HARQ-ACK sub-codebook is generated according to the method of the type-2 HARQ-ACK codebook on the PUSCH in 3GPP, wherein the C-DAI and/or the T-DAI in DCI #4 can replace the UL DAI. The HARQ-ACK codebook consists of a retransmitted HARQ-ACK sub-codebook and an initially transmitted HARQ-ACK sub-codebook. If the UE does not receive DCI #3, the UE may find the missed detection of DCI #3 according to DCI # 4. The method can improve the reliability of the HARQ-ACK codebook.

In some embodiments, the UE is configured with a dynamic HARQ-ACK codebook. The joint or separate counting of DAIs in the downlink DCI format triggering HARQ-ACK retransmission and the DAI associated with the retransmitted HARQ-ACK may be indicated by protocol specification and/or higher layer signaling configuration. For example, as shown in fig. 9E, SPS PDSCH #1 and SPS PDSCH #2 are fed back on PUCCH # 1. The DCI triggers HARQ-ACK retransmission carried by PUCCH #1 in PUCCH # 2.DCI #3 does not schedule PDSCH and/or DCI #3 does not indicate other HARQ-ACK (e.g., SPS release or secondary cell dormant). As shown in tables 1 and 2, the DAI count cannot directly indicate 0. In this case, a HARQ-ACK codebook (or sub-codebook) of how the DAI indicates 0 and/or the UE does not generate dynamic scheduling (e.g., HARQ-ACK information scheduled (or indicated) by DCI format) may be defined by a predefined rule. The predefined rule may be at least one of:

-the value of the DAI indication is a specific value (e.g. 4);

the UE does not receive any DCI scheduling (or indication) HARQ-ACK transmission in the slot where the retransmitted PUCCH (PUCCH carrying HARQ-ACK) is located;

the UE does not receive any DCI scheduling (or indication) HARQ-ACK (excluding the triggered HARQ-ACK retransmission) is sent in the slot where the PUCCH retransmitting HARQ-ACK is located.

In another example, the UE is configured with a dynamic HARQ-ACK codebook. The respective counts of the DAIs in the downlink DCI format triggering HARQ-ACK retransmission and the DAIs associated with the retransmitted HARQ-ACK may be indicated by protocol specification and/or higher layer signaling configuration. For example, as shown in fig. 9F, HARQ information in which 1 PDSCH is scheduled in each of DCI #1 and DCI #2 is fed back to PUCCH #1, and the C-DAI counts are 1 and 2, respectively. DCI #3 triggers retransmission of HARQ-ACK carried by PUCCH #1 in PUCCH # 2.DCI #3 does not schedule the PDSCH. It may be indicated by the above-mentioned predefined rule that DAI is 0, the ue may not generate HARQ-ACK information for a DCI format (e.g., DCI # 3) that does not schedule the PDSCH.

The method defines a method for not generating a dynamic HARQ-ACK codebook/sub-codebook, can reduce the cost of UCI, can improve the reliability of transmission and can improve the spectrum efficiency of a system.

In some embodiments, the UE is configured with a dynamic HARQ-ACK codebook. The DAI (e.g., total DAI) of the HARQ-ACK of the triggered retransmission may be indicated by a specific DAI field (e.g., a newly added DAI field) in a DCI format (the DCI format may be a downlink DCI format and/or a downlink DCI format) through protocol specification and/or higher layer signaling configuration. The method can improve the reliability of the HARQ-ACK codebook.

In some embodiments, the UE is configured with a dynamic HARQ-ACK codebook. The respective counts of the C-DAIs in the downlink DCI format triggering HARQ-ACK retransmission and the DAIs associated with the retransmitted HARQ-ACK may be indicated by protocol specification and/or higher layer signaling configuration. The DAI (e.g., total DAI) of the HARQ-ACK of the triggered retransmission is indicated by a T-DAI field in the downlink DCI format. The method can improve the reliability of the HARQ-ACK codebook.

In some embodiments, the UE is configured with a dynamic HARQ-ACK codebook. The UE is configured with CBG (code block group) based HARQ-ACK feedback. Through protocol specification and/or higher layer signaling configuration, if a DCI format indicating that HARQ-ACK retransmission is triggered schedules a TB (transport block) -based PDSCH reception, the DAI indication in the DCI format is determined as the DAI indication of the HARQ-ACK sub-codebook of the corresponding TB level, e.g., according to methods of other embodiments of the present disclosure. If a DCI format indicating that a HARQ-ACK retransmission is triggered schedules a CBG-based PDSCH reception, the DAI indication in the DCI format is determined to be the DAI indication of the HARQ-ACK subcodebook corresponding to the CBG level, e.g., according to methods of other embodiments of the present disclosure. The method reduces DCI overhead and can improve the spectrum efficiency of the system.

Fig. 10 illustrates a flow chart of a method 1000 performed by a terminal according to some embodiments of the present disclosure.

Referring to fig. 10, configuration information related to HARQ-ACK retransmission is received from a base station in operation S1010.

In operation S1020, HARQ-ACK information, which is canceled to be transmitted on the first PUCCH, is retransmitted based on the configuration information. For example, this step S1020 may include determining (e.g., identifying) HARQ-ACK information that was de-transmitted on the first PUCCH, and retransmitting the identified HARQ-ACK information based on the configuration information.

For example, the above operations or other operations in the method 1000 may be implemented with reference to one or more of the previously described embodiments.

For example, the method 1000 may include one or more of the operations described in various embodiments of the disclosure as being performed by a terminal (e.g., a UE).

Fig. 11 shows a block diagram of a first transceiving node 1100 according to some embodiments of the present disclosure.

Referring to fig. 11, a first transceiving node 1100 may comprise a transceiver 1101 and a controller 1102.

The transceiver 1101 may be configured to transmit first data and/or first control signaling to a second transceiving node and to receive second data and/or second control signaling from the second transceiving node in a time unit.

The controller 1102 may be an application specific integrated circuit or at least one processor. The controller 1102 may be configured to control overall operation of the first transceiving node, including controlling the transceiver 1101 to transmit first data and/or first control signaling to the second transceiving node and to receive second data and/or second control signaling from the second transceiving node in units of time.

In some implementations, the controller 1102 may be configured to perform one or more of the operations of the methods of the various embodiments described above.

In the following description, a base station is taken as an example (but not limited to) to describe a first transceiving node, and a UE is taken as an example (but not limited to) to describe a second transceiving node. The first data and/or first control signaling are illustrated with, but not limited to, downlink data and/or downlink control signaling. The HARQ-ACK codebook may be included in the second control signaling, which is illustrated with, but not limited to, uplink control signaling.

Fig. 12 shows a flow diagram of a method 1200 performed by a base station, in accordance with some embodiments of the present disclosure.

Referring to fig. 12, a base station transmits downlink data and/or downlink control information at step S1210.

In step S1220, the base station receives second data and/or second control information from the UE in a time unit.

For example, the method 1200 may include one or more of the operations described in various embodiments of the disclosure as being performed by a base station.

In some embodiments, the downlink channel may include a PDCCH and/or a PDSCH. The uplink channel may include PUCCH and/or PUSCH.

Fig. 13 shows a flow diagram of a method 1300 performed by a base station, in accordance with some embodiments of the present disclosure.

Referring to fig. 13, configuration information related to HARQ-ACK retransmission is transmitted to a terminal in operation S1310.

In operation S1320, retransmitted HARQ-ACK information is received from the terminal, wherein the HARQ-ACK information is cancelled on the first PUCCH, and wherein the HARQ-ACK information is retransmitted based on the configuration information.

For example, the above operations or other operations in the method 1300 may be implemented with reference to one or more of the previously described embodiments.

For example, the method 1300 may include one or more of the operations described in various embodiments of the disclosure as being performed by a base station.

Those skilled in the art will appreciate that the above illustrative embodiments are described herein and are not intended to be limiting. It should be understood that any two or more of the embodiments disclosed herein may be combined in any combination. In addition, other embodiments may be utilized and other changes may be made without departing from the spirit and scope of the subject matter presented herein. It will be readily understood that the aspects of the disclosed invention, as generally described herein, and illustrated in the figures, can be arranged, substituted, combined, separated, and designed in a wide variety of different configurations, all of which are contemplated herein.

Those of skill in the art would understand that the various illustrative logical blocks, modules, circuits, and steps described in this application may be implemented as hardware, software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The various illustrative logical blocks, modules, and circuits described herein may be implemented or performed with 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. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The steps of a method or algorithm described in this application may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

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

The above description is intended to be illustrative of the present invention and not to limit the scope of the invention, which is defined by the claims appended hereto.

Claims (15)

1. A method performed by a terminal for hybrid automatic repeat request-acknowledgement, HARQ-ACK, retransmission, comprising:

receiving configuration information related to HARQ-ACK retransmission from a base station; and

and retransmitting the HARQ-ACK information which is cancelled and transmitted on the first physical uplink control channel PUCCH based on the configuration information.

2. The method of claim 1, wherein configuration information related to HARQ-ACK retransmission comprises a Downlink Control Information (DCI) format indicating whether retransmission of the HARQ-ACK information on a second PUCCH is triggered.

3. The method of claim 2, wherein the DCI format comprises at least one of a first offset indicator to indicate a time unit interval of a first PUCCH and a second PUCCH for retransmitting the HARQ-ACK information, or a second offset indicator to indicate a time unit interval of a first PUCCH and a Physical Downlink Control Channel (PDCCH) carrying the DCI format.

4. The method of claim 3, wherein at least one of a plurality of fields in the DCI format is used for at least one of a first offset indicator or a second offset indicator, the plurality of fields including a Frequency Domain Resource Allocation (FDRA), a Modulation and Coding Scheme (MCS), a HARQ process number, or an antenna port.

5. The method of claim 2, wherein the DCI format is a group common DCI format to indicate whether to trigger retransmission of HARQ-ACK information for each terminal in a group of terminals including the terminal.

6. The method of claim 2, wherein a cyclic redundancy check, CRC, of the DCI format is scrambled by at least one of a cell radio network temporary identity, C-RNTI, a configuration scheduling, CS-RNTI, a modulation and coding scheme, MCS-C-RNTI, a multicast G-RNTI, or a multicast configuration scheduling, G-CS-RNTI.

7. The method of any of claims 2-6, wherein:

not expecting more than one DCI format to trigger retransmission of the HARQ-ACK information in the second PUCCH; and/or

The DCI format only triggers retransmission of the HARQ-ACK information as initial transmission; and/or

The retransmission of the HARQ-ACK information is not multiplexed with other HARQ-ACK information to a second PUCCH; and/or

A second PUCCH that is not expected to be used for retransmission of the HARQ-ACK information is earlier than or equal to the first PUCCH.

8. The method of any of claims 2-6, wherein:

retransmitting the HARQ-ACK information based on the configuration information comprises: when the DCI format indication triggers retransmission of the HARQ-ACK information on a second PUCCH, performing retransmission of the HARQ-ACK information on the second PUCCH; and/or

When a plurality of DCI formats which are received by the same PDCCH monitoring opportunity and indicate that HARQ-ACK is transmitted in the same PUCCH exist, configuration information related to HARQ-ACK retransmission in the plurality of DCI formats is not expected to be different; and/or

When the DCI format is received at a first PDCCH monitoring occasion and triggers retransmission of HARQ-ACK information in a second PUCCH, not expecting to receive another DCI format at a second PDCCH monitoring occasion that does not trigger retransmission of the HARQ-ACK information in the second PUCCH; and/or

When the HARQ-ACK information is retransmitted HARQ-ACK information and the DCI format is used to trigger retransmission of the retransmitted HARQ-ACK information, a time unit interval between a first PUCCH used for retransmission of the HARQ-ACK information and a second PUCCH used for retransmission of the HARQ-ACK information is not expected to be greater than or equal to a maximum time unit interval.

9. The method of any of claims 2-6, wherein retransmitting the HARQ-ACK information based on the configuration information comprises determining a HARQ-ACK codebook that includes the HARQ-ACK information and transmitting the HARQ-ACK codebook,

wherein determining the HARQ-ACK codebook including the HARQ-ACK information includes at least one of:

determining a HARQ-ACK codebook of the HARQ-ACK information based on a time unit interval between a first PUCCH and a second PUCCH for retransmitting the HARQ-ACK information and a set of timing values K1 for indicating timing of HARQ feedback; or

The HARQ-ACK codebook for the HARQ-ACK information triggered for retransmission is placed after or before a type-1 HARQ-ACK codebook in a second PUCCH indicated by a second DCI format for transmission if the HARQ-ACK codebook for the HARQ-ACK information triggered for retransmission only includes HARQ-ACK information of a semi-persistent scheduling (SPS) Physical Downlink Shared Channel (PDSCH); or

Placing HARQ-ACK information of at least one of the one or more SPS PDSCHs that satisfies a predefined condition for transmission after or before a type-1 HARQ-ACK codebook in a second PUCCH indicated by a second DCI format if the HARQ-ACK codebook of the HARQ-ACK information triggered for retransmission only includes HARQ-ACK information of one or more SPS PDSCHs, wherein the predefined condition includes that the at least one SPS PDSCH is not included in any of one or more downlink time units indicated by a set of corresponding timing values K1 of the second PUCCH.

10. The method of any of claims 2-6, wherein retransmitting the HARQ-ACK information based on the configuration information comprises determining a HARQ-ACK codebook including the HARQ-ACK information and transmitting the HARQ-ACK codebook,

wherein determining the HARQ-ACK codebook including the HARQ-ACK information comprises:

and jointly counting or respectively counting Downlink Allocation Indexes (DAIs) of DCI formats triggering retransmission of the HARQ-ACK information and DAIs of DCI formats corresponding to downlink transmission associated with the HARQ-ACK information, and determining an HARQ codebook of the HARQ-ACK information based on the jointly counted DAIs or the respectively counted DAIs.

11. The method according to any of claims 2-6, wherein, when the terminal is configured with a dynamic HARQ-ACK codebook, determining not to generate a HARQ-ACK codebook for dynamically scheduled downlink transmissions based on at least one of:

a value indicated by a DAI field included in the DCI format is a preset value;

the terminal does not receive any DCI format scheduling HARQ-ACK information and transmits the HARQ-ACK information in a time unit where a second PUCCH for retransmitting the HARQ-ACK information is located; or

The terminal does not receive any HARQ-ACK which does not comprise the HARQ-ACK information used for retransmission in the time unit where the second PUCCH used for retransmitting the HARQ-ACK information is transmitted.

12. The method of any of claims 2-6, wherein:

indicating, by a DAI field in the DCI format, a DAI of HARQ-ACK information for which retransmission is triggered; and/or

Triggering HARQ-ACK retransmission, wherein a counting downlink allocation index C-DAI in the DCI format serving as a downlink DCI format and the DAI associated with the retransmitted HARQ-ACK information are respectively counted; and/or

Indicating DAI of HARQ-ACK information triggered for retransmission through a total downlink assignment index (T-DAI) field in the DCI format as a downlink DCI format; and/or

Determining a DAI of a HARQ-ACK sub-codebook corresponding to a TB-based PDSCH reception based on a DAI field in the DCI format if the DCI format triggering HARQ-ACK retransmission schedules a transport block TB-based PDSCH reception; and/or

Determining a DAI of a HARQ-ACK sub-codebook corresponding to CBG-based PDSCH reception based on a DAI field in the DCI format if the DCI format triggering HARQ-ACK retransmission schedules PDSCH reception based on a codebook group CBG.

13. A method performed by a base station for hybrid automatic repeat request-acknowledgement, HARQ-ACK, retransmission, comprising:

transmitting configuration information related to HARQ-ACK retransmission to a terminal; and

receiving retransmitted HARQ-ACK information from a terminal, wherein the HARQ-ACK information is de-transmitted on a first physical uplink control channel, PUCCH,

wherein the HARQ-ACK information is retransmitted based on the configuration information.

14. A terminal, comprising:

a transceiver configured to transmit and receive signals; and

a controller coupled with the transceiver and configured to perform operations in the method of any of claims 1-12.

15. A base station, comprising:

a transceiver configured to transmit and receive signals; and

a controller coupled with the transceiver and configured to perform operations in the method of claim 13.

Images