Methods and apparatus for transmission and reception of uplink signal in a wireless communication system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method and apparatus for transmission and reception of an uplink signal are provided. The method includes receiving second information that indicates a hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback mode, resolving overlapping for uplink channels associated with a same value of a control resource set (CORESET) pool index parameter, and in case that the second information indicates the HARQ-ACK feedback mode as joint, resolving overlapping for uplink channels associated with different values of the CORESET pool index parameter. The invention provides an enhanced uplink signal transmission method.

Description

METHODS AND APPARATUS FOR TRANSMISSION AND RECEPTION OF UPLINK SIGNAL IN A WIRELESS COMMUNICATION SYSTEM

[0001] The disclosure relates to wireless communication technology, and more particularly, to a method and apparatus for transmission and reception of an uplink signal in a wireless communication system.

[0002] 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.

[0003] 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.

[0004] 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.

[0005] 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.

[0006] 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.

[0007] 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.

[0008] The present disclosure relates to wireless communication systems and, more specifically, the present disclosure relates to transmission and reception of uplink signal in a wireless communication system.

[0009] According to some aspects of the disclosure, a method performed by a terminal in a wireless communication system is provided. The method includes: receiving second information that indicates a hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback mode, resolving overlapping for uplink channels associated with a same value of a control resource set (CORESET) pool index parameter; and in case that the second information indicates the HARQ-ACK feedback mode as joint, resolving overlapping for uplink channels associated with different values of the CORESET pool index parameter.

[0010] In combination with one or more aspects of the method performed by the terminal described above, for example, resolving the overlapping for the uplink channels associated with the same value of the CORESET pool index parameter includes: resolving overlapping for physical uplink control channels (PUCCHs) and / or physical uplink shared channels (PUSCHs) with a same priority; or resolving overlapping for PUCCHs and / or PUSCHs with different priorities.

[0011] In combination with one or more aspects of the method performed by the terminal described above, for example, in case that one or more of the following conditions are satisfied, the terminal does not expect that a PUCCH associated with a first value of the CORESET pool index parameter and a PUCCH or PUSCH associated with a second value of the CORESET pool index parameter overlap in time domain: the terminal is not provided the CORESET pool index parameter or is provided the CORESET pool index parameter with a value of 0 for first CORESETs on active downlink (DL) bandwidth parts (BWPs) of serving cells; the terminal is provided the CORESET pool index parameter with a value of 1 for second CORESETs on active DL BWPs of the serving cells; the second information indicates the HARQ-ACK feedback mode as separate; or the terminal is configured with a higher layer parameter indicating simultaneous transmission of two or more PUSCHs.

[0012] In combination with one or more aspects of the method performed by the terminal described above, for example, in case that one or more physical downlink shared channels (PDSCH) are received, wherein the one or more PDSCH are scheduled by one or more DCI formats and HARQ-ACK information for the one or more PDSCH receptions is transmitted in a same uplink time unit, resolving the overlapping for the uplink channels associated with the same value of the CORESET pool index parameter includes: determining a value of the CORESET pool index parameter for a PUCCH with the HARQ-ACK information; and determining a PUCCH resource from one or more PUCCH resources associated with the determined value of the CORESET pool index parameter.

[0013] In connection with one or more aspects of the method performed by the terminal described above, for example, determining the value of the CORESET pool index parameter includes determining the value of the CORESET pool index parameter based on at least one of: a value of the CORESET pool index parameter for a last DCI format of the one or more DCI formats; a third value of the CORESET pool index parameter; the third value of the CORESET pool index parameter, in case that a value of the CORESET pool index parameter for at least one of the one or more DCI formats is the third value of the CORESET pool index parameter; or a fourth value of the CORESET pool index parameter, in case that all of values of the CORESET pool index parameter for all of the one or more DCI formats are not the third value of the CORESET pool index parameter, or all of the values of the CORESET pool index parameter for all of the one or more DCI formats are the fourth value of the CORESET pool index parameter.

[0014] In combination with one or more aspects of the method performed by the terminal described above, in some embodiments, for example, in case that one or more semi-persistent scheduling (SPS) PDSCHs are received, wherein HARQ-ACK information for the one or more SPS PDSCH receptions is transmitted in a same uplink time unit, resolving the overlapping for the uplink channels associated with the same value of the CORESET pool index parameter includes: determining a value of the CORESET pool index parameter for a PUCCH with the HARQ-ACK information; and determining a PUCCH resource from one or more PUCCH resources associated with the determined value of the CORESET pool index parameter.

[0015] In connection with one or more aspects of the method performed by the terminal described above, for example, determining the value of the CORESET pool index parameter includes determining the value of the CORESET pool index parameter based on at least one of: a third value of the CORESET pool index parameter; a third value of the CORESET pool index parameter, in case that a value of the CORESET pool index parameter for at least one of one or more DCI formats for activating the one or more SPS PDSCH is the third value of the CORESET pool index parameter; or a fourth value of the CORESET pool index parameter, in case that values of the CORESET pool index parameter for all of the one or more DCI formats are not the third CORESET pool index parameter, or the values of the CORESET pool index parameter for all of the one or more DCI formats are the fourth value of the CORESET pool index parameter.

[0016] In combination with one or more aspects of the method performed by the terminal described above, for example, in case that the second information indicates the HARQ-ACK feedback mode as separate, a PUCCH resource or a set of PUCCH resources for transmission of HARQ-ACK information for PDSCH receptions is separately configured for each value of the CORESET pool index parameter.

[0017] According to some aspects of the disclosure, a method performed by a base station in a wireless communication system is provided. The method includes transmitting second information to a terminal, wherein the second information indicates a hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback mode, and receiving an uplink channel from the terminal, wherein, in case that the second information indicates the HARQ-ACK feedback mode as joint, the second information is used to resolve overlapping for a plurality of uplink channels associated with different values of the CORESET pool index parameter.

[0018] In connection with one or more aspects of the method performed by the base station described above, for example, in case that one or more of the following conditions are satisfied, the base station does not schedule or indicate a first uplink channel and a second uplink channel, wherein the first uplink channel is associated with a first value of the CORESET pool index parameter and the second uplink channel is associated with a second value of the CORESET pool index parameter: the terminal is not provided the CORESET pool index parameter or is provided the CORESET pool index parameter with a value of 0 for first CORESETs on active downlink (DL) bandwidth parts (BWPs) of serving cells; the terminal is provided the CORESET pool index parameter with a value of 1 for second CORESETs on active DL BWPs of the serving cells; the second information indicates the HARQ-ACK feedback mode as separate; or the terminal is configured with a higher layer parameter indicating simultaneous transmission of two or more PUSCHs.

[0019] In combination with one or more aspects of the method performed by the base station described above, for example, in case that the second information indicates the HARQ-ACK feedback mode as separate, a PUCCH resource or a set of PUCCH resources for transmission of HARQ-ACK information for PDSCH receptions is separately configured for each value of the CORESET pool index parameter.

[0020] According to some aspects of the disclosure, there is also provided a terminal in a wireless communication system. The terminal includes a transceiver, and a controller coupled with the transceiver and configured to perform one or more aspects of the method performed by the terminal.

[0021] According to some aspects of the disclosure, there is also provided a base station in a wireless communication system. The base station includes a transceiver, and a controller coupled with the transceiver and configured to perform one or more aspects of the method performed by the base station.

[0022] According to some aspects of the disclosure, there is also provided a computer-readable storage medium on which one or more computer programs are stored, wherein one or more aspects of the above-described methods executed by a terminal can be implemented when the one or more computer programs are executed by one or more processors.

[0023] According to some aspects of the disclosure, there is also provided a computer-readable storage medium on which one or more computer programs are stored, wherein one or more aspects of the above-described methods executed by a base station can be implemented when the one or more computer programs are executed by one or more processors.

[0024] According to some aspects of the disclosure, there is also provided a method performed by a user equipment (UE) in a wireless communication system, the method comprising: receiving a radio resource control (RRC) configuration message including information indicating an acknowledgement (ACK) negative ACK (NACK) feedback mode and a control resource set (CORESET) pool index, wherein the ACK NACK feedback mode is at least one of a separate or a joint and wherein the CORESET pool index is 0 or 1; receiving a first downlink control information (DCI) in a physical downlink control channel (PDCCH) received in a first CORESET from first CORESETs associated with the CORESET pool index 0; receiving a second DCI in a PDCCH received in a second CORESET from second CORESETs associated with the CORESET pool index 1; and in case that the ACK NACK feedback mode is set to the joint and information indicating simultaneous transmission of two physical uplink shared channels (PUSCHs) is configured, transmitting uplink control information (UCI) in a physical uplink shared channel (PUSCH) associated with the CORESET pool index 0.

[0025] According to some aspects of the disclosure, there is also provided a method performed by a base station in a wireless communication system, the method comprising: transmitting, to a user equipment (UE), a radio resource control (RRC) configuration message including information indicating an acknowledgement (ACK) negative ACK (NACK) feedback mode and a control resource set (CORESET) pool index, wherein the ACK NACK feedback mode is at least one of a separate or a joint and wherein the CORESET pool index is 0 or 1; transmitting, to the UE, a first downlink control information (DCI) in a physical downlink control channel (PDCCH) received in a first CORESET from first CORESETs associated with the CORESET pool index 0; transmitting, to the UE a second DCI in a PDCCH received in a second CORESET from second CORESETs associated with the CORESET pool index 1; and in case that the ACK NACK feedback mode is set to the joint and information indicating simultaneous transmission of two physical uplink shared channels (PUSCHs) is configured, receiving, form the UE, uplink control information (UCI) in a physical uplink shared channel (PUSCH) associated with the CORESET pool index 0.

[0026] According to some aspects of the disclosure, there is also provided a user equipment (UE) in a wireless communication system, the UE comprising: a transceiver; and a controller coupled with the transceiver configured to: receive a radio resource control (RRC) configuration message including information indicating an acknowledgement (ACK) negative ACK (NACK) feedback mode and a control resource set (CORESET) pool index, wherein the ACK NACK feedback mode is at least one of a separate or a joint and wherein the CORESET pool index is 0 or 1, receive a first downlink control information (DCI) in a physical downlink control channel (PDCCH) received in a first CORESET from first CORESETs associated with the CORESET pool index 0, receive a second DCI in a PDCCH received in a second CORESET from second CORESETs associated with the CORESET pool index 1, and in case that the ACK NACK feedback mode is set to the joint and information indicating simultaneous transmission of two physical uplink shared channels (PUSCHs) is configured, transmit uplink control information (UCI) in a physical uplink shared channel (PUSCH) associated with the CORESET pool index 0.

[0027] According to some aspects of the disclosure, there is also provided a base station in a wireless communication system, the base station comprising: a transceiver; and a controller coupled with the transceiver configured to: transmit, to a user equipment (UE), a radio resource control (RRC) configuration message including information indicating an acknowledgement (ACK) negative ACK (NACK) feedback mode and a control resource set (CORESET) pool index, wherein the ACK NACK feedback mode is at least one of a separate or a joint and wherein the CORESET pool index is 0 or 1, transmit, to the UE, a first downlink control information (DCI) in a physical downlink control channel (PDCCH) received in a first CORESET from first CORESETs associated with the CORESET pool index 0, transmit, to the UE a second DCI in a PDCCH received in a second CORESET from second CORESETs associated with the CORESET pool index 1, and in case that the ACK NACK feedback mode is set to the joint and information indicating simultaneous transmission of two physical uplink shared channels (PUSCHs) is configured, receive, form the UE, uplink control information (UCI) in a physical uplink shared channel (PUSCH) associated with the CORESET pool index 0.

