EP4674214A1

EP4674214A1 - Method and apparatus for transmission and reception of control information in wireless communication system

Info

Publication number: EP4674214A1
Application number: EP24781215.9A
Authority: EP
Inventors: Sa ZHANG; Feifei SUN
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2023-03-31
Filing date: 2024-03-27
Publication date: 2026-01-07
Also published as: CN118741726A; EP4674214A4; KR20250168336A; WO2024205225A1

Abstract

This invention relates to a method comprising: receiving first information related to a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook; receiving second information indicating a number of physical downlink shared channel (PDSCH) receptions in a downlink time unit of a downlink bandwidth part (BWP), wherein the PDSCH receptions include one or more of multicast PDSCH receptions or unicast PDSCH receptions; determining a first set of occasions for candidate PDSCH receptions based on the first information and the second information; generating the HARQ-ACK codebook based on the first set of occasions for candidate PDSCH receptions; and transmitting the generated HARQ-ACK codebook.

Description

METHOD AND APPARATUS FOR TRANSMISSION AND RECEPTION OF CONTROL INFORMATION IN WIRELESS COMMUNICATION SYSTEM

The disclosure relates to wireless communication technology, and more specifically, to a method and an apparatus for transmission and reception of control information in a wireless communication system.

5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

Moreover, there has been ongoing standardization in air interface architecture/protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture/service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

5th generation (5G) or new radio (NR) mobile communications is recently gathering increased momentum with all the worldwide technical activities on the various candidate technologies from industry and academia. The candidate enablers for the 5G/NR mobile communications include massive antenna technologies, from legacy cellular frequency bands up to high frequencies, to provide beamforming gain and support increased capacity, new waveform (e.g., a new radio access technology (RAT)) to flexibly accommodate various services/applications with different requirements, new multiple access schemes to support massive connections, and so on.

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. Therefore, 5G or quasi-5G communication systems are also called "super 4G networks" or "post-LTE systems".

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

In addition, in the 5G communication system, based on the advanced small cell, Radio Access Network (RAN), ultra-dense network, device-to-device (D2D) communication, wireless backhaul, mobile network, cooperative communication, Coordinated Multi-Points (CoMP), receiver interference cancellation, etc., the system network is being improved.

In the 5G system, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (sliding window superposition coding, SWSC), Filter Bank Multi Carrier (FBMC), Non-Orthogonal Multiple Access (NOMA) and Sparse Code Multiple Access (SCMA) as advanced access technologies.

In line with development of the communication systems, there is a need for method and an apparatus for transmission and reception of control information.

The technical subjects pursued in the disclosure may not be limited to the above mentioned technical subjects, and other technical subjects which are not mentioned may be clearly understood, through the following descriptions, by those skilled in the art to which the disclosure pertains.

A method and an apparatus for transmission and reception of control information in a wireless communication system are provided. The method includes receiving first information related to a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook, receiving second information indicating a number of physical downlink shared channel (PDSCH) receptions in a downlink time unit of a downlink bandwidth part (BWP), where the PDSCH receptions include one or more of multicast PDSCH receptions or unicast PDSCH receptions, determining a first set of occasions for candidate PDSCH receptions based on the first information and the second information, generating the HARQ-ACK codebook based on the first set of occasions for candidate PDSCH receptions, and transmitting the generated HARQ-ACK codebook. An enhanced HARQ-ACK feedback method is provided.

A method performed by a terminal in a wireless communication system is described. The method includes: receiving first information related to a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook; receiving second information indicating a number of physical downlink shared channel (PDSCH) receptions in a downlink time unit of a downlink bandwidth part (BWP), wherein the PDSCH receptions include multicast PDSCH receptions and/or unicast PDSCH receptions; determining a first set of occasions for candidate PDSCH receptions based on the first information and the second information; generating a HARQ-ACK codebook based on the first set of occasions for candidate PDSCH receptions; and transmitting the generated HARQ-ACK codebook.

A terminal in a wireless communication system is described, which includes a transceiver, and a controller coupled to the transceiver and configured to: receive first information related to a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook; receive second information indicating a number of physical downlink shared channel (PDSCH) receptions in a downlink time unit of a downlink bandwidth part (BWP), wherein the PDSCH receptions include multicast PDSCH receptions and/or unicast PDSCH receptions; determine a first set of occasions for candidate PDSCH receptions based on the first information and the second information; generate a HARQ-ACK codebook based on the first set of occasions for candidate PDSCH receptions; and transmit the generated HARQ-ACK codebook.

A non-transitory computer-readable medium is described, which stores codes for wireless communication at a terminal. The code may include instructions executable by a processor to: receive first information related to a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook; receiving second information indicating a number of physical downlink shared channel (PDSCH) receptions in a downlink time unit of a downlink bandwidth part (BWP), wherein the PDSCH receptions include multicast PDSCH receptions and/or r unicast PDSCH receptions; determine a first set of occasions for candidate PDSCH receptions based on the first information and the second information; generate a HARQ-ACK codebook based on the first set of occasions for candidate PDSCH receptions; and transmit the generated HARQ-ACK codebook.

In some examples of the method, terminal and non-transitory computer-readable medium described herein, HARQ-ACK information for PDSCH receptions indicated by the second information is multiplexed in a physical uplink control channel (PUCCH) or an uplink time unit for transmission.

In some examples of the method, terminal and non-transitory computer-readable medium described herein, in case that a second set is not empty, the first set includes a first number of occasions for the candidate PDSCH receptions in the downlink time unit of the BWP, wherein the first number is determined based on the number of PDSCH receptions in the downlink time unit of the downlink BWP indicated by the second information, wherein the second set consists of rows of a time domain resource allocation table, wherein the rows in the second set correspond to the candidate PDSCH receptions in the downlink time unit of the downlink BWP.

In some examples of the method, the terminal and the non-transitory computer-readable medium described herein, the second information indicates one or more of the following: a maximum number of PDSCH receptions in the downlink time unit of the downlink BWP; a maximum number of PDSCH receptions in the downlink time unit of the downlink BWP of a serving cell; a maximum number of unicast PDSCH receptions in the downlink time unit of the downlink BWP; a maximum number of unicast PDSCH receptions in the downlink time unit of the downlink BWP of the serving cell; a maximum number of unicast PDSCH receptions or multicast PDSCH receptions in the downlink time unit of the downlink BWP; a maximum number of unicast PDSCH receptions or multicast PDSCH receptions in the downlink time unit of the downlink BWP of the serving cell; a maximum number of multicast PDSCH receptions in the downlink time unit of the downlink BWP; a maximum number of multicast PDSCH receptions in the downlink time unit of the downlink BWP of the serving cell; a maximum number of unicast PDSCH receptions and a maximum number of multicast PDSCH receptions in the downlink time unit of the downlink BWP; or a maximum number of unicast PDSCH receptions and a maximum number of multicast PDSCH receptions in the downlink time unit of the downlink BWP of the serving cell.

In some examples of the method, the terminal and the non-transitory computer-readable medium described herein, the second information is configured separately for each serving cell; and/or the second information is configured separately for each downlink BWP; and/or the second information is configured separately for each downlink BWP of each serving cell; and/or the second information is configured separately for unicast PDSCH receptions and multicast PDSCH receptions.

In some examples of the method, the terminal and the non-transitory computer-readable medium described herein, when the terminal is configured with two or more priorities, the second information is configured separately for each of the two or more priorities.

In some examples of the method, the terminal and the non-transitory computer-readable medium described herein, in case that the terminal is configured with two or more values of a control resource set pool index, the second information is configured separately for each of the two or more values, or the same second information is configured for the two or more values.

In some examples of the method, the terminal and the non-transitory computer-readable medium described herein, in case that the terminal is configured with two or more priorities and is configured with two or more values of a control resource set pool index, the second information is configured for each of combinations of the priorities and the values of the control resource set pool index, wherein the combination of the priorities and the values of the control resource set pool index includes any one of the two or more priorities and any one of the two or more values.

In some examples of the method, terminal and non-transitory computer-readable medium described in this paper, in case that the second information indicates that a maximum of the number of PDSCH receptions in the downlink time unit of the downlink BWP is 1: the terminal does not expect to receive a PDSCH and a downlink control information (DCI) format without scheduling a PDSCH reception in a same downlink time unit, wherein HARQ-ACK information for the PDSCH and HARQ-ACK information for the DCI format are transmitted in a same PUCCH or a same uplink time unit; and/or the terminal does not expect to receive more than one DCI format without scheduling a PDSCH reception in a same downlink time unit, wherein HARQ-ACK information for the more than one DCI format is transmitted in a same PUCCH or a same uplink time unit.

A method performed by a base station in a wireless communication system is described. The method includes: transmitting first information related to a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook to a terminal; transmitting second information indicating a number of physical downlink shared channel (PDSCH) receptions in a downlink time unit of a downlink bandwidth part (BWP) to a terminal, wherein the PDSCH receptions include multicast PDSCH receptions and/or unicast PDSCH receptions; and receiving a HARQ-ACK codebook from the terminal, wherein the HARQ-ACK codebook is generated based on a first set of occasions for candidate PDSCH receptions, wherein the first set of occasions for candidate PDSCH receptions is determined based on the first information and the second information.

A base station in a wireless communication system is described, which includes a transceiver; and a controller coupled to the transceiver and configured to: transmit first information related to a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook to a terminal; transmit second information indicating a number of physical downlink shared channel (PDSCH) receptions in a downlink time unit of a downlink bandwidth part (BWP) to a terminal, wherein the PDSCH receptions includes multicast PDSCH receptions or unicast PDSCH receptions; and receive a HARQ-ACK codebook from the terminal, wherein the HARQ-ACK codebook is generated based on a first set of occasions for candidate PDSCH receptions, wherein the first set of occasions for candidate PDSCH receptions is determined based on the first information and the second information.

A non-transitory computer readable medium is described, which stores codes for wireless communication at a base station. The code may include instructions executable by a processor to transmit first information related to a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook to a terminal; transmit second information indicating a number of physical downlink shared channel (PDSCH) receptions in a downlink time unit of a downlink bandwidth part (BWP) to a terminal, wherein the PDSCH receptions include multicast PDSCH receptions and/or unicast PDSCH receptions; and receive a HARQ-ACK codebook from the terminal, wherein the HARQ-ACK codebook is generated based on a first set of occasions for candidate PDSCH receptions, wherein the first set of occasions for candidate PDSCH receptions is determined based on the first information and the second information.

In some examples of the method, the base station and the non-transitory computer-readable medium described herein, HARQ-ACK information for PDSCH receptions indicated by the second information is multiplexed in a physical uplink control channel (PUCCH) or an uplink time unit for reception.

In some examples of the method, the base station and the non-transitory computer-readable medium described herein, in case that a second set is not empty, the first set includes a first number of occasions for the candidate PDSCH receptions in the downlink time unit of the BWP, wherein the first number is determined based on the number of PDSCH receptions in the downlink time unit of the downlink BWP indicated by the second information, wherein the second set consists of rows of a time domain resource allocation table, wherein the rows in the second set correspond to the candidate PDSCH receptions in the downlink time unit of the downlink BWP.

In some examples of the method, the base station and the non-transitory computer-readable medium described herein, the second information indicates one or more of: a maximum number of PDSCH receptions in the downlink time unit of the downlink BWP; a maximum number of PDSCH receptions in the downlink time unit of the downlink BWP of a serving cell; a maximum number of unicast PDSCH receptions in the downlink time unit of the downlink BWP; a maximum number of unicast PDSCH receptions in the downlink time unit of the downlink BWP of the serving cell; a maximum number of unicast PDSCH receptions or multicast PDSCH receptions in the downlink time unit of the downlink BWP; a maximum number of unicast PDSCH receptions or multicast PDSCH receptions in the downlink time unit of the downlink BWP of the serving cell; a maximum number of multicast PDSCH receptions in the downlink time unit of the downlink BWP; a maximum number of multicast PDSCH receptions in the downlink time unit of the downlink BWP of the serving cell; a maximum number of unicast PDSCH receptions and a maximum number of multicast PDSCH receptions in the downlink time unit of the downlink BWP; or a maximum number of unicast PDSCH receptions and a maximum number of multicast PDSCH receptions in the downlink time unit of the downlink BWP of the serving cell.

In some examples of the method, the base station and the non-transitory computer-readable medium described herein, the second information is configured separately for each serving cell; and/or the second information is configured separately for each downlink BWP; and/or the second information is configured separately for each downlink BWP of each serving cell; and/or the second information is configured separately for unicast PDSCH receptions and multicast PDSCH receptions.

In some examples of the method, the base station and the non-transitory computer-readable medium described herein, in case that two or more priorities are configured for the terminal, the second information is configured separately for each of the two or more priorities.

In some examples of the method, the base station and the non-transitory computer-readable medium described herein, in case that two or more values of a control resource set pool index are configured for the terminal, the second information is configured separately for each of the two or more values, or the same second information is configured for the two or more values of the control resource set pool index.

In some examples of the method, the base station and the non-transitory computer-readable medium described herein, in case that two or more priorities are configured for the terminal and/or two or more values of the control resource set pool index are configured, the second information is configured for each of combinations of the priorities and the values of the control resource set pool index, wherein the combination of the priorities and the values of the control resource set pool index includes any one of the two or more priorities and any one of the two or more values.

In some examples of the method, the base station and the non-transitory computer-readable medium described herein, in case that the second information indicates that a maximum of the number of PDSCH receptions in the downlink time unit of the downlink BWP is 1: the base station does not transmit a PDSCH and a downlink control information (DCI) format without scheduling a PDSCH reception in a same downlink time unit, wherein HARQ-ACK information for the PDSCH and HARQ-ACK information for the DCI format are transmitted in a same PUCCH or a same uplink time unit; and/or the base station does not transmit more than one DCI format without scheduling a PDSCH reception in a same downlink time unit, wherein HARQ-ACK information for the more than one DCI format is transmitted in a same PUCCH or a same uplink time unit.

The present disclosure provides an effective and efficient method for transmission and reception of control information.

Advantageous effects obtainable from the disclosure may not be limited to the above mentioned effects, and other effects which are not mentioned may be clearly understood, through the following descriptions, by those skilled in the art to which the disclosure pertains.