[0028] According to an embodiment of the disclosure, a wireless communication can be performed efficiently. Especially, a transmission and reception of uplink signal can be performed efficiently.

[0029] 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 which:

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

[0031] FIG. 2A illustrates example wireless transmission and reception paths according to some embodiments of the disclosure;

[0032] FIG. 2B illustrates example wireless transmission and reception paths according to some embodiments of the disclosure;

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

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

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

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

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

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

[0039] FIG. 8A illustrates some examples of uplink transmission timing according to some embodiments of the disclosure;

[0040] FIG. 8B illustrates some examples of uplink transmission timing according to some embodiments of the disclosure;

[0041] FIG. 8C illustrates some examples of uplink transmission timing according to some embodiments of the disclosure;

[0042] FIG. 9A illustrates examples of time domain resource allocation tables according to some embodiments of the disclosure;

[0043] FIG. 9B illustrates examples of time domain resource allocation tables according to some embodiments of the disclosure;

[0044] FIG. 10 illustrates a flowchart of a method performed by a terminal according to some embodiments of the disclosure; and

[0045] FIG. 11 illustrates a flowchart of a method performed by a base station according to some embodiments of the disclosure.

[0046] 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 pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also called “Beyond 4G networks” or “Post-LTE systems”.

[0047] In order to achieve a higher data rate, 5G communication systems are implemented in higher frequency (millimeter, mmWave) bands, e.g., 60 GHz bands. In order to reduce propagation loss of radio waves and increase a transmission distance, technologies such as beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antenna, analog beamforming and large-scale antenna are discussed in 5G communication systems.

[0048] In addition, in 5G communication systems, developments of system network improvement are underway based on advanced small cell, cloud radio access network (RAN), ultra-dense network, device-to-device (D2D) communication, wireless backhaul, mobile network, cooperative communication, coordinated multi-points (CoMP), reception-end interference cancellation, etc.

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

[0050] 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.

[0051] Before undertaking the DETAILED DESCRIPTION below, it can 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 can be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller can 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 can be used, and only one item in the list can 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.

[0052] Moreover, various functions described below can 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 can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.

[0053] 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.

[0054] 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.

[0055] 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.

[0056] 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.

[0057] As used herein, the term “set” means one or more. Accordingly, a set of items can be a single item or a collection of two or more items.

[0058] In the 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.

[0059] 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 can 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.

[0060] 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 can 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 can 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 can 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 can be applied to future-oriented communication technologies.

[0061] 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.

[0062] 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.

[0063] 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.

[0064] 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 can be used without departing from the scope of the disclosure.

[0065] 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.

[0066] Depending on a type of the network, other well-known terms such as “base station (BS)” or “access point” can be used instead of “gNodeB” or “gNB”. For convenience, the terms “gNodeB” and “gNB” are used in this patent document to refer to network infrastructure components that provide wireless access for remote terminals. 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” can 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).

[0067] 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 implementations, one or more of gNBs 101-103 can communicate with each other and with UEs 111-116 using 5G, Long Term Evolution (LTE), LTE-A, WiMAX or other advanced wireless communication technologies.

[0068] 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.

[0069] 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 implementations, one or more of gNB 101, gNB 102, and gNB 103 support codebook designs and structures for systems with 2D antenna arrays.

[0070] Although FIG. 1 illustrates an example of the wireless network 100, various changes can be made to FIG. 1. The wireless network 100 can include any number of gNBs and any number of UEs in any suitable arrangement, for example. Furthermore, gNB 101 can directly communicate with any number of UEs and provide wireless broadband access to the network 130 for those UEs. Similarly, each gNB 102-103 can 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 can provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0071] 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 can be described as being implemented in a gNB, such as gNB 102, and the reception path 250 can be described as being implemented in a UE, such as UE 116. However, it should be understood that the reception path 250 can be implemented in a gNB and the transmission path 200 can be implemented in a UE. In some implementations, 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.

[0072] 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.

[0073] 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 can also be filtered at a baseband before switching to the RF frequency.

[0074] 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.

[0075] 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.

[0076] Each of the components in FIGS. 2A and 2B can 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.

[0077] 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 can 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.).

[0078] 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 can be combined, further subdivided or omitted, and additional components can be added according to specific requirements. Furthermore, FIGS. 2A and 2B are intended to illustrate examples of types of transmission and reception paths that can be used in a wireless network. Any other suitable architecture can be used to support wireless communication in a wireless network.

[0079] 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 can 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.

[0080] 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.

[0081] 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).

[0082] 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.

[0083] The processor / controller 340 can 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 can 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 implementations, the processor / controller 340 includes at least one microprocessor or microcontroller.

[0084] 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 can move data into or out of the memory 360 as required by an execution process. In some implementations, 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 ability 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.

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

[0086] Although FIG. 3A illustrates an example of UE 116, various changes can be made to FIG. 3A. For example, various components in FIG. 3A can be combined, further subdivided or omitted, and additional components can be added according to specific requirements. As a specific example, the processor / controller 340 can 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 can be configured to operate as other types of mobile or fixed devices.

[0087] 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)).

[0088] 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 can 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 can include the same or similar structures as gNB 102.

[0089] 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.

[0090] 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.

[0091] 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.

[0092] The controller / processor 378 can include one or more processors or other processing devices that control the overall operation of gNB 102. For example, the controller / processor 378 can control the reception of forward channel signals and the transmission of 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 can also support additional functions, such as higher-level wireless communication functions. For example, the controller / processor 378 can perform a Blind Interference Sensing (BIS) process such as 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 implementations, the controller / processor 378 includes at least one microprocessor or microcontroller.

[0093] 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 can also support channel quality measurement and reporting for systems with 2D antenna arrays as described in embodiments of the disclosure. In some implementations, the controller / processor 378 supports communication between entities such as web RTCs. The controller / processor 378 can move data into or out of the memory 380 as required by an execution process.

[0094] 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 can 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 can 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 can allow gNB 102 to communicate with a larger network, such as the Internet, through a wired or wireless local area network or through a wired or wireless connection. 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.

[0095] The memory 380 is coupled to the controller / processor 378. A part of the memory 380 can include an RAM, while another part of the memory 380 can 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.

[0096] 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.

[0097] Although FIG. 3B illustrates an example of gNB 102, various changes may be made to FIG. 3B. For example, gNB 102 can include any number of each component shown in FIG. 3A. As a specific example, the access point can include many backhaul or network interfaces 382, and the controller / processor 378 can 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 can include multiple instances of each (such as one for each RF transceiver).

[0098] 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 can 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.

[0099] 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 can feedback HARQ-ACK is variable. For example, the delay of HARQ-ACK feedback can be dynamically indicated by physical layer signaling, or different HARQ-ACK delays can be determined based on factors such as different services or user capabilities.

[0100] 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.

[0101] When transmitting uplink channels, the problem of collision (e.g., overlapping) of uplink channels needs to be considered. For example, in some cases, UE can transmit multiple PUSCHs (e.g., two PUSCHs) on a serving cell simultaneously. When at least one of the multiple PUSCHs (e.g., two PUSCHs) transmitted simultaneously overlaps in time domain with other uplink channel(s), how to resolve the collision among the uplink channels is a problem that needs to be solved. Therefore, an enhanced uplink signal transmission method of the UE is needed to improve the reliability of uplink transmission.

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

[0103] In the example 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 example 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.

[0104] In describing a wireless communication system and in the disclosure described below, transferring methods (or configuration methods) of 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).

[0105] In the following description of the example embodiments 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.

[0106] - MIB (master information block)

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

[0108] - RRC signaling

[0109] - MAC CE

[0110] 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.

[0111] - PDCCH (physical downlink control channel)

[0112] - DCI (downlink control information)

[0113] - UE-specific DCI

[0114] - group common DCI

[0115] - common DCI (e.g., multicast DCI)

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

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

[0118] - PUCCH (physical uplink control channel)

[0119] - UCI (uplink control information)

[0120] - Paging

[0121] - PRACH (physical random access channel)

[0122] - RAR (random access response)

[0123] In the example 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.

[0124] In the example 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), non-scheduling DCI, paging, and RAR, 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.

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

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

[0127] 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.

[0128] 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 / or receive the second data and / or the second control signaling from the second transceiving node in the time unit.

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

[0130] 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.

[0131] Herein, depending on the network type, the term “base station” or “BS” can 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 wireless network 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.

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

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

[0134] 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.

[0135] 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 example 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.

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

[0137] 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.

[0138] 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.