In order to illustrate the technical schemes of the embodiments of the disclosure more clearly, the drawings of the embodiments of the disclosure will be briefly introduced below. Apparently, the drawings described below only refer to some embodiments of the disclosure, and do not limit the disclosure. In the drawings:

FIG. 1 illustrates a schematic diagram of an example wireless network according to some embodiments of the disclosure;

FIGS. 2A and 2B illustrate example wireless transmission and reception paths according to some embodiments of the disclosure;

FIG. 3A illustrates an example user equipment (UE) according to some embodiments of the disclosure;

FIG. 3B illustrates an example gNB according to some embodiments of the disclosure;

FIG. 4 illustrates a block diagram of a first transceiving node according to some embodiments of the disclosure;

FIG. 5 illustrates a block diagram of a second transceiving node according to some embodiments of the disclosure;

FIG. 6 illustrates a flowchart of a method performed by a base station according to some embodiments of the disclosure;

FIG. 7 illustrates a flowchart of a method performed by a UE according to some embodiments of the disclosure;

FIGS. 8A-8C illustrate some examples of uplink transmission timing according to some embodiments of the disclosure;

FIGS. 9A and 9B illustrate examples of time domain resource allocation tables according to some embodiments of the disclosure;

FIG. 10 illustrates an example of multiple start and length indicators (SLIVs) included in a time domain resource allocation table according to some embodiments of the disclosure;

FIG. 11 illustrates s a flowchart of a method performed by a terminal according to some embodiments of the disclosure;

FIG. 12 illustrates a flowchart of a method performed by a base station according to some embodiments of the disclosure.

In order to make the purpose, technical schemes and advantages of the embodiments of the disclosure clearer, the technical schemes of the embodiments of the disclosure will be described clearly and completely with reference to the drawings of the embodiments of the disclosure. Apparently, the described embodiments are a part of the embodiments of the disclosure, but not all embodiments. Based on the described embodiments of the disclosure, all other embodiments obtained by those of ordinary skill in the art without creative labor belong to the protection scope of the disclosure.

Before undertaking the DETAILED DESCRIPTION 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," as well as derivatives thereof, means to include, be included within, connect to, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, have a relationship to or with, or the like. 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 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. The phrase "at least one of," 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 needed. For example, "at least one of: A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C. For example, "at least one of: A, B, or C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A, B and C.

Moreover, various functions described below may be implemented or supported by one or more computer programs, each of which is 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 a 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 transport transitory electrical or other signals. A non-transitory computer-readable medium includes media where data may be permanently stored and media where data may be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.

Terms used herein to describe the embodiments of the disclosure are not intended to limit and/or define the scope of the present invention. For example, unless otherwise defined, the technical terms or scientific terms used in the disclosure shall have the ordinary meaning understood by those with ordinary skills in the art to which the present invention belongs.

It should be understood that "first", "second" and similar words used in the disclosure do not express any order, quantity or importance, but are only used to distinguish different components. Similar words such as singular forms "a", "an" or "the" do not express a limitation of quantity, but express the existence of at least one of the referenced item, unless the context clearly dictates otherwise. For example, reference to "a component surface" includes reference to one or more of such surfaces.

As used herein, any reference to "an example" or "example", "an implementation" or "implementation", "an embodiment" or "embodiment" means that particular elements, features, structures or characteristics described in connection with the embodiment is included in at least one embodiment. The phrases "in one embodiment" or "in one example" appearing in different places in the specification do not necessarily refer to the same embodiment.

As used herein, "a portion of" something means "at least some of" the thing, and as such may mean less than all of, or all of, the thing. As such, "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. Accordingly, a set of items may be a single item or a collection of two or more items.

In this disclosure, to determine whether a specific condition is satisfied or fulfilled, expressions, such as "greater than/larger than" or "less than/smaller than" are used by way of example and expressions, such as "greater than or equal to" or "less than or equal to" are also applicable and not excluded. For example, a condition defined with "greater than or equal to" may be replaced by "greater than" (or vice-versa), a condition defined with "less than or equal to" may be replaced by "less than" (or vice-versa), etc.

It will be further understood that similar words such as the term "include" or "comprise" mean that elements or objects appearing before the word encompass the listed elements or objects appearing after the word and their equivalents, but other elements or objects are not excluded. Similar words such as "connect" or "connected" are not limited to physical or mechanical connection, but may include electrical connection, whether direct or indirect. "Upper", "lower", "left" and "right" are only used to express a relative positional relationship, and when an absolute position of the described object changes, the relative positional relationship may change accordingly.

The various embodiments discussed below for describing the principles of the disclosure in the patent document are for illustration only and should not be interpreted as limiting the scope of the disclosure in any way. Those skilled in the art will understand that the principles of the disclosure may be implemented in any suitably arranged wireless communication system. For example, although the following detailed description of the embodiments of the disclosure will be directed to LTE and/or 5G communication systems, those skilled in the art will understand that the main points of the disclosure may also be applied to other communication systems with similar technical backgrounds and channel formats with slight modifications without departing from the scope of the disclosure. The technical schemes of the embodiments of the present application may be applied to various communication systems, and for example, the communication systems may include global systems for mobile communications (GSM), code division multiple access (CDMA) systems, wideband code division multiple access (WCDMA) systems, general packet radio service (GPRS) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, universal mobile telecommunications system (UMTS), worldwide interoperability for microwave access (WiMAX) communication systems, 5th generation (5G) systems or new radio (NR) systems, etc. In addition, the technical schemes of the embodiments of the present application may be applied to future-oriented communication technologies.

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

The text and drawings are provided as examples only to help readers understand the disclosure. They are not intended and should not be interpreted as limiting the scope of the disclosure in any way. Although certain embodiments and examples have been provided, based on the content disclosed herein, it will be apparent to those skilled in the art that changes may be made to the illustrated embodiments and examples without departing from the scope of the disclosure.

The following FIGS. 1- 3B describe various embodiments implemented by using orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication technologies in wireless communication systems. The descriptions of FIGS. 1- 3B do not mean physical or architectural implications for the manner in which different embodiments may be implemented. Different embodiments of the disclosure may be implemented in any suitably arranged communication systems.

FIG. 1 illustrates an example wireless network 100 according to some embodiments of the disclosure. The embodiment of the wireless network 100 shown in FIG. 1 is for illustration only. Other embodiments of the wireless network 100 may be used without departing from the scope of the disclosure.

The wireless network 100 includes a gNodeB (gNB) 101, a gNB 102, and a gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one Internet Protocol (IP) network 130, such as the Internet, a private IP network, or other data networks.

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

gNB 102 provides wireless broadband access to the network 130 for a first plurality of User Equipments (UEs) within a coverage area 120 of gNB 102. The first plurality of UEs include a UE 111, which may be located in a Small Business (SB); a UE 112, which may be located in an enterprise (E); a 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); a UE 116, which may be a mobile device (M), such as a cellular phone, a wireless laptop computer, a wireless PDA, etc. GNB 103 provides wireless broadband access to network 130 for a second plurality of UEs within a coverage area 125 of gNB 103. The second plurality of UEs include a UE 115 and a UE 116. In some embodiments, one or more of gNBs 101-103 may communicate with each other and with UEs 111-116 using 5G, Long Term Evolution (LTE), LTE-A, WiMAX or other advanced wireless communication technologies.

The dashed lines show approximate ranges of the coverage areas 120 and 125, and the ranges are shown as approximate circles merely for illustration and explanation purposes. It should be clearly understood that the coverage areas associated with the gNBs, such as the coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on configurations of the gNBs and changes in the radio environment associated with natural obstacles and man-made obstacles.

As will be 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 disclosure. In some embodiments, one or more of gNB 101, gNB 102, and gNB 103 support codebook designs and structures for systems with 2D antenna arrays.

Although FIG. 1 illustrates an example of the wireless network 100, various changes may be made to FIG. 1. The wireless network 100 may include any number of gNBs and any number of UEs in any suitable arrangement, for example. Furthermore, gNB 101 may directly communicate with any number of UEs and provide wireless broadband access to the network 130 for those UEs. Similarly, each gNB 102-103 may directly communicate with the network 130 and provide direct wireless broadband access to the network 130 for the UEs. In addition, gNB 101, 102 and/or 103 may provide access to other or additional external networks, such as external telephone networks or other types of data networks.

FIGS. 2A and 2B illustrate example wireless transmission and reception paths according to some embodiments of the disclosure. In the following description, the transmission path 200 may be described as being implemented in a gNB, such as gNB 102, and the reception path 250 may be described as being implemented in a UE, such as UE 116. However, it should be understood that the reception path 250 may be implemented in a gNB and the transmission path 200 may be implemented in a UE. In some embodiments, the reception path 250 is configured to support codebook designs and structures for systems with 2D antenna arrays as described in embodiments of the disclosure.

The transmission path 200 includes a channel coding and modulation block 205, a Serial-to-Parallel (S-to-P) block 210, a size N Inverse Fast Fourier Transform (IFFT) block 215, a Parallel-to-Serial (P-to-S) block 220, a cyclic prefix addition block 225, and an up-converter (UC) 230. The reception path 250 includes a down-converter (DC) 255, a cyclic prefix removal block 260, a Serial-to-Parallel (S-to-P) block 265, a size N Fast Fourier Transform (FFT) block 270, a Parallel-to-Serial (P-to-S) block 275, and a channel decoding and demodulation block 280.

In the transmission path 200, the channel coding and modulation block 205 receives a set of information bits, applies coding (such as Low Density Parity Check (LDPC) coding), and modulates the input bits (such as using Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM)) to generate a sequence of frequency-domain modulated symbols. The Serial-to-Parallel (S-to-P) block 210 converts (such as demultiplexes) serial modulated symbols into parallel data to generate N parallel symbol streams, where N is a size of the IFFT/FFT used in gNB 102 and UE 116. The size N IFFT block 215 performs IFFT operations on the N parallel symbol streams to generate a time domain output signal. The Parallel-to-Serial block 220 converts (such as multiplexes) parallel time domain output symbols from the Size N IFFT block 215 to generate a serial time domain signal. The cyclic prefix addition block 225 inserts a cyclic prefix into the time domain signal. The up-converter 230 modulates (such as up-converts) the output of the cyclic prefix addition block 225 to an RF frequency for transmission via a wireless channel. The signal may also be filtered at a baseband before switching to the RF frequency.

The RF signal transmitted from gNB 102 arrives at UE 116 after passing through the wireless channel, and operations in reverse to those at gNB 102 are performed at UE 116. The down-converter 255 down-converts the received signal to a baseband frequency, and the cyclic prefix removal block 260 removes the cyclic prefix to generate a serial time domain baseband signal. The Serial-to-Parallel block 265 converts the time domain baseband signal into a parallel time domain signal. The Size N FFT block 270 performs an FFT algorithm to generate N parallel frequency-domain signals. The Parallel-to-Serial block 275 converts the parallel frequency-domain signal into a sequence of modulated data symbols. The channel decoding and demodulation block 280 demodulates and decodes the modulated symbols to recover the original input data stream.

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

Each of the components in FIGS. 2A and 2B may be implemented using only hardware, or using a combination of hardware and software/firmware. As a specific example, at least some of the components in FIGS. 2A and 2B may be implemented in software, while other components may be implemented in configurable hardware or a combination of software and configurable hardware. For example, the FFT block 270 and IFFT block 215 may be implemented as configurable software algorithms, in which the value of the size N may be modified according to the implementation.

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

Although FIGS. 2A and 2B illustrate examples of wireless transmission and reception paths, various changes may be made to FIGS. 2A and 2B. For example, various components in FIGS. 2A and 2B may be combined, further subdivided or omitted, and additional components may be added according to specific requirements. Furthermore, FIGS. 2A and 2B are intended to illustrate examples of types of transmission and reception paths that may be used in a wireless network. Any other suitable architecture may be used to support wireless communication in a wireless network.

FIG. 3A illustrates an example UE 116 according to some embodiments of the disclosure. The embodiment of UE 116 shown in FIG. 3A is for illustration only, and UEs 111-115 of FIG. 1 may have the same or similar configuration. However, a UE has various configurations, and FIG. 3A does not limit the scope of the disclosure to any specific implementation of the UE.

UE 116 includes an antenna 305, a radio frequency (RF) transceiver 310, a transmission (TX) processing circuit 315, a microphone 320, and a reception (RX) processing circuit 325. UE 116 also includes a speaker 330, a processor/controller 340, an input/output (I/O) interface 345, an input device(s) 350, a display 355, and a memory 360. The memory 360 includes an operating system (OS) 361 and one or more applications 362.

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

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

The processor/controller 340 may include one or more processors or other processing devices and execute an OS 361 stored in the memory 360 in order to control the overall operation of UE 116. For example, the processor/controller 340 may control the reception of forward channel signals and the transmission of backward channel signals through the RF transceiver 310, the RX processing circuit 325 and the TX processing circuit 315 according to well-known principles. In some embodiments, the processor/controller 340 includes at least one microprocessor or microcontroller.

The processor/controller 340 is also capable of executing other processes and programs residing in the memory 360, such as operations for channel quality measurement and reporting for systems with 2D antenna arrays as described in embodiments of the disclosure. The processor/controller 340 may move data into or out of the memory 360 as required by an execution process. In some embodiments, the processor/controller 340 is configured to execute the application 362 based on the 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 UE 116 with the capability to connect to other devices such as laptop computers and handheld computers. I/O interface 345 is a communication path between these accessories and the processor/controller 340.

The processor/controller 340 is also coupled to the input device(s) 350 and the display 355. An operator of UE 116 may input data into UE 116 using the input device(s) 350. The 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). The memory 360 is coupled to the processor/controller 340. A part of the memory 360 may include a random access memory (RAM), while another part of the memory 360 may include a flash memory or other read-only memory (ROM).

Although FIG. 3A illustrates an example of UE 116, various changes may be made to FIG. 3A. For example, various components in FIG. 3A may be combined, further subdivided or omitted, and additional components may be added according to specific requirements. As a specific example, the processor/controller 340 may be divided into a plurality of processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Furthermore, although FIG. 3A illustrates that the UE 116 is configured as a mobile phone or a smart phone, UEs may be configured to operate as other types of mobile or fixed devices.