[0139] 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 (e.g., higher 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, the common DCI may be DCI common to all of UEs, and the common DCI may also be DCI common to all of UEs in a serving cell (e.g., cell common DCI). The DCI may also be multicast DCI or broadcast DCI. The DCI may be uplink DCI (e.g., DCI for scheduling a PUSCH) and / or downlink DCI (e.g., DCI for scheduling a PDSCH).

[0140] It should be noted that in the description of the example embodiments of the disclosure, the following terms may be used interchangeably:

[0141] - DCI

[0142] - DCI format

[0143] - PDCCH

[0144] - grant

[0145] - dynamic grant.

[0146] 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 (e.g., higher 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 the example embodiments of the disclosure, when UCI is carried by a PUCCH, the UCI may be used interchangeably with the PUCCH.

[0147] In some implementations, 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.

[0148] In some implementations, the CSI report may be Part 1 CSI and / or Part 2 CSI.

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

[0150] In implementations described in connection with FIG. 4 or 5, a time unit in which the second transceiving node transmits the second data and / or the second control signaling may be an uplink time unit. In some examples, the second time unit may be described by taking an uplink slot or PUCCH slot or PCell (primary cell) slot or PUCCH slot on PCell as an example (but not limited thereto). The “PUCCH slot” may be understood as a PUCCH transmission slot.

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

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

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

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

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

[0156] 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 example embodiments of the disclosure (e.g., various methods / manners described below).

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

[0158] 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.

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

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

[0161] [HARQ / scheduling general timing]

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

[0163] 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 example embodiments of the disclosure (e.g., various methods / manners described below).

[0164] In some implementations, acknowledgement / negative acknowledgement (ACK / NACK) for downlink transmission(s) may be performed through HARQ-ACK.

[0165] 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.

[0166] In an example, the UE receives a DCI format and receives a PDSCH according to time domain resources indicated by the DCI format. For example, a parameter K0 may be used to indicate a time unit interval (offset) between the PDSCH scheduled by the DCI format and the DCI format (e.g., a PDCCH carrying the DCI format), where K0 may be in units of slots, for example, PDSCH slots (that is, slots of an active BWP in a serving cell where PDSCH is located). For example, FIG. 8A gives an example in which K0=1. In the example illustrated in FIG. 8A, the time unit interval from the PDSCH scheduled by the DCI format to the PDCCH carrying the DCI format is one slot. In the example embodiments of the disclosure, “the UE receives a DCI / DCI format” may refer to that “the UE detects the DCI / DCI format.”

[0167] In another example, the UE receives a DCI format and transmits a PUSCH based on time domain resources indicated by the DCI format. For example, a timing parameter K2 may be used to indicate a time unit interval between the PUSCH scheduled by the DCI format and the DCI format (e.g., a PDCCH carrying the DCI format), where K2 may be in units of slots, for example, PUSCH slots (that is, slots of an active BWP in a serving cell where PUSCH is located). For example, FIG. 8B gives an example in which K2 = 1. In the example illustrated in FIG. 8B, the time unit interval between the PUSCH scheduled by the DCI format and the PDCCH carrying the DCI is one slot. K2 may also be used to indicate a time unit interval between a PDCCH for activating CG (configured grant) PUSCH(s) and the first activated CG PUSCH (e.g., CG PUSCH transmission occasion). 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 the example embodiments of the disclosure) and / or a PUSCH not scheduled by DCI (e.g., CG PUSCH).

[0168] In yet another example, the UE receives a PDSCH, and may transmit HARQ-ACK information for the PDSCH reception in a PUCCH in a time unit (e.g., uplink 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 indicate a time unit interval between the PUCCH with the HARQ-ACK information for the PDSCH reception and the PDSCH, and K1 may be in units of time units (e.g., uplink time units, such as PUCCH time units), such as slots or subslots. For example, FIG. 8A gives an example in which K1 = 3. In the example illustrated in FIG. 8A, the time unit interval between the PUCCH with the HARQ-ACK information for the PDSCH reception and the PDSCH is 3 slots. It should be noted that in the example embodiments of the disclosure, the timing parameter K1 may be used interchangeably with a time unit offset K1, the timing parameter K0 may be used interchangeably with a time unit offset K0, and the timing parameter K2 may be used interchangeably with a time unit offset K2.

[0169] The PDSCH may be a PDSCH scheduled by DCI and / or a SPS (semi-persistent scheduling) PDSCH. The UE periodically receives 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.

[0170] In the example 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). Or, for example, HARQ-ACK may be HARQ-ACK for a DCI format without scheduling PDSCH.

[0171] In yet another example, the UE receives DCI (e.g., DCI indicating SPS PDSCH release (deactivation)), and may transmit HARQ-ACK information for the DCI in a PUCCH in a time unit (e.g., uplink time unit). For example, the timing parameter K1 may be used to indicate a time unit interval between the PUCCH with the HARQ-ACK information for the DCI and the DCI, and K1 may be in units of time units (e.g., uplink 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 unit interval between the PUCCH with the HARQ-ACK information for the DCI and the DCI is 3 slots. For example, the timing parameter K1 may be used to indicate a time unit interval between a PDCCH reception carrying DCI indicating SPS PDSCH release (deactivation) and the PUCCH feeding back HARQ-ACK for the PDCCH reception.

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

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

[0174] [Two levels of priorities]

[0175] 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). The PUCCH resource configured by the first PUCCH-Config is a PUCCH resource of a lower priority, and the PUCCH resource configured by the second PUCCH-Config is a PUCCH resource of a higher priority. For another example, the priority of a PUCCH or a PUSCH may be indicated in a DCI format, for example, by a physical layer priority index (phy-PriorityIndex) field.

[0176] When two or more uplink physical channels on a serving cell overlap (for example, overlap in time), or PUCCH(s) and PUSCH(s) overlap (for example, overlap in time), it is necessary to resolve the overlapping for the physical channels. “Resolving the overlapping for the physical channels” may refer to “resolving the collision of overlapping physical channels”. The resulting physical channels after resolving the overlapping for the physical channels do not overlap or collide. The overlapping of physical channels may be resolved by multiplexing and / or prioritization. The multiplexing may refer to multiplexing UCI of two or more physical channels in a physical channel. For example, the multiplexing of multiple PUCCHs and / or PUSCHs that overlap in time domain may include multiplexing UCI of the PUCCHs in a PUCCH or PUSCH. It should be noted that in the description of the example embodiments of the disclosure, “resolving the overlapping for the physical channels” may also be used interchangeably with “determining the overlapping of the physical channels”. The prioritization may refer to transmitting a physical channel of the higher priority and not transmitting a physical channel of the lower priority. It should be noted that in the description of the example embodiments of this disclosure, “Not transmitting a physical channel”, “cancelling the transmission of a physical channel”, “stopping the transmission of a physical channel”, and “deprioritizing the priority of a physical channel” may be used interchangeably. For example, the prioritization of two PUCCHs and / or PUSCHs overlapping in time domain by the UE may include that the UE transmits the PUCCH or the PUSCH of the higher priority and / or the UE does not transmit the PUCCH or the PUSCH of the lower priority.

[0177] For example, if the UE is configured / indicated to multiplex UCIs (e.g., HARQ-ACK) of different priorities via higher layer signaling (e.g., via higher layer parameter uci-MuxWithDiffPrio), when resolving the overlapping for physical channels with different priorities, the UE may multiplex UCIs (e.g., HARQ-ACK) with different priorities; otherwise (e.g., if the UE is not configured the parameter for multiplexing UCIs with different priorities), when resolving the overlapping for physical channels with different priorities, the UE performs prioritization for PUCCHs and / or PUSCHs with different priorities.

[0178] 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 some example 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 example embodiments of the disclosure, the terms “first priority”, “higher priority”, “greater priority index” and “priority index 1” may be used interchangeably. In the example embodiments of the disclosure, the terms “second priority”, “lower priority”, “smaller priority index” and “priority index 0” may be used interchangeably.

[0179] For example, the multiplexing of multiple PUCCHs and / or PUSCHs that overlap in time domain may include multiplexing UCI of the PUCCH in a PUCCH or PUSCH.

[0180] For example, the prioritization of two PUCCHs and / or PUSCHs that overlap in time domain by the UE may include that the UE transmits a PUCCH or PUSCH of a higher priority, and / or the UE does not transmit a PUCCH or PUSCH of a lower priority.

[0181] [Subslot]

[0182] 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 the example 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.

[0183] 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.

[0184] 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., SPS PDSCH release, and / or indicating SCell dormancy, and / or triggering a Type-3 HARQ-ACK codebook report and without scheduling 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.

[0185] [Multicast service (MBS)]

[0186] In the example 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 the example 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 the example 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 the example embodiments of the disclosure, “multicast” may also be replaced by “broadcast”.

[0187] [HARQ-ACK codebook]

[0188] In some implementations, a HARQ-ACK codebook may include HARQ-ACK information (in the disclosure, it may also be called HARQ-ACK information bits) for one or more PDSCHs and / or DCI. If HARQ-ACK information for one or more PDSCH reception and / or DCI is multiplexed in a time unit (e.g., uplink time unit) (e.g., multiplexed in a same time unit) for transmission, the UE may generate the HARQ-ACK codebook based on a predefined rule. For example, if a TB or CBG in a PDSCH reception is successfully decoded, HARQ-ACK information for the TB or CBG in the PDSCH reception is positive ACK. The positive ACK may be represented by 1 in the HARQ-ACK codebook, for example. If a TB or CBG in a PDSCH is not successfully decoded, HARQ-ACK information for the TB or CBG in 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 codes 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 reception, 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 the example 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.

[0189] In some implementations, if HARQ-ACK information transmitted (or multiplexed) in a same time unit (e.g., uplink time unit) does not include HARQ-ACK information for any DCI format, nor does it include HARQ-ACK information for a dynamically scheduled PDSCH reception (e.g., a PDSCH reception scheduled by a DCI format) and / or DCI, or the HARQ-ACK information transmitted (or multiplexed) in the same time unit (e.g., uplink time unit) only includes HARQ-ACK information for one or more SPS PDSCH 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 PDSCH receptions. 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).

[0190] In some implementations, if HARQ-ACK information transmitted (or multiplexed) in a same time unit (e.g., uplink 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., parameter resourceSetToAddModList). The UE determines a PUCCH resource set (e.g., 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.

[0191] In some implementations, if HARQ-ACK information transmitted (multiplexed) in a same time unit (e.g., uplink time unit) includes only HARQ-ACK information for SPS PDSCHs (e.g., PDSCH receptions not scheduled by DCI formats), 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 for a HARQ-ACK codebook for SPS PDSCH receptions).

[0192] [Type-1 HARQ-ACK codebook]

[0193] 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).

[0194] 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 can transmit corresponding HARQ-ACK information in a PUCCH in an uplink slot .

[0195] may be determined by at least one of:

[0196] 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);

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

[0198] 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 active uplink BWP.

[0199] 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.

[0200] 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 ).

[0201] In the description of the example embodiments of the disclosure, 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 the description of the example 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.

[0202] 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 the example 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 time domain resource allocation table dynamically indicated by a DCI. Each row in 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 time domain resource allocation table. When all OFDM symbols in the downlink slot are downlink symbols, the maximum value of the 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.

[0203] FIGS. 9A and 9B illustrate examples of time domain resource allocation tables (TDRAs). 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}.

[0204] [Type-2 HARQ-ACK codebook]

[0205] 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 example embodiments of the disclosure are not limited thereto, and any other suitable assignment indicator may be adopted. It should be noted that the method for dynamic HARQ-ACK codebook in the disclosure may also be used for enhanced dynamic HARQ-ACK codebook.

[0206] In some implementations, the DAI field includes at least one of a first DAI and a second DAI.

[0207] 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 format(s) 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 also indicate: 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 format(s) indicating SPS PDSCH release (deactivation), or DCI 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.

[0208] 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 format(s) 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 a downlink DCI format and / or an uplink DCI format. The second DAI included in the uplink DCI format is also called UL DAI.

[0209] 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.

[0210] Tables 1 and 2 show a correspondence between the DAI field and or or . Numbers of bits of the C-DAI and T-DAI are limited.

[0211] For example, in case that a C-DAI or T-DAI in a DCI format is represented with 2 bits, the value of the C-DAI or T-DAI in the DCI may be determined by equations in Table 1. or is the value of the T-DAI in the DCI received in a PDCCH Monitoring Occasion (MO) m, and is the value of the C-DAI in the DCI for a serving cell c received in the PDCCH monitoring occasion m. Both and are related to a number of bits of the DAI field in the DCI. MSB is the most significant bit and LSB is the least significant bit.

[0212] [Table 1]

[0213]

[0214] 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).

[0215] 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.

[0216] [Table 2]

[0217]

[0218] In some implementations, the UE may generate a HARQ-ACK codebook in a PUCCH according to pseudo-code 1.

[0219] [Pseudo-code 1]

[0220]

[0221]

[0222]

[0223]

[0224]

[0225] In some implementations, for a HARQ-ACK codebook in a PUSCH, the UE may set after completing the c and m loops of generating the HARQ-ACK codebook in pseudo-code 1, where is UL DAI, the value of which may be determined according to Table 1.

[0226] [HARQ-ACK feed mode]

[0227] 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.

[0228] 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.

[0229] 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.

[0230] [Channel collision]

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

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

[0233] - in case that simultaneous transmission for PUSCH is not configured, a PUSCH overlapping in time domain with other PUSCH(s) on a same serving cell;

[0234] - in case that the simultaneous transmission for PUSCH is configured, a PUSCH overlapping in time domain with another PUSCH, on a same serving cell, with a same value of a CORESET pool index parameter (e.g., coresetPoolIndex); or

[0235] - a PUSCH overlapping in time domain with a PUCCH. For example, a 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.

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

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

[0238] - in case that simultaneous reception for PDSCH is not configured (for example, the UE is not configured with different values of the CORESET pool index parameter (e.g., coresetPoolIndex)), a PDSCH overlapping in time domain with other PUSCH(s) on a same serving cell;

[0239] - in case that simultaneous transmission for PDSCH is configured (for example, the UE is configured with a PDCCH configuration parameter (e.g., PDCCH-Config) including a CORESET parameter (e.g., ControlResourceSet) with different values of the CORESET pool index parameter (e.g., coresetPoolIndex)), a PDSCH overlapping in time domain with another PDSCH on a same serving cell with a same value of the CORESET pool index parameter (e.g., coresetPoolIndex); or

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

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

[0242] - a PUCCH overlapping in time domain with other PUCCH(s) and / or PUSCH(s); or

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

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

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

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

[0247] In the description of the example embodiments of the disclosure, “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.

[0248] It should be noted that, in the description of the example 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.

[0249] It should be noted that, unless the context clearly indicates otherwise, all or one or more of the methods, steps or operations described in the example 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 example 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).

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

[0251] It should be noted that, methods for downlink in the example 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.

[0252] It should be noted that, methods applicable to scheduling multiple PDSCHs / PUSCHs in the example 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.

[0253] 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 the example 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).

[0254] 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.

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

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

[0257] It should be noted that, in the example 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.

[0258] It should be noted that, in the example 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).

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

[0260] It should be noted that, in the example embodiments of the disclosure, “slot” may be replaced by “subslot” or “time unit”.

[0261] It should be noted that, in the example 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.

[0262] It should be noted that in the description of the example embodiments of this disclosure, “uplink” and “downlink” may be used interchangeably, “channel”, “channel transmission”, “physical channel” and “physical channel transmission” may be used interchangeably, and “physical channel” and “physical channel resource” may be used interchangeably.

[0263] It should be noted that in the description of the example embodiment of the disclosure, two or more physical channels may overlap in time domain and / or in frequency domain.

[0264] It should be noted that in the description of the example embodiments of the disclosure, the method applicable to RRC parameters may also be used for MAC CEs, and vice versa.

[0265] It should be noted that in the description of the example embodiments of this disclosure, “first and second” and “two” may be used interchangeably. For example, “first channel and second channel” may refer to two channels. In the description of example embodiments of the disclosure, “first and second” may also refer to two or more. For example, "first channel and second channel” may also refer to two or more channels.

[0266] It should be noted that in the description of the example embodiment of the disclosure, “serving cell” or “cell” may be “scheduling serving cell” and / or “scheduled serving cell”.

[0267] It should be noted that in the description of the example embodiments of the disclosure, the “beam” may be understood as a transmission configuration indicator (TCI) state / reference signal / channel / spatial relationship; or a TCI state ID / reference signal ID / channel ID / spatial relationship ID; or a spatial filter associated with a TCI state / reference signal / channel / spatial relationship; Or a spatial filter associated with a TCI state ID / reference signal ID / channel ID / spatial relationship ID. In example embodiments of the disclosure, the following descriptions may be used interchangeably:

[0268] - beam;

[0269] - spatial filter;

[0270] - spatial domain filter;

[0271] - spatial domain transmission filter;

[0272] - spatial setting;

[0273] - quasi co-location (QCL) assumption;

[0274] - QCL parameter (QCL-type (for example, type D (typeD)) parameter / reference signal);

[0275] - TCI state;

[0276] - unified TCI state;

[0277] - spatial relationship;

[0278] - information related to sounding reference signal (SRS) (for example, SRS resource indication (SRI)).

[0279] If the UE would transmit multiple overlapping PUCCHs in a slot or multiple overlapping PUCCHs and PUSCHs in a slot, and the UE is configured to multiplex different UCI types in one PUCCH, and at least one of the multiple overlapping PUCCHs or the PUSCHs is in response to a DCI format detection by the UE, if the following conditions (in the example embodiments of the disclosure, such conditions may be called conditions for UCI multiplexing, or simply UCI multiplexing conditions) are satisfied, the UE multiplexes all corresponding UCI types. If one of the PUCCH transmissions or PUSCH transmissions is in response to a DCI format detection by the UE, the UE expects that the first symbol of the earliest PUCCH or PUSCH, among a group of overlapping PUCCHs and PUSCHs in a slot, satisfies the following timeline conditions (in the example embodiments of the disclosure, such timeline conditions may be called conditions for UCI multiplexing, or simply UCI multiplexing conditions)

[0280] - If there is no aperiodic CSI report multiplexed in a PUSCH in the group of overlapping PUCCHs and PUSCHs (or if at least one PUSCH is included in the group of overlapping PUCCHs and PUSCHs), is not before a symbol (with CP) starting after time after the last symbol of

[0281] - any PDCCH with a DCI format scheduling an overlapping PUSCH, and

[0282] - any PDCCH providing a DCI format indicating / with corresponding HARQ-ACK information in an overlapping PUCCH in the slot.

[0283]

[0284] where , and correspond to the i-th PUSCH, is a parameter related to DM-RS. For example, if the first symbol of the PUSCH allocation consists of DM-RS only, then = 0, otherwise =1. is a BWP switching time. is selected based on the UE PUSCH processing capability (e.g., PUSCH timing capability) and SCS configuration of the i-th PUSCH, where corresponds to the smallest SCS configuration among SCS configurations used for the PDCCH scheduling the i-th PUSCH, the PDCCHs scheduling the PDSCHs, or providing the DCI format without scheduling PDSCHs, with corresponding HARQ-ACK information on a PUCCH which is in the group of overlapping PUCCHs / PUSCHs, and all PUSCHs in the group of overlapping PUCCH and PUSCH.

[0285] The conditions (e.g., timing / timeline conditions) for UCI multiplexing described above are only examples, and the example embodiments of the disclosure are not limited thereto. Any suitable conditions for UCI multiplexing may be set.

[0286] In some implementations, when the UE transmits multiple PUSCHs (e.g., multiple PUSCHs on respective service cells) in a slot (e.g., a slot for PUCCH transmission) and the multiple PUSCHs overlap with a PUCCH carrying UCI in the slot, the UE selects all the PUSCHs overlapping with the PUCCH as the candidate PUSCHs for UCI multiplexing within the slot.

[0287] For example, the UE may determine the PUSCH for UCI multiplexing by applying the following procedure on the candidate PUSCHs. If the candidate PUSCHs include a PUSCH with aperiodic CSI, the UE multiplexes the UCI in the PUSCH. If the candidate PUSCHs include first PUSCHs (for example, the first PUSCHs may be PUSCHs scheduled by DCI format(s)) and second PUSCHs (for example, the second PUSCHs may be PUSCHs configured by respective ConfiguredGrantConfig and / or semi-PersistentOnPUSCH), and the UE would multiplex UCI in one of the candidate PUSCHs, and the candidate PUSCHs satisfy the UCI multiplexing conditions, then the UE multiplexes the UCI in a PUSCH from the first PUSCHs. If the UE would multiplex UCI in one of the candidate PUSCHs and the UE does not multiplex aperiodic CSI in any of the candidate PUSCHs, the UE multiplexes the UCI in a PUSCH of a serving cell with the smallest serving cell index (e.g., ServCellIndex). If the UE transmits more than one PUSCH in the slot on the serving cell with the smallest serving cell index (e.g., the ServCellIndex), the UE multiplexes the UCI in the earliest PUSCH that the UE transmits in the slot.

[0288] In the following description of the example embodiments, for convenience, the term “first PUSCH” may refer to a PUSCH scheduled by a DCI format, and the term “second PUSCH” may refer to a PUSCH not scheduled by a DCI format, such as a PUSCH configured by respective higher layer parameters (such as ConfiguredGrantConfig and / or semi-PersistentOnPUSCH).

[0289] In some cases, the UE can transmit two or more PUSCHs (two PUSCHs are taken as an example to explain below) at the same time. For example, the two PUSCHs may be on a same serving cell. For another example, the two PUSCHs may be in a same BWP. For another example, the two PUSCHs may be associated with two different TRP / panels / beams. For another example, the UE may transmit the two PUSCHs through two different panels. The UE may be configured or indicated with simultaneous transmission of two PUSCHs (for example, two PUSCHs on a serving cell or a BWP). In this case, the UE is able to transmit two PUSCHs simultaneously or is allowed to transmit two PUSCHs simultaneously. In some examples, the UE may be configured with first information, which may be a parameter indicating simultaneous transmission of two PUSCHs (e.g., two PUSCHs on a serving cell or a BWP). If the UE is configured with the first information, the UE may transmit two PUSCHs at the same time. For example, the first parameter may be enableSTx2PofmDCI. In some examples, the UE may be configured by a PDCCH configuration parameter (e.g., higher layer signaling parameter PDCCH-Config), where the PDCCH configuration parameter (e.g., higher layer signaling parameter PDCCH-Config) includes two different values (e.g., value 0 and value 1) of a CORESET pool index parameter (e.g., coresetPoolIndex) (e.g., two different coresetPoolIndex values) in a control resource set parameter (e.g., ControlResourceSet). In this case, the UE can simultaneously transmit two PUSCHs on a serving cell or a BWP (for example, the two PUSCHs may correspond to different values of the CORESET pool index parameter (e.g., coresetPoolIndex)). The configuration of the control resource set parameter may be a configuration of a control resource set parameter for an active BWP of a serving cell. In some examples, the UE may be configured or provided an SRS resource set index parameter (e.g., SRS_resource_set_index) with two different values (e.g., value 0 and value 1). The first SRS resource set (with value 0 of the SRS resource set index parameter) may correspond to value 0 of the CORESET pool index parameter (CORESET pool index parameter value of 0, e.g., coresetPoolIndex value of 0), and the other SRS resource set (with value 1 of the SRS resource set index parameter) may correspond to value 1 of the CORESET pool index parameter (CORESET pool index parameter value of 1, e.g., coresetPoolIndex value of 1). In this case, the UE may simultaneously transmit two PUSCHs on a serving cell or a BWP (for example, the two PUSCHs may correspond to different values of the SRS resource set index parameter (for example, SRS_resource_set_index)). The uplink transmission of multi-panel / multi-antenna / multi-beam configured for the UE is described above by taking SRS resource set index parameter and CORESET pool index parameter as examples. However, the example embodiments of the disclosure are not limited to this, and other parameters associated with uplink (e.g., PUSCH) transmission may be configured. Although it is described above that two PUSCHs are transmitted simultaneously, the example embodiments of the disclosure are not limited to this, and a similar method may be adopted for configuring (for example, configuring N values of the CORESET pool index parameter, where N is an integer equal to or greater than 2), so that the UE is capable of or supports transmitting N PUSCHs simultaneously.

[0290] In example embodiments of the disclosure, the term “panel” may refer to a group / set of antenna ports or an antenna group / set. An uplink transmission configuration indicator (TCI) of each antenna panel may be used to indicate a beam for the antenna panel, which may be a beam associated with an indicated reference signal ID. An SRS set ID may be used to indicate the antenna panel ID, where each antenna panel is associated with an SRS set.