In some implementations, two or more UEs 116 may communicate directly using one or more sidelink channels (for example, without using a base station as a medium for communication with each other). For example, the UE 116 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocol (which, for example, may include vehicle-to-vehicle (V2V) protocol, vehicle-to-infrastructure (V2I) protocol, etc.), mesh network, etc. In this case, the UE 116 may perform scheduling operations, resource selection operations, and/or other operations performed by the base station as described elsewhere herein. For example, the base station may configure the UE 116 via downlink control information (DCI), radio resource control (RRC) signaling, medium access control-control element (MAC-CE) or via system information (e.g., system information block (SIB)).

FIG. 3B illustrates an example gNB 102 according to some embodiments of the disclosure. The embodiment of gNB 102 shown in FIG. 3B is for illustration only, and other gNBs of FIG. 1 may have the same or similar configuration. However, a gNB has various configurations, and FIG. 3B does not limit the scope of the disclosure to any specific implementation of a gNB. It should be noted that gNB 101 and gNB 103 may include the same or similar structures as gNB 102.

As shown in FIG. 3B, gNB 102 includes a plurality of antennas 370a-370n, a plurality of RF transceivers 372a-372n, a transmission (TX) processing circuit 374, and a reception (RX) processing circuit 376. In certain embodiments, one or more of the plurality of antennas 370a-370n include a 2D antenna array. gNB 102 also includes a controller/processor 378, a memory 380, and a backhaul or network interface 382.

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

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

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

The controller/processor 378 is also capable of executing programs and other processes residing in the memory 380, such as a basic OS. The controller/processor 378 may also support channel quality measurement and reporting for systems with 2D antenna arrays as described in embodiments of the disclosure. In some embodiments, the controller/processor 378 supports communication between entities such as web RTCs. The controller/processor 378 may move data into or out of the memory 380 as required by an execution process.

The controller/processor 378 is also coupled to the backhaul or network interface 382. The backhaul or network interface 382 allows gNB 102 to communicate with other devices or systems through a backhaul connection or through a network. The backhaul or network interface 382 may support communication over any suitable wired or wireless connection(s). For example, when gNB 102 is implemented as a part of a cellular communication system, such as a cellular communication system supporting 5G or new radio access technology or NR, LTE or LTE-A, the backhaul or network interface 382 may allow gNB 102 to communicate with other gNBs through wired or wireless backhaul connections. When gNB 102 is implemented as an access point, the backhaul or network interface 382 may 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. The backhaul or network interface 382 includes any suitable structure that supports communication through a wired or wireless connection, such as an Ethernet or an RF transceiver.

The memory 380 is coupled to the controller/processor 378. A part of the memory 380 may include an RAM, while another part of the memory 380 may include a flash memory or other ROMs. In certain embodiments, a plurality of instructions, such as the BIS algorithm, are stored in the memory. The plurality of instructions are configured to cause the controller/processor 378 to execute the BIS process and decode the received signal after subtracting at least one interference signal determined by the BIS algorithm.

As will be described in more detail below, the transmission and reception paths of gNB 102 (implemented using RF transceivers 372a-372n, TX processing circuit 374 and/or RX processing circuit 376) support aggregated communication with FDD cells and TDD cells.

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

Those skilled in the art will understand that, "terminal" and "terminal device" as used herein include not only devices with wireless signal receiver which have no transmitting capability, but also devices with receiving and transmitting hardware which may carry out bidirectional communication on a bidirectional communication link. Such devices may include cellular or other communication devices with single-line displays or multi-line displays or cellular or other communication devices without multi-line displays; a PCS (personal communications service), which may combine voice, data processing, fax and/or data communication capabilities; a PDA (Personal Digital Assistant), which may include a radio frequency receiver, a pager, an internet/intranet access, a web browser, a notepad, a calendar and/or a GPS (Global Positioning System) receiver; a conventional laptop and/or palmtop computer or other devices having and/or including a radio frequency receiver. "Terminal" and "terminal device" as used herein may be portable, transportable, installed in vehicles (aviation, sea transportation and/or land), or suitable and/or configured to operate locally, and/or in distributed form, operate on the earth and/or any other position in space. "Terminal" and "terminal device" as used herein may also be a communication terminal, an internet terminal, a music/video playing terminal, such as a PDA, a MID (Mobile Internet Device) and/or a mobile phone with music/video playing functions, a smart TV, a set-top box and other devices.

With the rapid development of information industry, especially the increasing demand from mobile Internet and internet of things (IoT), it brings unprecedented challenges to the future mobile communication technology. In order to meet the unprecedented challenges, the communication industry and academia have carried out extensive research on the fifth generation (5G) mobile communication technology to face the 2020s. At present in ITU report ITU-R M.[IMT.VISION], the framework and overall goals of the future 5G has been discussed, in which the demand outlook, application scenarios and important performance indicators of 5G are described in detail. With respect to new requirements in 5G, ITU report ITU-R M.[IMT.FUTURE TECHNOLOGY TRENDS] provides information related to the technology trends of 5G, aiming at solving significant problems such as significantly improved system throughput, consistent user experience, scalability to support IoT, delay, energy efficiency, cost, network flexibility, support of emerging services and flexible spectrum utilization. In 3GPP (3rd Generation Partnership Project), the first stage of 5G is already in progress. To support more flexible scheduling, the 3GPP decides to support variable hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback delay in 5G. In existing Long Term Evolution (LTE) systems, a time from reception of downlink data to uplink transmission of HARQ-ACK is fixed. For example, in Frequency Division Duplex (FDD) systems, the delay is 4 subframes. In Time Division Duplex (TDD) systems, a HARQ-ACK feedback delay is determined for a corresponding downlink subframe based on an uplink and downlink configuration. In 5G systems, whether FDD or TDD systems, for a determined downlink time unit (for example, a downlink slot or a downlink mini slot; for another example, a PDSCH time unit), the uplink time unit (for example, a PUCCH time unit) that may feedback HARQ-ACK is variable. For example, the delay of HARQ-ACK feedback may be dynamically indicated by physical layer signaling, or different HARQ-ACK delays may be determined based on factors such as different services or user capabilities.

The 3GPP has defined three directions of 5G application scenarios-eMBB (enhanced mobile broadband), mMTC (massive machine-type communication) and URLLC (ultra-reliable and low-latency communication). The eMBB scenario aims to further improve data transmission rate on the basis of the existing mobile broadband service scenario, so as to enhance user experience and pursue ultimate communication experience between people. mMTC and URLLC are, for example, the application scenarios of the Internet of Things, but their respective emphases are different: mMTC being mainly information interaction between people and things, while URLLC mainly reflecting communication requirements between things.

In some cases, there may be some padding bits (for example, NACK) in a HARQ-ACK codebook. The padding bits (e.g., NACK) may be called placeholder bits. The padding NACK may increase a number of information bits in the HARQ-ACK codebook, resulting in the need for more resources to transmit HARQ-ACK information. How to reduce the number of bits in the HARQ-ACK codebook is a problem to be solved. Therefore, an enhanced HARQ-ACK codebook generation method is needed.

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

In embodiments of the disclosure, for the 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. For another example, the embodiments of the disclosure may be applicable to the scenario of sidelink communication, in which case, the first transceiving node may be a UE, and the second transceiving node may be another UE. Therefore, the first transceiving node and the second transceiving node may each be any suitable communication node. In the following description, the base station is taken as an example (but not limited thereto) to illustrate the first transceiving node, and the UE is taken as an example (but not limited thereto) to illustrate the second transceiving node.

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

In the following description of the disclosure, higher layer signaling may be signaling corresponding to at least one or a combination of one or more of the following signaling.

- MIB (master information block)

- SIB (system information block) or SIB X (X = 1,2, ...)

- RRC signaling

- MAC CE

Physical layer (Layer 1 (L1)) signaling may be signaling corresponding to at least one or a combination of one or more of the following signaling.

- PDCCH (physical downlink control channel)

- DCI (downlink control information)

- UE-specific DCI

- group common DCI

- common DCI

- scheduling DCI (for example, DCI for scheduling downlink or uplink data)

- non-scheduling DCI (for example, DCI other than DCI for scheduling downlink or uplink data)

- PUCCH (physical uplink control channel)

- UCI (uplink control information)

In embodiments of the disclosure, uplink control signaling may include physical layer signaling and/or higher layer signaling. As described above, the physical layer signaling may include UCI and/or PUCCH, and the higher layer signaling may include RRC signaling and/or a MAC CE.

In embodiments of the disclosure, downlink control signaling may include physical layer signaling and/or higher layer signaling. As mentioned above, the physical layer signaling may include one or more of PDCCH, DCI, UE-specific DCI, group common DCI, common DCI, scheduling DCI (for example, DCI for scheduling downlink or uplink data), and non-scheduling DCI, and the higher layer signaling may include one or more of a MIB, a SIB or SIB X (X = 1, 2, ...), RRC signaling or a MAC CE. Therefore, "configuring or indicating X through downlink control signaling" will be understood as configuring or indicating X through physical layer signaling, or configuring or indicating X through higher layer signaling, or configuring or indicating X through a combination of higher layer signaling and physical layer signaling.

FIG. 4 illustrates a block diagram of a first transceiving node 400 according to some embodiments of the disclosure.

Referring to FIG. 4, the first transceiving node 400 may include a transceiver 401 and a controller 402.

The transceiver 401 may be configured to transmit first data and/or first control signaling to a second transceiving node, and/or receive second data and/or second control signaling from the second transceiving node in a 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 first transceiving node 400, including controlling the transceiver 401 to transmit the first data and/or the first control signaling to the second transceiving node and receive the second data and/or the second control signaling from the second transceiving node in the time unit.

In some implementations, the controller 402 may be configured to perform one or more of operations in methods of various embodiments described below, for example, operations that may be performed by a base station.

In the following description, the base station is taken as an example (but not limited thereto) to illustrate the first transceiving node, and the UE is taken as an example (but not limited thereto) to illustrate the second transceiving node. Downlink data (but not limited thereto) is used to illustrate the first data. Downlink control signaling (but not limited thereto) is used to illustrate the first control signaling. Uplink control signaling (but not limited thereto) is used to illustrate the second control signaling.

Herein, depending on the network type, the term "base station" or "BS" may refer to any component (or a set of components) configured to provide wireless access to a network, such as a Transmission Point (TP), a Transmission and Reception Point (TRP), an evolved base station (eNodeB or eNB), a 5G base station (gNB), a macrocell, a femtocell, a WiFi access point (AP), or other wirelessly enabled devices. Base stations may provide wireless access in accordance with one or more wireless communication protocols, e.g., 5G 3GPP new radio (NR) interface/access, Long Term Evolution (LTE), LTE advanced (LTE-A), High Speed Packet Access (HSPA), Wi-Fi 802.11a/b/g/n/ac, etc.

FIG. 5 illustrates a block diagram of a second transceiving node according to some embodiments of the disclosure.

Referring to FIG. 5, the second transceiving node 500 may include a transceiver 501 and a controller 502.

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

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

In some implementations, the controller 502 may be configured to perform one or more of operations in methods of various embodiments described below, for example, operations that may be performed by a terminal (UE).

In implementations described in connection with FIG. 4 or 5, the first data may be data transmitted by the first transceiving node to the second transceiving node. In the following examples, downlink data carried by a PDSCH (Physical Downlink Shared Channel) is taken as an example (but not limited thereto) to illustrate the first data.

In implementations described in connection with FIG. 4 or 5, the second data may be data transmitted by the second transceiving node to the first transceiving node. In the following examples, uplink data carried by a PUSCH (Physical Uplink Shared Channel) is taken as an example (but not limited thereto) to illustrate the second data.

In implementations described in connection with FIG. 4 or 5, the first control signaling may be control signaling transmitted by the first transceiving node to the second transceiving node. In the following examples, downlink control signaling is taken as an example (but not limited thereto) to illustrate the first control signaling. 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, and the DCI may also be common DCI. The common DCI may be DCI common to a part of UEs, such as group common DCI, and the common DCI may also be DCI common to all of the UEs. The DCI may be uplink DCI (e.g., DCI for scheduling a PUSCH) and/or downlink DCI (e.g., DCI for scheduling a PDSCH).

In implementations described in connection with FIG. 4 or 5, the second control signaling may be control signaling transmitted by the second transceiving node to the first transceiving node. In the following examples, uplink control signaling is taken as an example (but is not limited thereto) to illustrate the second control signaling. The uplink control signaling may be UCI (Uplink Control Information) carried by a PUCCH (Physical Uplink Control Channel) and/or control signaling carried by a PUSCH (Physical Uplink Shared Channel). A type of UCI may include one or more of: HARQ-ACK information, SR (Scheduling Request), LRR (Link Recovery Request), CSI (Chanel State Information), or CG (Configured Grant) UCI. In embodiments of the disclosure, when UCI is carried by a PUCCH, the UCI may be used interchangeably with the PUCCH.

In some embodiments, a PUCCH with an SR may be a PUCCH with a positive SR and/or a negative SR. The SR may be the positive SR and/or the negative SR.

In some embodiments, the CSI may also be Part 1 CSI and/or Part 2 CSI.

In implementations described in connection with FIG. 4 or 5, a first time unit is a time unit in which the first transceiving node transmits the first data and/or the first control signaling. In some examples, a downlink time unit or downlink slot may be taken as an example (but not limited thereto) to illustrate the first time unit.

In implementations described in connection with FIG. 4 or 5, a 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 examples, an uplink time unit or uplink slot or PUCCH slot or PCell (Primary Cell) slot or PUCCH slot on PCell is taken as an example (but not limited thereto) to illustrate the second time unit. The "PUCCH slot" may be understood as a PUCCH transmission slot.

In embodiments of the disclosure, a time unit (for example, the first time unit or the second time unit) may be one or more slots, one or more subslots, one or more OFDM symbols, one or more spans, or one or more subframes.

FIG. 6 illustrates a flowchart of a method 600 performed by a base station according to some embodiments of the disclosure.

Referring to FIG. 6, in operation S610, the base station transmits downlink data and/or downlink control signaling.

In operation S620, the base station receives uplink data and/or uplink control signaling from a UE in a time unit.

In some implementations, operations S610 and/or S620 may be performed based on the methods described according to various embodiments of the disclosure (e.g., various methods/manners described below).

In some implementations, the method 600 may omit one or more of operation S610 or S620, or may include additional operations, for example, the operations performed by the base station based on the methods described according to various embodiments of the disclosure (e.g., various methods/manners described below).