[0291] In some implementations, the UE may receive downlink control signaling (including physical layer signaling and / or higher layer signaling). The downlink control signaling may configure / indicate the UE to transmit overlapping PUSCH(s) and / or PUCCH(s). At least one of the following methods MN 1 to MN 8 may be used to determine PUCCH(s) and / or PUSCH(s) to be transmitted.

[0292] Method MN1

[0293] According to some aspects of the Method MN1, the UE may receive second information that indicates an ACK NACK feedback mode (ackNackFeedbackMode). For example, the UE may receive the second information from the base station. For example, the second information may indicate whether the ACK NACK feedback mode (ackNackFeedbackMode) is separate feedback (ackNackFeedbackMode = separate) or joint feedback (ackNackFeedbackMode = joint). As an example, the separate feedback may correspond to a feedback mode in which the UE cannot or is not allowed to multiplex UCI of a PUCCH associated with a first CORESET (e.g., a first value of a CORESET pool index parameter) (e.g., a PUCCH with the first value of the CORESET pool index parameter) in a PUSCH associated with second CORESETs (e.g., a second value of the CORESET pool index parameter) (e.g., a PUSCH with the second value of the CORESET pool index parameter). The joint feedback may correspond to a feedback mode in which the UE can or is allowed to multiplex UCI of a PUCCH associated with the first CORESET (e.g., with the first value of the CORESET pool index parameter) (e.g., a PUCCH with the first value of the CORESET pool index parameter) in a PUSCH associated with the second CORESETs (e.g., with the second value of the CORESET pool index parameter).

[0294] The UE may resolve (or determine) overlapping for PUCCH and / or PUSCH transmissions with the same value of the CORESET pool index parameter (e.g., coresetPoolIndex) (the same coresetPoolIndex value).

[0295] If the second information indicates the ACK NACK feedback mode (ackNackFeedbackMode) as joint, the UE resolves overlapping for PUCCH and / or PUSCH transmissions with different values of the CORESET pool index parameter (e.g., coresetPoolIndex). For example, “Resolving overlapping for PUCCH and / or PUSCH transmissions with different values of the CORESET pool index parameter (e.g., coresetPoolIndex)” may be performed after “resolving (or determining) overlapping for PUCCH and / or PUSCH transmissions with the same value of CORESET pool index parameter (e.g., coresetPoolIndex)”. The CORESET pool index parameter values including values 0 and 1 will be described as an example. For example, after resolving (or determining) overlapping for first PUCCH and / or first PUSCH transmissions with the CORESET pool index parameter (e.g., coresetPoolIndex) value of 0, one or more first PUCCH and / or first PUSCH transmissions may be determined from the overlapping first PUCCH and / or first PUSCH transmissions. After resolving (or determining) overlapping for second PUCCH and / or second PUSCH transmissions with the CORESET pool index parameter (e.g., coresetPoolIndex) value of 1, one or more second PUCCH and / or second PUSCH transmissions may be determined from the overlapping second PUCCH and / or second PUSCH transmissions. Then, if the second information indicates the ACK NACK feedback mode (ackNackFeedbackMode) as joint, the UE resolves the overlapping for PUCCH and / or PUSCH transmissions among one or more first PUCCH and / or first PUSCH transmissions and one or more second PUCCH and / or second PUSCH transmissions. For example, resolving overlapping for one or more PUCCH and / or PUSCH transmissions may include determining, from the one or more PUCCH and / or PUSCH transmissions, PUCCH and / or PUSCH transmission(s) to be transmitted, and / or PUCCH and / or PUSCH transmission(s) for multiplexing UCI.

[0296] The UE may transmit the PUCCH(s) and / or PUSCH(s). For example, the UE may transmit the PUCCH(s) and / or PUSCH(s) after resolving channel overlapping or collision.

[0297] It should be noted that the second information may also indicate whether to enable (or not) multiplexing UCI of a PUCCH with the first value of the CORESET pool index parameter (the first CORESET pool index parameter value) in a PUSCH with the second value of the CORESET pool index parameter (the second CORESET pool index parameter value). Here, the first CORESET pool index parameter value is different from the second CORESET pool index parameter value. For example, “if the second information indicates the ACK NACK feedback mode (ackNackFeedbackMode) as joint” in the example embodiments of the disclosure may be replaced with “if the second information indicates that UCI of a PUCCH with the first CORESET pool index parameter value can be multiplexed in a PUSCH with the second CORESET pool index parameter value”.

[0298] In an example, when the UE determines overlapping for PUCCH and / or PUSCH transmissions of the same priority index with the same CORESET pool index parameter (e.g., coresetPoolIndex) value,

[0299] - first, the UE resolves overlapping for PUCCHs with repetitions (if any)

[0300] - second, the UE resolves overlapping for PUCCHs without repetitions (if any)

[0301] - third, the UE resolves overlapping for PUSCHs and PUCCHs with repetitions (if any)

[0302] - fourth, the UE resolves overlapping for PUSCHs and PUCCHs without repetitions (if any).

[0303] When the UE determines overlapping for PUCCH and / or PUSCH transmissions of the same priority index with different CORESET pool index parameter (e.g., coresetPoolIndex) values,

[0304] - first, the UE resolves overlapping for PUCCHs with repetitions (if any)

[0305] - second, the UE resolves overlapping for PUCCHs without repetitions (if any)

[0306] - third, the UE resolves overlapping for PUSCHs and PUCCHs with repetitions (if any)

[0307] - fourth, the UE resolves overlapping for PUSCHs and PUCCHs without repetitions (if any)

[0308] The method clarifies the behavior of the UE, and the UE can determine PUCCH(s) and / or PUSCH(s) to be transmitted according to the method, so that the understanding of the transmission of PUCCH(s) and / or PUSCH(s) between the UE and the base station can be consistent, thereby improving the reliability of uplink transmission.

[0309] Method MN2

[0310] According to some aspects of the Method MN2, the UE receives second information that indicates an ACK NACK feedback mode (ackNackFeedbackMode). The UE may receive the second information from the base station. For example, the second information may indicate whether the ACK NACK feedback mode (ackNackFeedbackMode) is separate feedback (ackNackFeedbackMode = separate) or joint feedback (ackNackFeedbackMode = joint). The details of the ACK NACK feedback mode (ackNackFeedbackMode) may refer to the description of Method MN1.

[0311] If the second information indicates the ACK NACK feedback mode (ackNackFeedbackMode) as 'separate', the UE may resolve (or determine) overlapping for PUCCH and / or PUSCH transmissions with the same CORESET pool index parameter (e.g., coresetPoolIndex) value.

[0312] If the second information indicates the ACK NACK feedback mode (ackNackFeedbackMode) as 'joint', the UE may determine a PUSCH among candidate PUSCHs according to the following method:

[0313] - if the candidate PUSCHs include a PUSCH with aperiodic CSI (A-CSI), the UE multiplexes UCI in the PUSCH.

[0314] - if the candidate PUSCHs include first PUSCHs (for example, the first PUSCHs may be PUSCHs scheduled by DCI format(s)) and second PUSCHs (for example, the second PUSCHs may be PUSCHs configured by respective ConfiguredGrantConfig and / or semi-PersistentOnPUSCH), and the UE would multiplex UCI in one of the candidate PUSCHs, and the candidate PUSCHs satisfy the UCI multiplexing conditions, then the UE multiplexes the UCI in a PUSCH from the first PUSCHs.

[0315] - if the UE would multiplex UCI in one of the candidate PUSCHs and the UE does not multiplex aperiodic CSI in any of the candidate PUSCHs, the UE multiplexes the UCI in a PUSCH of a serving cell with the smallest serving cell index (e.g., ServCellIndex). If the UE transmits more than one PUSCH in the slot on the serving cell with the smallest serving cell index (e.g., the ServCellIndex), the UE multiplexes the UCI in the earliest PUSCH that the UE transmits in the slot. If the UE would transmit two (or more) earliest PUSCHs in a slot on a serving cell with the smallest serving cell index (e.g., ServCellIndex), the UE multiplexes the UCI in a PUSCH with the smallest CORESET pool index parameter (e.g., coresetPoolIndex) value among the two (or more) earliest PUSCHs; or, the UE multiplexes the UCI in a PUSCH with the same CORESET pool index parameter (e.g., coresetPoolIndex) value as the PUCCH, among the two (or more) earliest PUSCH.

[0316] The UE may transmit the PUCCH and / or the PUSCH.

[0317] It should be noted that the multiplexing of UCI may need to satisfy predefined timing / timeline conditions, for example, timing / timeline conditions in other embodiments of the disclosure, or any suitable timing / timeline conditions, which are not limited by the example embodiments of the disclosure.

[0318] It should be noted that “if the second information indicates the ACK NACK feedback mode (ackNackFeedbackMode) as 'separate'” in the example embodiments of the disclosure may be replaced with “if the second information is configured to indicate that UCI of a PUCCH with the first CORESET pool index parameter value cannot be multiplexed in a PUSCH with the second CORESET pool index parameter value”.

[0319] The method clarifies the behavior of the UE, and the UE can determine the PUCCH(s) and / or PUSCH(s) to be transmitted according to the method, so that the understanding of the transmission of the PUCCH(s) and / or PUSCH(s) between the UE and the base station can be consistent, thereby improving the reliability of uplink transmission.

[0320] In some cases, the UE may be configured with two levels of priorities (e.g., physical layer priorities). At least one of the Methods MN3 to MN4 may be adopted to resolve overlapping for PUCCH and PUSCH transmissions.

[0321] Method MN3

[0322] The UE resolves (or determines) overlapping for PUCCH and / or PUSCH transmissions with the same CORESET pool index parameter (e.g., coresetPoolIndex) value.

[0323] - The UE resolves (or determines) overlapping for PUCCH and / or PUSCH transmissions with the same priority.

[0324] - The UE resolves (or determines) overlapping for PUCCH and / or PUSCH transmissions with different priorities.

[0325] Optionally (e.g., if the second information indicates the ACK NACK feedback mode (ackNackFeedbackMode) as joint), the UE resolves (or determines) overlapping for PUCCH and / or PUSCH transmissions with different CORESET pool index parameter (e.g., coresetPoolIndex) values.

[0326] - The UE resolves (or determines) overlapping for PUCCH and / or PUSCH transmissions with the same priority.

[0327] - The UE resolves (or determines) overlapping for PUCCH and / or PUSCH transmissions with different priorities.

[0328] A specific example according to the Method MN3 will be described below. Consider the following scenario: a first PUCCH, a second PUCCH, a first PUSCH and a second PUSCH are associated with the value 0 of the CORESET pool index parameter; a third PUCCH, a fourth PUCCH, a third PUSCH and a fourth PUSCH are associated with the value 1 of the CORESET pool index parameter; the first PUCCH, the first PUSCH, the third PUCCH and the third PUSCH are of a first priority, and the second PUCCH, the second PUSCH, the fourth PUCCH and the fourth PUSCH are of a second priority. For the value 0 of the CORESET pool index parameter, the UE resolves overlapping for the first PUCCH and the first PUSCH to determine a fifth PUCCH and / or PUSCH, and resolves overlapping for the second PUCCH and the second PUSCH to determine the sixth PUCCH and / or PUSCH. Then, the UE resolves overlapping for the fifth PUCCH and / or PUSCH and the sixth PUCCH and / or PUSCH to determine a ninth PUCCH and / or PUSCH. Similarly, for the value 1 of the CORESET pool index parameter, the UE resolves overlapping for the third PUCCH and the third PUSCH to determine a seventh PUCCH and / or PUSCH, and resolves overlapping for the fourth PUCCH and the fourth PUSCH to determine an eighth PUCCH and / or PUSCH. Then, the UE resolves overlapping for the seventh PUCCH and / or PUSCH and the eighth PUCCH and / or PUSCH to determine a tenth PUCCH and / or PUSCH. Additionally, in case that the second information indicates the ACK NACK feedback mode (ackNackFeedbackMode) as joint, the UE resolves overlapping for PUCCHs and / or PUSCHs with the same priority among the ninth PUCCH and / or PUSCH and / or the tenth PUCCH and / or PUSCH to determine an eleventh PUCCH and / or PUSCH. Then, the UE resolves overlapping for PUCCHs and / or PUSCHs with different priorities among the eleventh PUCCH and / or PUSCH to determine a twelfth PUCCH and / or PUSCH. The UE may transmit the twelfth PUCCH and / or PUSCH. The twelfth PUCCH and / or PUSCH may carry UCI.

[0329] The method clarifies the behavior of the UE, and the UE can determine PUCCH(s) and / or PUSCH(s) to be transmitted according to the method, so that the understanding of the transmission of PUCCH(s) and / or PUSCH(s) between the UE and the base station can be consistent, thereby improving the reliability of uplink transmission.

[0330] It should be noted that this method may be applicable when the UE is configured with the first parameter.

[0331] Method MN4

[0332] The UE resolves (or determines) overlapping for PUCCH and / or PUSCH transmissions with the same priority.

[0333] - The UE resolves (or determines) overlapping for PUCCH and / or PUSCH transmissions with the same CORESET pool index parameter (e.g., coresetPoolIndex) value.

[0334] - Optionally (e.g., if the second information indicates the ACK NACK feedback mode (ackNackFeedbackMode) as joint), the UE resolves (or determines) overlapping for PUCCH and / or PUSCH transmissions with different CORESET pool index parameter (e.g., coresetPoolIndex) values.

[0335] The UE resolves (or determines) overlapping for PUCCH and / or PUSCH transmissions with different priorities.

[0336] - The UE resolves (or determines) overlapping for PUCCH and / or PUSCH transmissions with the same CORESET pool index parameter (e.g., coresetPoolIndex) value.

[0337] - Optionally (e.g., if the second information indicates the ACK NACK feedback mode (ackNackFeedbackMode) as joint), the UE resolves (or determines) overlapping for PUCCH and / or PUSCH transmissions with different CORESET pool index parameter (e.g., coresetPoolIndex) values.

[0338] The method clarifies the behavior of the UE, and the UE can determine PUCCH(s) and / or PUSCH(s) to be transmitted according to the method, so that the understanding of the transmission of PUCCH(s) and / or PUSCH(s) between the UE and the base station can be consistent, thereby improving the reliability of uplink transmission.

[0339] Method MN5

[0340] In some implementations, if at least one of the following conditions is satisfied (e.g., all conditions are satisfied),

[0341] - the UE is not provided the CORESET pool index parameter (e.g., coresetPoolIndex) or is provided the CORESET pool index parameter (e.g., coresetPoolIndex) with a value of 0 for first CORESETs on active DL BWPs of serving cells

[0342] - the UE is provided the CORESET pool index parameter (e.g., coresetPoolIndex) with a value of 1 for second CORESETs on active DL BWPs of the serving cells

[0343] - the UE is provided ACK NACK feedback mode (ackNackFeedbackMode) = separate.

[0344] - the UE is provided the first information

[0345] the UE does not expect that a PUCCH with the first CORESET pool index parameter (e.g., coresetPoolIndex) value overlaps in time domain with a PUCCH or PUSCH with the second CORESET pool index parameter (e.g., coresetPoolIndex) value.

[0346] Or, after resolving the overlapping for PUCCH and / or PUSCH transmissions with the same CORESET pool index parameter (e.g., coresetPoolIndex) value, the UE does not expect that a PUCCH with the first CORESET pool index parameter (e.g., coresetPoolIndex) value overlaps in time domain with a PUCCH or PUSCH with the second CORESET pool index parameter (e.g., coresetPoolIndex) value, or the UE does not expect that a PUCCH overlaps in time domain with other PUCCH(s) or PUSCH(s).

[0347] Or, the UE does not expect that a PUCCH with the first CORESET pool index parameter (e.g., coresetPoolIndex) value overlaps in time domain with a PUCCH or PUSCH with the second CORESET pool index parameter (e.g., coresetPoolIndex) value if (or and) the PUCCH with the first CORESET pool index parameter (e.g., coresetPoolIndex) value does not overlap in time domain with a PUSCH with the first CORESET pool index parameter (e.g., coresetPoolIndex) value.

[0348] It should be noted that “PUCCH / PUSCH with the first CORESET pool index parameter (e.g., coresetPoolIndex) value” may be understood as a PUCCH / PUSCH triggered by a DCI format, where the DCI format is received in a PDCCH in a first CORESET, and / or the UE is configured with the first CORESET pool index parameter (e.g., coresetPoolIndex) value (or configured with the first SRS resource set index parameter value) in PUCCH resource / PUSCH (e.g., Type-1 CG PUSCH) configuration parameter.

[0349] The method can reduce the implementation complexity.

[0350] In some cases, if the UE is configured with a parameter (e.g., simutaneousPUCCH-PUSCH) that enables simultaneous transmission of a PUCCH and a PUSCH, the UE does not expect that a PUCCH with the first CORESET pool index parameter (e.g., coresetPoolIndex) value overlaps in time domain with a PUSCH with the second CORESET pool index parameter (e.g., coresetPoolIndex) value, where the PUCCH is of the same priority as the PUSCH. The UE does not expect that a PUCCH with the first CORESET pool index parameter (e.g., coresetPoolIndex) value overlaps in time domain with a PUCCH with the second CORESET pool index parameter (e.g., coresetPoolIndex) value.

[0351] Or, after resolving the overlapping for PUCCH and / or PUSCH transmissions with the same CORESET pool index parameter (e.g., coresetPoolIndex) value, the UE does not expect that a PUCCH with the first CORESET pool index parameter (e.g., coresetPoolIndex) value overlaps in time domain with a PUSCH with the second CORESET pool index parameter (e.g., coresetPoolIndex) value, where the PUCCH is of the same priority as the PUSCH, and the UE does not expect that the PUCCH with the first CORESET pool index parameter (e.g., coresetPoolIndex) value overlaps in time domain with a PUCCH with the second CORESET pool index (e.g., coresetPoolIndex) value. Or, the UE does not expect that a PUCCH overlaps in time domain with other PUCCH(s) or PUSCH(s), where the PUCCH is of the same priority as the other PUCCH(s) or PUSCH(s).

[0352] It should be noted that the UE may report a capability to support simultaneous transmission of a PUCCH and a PUSCH (e.g., a PUCCH and a PUSCH with different priorities) and simultaneous transmission of a PUSCH and a PUSCH on a same serving cell.

[0353] In some cases, the CORESET pool index parameter (e.g., coresetPoolIndex) value may be configured for each PUCCH resource (or each PUCCH resource set). A PUCCH resource may be determined according to at least one of the Methods MN6 to MN8.

[0354] Method MN6

[0355] The UE may receive one or more DCI formats that schedules PDSCHs and indicates a same uplink slot for transmission of HARQ-ACK for the PDSCHs. For a PUCCH resource that carries the HARQ-ACK for the PDSCH receptions scheduled by the DCI formats in the uplink slot, a CORESET pool index parameter (e.g., coresetPoolIndex) value for the PUCCH resource may be determined according to at least one of the following, and a PUCCH resource is then determined from PUCCH resources corresponding to the CORESET pool index parameter (e.g., coresetPoolIndex) value:

[0356] - a CORESET pool index parameter (e.g., coresetPoolIndex) value for a last DCI format is the CORESET pool index parameter (e.g., coresetPoolIndex) value for the PUCCH resource.

[0357] - a third value of the CORESET pool index parameter (e.g., coresetPoolIndex) (third coresetPoolIndex value), where the third value of the CORESET pool index parameter (e.g., third coresetPoolIndex value) may be specified by protocols, which may be 0 (or 1), for example. Alternatively, the third value of the CORESET pool index parameter (e.g., third coresetPoolIndex value) may be configured by higher layer parameters.