FIG. 7 illustrates a flowchart of a method 700 performed by a UE according to embodiments of the disclosure.

Referring to FIG. 7, in operation S710, the UE may receive downlink (DL) data (e.g., downlink data carried by a PDSCH) and/or downlink control signaling from a base station. For example, the UE may receive the downlink data and/or the downlink control signaling from the base station based on predefined rules and/or received configuration parameters.

In operation S720, the UE determines uplink (UL) data and/or uplink control signaling, a transmission power of the uplink data and/or uplink control signaling, and a second time unit based on the downlink data and/or the downlink control signaling.

In operation S730, the UE transmits the uplink data and/or the uplink control signaling to the base station in the second time unit based on the determined transmission power.

[HARQ/ scheduling general timing]

In some implementations, operations S710 and/or S720 and/or S730 may be performed based on the methods described according to various embodiments of the disclosure (e.g., various methods/manners described below).

In some implementations, the method 700 may omit one or more of operation S710, S720 or S730, or may include additional operations, for example, the operations performed by the UE (terminal) based on the methods described according to various embodiments of the disclosure (e.g., various methods/manners described below).

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

In some implementations, the downlink control signaling may include DCI carried by a PDCCH and/or control signaling carried by 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 FIGS. 8A-8C.

In an example, the UE receives the DCI and receives the PDSCH based on time domain resources indicated by the DCI. For example, a parameter K0 may be used to represent a time interval between the PDSCH scheduled by the DCI and the PDCCH carrying the DCI, and K0 may be in units of slots. For example, FIG. 8A gives an example in which K0 = 1. In the example illustrated in FIG. 8A, the time interval from the PDSCH scheduled by the DCI to the PDCCH carrying the DCI is one slot. In an embodiment of the disclosure, "a UE receives DCI" may mean that "the UE detects the DCI."

In another example, the UE receives the DCI and transmits the PUSCH based on time domain resources indicated by the DCI. For example, a timing parameter K2 may be used to represent a time interval between the PUSCH scheduled by the DCI and the PDCCH carrying the DCI, and K2 may be in units of slots. For example, FIG. 8B gives an example in which K2 = 1. In the example illustrated in FIG. 8B, the time interval between the PUSCH scheduled by the DCI and the PDCCH carrying the DCI is one slot. K2 may also represent a time interval between a PDCCH for activating a CG (configured grant) PUSCH and the first activated CG PUSCH. In examples of the disclosure, unless otherwise specified, the PUSCH may be a dynamically scheduled PUSCH (e.g., scheduled by DCI) (e.g., may be referred to as DG (dynamic grant) PUSCH, in an embodiment of the disclosure) and/or a PUSCH not scheduled by DCI (e.g., CG PUSCH).

In yet another example, the UE receives the PDSCH, and may transmit HARQ-ACK information for the PDSCH reception in a PUCCH in the second time unit. For example, a timing parameter (which may also be referred to as a timing value) K1 (e.g., the higher layer parameter dl-DataToUL-ACK) may be used to represent a time interval between the PUCCH for transmitting the HARQ-ACK information for the PDSCH reception and the PDSCH, and K1 may be in units of second time units, such as slots or subslots. In a case where K1 is in units of slots, the time interval is a value of a slot offset between the PUCCH for feeding back the HARQ-ACK information for the PDSCH reception and the PDSCH, and K1 may be referred to as a slot timing value. For example, FIG. 8A gives an example in which K1 = 3. In the example illustrated in FIG. 8A, the time interval between the PUCCH for transmitting the HARQ-ACK information for the PDSCH reception and the PDSCH is 3 slots. It should be noted that in embodiments of the disclosure, the timing parameter K1 may be used interchangeably with a timing parameter K₁, the timing parameter K0 may be used interchangeably with a timing parameter K₀, and the timing parameter K2 may be used interchangeably with a timing parameter K₂.

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

In embodiments of the disclosure, HARQ-ACK may be HARQ-ACK for a SPS PDSCH reception (e.g., HARQ-ACK not indicated by DCI) and/or HARQ-ACK indicated by a DCI format (e.g., HARQ-ACK for a PDSCH reception scheduled by a DCI format).

In yet another example, the UE receives the DCI (e.g., DCI indicating SPS (Semi-Persistent Scheduling) PDSCH release (deactivation)), and may transmit HARQ-ACK information for the DCI in the PUCCH in the second time unit. For example, the timing parameter K1 may be used to represent a time interval between the PUCCH for transmitting the HARQ-ACK information for the DCI and the DCI, and K1 may be in units of second time units, such as slots or subslots. For example, FIG. 8C gives an example in which K1 = 3. In the example of FIG. 8C, the time interval between the PUCCH for transmitting the HARQ-ACK information for the DCI and the DCI is 3 slots. For example, the timing parameter K1 may be used to represent a time interval between a PDCCH reception carrying DCI indicating SPS PDSCH release (deactivation) and the PUCCH feeding back HARQ-ACK for the PDCCH reception.

In some implementations, in step S520, the UE may report (or signal/transmit) a UE capability to the base station or indicate the UE capability. For example, the UE reports (or signals/transmits) the UE capability to the base station by transmitting the PUSCH. In this case, UE capability information is included in the PUSCH transmitted by the UE.

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

In some implementations, downlink channels (downlink resources) may include PDCCHs and/or PDSCHs. Uplink channels (uplink resources) may include PUCCHs and/or PUSCHs.

[Two levels of priorities]

In some implementations, the UE may be configured with two levels of priorities for uplink transmission (for example, the UE is configured with the higher layer parameter PUCCH-ConfigurationList). For example, the UE may be configured to multiplex UCIs with different priorities via higher layer signaling (e.g., via higher layer parameter uci-MuxWithDiffPrio), otherwise (e.g., if the UE is not configured to multiplex UCIs with different priorities), the UE performs prioritization for PUCCHs and/or PUSCHs with different priorities. For example, the two levels of priorities may include a first priority and a second priority which are different from each other. In an example, the first priority may be higher than the second priority, that is, the first priority is the higher priority, and the second priority is the lower priority. In another example, the first priority may be lower than the second priority. However, embodiments of the disclosure are not limited to this, and for example, the UE may be configured with more than two levels of priorities. For the sake of convenience, in embodiments of the disclosure, description will be made considering that the first priority is higher than the second priority. It should be noted that all embodiments of the disclosure are applicable to situations where the first priority may be higher than the second priority; all embodiments of the disclosure are applicable to situations where the first priority may be lower than the second priority; and all embodiments of the disclosure are applicable to situations where the first priority may be equal to the second priority. In some embodiments of the disclosure, the terms "first priority", "higher priority", "greater priority index" and "priority index 1" may be used interchangeably. In embodiments of the disclosure, the terms "second priority", "lower priority", "smaller priority index" and "priority index 0" may be used interchangeably.

For example, multiplexing of multiple PUCCHs and/or PUSCHs overlapping in time domain may include multiplexing of UCI of the PUCCH in a PUCCH or PUSCH.

For example, prioritizing of two PUCCHs and/or PUSCHs overlapping in time domain by the UE may include that the UE transmits the PUCCH or the PUSCH with the higher priority and/or the UE does not transmit the PUCCH or the PUSCH with the lower priority..

[Subslot]

In some implementations, the UE may be configured with a subslot-based PUCCH transmission. For example, a subslot length parameter (which may also be referred to as a parameter with respect to a subslot length in embodiments of the disclosure) (e.g., the higher layer parameter subslotLengthForPUCCH) of each PUCCH configuration parameter of the first PUCCH configuration parameter and the second PUCCH configuration parameter may be 7 OFDM symbols or 6 OFDM symbols or 2 OFDM symbols. Subslot configuration length parameters in different PUCCH configuration parameters may be configured separately. If no subslot length parameter is configured in a PUCCH configuration parameter, the scheduling time unit of the PUCCH configuration parameter is one slot by default. If a subslot length parameter is configured in the PUCCH configuration parameter, the scheduling time unit of the PUCCH configuration parameter is L (L is the configured subslot configuration length) OFDM symbols.

The mechanism of a slot-based PUCCH transmission is basically the same as that of a subslot-based PUCCH transmission. In the disclosure, a slot may be used to represent a PUCCH occasion unit; for example, if the UE is configured with subslots, a slot which is a PUCCH occasion unit may be replaced with a subslot. For example, it may be specified by protocols that if the UE is configured with the subslot length parameter (e.g., the higher layer parameter subslotLengthForPUCCH), unless otherwise indicated, a number of symbols included in the slot of the PUCCH transmission is indicated by the subslot length parameter.

For example, if the UE is configured with the subslot length parameter, and a subslot n is the last uplink subslot overlapping with a PDSCH reception or PDCCH reception (e.g., indicating SPS PDSCH release, and/or indicating SCell dormancy, and/or triggering a Type-3 HARQ-ACK codebook report and without scheduling a PDSCH reception), then HARQ-ACK information for the PDSCH reception or PDCCH reception is transmitted in an uplink subslot n+k, where k is determined by the timing parameter K1 (the definition of the timing parameter K1 may refer to the previous description). For another example, if the UE is not configured with the subslot length parameter, and a slot n is the last uplink slot overlapping with a downlink slot where the PDSCH reception or PDCCH reception is located, then the HARQ-ACK information for the PDSCH reception or PDCCH reception is transmitted in an uplink slot n+k, where K is determined by the timing parameter K1.

[Multicast Service (MBS)]

In embodiments of the disclosure, unicast may refer to a manner in which a network communicates with a UE, and multicast (or groupcast) may refer to a manner in which a network communicates with multiple UEs. For example, a unicast PDSCH may be a PDSCH received by one UE, and scrambling of the PDSCH may be based on a Radio Network Temporary Identifier (RNTI) specific to the UE, e.g., Cell-RNTI (C-RNTI). A multicast PDSCH may be a PDSCH received by more than one UE simultaneously, and scrambling of the multicast PDSCH may be based on a UE-group common RNTI. For example, the UE-group common RNTI for scrambling the multicast PDSCH may include an RNTI (which may be referred to as Group RNTI (G-RNTI) in embodiments of the disclosure) for scrambling of a dynamically scheduled multicast transmission (e.g., PDSCH) or an RNTI (which may be referred to as group configured scheduling RNTI (G-CS-RNTI) in embodiments of the disclosure) for scrambling of a multicast SPS transmission (e.g., SPS PDSCH). UCI of the unicast PDSCH may include HARQ-ACK information, an SR, or CSI of the unicast PDSCH reception. UCI of the multicast PDSCH may include HARQ-ACK information of the multicast PDSCH reception. In embodiments of the disclosure, "multicast" may also be replaced by "broadcast"

[HARQ-ACK codebook]

In some implementations, a HARQ-ACK codebook may include HARQ-ACK information (which may also be referred to as "HARQ-ACK information bit") for one or more PDSCHs and/or DCI. If the HARQ-ACK information for the one or more PDSCHs and/or DCI is transmitted in a second time unit (e.g., multiplexed in a same second time unit), the UE may generate the HARQ-ACK codebook based on a predefined rule. For example, if a PDSCH is successfully decoded, the HARQ-ACK information for the PDSCH reception is positive ACK. The positive ACK may be represented by 1 in the HARQ-ACK codebook, for example. If a PDSCH is not successfully decoded, the HARQ-ACK information for the PDSCH reception is Negative ACK (NACK). The NACK may be represented by 0 in the HARQ-ACK codebook, for example. For example, the UE may generate the HARQ-ACK codebook based on pseudo code specified by protocols. In an example, if the UE receives a DCI format that indicates 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 that indicates secondary cell dormancy, the UE transmits HARQ-ACK information (ACK) for the DCI format. In yet another example, if the UE receives a DCI format that indicates to transmit HARQ-ACK information (e.g., a Type-3 HARQ-ACK codebook) of all HARQ-ACK processes of all configured serving cells, the UE transmits the HARQ-ACK information of all the HARQ-ACK processes of all the configured serving cells. In order to reduce a size of the Type-3 HARQ-ACK codebook, in an enhanced Type-3 HARQ-ACK codebook, the UE may transmit HARQ-ACK information of a specific HARQ-ACK process of a specific serving cell based on an indication of the DCI. In yet another example, if the UE receives a DCI format that schedules a PDSCH, the UE transmits HARQ-ACK information for the PDSCH reception. In yet another example, the UE receives a SPS PDSCH, and the UE transmits HARQ-ACK information for the SPS PDSCH reception. In yet another example, if the UE is configured by higher layer signaling to receive a SPS PDSCH, the UE transmits HARQ-ACK information for the SPS PDSCH reception. The reception of the SPS PDSCH configured by higher layer signaling may be cancelled by other signaling. In yet another example, if at least one uplink symbol (e.g., OFDM symbol) of the UE in a semi-static frame structure configured by higher layer signaling overlaps with a symbol of the SPS PDSCH reception, the UE does not receive the SPS PDSCH. In yet another example, if the UE is configured by higher layer signaling to receive a SPS PDSCH according to a predefined rule, the UE transmits HARQ-ACK information for the SPS PDSCH reception. It should be noted that, in embodiments of the disclosure, "'A' overlaps with 'B'" may mean that 'A' at least partially overlaps with 'B'. That is, "'A' overlaps with 'B'" includes a case where 'A' completely overlaps with 'B'. "'A' overlaps with 'B'" may mean that 'A' overlaps with 'B' in time domain and/or 'A' overlaps with 'B' in frequency domain.

In some implementations, if HARQ-ACK information transmitted in a same second time unit (or, multiplexed in a same second time unit) does not include HARQ-ACK information for any DCI format, nor does it include HARQ-ACK information for a dynamically scheduled PDSCH (e.g., a PDSCH scheduled by a DCI format) and/or DCI, or the HARQ-ACK information transmitted in the same second time unit (or, multiplexed in a same second time unit) only includes HARQ-ACK information for one or more SPS PDSCHs receptions, the UE may generate HARQ-ACK information (e.g., HARQ-ACK information only for SPS PDSCH receptions) according to a rule for generating a HARQ-ACK codebook for SPS PDSCHs. The UE may multiplex the HARQ-ACK information only for SPS PDSCH receptions in a specific PUCCH resource. For example, if the UE is configured with a PUCCH list parameter for SPS (e.g., SPS-PUCCH-AN-List), the UE multiplexes the HARQ-ACK information only for SPS PDSCH receptions in a PUCCH of a PUCCH list for SPS. For example, the UE determines a PUCCH resource in the PUCCH list for the SPS according to a number of HARQ-ACK information bits. If the UE is not configured with the PUCCH list parameter for SPS, the UE multiplexes the HARQ-ACK information only for SPS PDSCH receptions in a PUCCH resource specific to SPS HARQ-ACK (for example, the PUCCH resource is configured by the parameter n1PUCCH-AN).