[0358] - if a CORESET pool index parameter (e.g., coresetPoolIndex) value for at least one of the one or more DCI formats is the third CORESET pool index parameter (e.g., coresetPoolIndex) value, then the CORESET pool index parameter (e.g., coresetPoolIndex) value for the PUCCH resource is the third CORESET pool index parameter (e.g., coresetPoolIndex) value. Otherwise, if none of the one or more DCI formats has a CORESET pool index parameter (e.g., coresetPoolIndex) value of the third CORESET pool index parameter (e.g., coresetPoolIndex) value (or, if CORESET pool index parameter (e.g., coresetPoolIndex) values for all of the one or more DCI formats are a fourth value of the CORESET pool index parameter (e.g., coresetPoolIndex) value (the fourth coresetPoolIndex value), then the CORESET pool index parameter (e.g., coresetPoolIndex) value for the PUCCH resource is the fourth CORESET pool index parameter (e.g., coresetPoolIndex) value. Here, the fourth CORESET pool index parameter (e.g., coresetPoolIndex) value may be determined by the third CORESET pool index parameter (e.g., coresetPoolIndex) value. For example, the third CORESET pool index parameter (e.g., coresetPoolIndex) value is of 0 (or 1), and the fourth CORESET pool index parameter (e.g., coresetPoolIndex) value is of 1 (or 0).

[0359] It should be noted that this method may be applicable to the second information that indicates the ACK NACK feedback mode (ackNackFeedbackMode) as joint. In this manner, the behavior of the UE can be clarified and the reliability of uplink transmission can be improved.

[0360] Method MN7

[0361] The UE may receive one or more SPS PDSCHs and HARQ-ACK for the SPS PDSCHs is transmitted in a same uplink slot, where a PUCCH resource carrying the HARQ-ACK for the SPS PDSCH receptions is transmitted in the uplink slot, and a CORESET pool index parameter (e.g., coresetPoolIndex) value for the PUCCH resource may be determined according to at least one of the following, and a PUCCH resource is then determined from PUCCH resources corresponding to the CORESET pool index parameter (e.g., coresetPoolIndex) value:

[0362] - the third CORESET pool index parameter (e.g., coresetPoolIndex) value, where the third CORESET pool index parameter (e.g., coresetPoolIndex) value may be specified by protocols, which may be 0 (or 1), for example. Alternatively, the third CORESET pool index parameter (e.g., coresetPoolIndex) value may be configured by higher layer parameters.

[0363] - if a CORESET pool index parameter (e.g., coresetPoolIndex) value for at least one of DCI formats activating the SPS PDSCHs is the third CORESET pool index parameter (e.g., coresetPoolIndex) value, then the CORESET pool index parameter (e.g., coresetPoolIndex) value for the PUCCH resource is the third CORESET pool index parameter (e.g., coresetPoolIndex) value. Otherwise, if none of the DCI formats activating the SPS PDSCHs has a CORESET pool index parameter (e.g., coresetPoolIndex) value of the third CORESET pool index parameter (e.g., coresetPoolIndex) value (or, if the CORESET pool index parameter (e.g., coresetPoolIndex) values for all of the DCI formats activating the SPS PDSCHs are the fourth CORESET pool index parameter (e.g., coresetPoolIndex) value, then the CORESET pool index parameter (e.g., coresetPoolIndex) value for the PUCCH resource is the fourth CORESET pool index parameter (e.g., coresetPoolIndex) value. Here, the fourth CORESET pool index parameter (e.g., coresetPoolIndex) value may be determined by the third CORESET pool index parameter (e.g., coresetPoolIndex) value. For example, the third CORESET pool index parameter (e.g., coresetPoolIndex) value is of 0 (or 1), and the fourth CORESET pool index parameter (e.g., coresetPoolIndex) value is of 1 (or 0).

[0364] It should be noted that this method may be applicable to a scenario where CORESET pool index parameter (e.g., coresetPoolIndex) values for DCI format activating SPS PDSCHs are different and / or a scenario where the second information indicates the ACK NACK feedback mode (ackNackFeedbackMode) as joint. In this manner, the behavior of the UE can be clarified and the reliability of uplink transmission can be improved.

[0365] Method MN8

[0366] In some cases, the UE is configured with the first information, and PUCCH resources or PUCCH resource sets / lists for carrying HARQ-ACK for PDSCH receptions may be configured separately for each CORESET pool index parameter (e.g., coresetPoolIndex) value.

[0367] In an example, PUCCH resources (e.g., SPS-PUCCH-AN) or PUCCH resource sets / lists (e.g., SPS-PUCCH-AN-List) for carrying HARQ-ACK for SPS PDSCH receptions may be configured separately for each CORESET pool index parameter (e.g., coresetPoolIndex) value.

[0368] If the second information indicates the ACK NACK feedback mode (ackNackFeedbackMode) as separate, the UE separately determines a PUCCH resource for carrying HARQ-ACK for SPS PDSCH receptions according to the CORESET pool index parameter (e.g., coresetPoolIndex) value. For example, if the CORESET pool index parameter (e.g., coresetPoolIndex) value for the DCI format activating the SPS PDSCHs is 0, the PUCCH resource for the HARQ-ACK for the SPS PDSCH receptions is determined from PUCCH resources associated with the CORESET pool index parameter (e.g., coresetPoolIndex) value of 0.

[0369] It should be noted that this method is also applicable to HARQ-ACK for PDSCH receptions scheduled by DCI formats.

[0370] This method can improve the flexibility of scheduling and reduce the uplink transmission delay.

[0371] Method MN9

[0372] In some implementations, when the UE determines overlapping for PUCCH and / or PUSCH transmissions (e.g., overlapping for PUCCH and / or PUSCH transmissions of the same priority index) with the same CORESET pool index parameter (e.g., coresetPoolIndex) value, a PUCCH and a PUSCH with the same CORESET pool index parameter (e.g., coresetPoolIndex) value and overlapping need to satisfy a predefined timing / timeline condition, while a PUCCH and a PUSCH with different CORESET pool index parameter (e.g., coresetPoolIndex) values need not (or are not required to) satisfy the predefined timing / timeline condition. For example, the timing / timeline condition may be timing / timeline conditions defined in other embodiments of the disclosure.

[0373] This method can improve the scheduling flexibility and reduce the scheduling delay, thereby improving the spectrum efficiency.

[0374] It should be noted that this method may be applicable when the UE is configured with the first parameter.

[0375] Method MN11

[0376] In some implementations, if the UE is configured with the first information, such as parameter enableSTx2PofmDCI, it may not be required to satisfy a predefined timing / timeline condition for overlapping PUSCHs (e.g., PUSCHs overlapping in time domain) scheduled by PDCCHs that are associated with different control resource set parameters (e.g., different ControlResourceSets) having different values of the CORESET pool index parameter (e.g., coresetPoolIndex) on a serving cell. For example, the timing / timeline condition may be timing / timeline conditions defined in other embodiments of the disclosure. This method can improve the flexibility of scheduling.

[0377] In an example, except for the case when the UE is configured by the PDCCH configuration parameter (e.g., higher layer parameter　PDCCH-Config)　that contains two different values of the 　CORESET pool index parameter (e.g., CoresetPoolIndex)　in　the control resource set parameter (e.g., ControlResourceSet)　for an active BWP of a serving cell and PDCCHs that schedule two　non-overlapping in time domain　PUSCHs are associated to different control resource set parameters (e.g., different ControlResourceSets)　having different values of　the CORESET pool index parameter (e.g., coresetPoolIndex) or PDCCHs that schedule two　PUSCHs (　e.g., PUSCHs overlapping in time domain) are associated to different control resource set parameters (e.g., different ControlResourceSets) having different values of the CORESET pool index parameter (e.g., coresetPoolIndex) and the UE is configured with the first information (e.g., parameter enableSTx2PofmDCI),　for any two HARQ process IDs in a given scheduled cell, if the UE is scheduled to start a first PUSCH transmission starting in symbol　j　by a PDCCH ending in symbol　i　on a scheduling cell, the UE is not expected to be scheduled to transmit a PUSCH (e.g., a second PUSCH) starting earlier than the end of the first PUSCH by a PDCCH that ends later than symbol　i　of the scheduling cell.

[0378] In another example, when the UE is configured by the PDCCH configuration parameter (e.g., higher layer parameter　PDCCH-Config)　that contains two different values of the 　CORESET pool index parameter (e.g., CoresetPoolIndex)　in　the control resource set parameter (e.g., ControlResourceSet)　for an active BWP of a serving cell and PDCCHs that schedule two　non-overlapping in time domain　PUSCHs are associated to different control resource set parameters (e.g., different ControlResourceSets)　having different values of　the CORESET pool index parameter (e.g., coresetPoolIndex) or PDCCHs that schedule two　PUSCHs (　e.g., PUSCHs overlapping in time domain) are associated to different control resource set parameters (e.g., different ControlResourceSets) having different values of the CORESET pool index parameter (e.g., coresetPoolIndex) and the UE is configured with the first information (e.g., parameter enableSTx2PofmDCI),　for any two HARQ process IDs in a given scheduled cell, if the UE is scheduled to start a first PUSCH transmission starting in symbol　j　by a PDCCH that is associated to a value of　the CORESET pool index parameter (e.g., coresetPoolIndex) (e.g., the first value of the coresetPoolIndex, i.e., first coresetPoolIndex value) and ends in symbol　i　on a scheduling cell, the UE may transmit a PUSCH (e.g., a second PUSCH) starting earlier than the end of the first PUSCH by a PDCCH that associated to a different value of　the CORESET pool index parameter (e.g., coresetPoolIndex) (e.g., the second value of the coresetPoolIndex, i.e., second coresetPoolIndex value) and ends later than symbol　i　of the scheduling cell.

[0379] Method MN10

[0380] In some implementations, it may be configured by higher layer signaling (e.g., the first parameter) or based on UE capability report whether the UE is enabled / able to receive a second PDCCH after receiving a first PDCCH, where a first DCI format carried by the first PDCCH schedules a PUSCH (e.g., PUSCH transmission with repetitions) and a second DCI format carried by the second PDCCH indicates a PUCCH (e.g., PUCCH with HARQ-ACK) and the PUCCH overlaps in time domain with the PUSCH. For example, the PUCCH overlaps with a repetition of the PUSCH transmission. For example, the repetition of the PUSCH transmission may be a repetition of the PUSCH transmission other than a first repetition. The repetition of the PUSCH transmission may be a repetition of the PUSCH transmission that does not overlap with a first predefined symbol.

[0381] It should be noted that “the PUCCH overlaps in time domain with the PUSCH” may be replaced by “if the UE multiplexes the HARQ-ACK in the PUSCH”.

[0382] For example, the UE does not expect to detect a DCI format indicating corresponding HARQ-ACK information in a slot, if the UE is not configured with the first parameter, and if the UE previously detects a DCI format scheduling a PUSCH transmission in the slot, and if the UE multiplexes the HARQ-ACK information in the PUSCH transmission.

[0383] For another example, the UE does not expect to detect a DCI format indicating corresponding HARQ-ACK information in a slot, if the UE previously detects a DCI format scheduling a PUSCH transmission in the slot, and if the UE multiplexes the HARQ-ACK information in the PUSCH transmission, and if the UE is not configured with the first parameter and the PUSCH transmission is configured or indicated with repetitions.

[0384] The first predefined symbol may be specified by protocols and / or configured by higher layer signaling. For example, the first predefined symbol may be at least one of the following.

[0385] - Downlink symbol(s) configured semi-statically (configured by higher signaling) (e.g., downlink symbol(s) configured by 3GPP parameters tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated).

[0386] - Symbol(s) of an SSB.

[0387] - Symbol(s) for CORESET0 (a CORESET associated with a Type0-PDCCH CSS set).

[0388] - Unavailable symbol(s) configured by higher layer signaling.

[0389] - Y symbols after an SSB. Here, y is an integer, which may be specified by protocols and / or configured by higher layer signaling.

[0390] It should be noted that, when the UE reports that it can receive a second DCI format scheduling a PUCCH with HARQ-ACK after receiving a first DCI format scheduling a PUSCH through the capability report and the UE multiplexes the HARQ-ACK in the PUSCH, the UE may report whether at least one of the following is supported through the capability report:

[0391] - Change of the HARQ-ACK codebook size (a number of HARQ-ACK information bits) in the PUSCH after receiving the second DCI format.

[0392] - PUCCH resource change in time domain (e.g., OFDM symbol(s)) with the HARQ-ACK after receiving the second DCI format.

[0393]

[0394] In an example, when the UE does not report the capability to support PUCCH resource change in time domain with the HARQ-ACK after receiving the second DCI format, the UE does not expect to detect the second DCI format indicating a first PUCCH with corresponding HARQ-ACK information in a slot, if the UE previously detects a first DCI format scheduling a PUSCH transmission in the slot, and if the UE multiplexes HARQ-ACK information of a second PUCCH in the PUSCH transmission in the slot before detecting the second DCI format and the time domain resource of the first PUCCH is different from that of the second PUCCH.

[0395] It should be noted that “the UE is not configured with the first parameter” in the example embodiments of the disclosure may be replaced by “the UE does not report a capability to support the first capability”. The first capability may be that the UE receive a second PDCCH after receiving a first PDCCH, where a first DCI format carried by the first PDCCH schedules a PUSCH (e.g., PUSCH transmission with repetitions) and a second DCI format carried by the second PDCCH indicates a PUCCH (e.g., PUCCH with HARQ-ACK) and the PUCCH overlaps in time domain with the PUSCH.

[0396] The method can improve the flexibility of scheduling, and the network can adopt different scheduling methods for UEs with different capabilities by reporting different UE capabilities, thereby improving the flexibility of scheduling.

[0397] In some implementations, it may also be specified by protocols and / or higher layer signaling that if the UE receives a first DCI format scheduling a PUSCH that overlaps with a first PUCCH with HARQ-ACK in a slot and the UE multiplexes the HARQ-ACK in the PUSCH, if the UE receives, after the first DCI format, a second DCI format indicating multiplexing of the HARQ-ACK in a second PUCCH transmission in the slot, the UE determine a PUSCH for multiplexing according to a time domain resource (or, symbol(s)) of the first PUCCH; and / or, the UE multiplexes the HARQ-ACK in the PUSCH regardless of whether the second PUSCH overlaps with the PUSCH; and / or the UE multiplexes the HARQ-ACK in the PUSCH regardless of whether time domain resources of the second PUCCH change. That is, the UE does not re-determine a PUSCH overlapping with the PUCCH. Or, the UE does not re-determine a PUSCH for multiplexing the HARQ-ACK information in the slot.

[0398] The method can reduce the implementation complexity of the UE while improving the flexibility of scheduling, and can prevent the UE from re-determining PUCCH and / or PUSCH resources.

[0399] It should be noted that this method may be applicable to the case where the UE is not configured with a parameter indicating UCI multiplexing with different priorities (e.g., uci-MuxWithDiffPrio), which may simplify the implementation complexity of the UE.

[0400] In an example, when the UE is not configured with the first parameter or the UE is configured with the parameter indicating UCI multiplexing with different priorities (e.g., uci-MuxWithDiffPrio), the UE does not expect to detect a DCI format indicating corresponding HARQ-ACK information in a slot, if the UE previously detects a DCI format scheduling the PUSCH transmission in the slot, and if the UE multiplexes the HARQ-ACK information in the PUSCH transmission.

[0401] In another example, the UE does not expect to detect a DCI format indicating corresponding HARQ-ACK information in a slot, if the UE previously detects a DCI format scheduling a PUSCH transmission in the slot, and if the UE multiplexes the HARQ-ACK information in the PUSCH transmission, and if the UE is not configured with the first parameter or is configured with the parameter indicating UCI multiplexing with different priorities (e.g., uci-MuxWithDiffPrio) and the PUSCH transmission is configured or indicated with repetitions.

[0402] It should be noted that “a DCI format indicating corresponding HARQ-ACK information” may refer to a DCI format scheduling a PDSCH reception and indicating HARQ-ACK information for the PDSCH reception or a DCI format without scheduling a PDSCH reception and indicating HARQ-ACK information for the DCI format.

[0403] In some implementations, it should be noted that, when the UE reports that it can receive a second DCI format scheduling a PUCCH with HARQ-ACK after receiving a first DCI format scheduling a PUSCH through the capability report and the UE multiplexes the HARQ-ACK in the PUSCH, the UE may report whether at least one of the following is supported through the capability report.

[0404] - Change of the HARQ-ACK codebook size (a number of HARQ-ACK information bits) in the PUSCH after receiving the second DCI format.

[0405] - PUCCH resource change in time domain (e.g., OFDM symbol(s)) with the HARQ-ACK after receiving the second DCI format.

[0406]

[0407] - UCI multiplexing with different priorities. For example, multiplexing of HARQ-ACK with different priorities in a PUCCH or PUSCH.

[0408] It should be noted that “the UE is configured with the parameter indicating UCI multiplexing with different priorities (e.g., uci-MuxWithDiffPrio)” in the example embodiments of the disclosure may also be replaced by “the UE does not report a capability to support UCI multiplexing with different priorities”, for example, additional UE capabilities in the scenario discussed in the examples of the disclosure.

[0409] FIG. 10 illustrates a flowchart of a method performed by a terminal according to some embodiments of the disclosure.

[0410] Referring to FIG. 10, in operation S1010, the terminal receives second information that indicates a HARQ-ACK feedback mode. For example, the terminal may receive the second information from a base station through downlink control signaling.

[0411] Next, in operation S1020, the terminal resolves overlapping for uplink channels associated with a same value of a CORESET pool index parameter. The uplink channels may include PUCCH(s) and / or PUSCH(s).

[0412] Then, in operation S1030, in case that the second information indicates the HARQ-ACK feedback mode as joint, the terminal resolves overlapping for uplink channels associated with different values of the CORESET pool index parameter.

[0413] In some implementations, one or more of operations S1010 to S1030 may be performed based on the methods described according to various example embodiments of the disclosure (e.g., the embodiments described in connection with FIGS. 4-7, and various methods described above, such as Methods MN1-MN10).

[0414] In some implementations, the method 1000 may omit one or more of operations S1010 to S1030, or may include additional operations, for example, operations described by a terminal (e.g., a UE) according to various example embodiments of the disclosure (e.g., the embodiments described in connection with FIGS. 4-7, and various methods described above, such as Methods MN1-MN10).

[0415] FIG. 11 illustrates a flowchart of a method performed by a base station according to some embodiments of the disclosure.

[0416] Referring to FIG. 11, in operation S1110, the base station transmits second information to the terminal, where the second information indicates a HARQ-ACK feedback mode. For example, the base station may transmit the second information to the terminal through downlink control signaling.

[0417] Next, the base station receives an uplink channel from the terminal in operation S1120. In case that the second information indicates the HARQ-ACK feedback mode as joint, the second information is used to resolve multiple uplink channels associated with different values of a CORESET pool index parameter. The uplink channels may include PUCCH(s) and / or PUSCH(s).

[0418] In some implementations, one or more of S1110 to S1120 may be performed based on the methods described according to various example embodiments of the disclosure (e.g., the embodiments described in connection with FIGS. 4-7, and various manners described above, such as in manners MN1-MN10).

[0419] In some implementations, the method 1100 may omit one or more of operations S1110 to S1120, or may include additional operations, such as those described by the base station according to various example embodiments of the disclosure (for example, the embodiments described in connection with FIGS. 4-7, and various manners described above, such as manners MN1-MN10).

[0420] 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.

[0421] 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.

[0422] 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, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

[0423] 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.

[0424] 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.

[0425] 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

1.A method performed by a user equipment (UE) in a wireless communication system, the method comprising:receiving a radio resource control (RRC) configuration message including information indicating an acknowledgement (ACK) negative ACK (NACK) feedback mode and a control resource set (CORESET) pool index, wherein the ACK NACK feedback mode is at least one of a separate or a joint and wherein the CORESET pool index is 0 or 1;receiving a first downlink control information (DCI) in a physical downlink control channel (PDCCH) received in a first CORESET from first CORESETs associated with the CORESET pool index 0;receiving a second DCI in a PDCCH received in a second CORESET from second CORESETs associated with the CORESET pool index 1; andin case that the ACK NACK feedback mode is set to the joint and information indicating simultaneous transmission of two physical uplink shared channels (PUSCHs) is configured, transmitting uplink control information (UCI) in a physical uplink shared channel (PUSCH) associated with the CORESET pool index 0.2.The method of claim 1,wherein in case that the ACK NACK feedback mode is set to the separate, the UCI is not transmitted in a PUSCH associated with the first CORESETs to overlap with a PUSCH associated with the second CORESETs and not overlap with a PUSCH associated with first CORESETs.3.The method of claim 1,wherein the UCI is transmitted in a PUSCH in the slot that start at a same symbol on a serving cell with a smallest index.4.The method of claim 1,wherein the information indicating simultaneous transmission of the two PUSCHs is included in the RRC configuration message.5.A method performed by a base station in a wireless communication system, the method comprising:transmitting, to a user equipment (UE), a radio resource control (RRC) configuration message including information indicating an acknowledgement (ACK) negative ACK (NACK) feedback mode and a control resource set (CORESET) pool index, wherein the ACK NACK feedback mode is at least one of a separate or a joint and wherein the CORESET pool index is 0 or 1;transmitting, to the UE, a first downlink control information (DCI) in a physical downlink control channel (PDCCH) received in a first CORESET from first CORESETs associated with the CORESET pool index 0;transmitting, to the UE a second DCI in a PDCCH received in a second CORESET from second CORESETs associated with the CORESET pool index 1; andin case that the ACK NACK feedback mode is set to the joint and information indicating simultaneous transmission of two physical uplink shared channels (PUSCHs) is configured, receiving, form the UE, uplink control information (UCI) in a physical uplink shared channel (PUSCH) associated with the CORESET pool index 0.6.The method of claim 5,wherein in case that the ACK NACK feedback mode is set to the separate, the UCI is not transmitted in a PUSCH associated with the first CORESETs to overlap with a PUSCH associated with the second CORESETs and not overlap with a PUSCH associated with first CORESETs.7.The method of claim 5,wherein the UCI is transmitted in a PUSCH in the slot that start at a same symbol on a serving cell with a smallest index.8.The method of claim 5,wherein the information indicating simultaneous transmission of the two PUSCHs is included in the RRC configuration message.9.A user equipment (UE) in a wireless communication system, the UE comprising:a transceiver; anda controller coupled with the transceiver configured to:receive a radio resource control (RRC) configuration message including information indicating an acknowledgement (ACK) negative ACK (NACK) feedback mode and a control resource set (CORESET) pool index, wherein the ACK NACK feedback mode is at least one of a separate or a joint and wherein the CORESET pool index is 0 or 1,receive a first downlink control information (DCI) in a physical downlink control channel (PDCCH) received in a first CORESET from first CORESETs associated with the CORESET pool index 0,receive a second DCI in a PDCCH received in a second CORESET from second CORESETs associated with the CORESET pool index 1, andin case that the ACK NACK feedback mode is set to the joint and information indicating simultaneous transmission of two physical uplink shared channels (PUSCHs) is configured, transmit uplink control information (UCI) in a physical uplink shared channel (PUSCH) associated with the CORESET pool index 0.10.The UE of claim 9,wherein in case that the ACK NACK feedback mode is set to the separate, the UCI is not transmitted in a PUSCH associated with the first CORESETs to overlap with a PUSCH associated with the second CORESETs and not overlap with a PUSCH associated with first CORESETs.11.The UE of claim 9,wherein the UCI is transmitted in a PUSCH in the slot that start at a same symbol on a serving cell with a smallest index.12.The UE of claim 9,wherein the information indicating simultaneous transmission of the two PUSCHs is included in the RRC configuration message.13.A base station in a wireless communication system, the base station comprising:a transceiver; anda controller coupled with the transceiver configured to:transmit, to a user equipment (UE), a radio resource control (RRC) configuration message including information indicating an acknowledgement (ACK) negative ACK (NACK) feedback mode and a control resource set (CORESET) pool index, wherein the ACK NACK feedback mode is at least one of a separate or a joint and wherein the CORESET pool index is 0 or 1,transmit, to the UE, a first downlink control information (DCI) in a physical downlink control channel (PDCCH) received in a first CORESET from first CORESETs associated with the CORESET pool index 0,transmit, to the UE a second DCI in a PDCCH received in a second CORESET from second CORESETs associated with the CORESET pool index 1, andin case that the ACK NACK feedback mode is set to the joint and information indicating simultaneous transmission of two physical uplink shared channels (PUSCHs) is configured, receive, form the UE, uplink control information (UCI) in a physical uplink shared channel (PUSCH) associated with the CORESET pool index 0.14.The base station of claim 13,wherein in case that the ACK NACK feedback mode is set to the separate, the UCI is not transmitted in a PUSCH associated with the first CORESETs to overlap with a PUSCH associated with the second CORESETs and not overlap with a PUSCH associated with first CORESETs.15.The base station of claim 13,wherein the UCI is transmitted in a PUSCH in the slot that start at a same symbol on a serving cell with a smallest index, andwherein the information indicating simultaneous transmission of the two PUSCHs is included in the RRC configuration message.

Images