In some implementations, if the HARQ-ACK information transmitted in the same second time unit (or multiplexed in a same second time unit) includes HARQ-ACK information for a DCI format, and/or a dynamically scheduled PDSCH (e.g., a PDSCH scheduled by a DCI format), the UE may generate HARQ-ACK information according to a rule for generating a HARQ-ACK codebook for a dynamically scheduled PDSCH and/or a DCI format. For example, the UE may determine to generate a semi-static HARQ-ACK codebook (e.g., Type-1 HARQ-ACK codebook) or a dynamic HARQ-ACK codebook (e.g., Type-2 HARQ-ACK codebook) according to a PDSCH HARQ-ACK codebook configuration parameter (e.g., the higher layer parameter pdsch-HARQ-ACK-Codebook). The dynamic HARQ-ACK codebook may also be an enhanced dynamic HARQ-ACK codebook (e.g., Type-2 HARQ-ACK codebook based on grouping and HARQ-ACK retransmission). The UE may multiplex the HARQ-ACK information in a PUCCH resource for HARQ-ACK associated with dynamically scheduling, which may be configured in a resource set list parameter (e.g., the parameter resourceSetToAddModList). The UE determines a PUCCH resource set (e.g., the parameter PUCCH-ResourceSet) in a resource set list according to a number of HARQ-ACK information bits, and the PUCCH resource may be determined as a PUCCH in the PUCCH resource set according to a PRI (PUCCH Resource Indicator) field indication in the last DCI format.

In some implementations, if the HARQ-ACK information transmitted in the same second time unit (or multiplexed in a same second time unit) includes only HARQ-ACK information for SPS PDSCHs (e.g., a PDSCH not scheduled by a DCI format), the UE may generate the HARQ-ACK codebook according to a rule for generating a HARQ-ACK codebook for SPS PDSCH receptions (e.g., the pseudo code of a HARQ-ACK codebook for SPS PDSCH receptions).

[Type-1 HARQ-ACK codebook]

The semi-static HARQ-ACK codebook (e.g., Type-1 HARQ-ACK codebook), may determine the size of the HARQ-ACK codebook and an order of HARQ-ACK information bits according to a semi-statically configured parameter (e.g., a parameter configured by higher layer signaling).

For a serving cell c, an active downlink BWP (bandwidth part), and an active uplink BWP, the UE determines a set of occasions for candidate PDSCH receptions for which the UE may transmit corresponding HARQ-ACK information in a PUCCH in an uplink slot .

may be determined by at least one of:

a) a set of HARQ-ACK slot timing values K1 associated with the active uplink BWP on a primary cell or PUCCH-sScell (PUCCH switching SCell);

b) a set of row indexes of a time domain resource allocation (TDRA) table associated with the downlink active BWP;

c) , where is the configuration of a downlink subcarrier spacing (SCS) of the downlink active BWP, and is the configuration of an uplink subcarrier spacing of the uplink active BWP.

d) a semi-static uplink and downlink frame structure configuration, such as the parameter tdd-UL-DL-ConfigurationCommon and the parameter tdd-UL-DL-ConfigurationDedicated.

e) a downlink slot offset parameter (e.g., the higher layer parameter ) for the serving cell c and its corresponding slot offset SCS (e.g., the higher layer parameter ), and a slot offset parameter (e.g., the higher layer parameter ) for a primary cell and its corresponding slot offset SCS (e.g., the higher layer parameter ).

The set of the parameter K1 is used to determine a candidate uplink slot, and then determine candidate downlink slots according to the candidate uplink slot. The candidate downlink slots satisfy at least one of the following conditions: (i) if the time unit of the PUCCH is a subslot, the end of at least one candidate PDSCH reception in the candidate downlink slots overlaps with the candidate uplink slot in time domain; or (ii) if the time unit of the PUCCH is a slot, the end of the candidate downlink slots overlaps with the candidate uplink slot in time domain. It should be noted that, in embodiments of the disclosure, a starting symbol may be used interchangeably with a starting position, and an end symbol may be used interchangeably with an end position. In some implementations, the starting symbol may be replaced by the end symbol, and/or the end symbol may be replaced by the starting symbol.

A number of PDSCHs in a candidate downlink slot for which HARQ-ACK needs to be fed back is determined by a maximum value of a number of non-overlapping valid PDSCHs in the downlink slot (e.g., the valid PDSCHs may be PDSCHs that do not overlap with semi-statically configured uplink symbols). Time domain resources occupied by the PDSCHs may be determined by (i) a time domain resource allocation table configured by higher layer signaling (in embodiments of the disclosure, it may also be referred to as a table associated with time domain resource allocation) and (ii) a certain row in the time domain resource allocation table dynamically indicated by a DCI. Each row in the time domain resource allocation table may define information with respect to time domain resource allocation. For example, for the time domain resource allocation table, an indexed row defines a timing value (e.g., time unit (e.g., slot) offset (e.g., K0)) between a PDCCH and a PDSCH, and a start and length indicator (SLIV), or directly defines a starting symbol and allocation length. For example, for the first row of the time domain resource allocation table, a starting OFDM symbol is 0 and an OFDM symbol length is 4; for the second row of the time domain resource allocation table, the starting OFDM symbol is 4 and the OFDM symbol length is 4; and for the third row of the time domain resource allocation table, the starting OFDM symbol is 7 and the OFDM symbol length is 4. The DCI for scheduling the PDSCH may indicate any row in the time domain resource allocation table. When all OFDM symbols in the downlink slot are downlink symbols, a maximum number of non-overlapping valid PDSCHs in the downlink slot is 2. At this time, the Type-1 HARQ-ACK codebook may need to feed back HARQ-ACK information for two PDSCHs in the downlink slot on the serving cell.

FIGS. 9A and 9B illustrate examples of time domain resource allocation (TDRA) tables. Specifically, FIG. 9A illustrates a time domain resource allocation table in which one PDSCH is scheduled in one row, and FIG. 9B illustrates a time domain resource allocation table in which multiple PDSCHs are scheduled in one row. Referring to FIG. 9A, each row corresponds to a set of {K0, mapping type, SLIV}, which includes a timing parameter K0 value, a mapping type, and an SLIV. Referring to FIG. 9B, unlike FIG. 9A, each row corresponds to multiple sets of {K0, mapping type, SLIV}.

[Type-2 HARQ-ACK codebook]

In some implementations, the dynamic HARQ-ACK codebook (e.g., Type-2 HARQ-ACK codebook) and/or the enhanced dynamic HARQ-ACK codebook (e.g., Type-2 HARQ-ACK based on grouping and HARQ-ACK retransmission) may determine a size and an order of the HARQ-ACK codebook according to an assignment indicator. For example, the assignment indicator may be a DAI (Downlink Assignment Indicator). In the following embodiments, the assignment indicator as the DAI is taken as an example for illustration. However, the embodiments of the disclosure are not limited thereto, and any other suitable assignment indicator may be adopted.

In some implementations, a 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 an accumulative number of at least one of DCI scheduling PDSCH(s), DCI indicating SPS PDSCH release (deactivation), or DCI indicating secondary cell dormancy. For example, the accumulative number may be an accumulative number up to the current serving cell and/or the current time unit. For example, the C-DAI may refer to: an accumulative number of {serving cell, time unit} pair(s) scheduled by PDCCH(s) up to the current time unit within a time window (which may also include a number of PDCCHs (e.g., PDCCHs indicating SPS release and/or PDCCHs indicating secondary cell dormancy)); or an accumulative number of PDCCH(s) up to the current time unit; or an accumulative number of PDSCH transmission(s) up to the current time unit; or an accumulative number of {serving cell, time unit} pair(s) in which PDSCH transmission(s) related to PDCCH(s) (e.g., scheduled by the PDCCH(s)) and/or PDCCH(s) (e.g., PDCCH indicating SPS release and/or PDCCH indicating secondary cell dormancy) is present, up to the current serving cell and/or the current time unit; or an accumulative number of PDSCH(s) with corresponding PDCCH(s) and/or PDCCHs (e.g., PDCCHs indicating SPS release and/or PDCCHs indicating secondary cell dormancy) already scheduled by a base station up to the current serving cell and/or the current time unit; or an accumulative number of PDSCHs (the PDSCHs are PDSCHs with corresponding PDCCHs) already scheduled by the base station up to the current serving cell and/or the current time unit; or an accumulative number of time units with PDSCH transmissions (the PDSCHs are PDSCHs with corresponding PDCCHs) already scheduled by the base station up to the current serving cell and/or the current time unit. The order of each bit in the HARQ-ACK codebook corresponding to at least one of PDSCH reception(s), DCI(s) indicating SPS PDSCH release (deactivation), or DCI(s) indicating secondary cell dormancy may be determined by the time when the first DAI is received and the information of the first DAI. The first DAI may be included in a downlink DCI format.

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

In the following examples, the first DAI as the C-DAI and the second DAI as the T-DAI are taken as an example (but not limited thereto) for illustration.

For example, when the C-DAI or T-DAI is 1, 5 or 9, as shown in Table 1, all of the DAI field are indicated with "00", and the value of or is represented as "1" by the equation in Table 1. Y may represent the value of the DAI corresponding to the number of DCIs actually transmitted by the base station (the value of the DAI before conversion by the equation in the table).

For example, in case that the C-DAI or T-DAI in the DCI is 1 bit, values greater than 2 may be represented by equations in Table 2.

[HARQ feedback mode]

In some implementations, whether to feed back HARQ-ACK information may be configured by higher layer parameters or dynamically indicated by a DCI. The mode of feeding back (or reporting) the HARQ-ACK information (HARQ-ACK feedback mode or HARQ-ACK reporting mode) may also be at least one of the following modes.

- HARQ-ACK feedback mode 1: transmitting ACK or NACK (ACK/NACK). For example, for a PDSCH reception, if the UE decodes a corresponding transport block (TB) correctly, the UE transmits ACK; and/or, if the UE does not decode the corresponding transport block correctly, the UE transmits NACK. For example, a HARQ-ACK information bit of the HARQ-ACK information provided according to the HARQ-ACK feedback mode 1 is an ACK value or a NACK value.

- HARQ-ACK feedback mode 2: transmitting NACK only (NACK-only). For example, for a PDSCH reception, if the UE decodes the corresponding transport block correctly, the UE does not transmit the HARQ-ACK information; and/or, if the UE does not decode the corresponding transport block correctly, the UE transmits NACK. For example, at least one HARQ-ACK information bit of the HARQ-ACK information provided according to the HARQ-ACK feedback mode 2 is a NACK value. For example, for the HARQ-ACK feedback mode 2, the UE does not transmit a PUCCH that would include only HARQ-ACK information with ACK values.

[Channel collision]

In some implementations, a PUSCH conflicting/colliding with other physical channel(s) may be at least one of:

- the PUSCH overlapping in time domain with other PUSCH(s) and/or PUCCH(s) and/or PDSCH(s) and/or PDCCH(s) on a same serving cell; or

- the PUSCH overlapping in time domain with a PUCCH. For example, the PUSCH overlaps in time domain with a PUCCH on a different serving cell, and/or the serving cell does not support simultaneous transmission of the PUSCH and the PUCCH.

In some implementations, a PDSCH conflicting/colliding with other physical channel(s) may be at least one of:

- the PDSCH overlapping in time domain with other PUSCH(s) and/or PUCCH(s) and/or PDSCH(s) on a same serving cell; or

- the PDSCH overlapping in both time domain and frequency domain with a PDCCH on a same serving cell.

In some implementations, a PUCCH conflicting/colliding with other physical channel(s) may be at least one of:

- the PUCCH overlapping in time domain with other PUCCH(s) and/or PUSCH(s); or

- the PUCCH overlapping in time domain with other PDSCH(s) on a same serving cell.

In some implementations, a PDCCH conflicting/colliding with other physical channel(s) may be at least one of:

- the PDCCH overlapping in time domain with other PUSCH(s) and/or PUCCH(s) on a same serving cell; or

- the PDCCH overlapping in both time domain and frequency domain with other PDSCH(s) on a same serving cell.

In some implementations, "a set of overlapping channels" may be understood as that each channel of the set of overlapping channels overlaps (or collides) with at least one of channels in the set except this channel. The channels may include one or more PUCCHs and/or one or more PUSCHs. For example, "a set of overlapping channels" may include "a set of overlapping PUCCHs and/or PUSCHs". As a specific example, when a first PUCCH overlaps with at least one of a second PUCCH and a third PUCCH, the second PUCCH overlaps with at least one of the first PUCCH and the third PUCCH, and the third PUCCH overlaps with at least one of the first PUCCH and the second PUCCH, the first PUCCH, the second PUCCH and the third PUCCH constitute a set of overlapping channels (PUCCHs). For example, the first PUCCH overlaps with the second PUCCH and the third PUCCH, and the second PUCCH and the third PUCCH do not overlap.

It should be noted that, in embodiments of the disclosure, "resolving overlapping channels" may be understood as resolving the collision of overlapping channels. For example, when a PUCCH overlaps with a PUSCH, resolving the overlapping or collision may include multiplexing UCI of the PUCCH in the PUSCH, or may include transmitting the PUCCH or PUSCH with a higher priority. For another example, when a PUCCH overlaps with one or another PUCCH, resolving the overlapping or collision may include multiplexing UCI in a PUCCH, or may include transmitting the PUCCH with a higher priority. For yet another example, when two PUSCHs on a same serving cell overlap, resolving the overlapping or collision may include transmitting a PUSCH with a higher priority of the two PUSCHs.

It should be noted that, unless the context clearly indicates otherwise, all or one or more of the methods, steps or operations described in embodiments of the disclosure may be specified by protocols and/or configured by higher layer signaling and/or indicated by dynamic signaling. The dynamic signaling may be a PDCCH and/or DCI and/or a DCI format. For example, a SPS PDSCH and/or CG PUSCH may be dynamically indicated in a corresponding activated 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 approach (e.g., approach A), otherwise (if the parameter, e.g., parameter X, is not configured), the UE performs another approach (e.g., approach B). Unless otherwise specified, the parameters in the embodiments of the disclosure may be higher layer parameters. For example, the higher layer parameters may be parameters configured or indicated by higher layer signaling (e.g., RRC signaling).

It should be noted that, a PCell (Primary Cell) or PSCell (Primary Secondary Cell) in embodiments of the disclosure may be used interchangeably with a cell having a PUCCH. A serving cell may be used interchangeably with a cell.

It should be noted that, methods for downlink in embodiments of the disclosure may also be applicable to uplink, and methods for uplink may also be applicable to downlink. For example, a PDSCH may be replaced with a PUSCH, a SPS PDSCH may be replaced with a CG PUSCH, and downlink symbols may be replaced with uplink symbols, so that methods for downlink may be applicable to uplink.

It should be noted that, methods applicable to scheduling multiple PDSCHs/PUSCHs in embodiments of the disclosure may also be applicable to a PDSCH/PUSCH transmission with repetitions. For example, a PDSCH/PUSCH of multiple PDSCHs/PUSCHs may be replaced by a repetition of multiple repetitions of the PDSCH/PUSCH transmission.

It should be noted that in methods of the disclosure, "configured with and/or indicated a transmission with repetitions" may be understood that a number of the repetitions of the transmission is greater than 1. For example, "configured with and/or indicated a PUCCH transmission with repetitions" may be understood that "the PUCCH transmission is repeated on more than one slot/subslot". "Not configured with and/or indicated a transmission with repetitions" may be understood that a number of the repetitions of the transmission is equal to 1. For example, "not configured with and/or indicated a PUCCH transmission with repetitions" may be understood that "a number of the repetitions of the PUCCH transmission is equal to 1". For example, the UE may be configured with a parameter related to a number of repetitions of a PUCCH transmission; when the parameter is greater than 1, it may mean that the UE is configured with a PUCCH transmission with repetitions, and the UE may repeat the PUCCH transmission on time units (e.g., slots); when the parameter is equal to 1, it may mean that the UE is not configured with a PUCCH transmission with repetitions. For example, the PUCCH transmission with repetitions may include only one type of UCI. If the PUCCH is configured with repetitions, in embodiments of the disclosure, a repetition of the multiple repetitions of the PUCCH may be used as a PUCCH (or a PUCCH resource), or all of the repetitions of the PUCCH may be used as a PUCCH (or a PUCCH resource), or a specific repetition of the multiple repetitions of the PUCCH may be used as a PUCCH (or a PUCCH resource).

It should be noted that, in methods of the disclosure, a PDCCH and/or DCI and/or a DCI format schedules multiple PDSCHs/PUSCHs, which may be multiple PDSCHs/PUSCHs on a same serving cell and/or multiple PDSCHs/PUSCHs on different serving cells.

It should be noted that, multiple manners/methods described in the disclosure may be combined in any order. In a combination, a manner may be performed one or more times.

It should be noted that, steps/operations of manners/methods of the disclosure may be implemented in any order.

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

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

It should be noted that, in embodiments of the disclosure, a PUCCH/PUSCH carrying/with/including A may be understood as a PUCCH/PUSCH only carrying/with/including A, and may also be understood as a PUCCH/PUSCH carrying/with/including at least A.

It should be noted that, in embodiments of the disclosure, "slot" may be replaced by "subslot" or "time unit"

It should be noted that, in embodiments of the disclosure, "performing a predefined method (or step) if a predefined condition is satisfied" and "not performing the predefined method (or step) if the predefined condition is not satisfied" may be used interchangeably. "Not performing a predefined method (or step) if a predefined condition is satisfied" and "performing the predefined method (or step) if the predefined condition is not satisfied" may be used interchangeably.

In some embodiments, the UE may be configured with a HARQ-ACK codebook as semi-static by higher layer signaling. For example, the UE may be configured with a parameter pdsch-HARQ-ACK-Codebook = semi-static. If the UE reports a capability to receive more than one PDSCH in a slot (for example, the PDSCH may be a unicast PDSCH or a multicast PDSCH), the UE determines occasions for candidate PDSCH receptions for a downlink slot. The UE generates HARQ-ACK information for each of the determined occasions for candidate PDSCH receptions. As an example, the UE is configured by higher layer signaling that a PDSCH can includes one TB, and the UE generates 1-bit HARQ-ACK information for each of the occasions for candidate PDSCH receptions. If the UE receives a PDSCH for a PDSCH reception occasion and HARQ-ACK for the PDSCH is indicated to be transmitted in a PUCCH in an uplink slot , for HARQ-ACK information in a HARQ-ACK codebook in the uplink slot , if the PDSCH is successfully decoded, the UE generates 1-bit ACK information; otherwise, if the PDSCH is not successfully decoded, the UE generates 1-bit NACK information. If the UE does not receive a PDSCH for a PDSCH reception occasion, the UE generates 1-bit NACK information for HARQ-ACK information corresponding to the PDSCH reception occasion in the HARQ-ACK codebook in the uplink slot .

A TDRA table configured for the UE (examples of the TDRA table may refer to the description of FIGS. 9A and 9B) may include multiple SLIVs. The TDRA table including two SLIVs is taken as an example to explain in the following. In one example, the TDRA table is configured with two rows, where each row includes one SLIV, and the two SLIVs (SLIV #1 and SLIV #2) of the TDRA table do not overlap in the time domain (as shown in Figure 10). When there are two occasions for candidate PDSCH receptions in a downlink slot, and the UE is configured by higher layer signaling that a PDSCH can include one TB, the UE generates 2-bit HARQ-ACK information for the downlink slot. If a time domain resource of a PDSCH reception that the UE is scheduled to receive by DCI is indicated by SLIV #1, and the UE does not receive other PDSCHs in the downlink slot, the first bit in a HARQ-ACK codebook corresponding to the downlink slot corresponds to a decoding result of the PDSCH, and the second bit is NACK.

In some cases, a TDRA table configured for the UE may include multiple SLIVs, as described above. At this time, the base station may only schedule one PDSCH in a downlink slot, and accordingly, there may be padding NACK bit(s) in a HARQ-ACK codebook, as described above. How to reduce the number of bits in the HARQ-ACK codebook is a problem to be solved. An enhanced HARQ-ACK codebook generation method is needed to reduce the padding NACK bit(s).

In some embodiments, at least one of Methods MN1~MN7 may be adopted to determine a set of occasions for candidate PDSCH receptions.

Method MN1

In Method MN1, the UE may be configured with information related to a HARQ-ACK codebook (e.g., a semi-static HARQ-ACK codebook) by higher layer signaling. For example, the UE may receive first information (e.g., from the base station), where the first information may be or include information related to a HARQ-ACK codebook (e.g., a semi-static HARQ-ACK codebook). For example, the information related to a HARQ-ACK codebook (e.g., a semi-static HARQ-ACK codebook) may be or include configuration information for generating a HARQ-ACK codebook (e.g., a semi-static HARQ-ACK codebook). The first information may include the second information, or the UE may also receive the second information (e.g., from the base station). The second information is used to indicate a number of PDSCH receptions (e.g., unicast PDSCH receptions and/or multicast PDSCH receptions) in a downlink slot for a serving cell c (for example, to indicate whether the number of PDSCH receptions is greater than a predefined number (for example, the predefined number is 1); for another example, to indicate a maximum value of the number of PDSCH receptions (a maximum number of PDSCH receptions)). In one example, the maximum number of PDSCH receptions is 1. Or, the second information is used to indicate a number of PDSCH receptions (e.g., unicast PDSCH receptions and/or multicast PDSCH receptions) in a downlink slot for a downlink BWP. For example, the downlink BWP is an active downlink BWP for a serving cell c.

The UE may determine a first set based on the first information, where the first set is a set of occasions for candidate PDSCH receptions.

The determination of the first set may include that, for a downlink slot for a serving cell c, if the UE is configured with the second information (or is configured with the second information indicating a predefined value (for example, the predefined value may be 'enable'; the predefined value may also be a predefined number (for example, the predefined number is 1))), and a second set (which may be represented by "R" in embodiments of the disclosure) is not empty, then a number of occasions for candidate PDSCH receptions in the downlink slot on the serving cell that may be included in the first set is a first predefined number, where the first predefined number is 1. Alternatively, the determination of the first set may include that, for a downlink slot for a serving cell c, if the UE is configured with the second information (or is configured with the second information indicating a predefined value (for example, the predefined value may be 'enable', and for another example, the predefined value may be 'disable'; the predefined value may also be a predefined number (for example, the predefined number is 1))), then the first set may include (or be determined to include) at most the first predefined number of occasions for candidate PDSCH receptions in the downlink slot on the serving cell. For example, the second set consists of rows of a time domain resource allocation table, where each row corresponds to a predefined candidate PDSCH reception in the downlink slot on the serving cell. For example, the predefined candidate PDSCH reception may be a valid PDSCH reception. For example, when a candidate PDSCH reception does not overlap with semi-static uplink symbols in the time domain, the candidate PDSCH reception is a valid PDSCH reception.

The UE may generate a semi-static HARQ-ACK codebook based on the first set.

The UE may transmit a PUCCH including or carrying the semi-static HARQ-ACK codebook.

The method can reduce the number of bits in the semi-static HARQ-ACK codebook, and thus can reduce the PUCCH resources carrying HARQ-ACK, thereby improving the spectrum efficiency.

Method MN2

According to implementations of Method MN2, the second information may indicate at least one of the following:

- there is at most one PDSCH reception in a downlink slot of an active downlink BWP.

- there is at most one unicast PDSCH reception in a downlink slot of an active downlink BWP.

- there is at most one unicast PDSCH or multicast PDSCH reception in a downlink slot of an active downlink BWP. For example, the UE is not configured with a FDMed multicast reception parameter (e.g., fdmed-ReceptionMulticast) and/or the UE is configured to monitor unicast DCI formats and multicast DCI formats.

- there is at most one multicast PDSCH reception in a downlink slot of an active downlink BWP.

- there is at most one unicast PDSCH reception and at most one multicast PDSCH reception in a downlink slot of an active downlink BWP. For example, the UE is configured with the FDMed multicast reception parameter (e.g., fdmed-ReceptionMulticast) and/or the UE is configured to monitor unicast DCI formats and multicast DCI formats.

It should be noted that the above indication of the second information may be determined based on the following: the second information is configured; and/or the value of the second information is a predefined value, such as 'enable'. As another example, the predefined value may be a predefined number (for example, the predefined number is 1).

It should be noted that "a downlink slot of an active downlink BWP" may be replaced by "a downlink slot of an active downlink BWP of a serving cell" or "a downlink slot of a serving cell".

It should be noted that "there is at most one PDSCH reception" may be replaced by "at most one PDSCH reception is received". "there is at most one" may be replaced by "there is no more than one".

It should be noted that "there is at most one PDSCH reception" may be replaced by "at most the first predefined number of PDSCH receptions is received". "there is at most one" may be replaced by "there is no more than the first predefined number of".

Method MN3

In some embodiments, the second information may be configured by at least one of the following configuration modes.

Configuration mode 1-1

The second information may be configured per serving cell. For example, the second information may be configured separately for each serving cell. For example, the second information may be configured in a PDSCH configuration parameter (e.g., PDSCH-Config). For another example, the second information may be configured for each serving cell in a PUCCH configuration parameter (e.g., PUCCH-Config). For yet another example, the second information may be configured in a cell group configuration parameter (e.g., parameter CellGroupConfig). In an example, a parameter list may be configured, and each parameter in the parameter list corresponds to a serving cell of the PUCCH group.

Compared with other configuration methods, the mode is simple to implement and is beneficial to reduce the implementation complexity of the UE and the base station.

Configuration mode 1-2

The second information may be configured per DL BWP. For example, the second information may be configured separately for each downlink BWP (e.g., each downlink BWP of each serving cell). For example, it may be configured in a downlink dedicated BWP parameter (e.g., parameter BWP-DownlinkDedicated).

Compared with configuration mode 1-1, the mode can further improve the flexibility of configuration.

It should be noted that for the above configuration modes 1-1 to 1-2, the second information may be configured uniformly for unicast PDSCH receptions and multicast PDSCH reception. As an example, in case that the second information is configured for a downlink BWP using configuration mode 1-2, the second information for the downlink BWP may be used to indicate a number (e.g., a maximum number, such as 1) of unicast PDSCH receptions and/or multicast PDSCH receptions in a downlink slot for the downlink BWP. This is simple to implement and may reduce the implementation complexity of the UE and the base station.

Configuration mode 1-3

The second information may be configured separately for unicast PDSCH receptions and multicast PDSCH receptions. For example, for the above configuration modes 1-1 to 1-2, the second information corresponding to unicast and multicast may be configured by different parameters. For another example, the second information configured in the above configurations 1-1 to 1-2 is used to indicate for unicast PDSCH receptions. Or, the second information configured in the above configurations 1-1 to 1-2 is used to indicate for unicast PDSCH receptions or multicast PDSCH receptions.

As an example, for a downlink BWP, the second information may be configured for unicast PDSCH receptions (referred to as second information INFO1, for convenience of description) and the second information may be configured for multicast PDSCH receptions (referred to as second information INFO2, for convenience of description). The second information INFO1 may be used to indicate a number (e.g., a maximum number, such as 1) of unicast PDSCH receptions in a downlink slot for the downlink BWP. The second information INFO2 may be used to indicate a number (e.g., a maximum number, such as 1) of multicast PDSCH receptions in a downlink slot for the downlink BWP.

As another example, in case that the configuration mode 1-2 is used to configure the second information for a downlink BWP, the second information for the downlink BWP may be used to: indicate a number (e.g., a maximum number, such as 1) of unicast PDSCH receptions in a downlink slot for the downlink BWP; or indicate a number (e.g., a maximum number, such as 1) of unicast PDSCH receptions or multicast PDSCH receptions in a downlink slot for the downlink BWP.

In the case of multicast PDSCH receptions, the second information may also be configured in a multicast common frequency domain resource configuration parameter (e.g., parameter CFR-ConfigMulticast).

The method can further improve the flexibility of configuration.

Method MN4

The UE may be configured with a parameter related to two levels of priorities (e.g., physical layer priorities). In this case, according to some implementations of Method MN4, the second information defined in Method MN2 may be the second information corresponding to a specific priority (e.g., a higher priority or a lower priority). For example, "the second information may indicate at least one of the following" in Method MN2 may be replaced by "for a HARQ-ACK codebook (e.g., a semi-static HARQ-ACK codebook) of a priority, the second information may indicate at least one of the following".

According to some implementations of Method MN4, the second information may be configured separately for different priorities. In some examples, the configuration mode of the second information defined in Method MN3 may be the configuration mode of the second information corresponding to a specific priority (e.g., a higher priority or a lower priority). For example, a parameter list may be configured, the first parameter in the parameter list corresponds to the second information with a second priority (e.g., a priority index (e.g., a priority index of HARQ-ACK) is 0) (or a first priority (for example, the priority index is 1)), and the second parameter in the parameter list corresponds to the first priority (e.g., the priority index is 1) (or the second priority). As a specific example, when configuring the second information using configuration mode 1-2, the second information may be configured separately for different priorities through a parameter list in a downlink dedicated BWP parameter (e.g., parameter BWP-DownlinkDedicated). The first parameter (e.g., the parameter of the second information) in the parameter list may correspond to the second priority (or the first priority), and the second parameter (e.g., the parameter of the second information) in the parameter list may correspond to the first priority (or the second priority). Or, two parameters of the second information may be configured in a BWP parameter dedicated for downlink (e.g., parameter BWP-DownlinkDedicated), where the two parameters of the second information correspond to the second information for the first priority and the second information for the second priority, respectively.

Because services of different priorities have different latency requirements, the second information may be configured separately for services of different priorities. For example, the second information may be configured for services of a lower priority, while the second information may not be configured for services of a higher priority. In this way, the scheduling flexibility can be improved, and the size of the HARQ-ACK codebook of the lower priority can be reduced under the condition of meeting the latency requirement for services of the higher priority.

It should be noted that the indication and configuration of the second information may also be indicated and configured uniformly for HARQ-ACK codebooks of different priorities.

Method MN5

In some cases, the UE may be configured with two or more values of a control resource set (CORESET) pool index parameter (e.g., parameter coresetPoolIndex). For example, the UE may be configured by a PDCCH configuration parameter (e.g., higher layer parameter PDCCH-Config), where the PDCCH configuration parameter (e.g., higher layer parameter PDCCH-Config) includes two different values (e.g., value 0 and value 1) of the CORESET pool index parameter (e.g., ControlResourceSet). The CORESET pool index parameter may be understood as a TRP/panel/beam-related parameter.

According to some implementations of Method MN5, the second information defined in Method MN2 may be the second information corresponding to a value (e.g., 0 or 1) of the CORESET pool index parameter. For example, "the second information may indicate at least one of the following" in Method MN2 may be replaced by "for a value of the CORESET pool index parameter, the second information may indicate at least one of the following".

According to some implementations of Method MN5, the second information may be configured separately for different CORESET pool indexes. For example, the configuration mode of the second information defined in Method MN3 may be the configuration mode of the second information corresponding to a CORESET pool index. That is, it may be configured separately for different CORESET pool indexes. For example, a parameter list may be configured, where the first parameter in the parameter list corresponds to the second information for the CORESET pool index with a value of 0 (or 1), and the second parameter in the parameter list corresponds to the second information for the CORESET pool index with a value of 1 (or 0). Or, the configuration mode of the second information defined in Method MN3 may be configured uniformly for different values of the CORESET pool index parameter. That is, different values of the CORESET pool index parameter for an activated BWP (or a serving cell) correspond to the same second parameter. As a specific example, when configuring the second information using configuration mode 1-2, the second information may be configured separately for different CORESET pool indexes (e.g., 0 or 1) through a parameter list in a downlink dedicated BWP parameter (e.g., parameter BWP-DownlinkDedicated). The first parameter in the parameter list may correspond to the CORESET pool index with a value of 0 (or the CORESET pool index with a value of 1) e, and the second parameter in the parameter list may correspond to the CORESET pool index with a value of 1 (or the CORESET pool index with a value of 0). Or, two parameters of the second information may be configured in a downlink dedicated BWP parameter (e.g., parameter BWP-DownlinkDedicated), where the two parameters of the second information correspond to the second information for the CORESET pool index with a value of 0 (or 1) and the second information for the CORESET pool index with a value of 1 (or 0), respectively.

The method can improve the flexibility of scheduling.

Method MN6

In some cases, the UE may be configured with a parameter related to two levels of priorities (e.g., physical layer priorities) and two or more values of a control resource set (CORESET) pool index parameter (e.g., parameter coresetPoolIndex).

According to some implementations of Method MN6, the second information defined in Method MN2 may be the second information corresponding to a value (e.g., 0 or 1) of the CORESET pool index parameter of a specific priority (e.g., a higher priority or a lower priority). For example, "the second information may indicate at least one of the following" in Method MN2 may be replaced by "for a value of the CORESET pool index parameter for a HARQ-ACK codebook (e.g., a semi-static HARQ-ACK codebook) of a priority, the second information may indicate at least one of the following" or "for a HARQ-ACK codebook (e.g., a semi-static HARQ-ACK codebook) of a priority for a value of the CORESET pool index parameter, the second information may indicate at least one of the following".

According to some implementations of Method MN6, the configuration mode of the second information defined in Method MN3 may be the configuration mode of the second information corresponding to a CORESET pool index of a specific priority (e.g., a higher priority or a lower priority). Or, the configuration mode of the second information defined in Method MN3 may be the configuration mode of the second information corresponding to a specific priority (e.g., the higher priority or the lower priority). That is, for a specific priority, the configuration mode of the second information may be uniformly configured for the different values of the CORESET pool index parameter.

The method can improve the flexibility of scheduling.

Method MN7

According to some implementations of Method MN7, if a serving cell c is deactivated, it may be considered that the second parameter is configured, that is, for a downlink slot of the serving cell c, the first set includes at most one occasion for candidate PDSCH receptions in the downlink slot on the serving cell.

The method can reduce the number of HARQ-ACK bits and improve the reliability of uplink transmission.

Method MN8

According to some implementations of Method MN8, the second information in Methods MN1 to MN7 may indicate information regarding a number of PDSCH receptions for which the UE feeds back (or transmits) HARQ-ACK in a same PUCCH (or in a same slot). For example, if the UE is configured with the second information, which indicates that a maximum number of PDSCH receptions for which the UE feeds back HARQ-ACK in a same PUCCH (or in a same slot) is 1, the UE may be scheduled with two PDSCHs in a same downlink slot, and HARQ-ACKs for the two PDSCHs are fed back in different uplink slots.

For example, when a serving cell is configured with the second information, the network does not schedule the UE with more than one PDSCH in a slot on the serving cell if HARQ-ACKs for any two PDSCHs are supposed to be reported on one PUCCH resource in the same slot.

For another example, when a serving cell is configured with the second information, the network schedule the UE with at most one PDSCH in a slot on the serving cell if HARQ-ACKs for PDSCHs are supposed to be reported on one PUCCH resource in the same slot.

In some examples, the second information in Methods MN1~MN7 may indicate a number of PDSCH receptions in a downlink slot of a downlink BWP for which the UE transmits HARQ-ACK information in a same PUCCH or a same uplink slot.

The method can improve the flexibility of scheduling.

Method MN9

According to some implementations of Method MN9, if the UE is configured with the second information (e.g., the second information as described in the above methods), the UE does not expect to receive, in a same downlink slot, a PDSCH and a DCI format without scheduling PDSCHs (e.g., a DCI format indicating SPS PDSCH release or a DCI format indicating TCI state update) for which the UE feeds back/transmits HARQ-ACK in a same PUCCH (or in a same slot).

According to some implementations of Method MN9, if the UE is configured with the second information (e.g., the second information as described in the above methods), the UE does not expect to receive, in a same downlink slot, more than one DCI format without scheduling PDSCHs (e.g., a DCI format indicating SPS PDSCH release or a DCI format indicating TCI state update) for which the UE feeds back/transmits HARQ-ACK in a same PUCCH (or in a same slot).

The method can reduce the implementation complexity of the UE.

It should be noted that if a PDSCH is repeatedly transmitted in a slot, it may be considered repetitions of the transmission of the PDSCH as one PDSCH. For example, if a PDSCH is repeatedly transmitted twice in a slot, it may be considered that a number of PDSCHs in the slot is 1.

It should be noted that if a PDSCH is repeatedly transmitted across slots, repetitions of the transmission of the PDSCH in a slot may be considered as one PDSCH in the slot regardless of whether the repetitions overlap with uplink symbols configured by higher layer signaling.

Method MN10

According to some implementations of Method MN10, if a first predefined condition is satisfied, a number of occasions for candidate PDSCH receptions in a downlink slot on a serving cell that may be included in the first set (such as the first set described in the above various methods) is a first predefined number, where the first predefined number may be 1. The first predefined condition may be at least one of the following:

- The second information is configured and .

- The second information indicating a predefined value is configured and .

- The second information is configured.

- The second information indicating the predefined value is configured.

Herein, the second information may be the second information as described in at least one of Methods MN1-MN9. The predefined value may be 'enable' or 'disable', and the predefined value may also be a predefined number (e.g., the predefined number is 1).

In one example, for a downlink slot of a serving cell c, a set of occasions for candidate PDSCH receptions in the downlink slot may be determined according to the following pseudo code 1-1. Here, j is index of occasion for candidate PDSCH reception or SPS PDSCH release, and R is the second set as described in at least one of Methods MN1-MN9.

[Rectified under Rule 91, 15.04.2024]

The method can reduce the number of bits in the HARQ-ACK codebook and improve the reliability of uplink transmission.

Method MN11

In some cases, the UE may be configured with two or more values of a CORESET pool index parameter (e.g., parameter coresetPoolIndex). The CORESET pool index parameter may be understood as a TRP-related parameter. The value of the CORESET pool index for multicast PDSCHs may be determined according to a CORESET of a PDCCH that schedules the multicast PDSCHs, or it may be specified by protocols that the value of the CORESET pool index for multicast PDSCHs is 0.

According to some implementations of Method MN11, if the UE is configured with a FDMed multicast reception parameter (e.g., fdmed-ReceptionMulticast) and/or the UE is configured to monitor unicast DCI formats and multicast DCI formats, or if the UE is able to receive FDMed unicast and multicast PDSCHs in each slot of each carrier, the UE would be able to decode a PDSCH scheduled by a DCI format with C-RNTI or a PDSCH scheduled by a DCI format with CS-RNTI for retransmission of TB, and a PDSCH scheduled by a DCI format with G-RNTI for multicast or a PDSCH scheduled by a DCI format with G-CS-RNTI for retransmission of TB, where the PDSCHs partially or completely overlap in time in non-overlapping PRBs and have the same value of the CORESET pool index parameter (e.g., the parameter coresetPoolIndex). In this way, it can support receiving multicast PDSCHs and unicast PDSCHs based on FDM on a TRP. The UE may report a capability to support receiving multicast PDSCHs and unicast PDSCHs based on FDM on a TRP through capability report. Or, the UE may report a capability to support receiving multicast PDSCHs and unicast PDSCHs having the same value of the CORESET pool index parameter (e.g., parameter coresetPoolIndex) based on FDM through capability report.

According to some implementations of Method MN11, it may be specified by protocols that that the UE does not expect to be configured with the FDMed multicast reception parameter (e.g., fdmed-ReceptionMulticast) and configured with a higher layer PDCCH configuration parameter (e.g., PDCCH- Config) that includes two different values of the CORESET pool index parameter (e.g., parameter coresetPoolIndex) in a CORESET parameter (e.g., ControlResourceSet). The method can reduce the implementation complexity of the UE and the base station.

According to some implementations of Method MN11, for any HARQ process ID on a given scheduling cell, if the UE is not configured with the higher layer PDCCH configuration parameter (e.g., PDCCH- Config) that includes two different values of the CORESET pool index parameter (e.g., parameter coresetPoolIndex) in the CORESET parameter (e.g., ControlResourceSet), the UE is not expected to receive a PDSCH that overlaps in time with another PDSCH. Otherwise, if the UE is configured with the higher layer PDCCH configuration parameter (e.g., PDCCH- Config) that includes two different values of the CORESET pool index parameter (e.g., parameter coresetPoolIndex) in the CORESET parameter (e.g., ControlResourceSet), the UE does not expect to receive a PDSCH that overlaps in time with another PDSCH having the same value of the coresetPoolIndex. The method can reduce the implementation complexity of the UE.

It should be noted that the second information may be specific to indicate information regarding a number of PDSCH receptions, in a slot on a serving cell (or BWP), related to a Type-1 HARQ-ACK codebook (or semi-static HARQ-ACK codebook), or the second information may also be used to indicate a number of PDSCH receptions in a slot on a serving cell (or BWP).

It should be noted that the second information may be applied to a case where HARQ-ACK includes at least HARQ-ACK for a PDSCH scheduled by a DCI format or HARQ-ACK for a DCI format without scheduling PDSCHs, that is, the second information may only be applied to a PDSCH scheduled by a DCI. The method can avoid the influence on SPS PDSCHs and reduce the implementation complexity.

In some embodiments, the third information may also indicate a number of PDSCH receptions (or SPS PDSCH receptions) in a slot on a serving cell (or BWP). For example, the third information may be configured by a mode for configuring the second information in the embodiments of the disclosure. For another example, the second information in Method MN2 may be replaced by the third information. Therein, the PDSCH may also be replaced by SPS PDSCH. The third information may also be the second information.

Method MN12

According to implementations of Method MN12, the third information may indicate at least one of the following:

- A number of PDSCH receptions in a downlink slot of an active downlink BWP.

- A number of unicast PDSCH receptions or multicast PDSCH receptions in a downlink slot of an active downlink BWP.

- A number of multicast PDSCH receptions in a downlink slot of an active downlink BWP.

It should be noted that "PDSCH" may be replaced by "SPS PDSCH" in the method.

It should be noted that "a downlink slot of an active downlink BWP" may be replaced by "a downlink slot of an active downlink BWP of a serving cell" or "a downlink slot on a serving cell".

It should be noted that, in some cases, the UE may be configured with two or more values of a pool CORESET index parameter (e.g., the parameter coresetPoolIndex), and the third information defined in Method MN12 may be the third information corresponding to a value (e.g., 0 or 1) of the CORESET pool index parameter. For example, "the third information may indicate at least one of the following" in Method MN12 may be replaced by "for a value of the CORESET pool index parameter, the third information may indicate at least one of the following".

The method can reduce the number of SPS PDSCHs decoded by the UE, and thus can reduce the implementation complexity of the UE. The method may also reduce the number of bits in the HARQ-ACK codebook, and thus can improve the reliability of the UCI transmission, thereby improving the spectrum efficiency.

In an example, if multiple PDSCHs on a serving cell each without a corresponding PDCCH transmission are in a slot, after resolving overlapping with symbols indicated as uplink by higher layer signaling (e.g., tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated), the UE receives one or more PDSCHs without corresponding PDCCH transmissions in the slot as specified below.

- Step 0: set j=0, where j is the number of selected PDSCH(s) for decoding. Q is the set of activated PDCCH without corresponding PDCCH transmissions within the slot.

- Step 1: the UE receives one PDSCH with the lowest configured SPS configuration index (e.g., sps-ConfigIndex) within Q, set j=j+1. Designate the received PDSCH as survivor PDSCH.

- Step 2: The survivor PDSCH in step 1 and any other PDSCH(s) overlapping (even partially) with the survivor PDSCH in step 1 are excluded from Q.

- Step 3: Repeat steps 1 and 2 until Q is empty or j is equal to the number of unicast/multicast PDSCHs in a slot supported by the UE or j is equal to the third information.

It should be noted that "PDSCH without a corresponding PDCCH transmission" may be used interchangeably with "SPS PDSCH".

It should be noted that step 3 may be replaced by the following: repeat steps 1 and 2 until Q is empty or j is equal to the number of unicast/multicast PDSCHs in a slot supported by the UE if the third information is not configured or j is equal to the third information if the third information is configured.

In another example, a HARQ-ACK codebook may be generated according to [Pseudo code -1].

FIG. 11 illustrates a flowchart of a method 1100 performed by a terminal according to some embodiments of the disclosure.

Referring to FIG. 11, in operation S1110, the terminal receives first information related to a HARQ-ACK codebook. For example, the terminal may receive the first information related to a HARQ-ACK codebook from the base station, for example, via a higher layer (e.g., RRC) message and/or a DCI message. Examples of the first information may refer to the descriptions in Methods MN1-MN12.

Next, in operation S1120, the terminal receives second information indicating a number of PDSCH receptions in a downlink time unit (e.g., downlink slot) of a downlink BWP, where the PDSCH receptions include multicast PDSCH receptions and/or unicast PDSCH receptions. For example, the terminal may receive the second information from the base station, for example, via a higher layer (e.g., RRC) message and/or a DCI message. Examples of the second information may refer to the descriptions in Methods MN1-MN12.

Then, in operation S1130, the terminal determines a first set of occasions for candidate PDSCH receptions based on the first information and the second information.

Next, in operation S1140, the terminal generates a HARQ-ACK codebook based on the first set of occasions for candidate PDSCH receptions.

Then, in operation S1150, the terminal transmits the generated HARQ-ACK codebook. For example, the terminal may transmit the generated HARQ-ACK codebook to the base station.

In some embodiments, one or more of operations S1110 to S1150 may be performed based on the methods described according to various embodiments of the disclosure (e.g., various methods described above, such as Methods MN1-MN12).

In some embodiments, the method 1100 may omit one or more of operations S1110 to S1150, or may include additional operations, for example, operations that may be performed by a terminal (e.g., the UE) according to various embodiments of the disclosure (e.g., various methods described above, such as Methods MN1-MN12).

FIG. 12 illustrates a flowchart of a method 1200 performed by a base station according to some embodiments of the disclosure.

Referring to FIG. 12, in operation S1210, the base station transmits first information related to a HARQ-ACK codebook to the terminal. For example, the base station may transmit the first information related to a HARQ-ACK codebook, for example, via a higher layer (e.g., RRC) message and/or a DCI message. Examples of the first information may refer to the descriptions in Methods MN1-MN12.

Next, in operation S1220, the base station transmits second information indicating a number of PDSCH receptions in a downlink time unit (e.g., downlink slot) of a BWP to the terminal, where the PDSCH receptions include multicast PDSCH receptions and/or unicast PDSCH receptions. For example, the base station may transmit the second information via a higher layer (e.g., RRC) message.

Then, in operation S1230, the base station receives a HARQ-ACK codebook from the terminal, where the HARQ-ACK codebook is generated based on a first set of occasions for candidate PDSCH receptions, and the first set of occasions for candidate PDSCH receptions is determined based on the first information and the second information.

In some embodiments, one or more of S1210 to S1230 may be performed based on the methods described according to various embodiments of the disclosure (e.g., various methods described above, such as Methods MN1-MN12).

In some embodiments, the method 1200 may omit one or more of operations S1210 to S1230, or may include additional operations, for example, the operations described according to various embodiments of the disclosure (e.g., various methods described above, such as Methods MN1-MN12).

Those skilled in the art will understand 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. Furthermore, 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 aspects of the invention of the disclosure as generally described herein and shown in the drawings may be arranged, replaced, combined, separated and designed in various different configurations, all of which are contemplated herein.

Those skilled in the art will understand that the various illustrative logic blocks, modules, circuits, and steps described in this application may be implemented as hardware, software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, various illustrative components, blocks, modules, circuits, and steps are generally described above in the form of their functional sets. Whether such function sets are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Technicians may implement the described function sets in different ways for each specific application, but such design decisions should not be interpreted as causing a departure from the scope of this application.

The various illustrative logic blocks, modules, and circuits described in this application may be implemented or performed by 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 devices, discrete gates or transistor logics, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

The steps of the 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 thereof. The software module may reside in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor to enable the processor to read and write information from/to the storage medium. In an alternative, the storage medium may be integrated into the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a communication apparatus (e.g., a terminal or a base station). In an alternative, the processor and the storage medium may reside in a communication apparatus (e.g., a terminal or a base station) as discrete components.

In one or more exemplary designs, the functions may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, each function may be stored as one or more pieces of instructions or codes on a computer-readable medium or delivered through it. The computer-readable medium includes both a computer storage medium and a communication medium, the latter including any medium that facilitates the transfer of computer programs from one place to another. The storage medium may be any available medium that may be accessed by a general purpose or special purpose computer.

The above description is only an exemplary implementation of the present invention, and is not intended to limit the scope of protection of the present invention, which is determined by the appended claims.

Claims

A method performed by a terminal in a wireless communication system, comprising:

receiving first information related to a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook;

receiving second information indicating a number of physical downlink shared channel (PDSCH) receptions in a downlink time unit of a downlink bandwidth part (BWP), wherein the PDSCH receptions include one or more of multicast PDSCH receptions or unicast PDSCH receptions;

determining a first set of occasions for candidate PDSCH receptions based on the first information and the second information;

generating the HARQ-ACK codebook based on the first set of occasions for candidate PDSCH receptions; and

transmitting the generated HARQ-ACK codebook.
The method of claim 1, wherein HARQ-ACK information for PDSCH receptions indicated by the second information is multiplexed in a physical uplink control channel (PUCCH) or an uplink time unit for transmission.
The method of any of claim 1 or 2, wherein, in case that a second set is not empty, the first set includes a first number of occasions for the candidate PDSCH receptions in the downlink time unit of the BWP, wherein the first number is determined based on the number of PDSCH receptions in the downlink time unit of the downlink BWP indicated by the second information, wherein the second set consists of rows of a time domain resource allocation table, wherein the rows in the second set correspond to the candidate PDSCH receptions in the downlink time unit of the downlink BWP.
The method of any of claims 1-3, wherein the second information indicates one or more of:

a maximum number of PDSCH receptions in the downlink time unit of the downlink BWP;

a maximum number of PDSCH receptions in the downlink time unit of the downlink BWP of a serving cell;

a maximum number of unicast PDSCH receptions in the downlink time unit of the downlink BWP;

a maximum number of unicast PDSCH receptions in the downlink time unit of the downlink BWP of the serving cell;

a maximum number of unicast PDSCH receptions or multicast PDSCH receptions in the downlink time unit of the downlink BWP;

a maximum number of unicast PDSCH receptions or multicast PDSCH receptions in the downlink time unit of the downlink BWP of the serving cell;

a maximum number of multicast PDSCH receptions in the downlink time unit of the downlink BWP;

a maximum number of multicast PDSCH receptions in the downlink time unit of the downlink BWP of the serving cell;

a maximum number of unicast PDSCH receptions and a maximum number of multicast PDSCH receptions in the downlink time unit of the downlink BWP; or

a maximum number of unicast PDSCH receptions and a maximum number of multicast PDSCH receptions in the downlink time unit of the downlink BWP of the serving cell.
The method of any of claims 1-4, wherein:

the second information is configured separately for each serving cell; and/or

the second information is configured separately for each downlink BWP; and/or

the second information is configured separately for each downlink BWP of each serving cell; and/or

the second information is configured separately for unicast PDSCH receptions and multicast PDSCH receptions.
The method of any of claims 1-5, wherein, in case that the terminal is configured with two or more priorities, the second information is configured separately for each of the two or more priorities,

wherein, in case that the terminal is configured with two or more values of a control resource set pool index, the second information is configured separately for each of the two or more values, or the same second information is configured for the two or more values,

wherein, in case that the terminal is configured with two or more priorities and is configured with two or more values of a control resource set pool index, the second information is configured for each of combinations of the priorities and the values of the control resource set pool index, wherein the combination of the priorities and the values of the control resource set pool index includes any one of the two or more priorities and any one of the two or more values.
The method of any of claims 1-6, wherein, in case that the second information indicates that a maximum of the number of PDSCH receptions in the downlink time unit of the downlink BWP is 1:

the terminal does not expect to receive a PDSCH and a downlink control information (DCI) format without scheduling a PDSCH reception in a same downlink time unit, wherein HARQ-ACK information for the PDSCH and HARQ-ACK information for the DCI format are transmitted in a same PUCCH or a same uplink time unit; and/or

the terminal does not expect to receive more than one DCI format without scheduling a PDSCH reception in a same downlink time unit, wherein HARQ-ACK information for the more than one DCI format is transmitted in a same PUCCH or a same uplink time unit.
A method perform by a base station in a wireless communication system, comprising:

transmitting first information related to a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook to a terminal;

transmitting second information indicating a number of physical downlink shared channel (PDSCH) receptions in a downlink time unit of a downlink bandwidth part (BWP) to a terminal, wherein the PDSCH receptions include one or more of multicast PDSCH receptions or unicast PDSCH receptions; and

receiving a HARQ-ACK codebook from the terminal,

wherein the HARQ-ACK codebook is generated based on a first set of occasions for candidate PDSCH receptions, and

wherein the first set of occasions for candidate PDSCH receptions is determined based on the first information and the second information.
The method of claim 8, wherein HARQ-ACK information for PDSCH receptions indicated by the second information is multiplexed in a physical uplink control channel (PUCCH) or an uplink time unit for reception,

wherein, in case that a second set is not empty, the first set includes a first number of occasions for the candidate PDSCH receptions in the downlink time unit of the BWP, wherein the first number is determined based on the number of PDSCH receptions in the downlink time unit of the downlink BWP indicated by the second information, wherein the second set consists of rows of a time domain resource allocation table, wherein the rows in the second set correspond to the candidate PDSCH receptions in the downlink time unit of the downlink BWP.
The method of any of claims 8 or 9, wherein the second information indicates one or more of:

a maximum number of PDSCH receptions in the downlink time unit of the downlink BWP;

a maximum number of PDSCH receptions in the downlink time unit of the downlink BWP of a serving cell;

a maximum number of unicast PDSCH receptions in the downlink time unit of the downlink BWP;

a maximum number of unicast PDSCH receptions in the downlink time unit of the downlink BWP of the serving cell;

a maximum number of unicast PDSCH receptions or multicast PDSCH receptions in the downlink time unit of the downlink BWP;

a maximum number of unicast PDSCH receptions or multicast PDSCH receptions in the downlink time unit of the downlink BWP of the serving cell;

a maximum number of multicast PDSCH receptions in the downlink time unit of the downlink BWP;

a maximum number of multicast PDSCH receptions in the downlink time unit of the downlink BWP of the serving cell;

a maximum number of unicast PDSCH receptions and a maximum number of multicast PDSCH receptions in the downlink time unit of the downlink BWP; or

a maximum number of unicast PDSCH receptions and a maximum number of multicast PDSCH receptions in the downlink time unit of the downlink BWP of the serving cell.
The method of any of claims 8-10, wherein:

the second information is configured separately for each serving cell; and/or

the second information is configured separately for each downlink BWP; and/or

the second information is configured separately for each downlink BWP of each serving cell; and/or

the second information is configured separately for unicast PDSCH receptions and multicast PDSCH receptions.
The method of any of claims 8-11, wherein, in case that two or more priorities are configured for the terminal, the second information is configured separately for each of the two or more priorities,

wherein, in case that two or more values of a control resource set pool index are configured for the terminal, the second information is configured separately for each of the two or more values, or the same second information is configured for the two or more values of the control resource set pool index,

wherein, in case that two or more priorities are configured for the terminal and/or two or more values of the control resource set pool index are configured, the second information is configured for each of combinations of the priorities and the values of the control resource set pool index, wherein the combination of the priorities and the values of the control resource set pool index includes any one of the two or more priorities and any one of the two or more values.
The method of any of claims 8-12, wherein, in case that the second information indicates that a maximum of the number of PDSCH receptions in the downlink time unit of the downlink BWP is 1:

the base station does not transmit a PDSCH and a downlink control information (DCI) format without scheduling a PDSCH reception in a same downlink time unit, wherein HARQ-ACK information for the PDSCH and HARQ-ACK information for the DCI format are transmitted in a same PUCCH or a same uplink time unit; and/or

the base station does not transmit more than one DCI format without scheduling a PDSCH reception in a same downlink time unit, wherein HARQ-ACK information for the more than one DCI format is transmitted in a same PUCCH or a same uplink time unit.
A terminal in a wireless communication system, comprising:

a transceiver; and

a controller coupled with the transceiver and configured to perform the method of any of claims 1-7.
A base station in a wireless communication system, comprising:

a transceiver; and

a controller coupled with the transceiver and configured to perform the method of any of claims 8-13.