Method and apparatus in wireless communication system

Abstract

A method and an apparatus in a wireless communication system are provided. The method includes receiving configuration information of a first configured grant (CG) physical uplink shared channel (PUSCH) for a first serving cell, wherein the first CG PUSCH overlaps in a time domain with a physical uplink control channel (PUCCH) with uplink control information (UCI), receiving a physical downlink control channel (PDCCH) that carries a downlink control information (DCI) format, wherein the DCI format indicates a reception of a physical downlink channel or a physical downlink signal on the first serving cell, and in case that the first CG PUSCH does not overlap in the time domain with the physical downlink channel or the physical downlink signal, multiplexing the UCI in the first CG PUSCH, and / or in case that the first CG PUSCH overlaps in the time domain with the physical downlink channel or the physical downlink signal, not multiplexing the UCI in the first CG PUSCH.

Description

METHOD AND APPARATUS IN WIRELESS COMMUNICATION SYSTEM

[0001] The disclosure relates to the wireless communication technology, and more specifically, to a method and an apparatus 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 procedure (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] According to some aspects of the disclosure, a method performed by a terminal in a wireless communication system is provided. The method includes: receiving configuration information of a first configured grant (CG) physical uplink shared channel (PUSCH) for a first serving cell, wherein the first CG PUSCH overlaps in a time domain with a physical uplink control channel (PUCCH) with uplink control information (UCI); receiving a physical downlink control channel (PDCCH) that carries a downlink control information (DCI) format, wherein the DCI format indicates a reception of a physical downlink channel or a physical downlink signal on the first serving cell; and in case that the first CG PUSCH does not overlap in the time domain with the physical downlink channel or the physical downlink signal, multiplexing the UCI in the first CG PUSCH, and / or in case that the first CG PUSCH overlaps in the time domain with the physical downlink channel or the physical downlink signal, not multiplexing the UCI in the first CG PUSCH, wherein an interval between an ending symbol of the PDCCH reception and a starting symbol of the PUCCH transmission is greater than or equal to a first time.

[0009] In combination with one or more aspects of the method performed by the terminal described above, for example, in case that the first CG PUSCH does not overlap in the time domain with the physical downlink channel or the physical downlink signal, the PUCCH is not transmitted; and / or in case that the first CG PUSCH overlaps in the time domain with the physical downlink channel or the physical downlink signal, the PUCCH is transmitted.

[0010] In combination with one or more aspects of the method performed by the terminal described above, for example, the first time is a predefined time; and / or the first time is a preparation time for canceling the transmission of the first CG PUSCH.

[0011] In combination with one or more aspects of the method performed by the terminal described above, for example, based on a transmission time of the first CG PUSCH not overlapping with a reception time of the physical downlink channel or the physical downlink signal, the first CG PUSCH does not overlap in the time domain with the physical downlink channel or the physical downlink signal; and / or based on the transmission time of the first CG PUSCH overlapping with the reception time of the physical downlink channel or the physical downlink signal, the first CG PUSCH overlaps in the time domain with the physical downlink channel or the physical downlink signal.

[0012] In combination with one or more aspects of the method performed by the terminal described above, for example, the method further includes: in case that the first CG PUSCH does not overlap with higher layer configured downlink symbols or subband full duplex (SBFD) symbols, multiplexing the UCI in the first CG PUSCH and / or not transmitting the PUCCH; and / or in case that the first CG PUSCH overlaps with a higher layer configured downlink symbol or SBFD symbol, not multiplexing the UCI in the first CG PUSCH and / or transmitting the PUCCH.

[0013] In combination with one or more aspects of the method performed by the terminal described above, for example, the method further includes: in case that the first CG PUSCH overlaps with at least one higher layer configured downlink symbol or SBFD symbol and all frequency domain resources of the first CG PUSCH on the at least one higher layer configured downlink symbol or SBFD symbol are located in an uplink subband, multiplexing the UCI in the first CG PUSCH and / or not transmitting the PUCCH; and / or in case that the first CG PUSCH overlaps with at least one higher layer configured downlink symbol or SBFD symbol and at least a portion of frequency domain resources of the first CG PUSCH on the at least one higher layer configured downlink symbol or SBFD symbol are located in a downlink subband, not multiplexing the UCI in the first CG PUSCH and / or transmitting the PUCCH.

[0014] In combination with one or more aspects of the method performed by the terminal described above, for example, the first CG PUSCH overlaps with at least one higher layer configured downlink symbol or SBFD symbol, and all frequency domain resources of the first CG PUSCH on the at least one higher layer configured downlink symbol or SBFD symbol are located in an uplink subband.

[0015] In combination with one or more aspects of the method performed by the terminal described above, for example, the method further includes: in case that the PUCCH overlaps in the time domain with a second CG PUSCH transmission that does not overlap with higher layer configured downlink symbols, multiplexing the UCI in the second CG PUSCH transmission.

[0016] In combination with one or more aspects of the method performed by the terminal described above, for example, the second CG PUSCH is on the first serving cell; or the second CG PUSCH is on a second serving cell different from the first serving cell.

[0017] In combination with one or more aspects of the method performed by the terminal described above, for example, the first serving cell includes an SBFD cell; the second serving cell includes a non-SBFD cell.

[0018] In combination with one or more aspects of the method performed by the terminal described above, for example, the method further includes: not multiplexing the UCI in the first CG PUSCH, and / or transmitting the PUCCH.

[0019] 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, to a terminal, configuration information of a first configured grant (CG) physical uplink shared channel (PUSCH) for a first serving cell, wherein the first CG PUSCH overlaps in a time domain with a physical uplink control channel (PUCCH) with uplink control information (UCI); and transmitting, to the terminal, a physical downlink control channel (PDCCH) that carries a downlink control information (DCI) format, wherein the DCI format indicates a transmission of a physical downlink channel or a physical downlink signal on the first serving cell, wherein in case that the first CG PUSCH does not overlap in the time domain with the physical downlink channel or the physical downlink signal, the UCI is multiplexed in the first CG PUSCH, and / or in case that the first CG PUSCH overlaps in the time domain with the physical downlink channel or the physical downlink signal, the UCI is not multiplexed in the first CG PUSCH, wherein an interval between an ending symbol of the PDCCH and a starting symbol of the PUCCH is greater than or equal to a first time.

[0020] In combination with one or more aspects of the method performed by the base station described above, for example, in case that the first CG PUSCH does not overlap in the time domain with the physical downlink channel or the physical downlink signal, the PUCCH is not transmitted by the terminal; and / or in case that the first CG PUSCH overlaps in the time domain with the physical downlink channel or the physical downlink signal, the base station receives the PUCCH.

[0021] In combination with one or more aspects of the method performed by the base station described above, for example, the first time is a predefined time; and / or the first time is a preparation time for canceling the transmission of the first CG PUSCH.

[0022] In combination with one or more aspects of the method performed by the base station described above, for example, based on a reception time of the first CG PUSCH not overlapping with a transmission time of the physical downlink channel or the physical downlink signal, the first CG PUSCH does not overlap in the time domain with the physical downlink channel or the physical downlink signal; and / or based on the reception time of the first CG PUSCH overlapping with the transmission time of the physical downlink channel or the physical downlink signal, the first CG PUSCH overlaps in the time domain with the physical downlink channel or the physical downlink signal.

[0023] In combination with one or more aspects of the method performed by the base station described above, for example, in case that the first CG PUSCH does not overlap with higher layer configured downlink symbols or subband full duplex (SBFD) symbols, the UCI is multiplexed in the first CG PUSCH and / or the PUCCH is not transmitted by the terminal; and / or in case that the first CG PUSCH overlaps with a higher layer configured downlink symbol or SBFD symbol, the UCI is not multiplexed in the first CG PUSCH and / or the base station receives the PUCCH.

[0024] In combination with one or more aspects of the method performed by the base station described above, for example, in case that the first CG PUSCH overlaps with at least one higher layer configured downlink symbol or SBFD symbol and all frequency domain resources of the first CG PUSCH on the at least one higher layer configured downlink symbol or SBFD symbol are located in an uplink subband, the UCI is multiplexed in the first CG PUSCH and / or the PUCCH is not transmitted by the terminal; and / or in case that the first CG PUSCH overlaps with at least one higher layer configured downlink symbol or SBFD symbol and at least a portion of frequency domain resources of the first CG PUSCH on the at least one higher layer configured downlink symbol or SBFD symbol are located in a downlink subband, the UCI is not multiplexed in the first CG PUSCH and / or the base station receives the PUCCH.

[0025] In combination with one or more aspects of the method performed by the base station described above, for example, the first CG PUSCH overlaps with at least one higher layer configured downlink symbol or SBFD symbol, and all frequency domain resources of the first CG PUSCH on the at least one higher layer configured downlink symbol or SBFD symbol are located in an uplink subband.

[0026] In combination with one or more aspects of the method performed by the base station described above, for example, in case that the PUCCH overlaps in the time domain with a second CG PUSCH transmission that does not overlap with higher layer configured downlink symbols, the UCI is multiplexed in the second CG PUSCH transmission.

[0027] In combination with one or more aspects of the method performed by a base station described above, for example, the second CG PUSCH is on the first serving cell; or the second CG PUSCH is on a second serving cell different from the first serving cell.

[0028] In combination with one or more aspects of the method performed by the base station described above, for example, the first serving cell includes an SBFD cell; the second serving cell includes a non-SBFD cell.

[0029] In combination with one or more aspects of the method performed by the base station described above, for example, the UCI is not multiplexed in the first CG PUSCH, and / or the base station receives the PUCCH.

[0030] According to some aspects of the disclosure, there is also provided a terminal in a wireless communication system. The terminal includes a transceiver, and one or more processors coupled with the transceiver and configured to perform one or more aspects of the above-mentioned methods performed by the terminal.

[0031] 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 one or more processors coupled with the transceiver and configured to perform one or more aspects of the methods performed by the base station.

[0032] 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 performed by the terminal can be implemented when the one or more computer programs are executed by one or more processors.

[0033] 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 performed by the base station can be implemented when the one or more computer programs are executed by one or more processors.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0047] 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".

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

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

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

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

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

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

[0054] Terms used herein to describe the disclosure are not intended to limit and / or define the scope of the disclosure. 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 disclosure belongs.

[0055] 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 items, unless the context clearly dictates otherwise. For example, reference to "a component surface" includes reference to one or more such surfaces.

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

[0057] As used herein, "a portion of" or "a part 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.

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

[0059] In the disclosure, ' / ' as a parallel symbol may mean 'and / or'. For example, 'A / B' may refer to A and / or B.

[0060] 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. As another example, "less than", "less than or equal to" and "no greater than" may be used interchangeably. "Greater than", "greater than or equal to" and "no less than" may be used interchangeably.

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

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

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

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

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

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

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

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

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

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

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

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

[0073] 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 the disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0089] In some implementations, two or more UEs 116 may communicate directly using one or more sidelink channels (e.g., 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)).

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

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

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

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

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

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

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

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

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

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

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

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

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

[0103] In some cases, one or more physical downlink channels or signals may overlap in the time domain with one or more uplink physical channels or signals. At this time, how to ensure the reliability of uplink transmission is a problem that needs to be solved. Therefore, there is a need for an enhanced transmission method of uplink data and / or control information.

[0104] In order to at least solve the above technical problems, the disclosure provides 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.

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

[0106] 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 (DL) data channel of a physical layer or from a terminal to a base station over an uplink (UL) 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).

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

[0108] - MIB (master information block)

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

[0110] - RRC signaling

[0111] - MAC CE

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

[0113] - PDCCH (physical downlink control channel)

[0114] - DCI (downlink control information)

[0115] - UE-specific DCI

[0116] - group common DCI

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

[0118] - scheduling DCI (e.g., DCI for scheduling downlink or uplink data)

[0119] - non-scheduling DCI (e.g., DCI other than DCI for scheduling downlink or uplink data)

[0120] - PUCCH (physical uplink control channel)

[0121] - UCI (uplink control information)

[0122] - Paging

[0123] - PRACH (physical random access channel)

[0124] - RAR (random access response)

[0125] In 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 / or PRACH, and the higher layer signaling may include RRC signaling and / or a MAC CE.

[0126] In 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 (e.g., 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.

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

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

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

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

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

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

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

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

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

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

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

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

[0139] In implementations described in connection with FIG. 4 or FIG. 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.

[0140] In implementations described in connection with FIG. 4 or FIG. 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.

[0141] In implementations described in connection with FIG. 4 or FIG. 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, 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).

[0142] It should be noted that, in the disclosure, the following terms may be used interchangeably:

[0143] - DCI

[0144] - DCI format

[0145] - PDCCH

[0146] - grant

[0147] - dynamic grant.

[0148] In implementations described in connection with FIG. 4 or FIG. 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), CG (Configured Grant) UCI, or UTO (unused transmission occasion)-UCI. In the disclosure, when UCI is carried by a PUCCH, the UCI may be used interchangeably with the PUCCH.

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

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

[0151] In implementations described in connection with FIG. 4 or FIG. 5, a time unit where the first transceiving node transmits the first data and / or the first control signaling may be a downlink time unit, such as a downlink slot.

[0152] In implementations described in connection with FIG. 4 or FIG. 5, a time unit where the second transceiving node transmits the second data and / or the second control signaling may be an uplink time unit, such as an uplink slot or PUCCH slot or PCell (primary cell) slot or PUCCH slot on PCell. The "PUCCH slot" may be understood as a PUCCH transmission slot.

[0153] In the disclosure, a time unit (e.g., a downlink time unit or an uplink 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.

[0154] FIG. 6 illustrates a flowchart of a method 600 performed by a base station according to an example embodiment of the disclosure.

[0155] Referring to FIG. 6, in operation S610, the base station transmits downlink data and / or downlink control signaling. For example, the base station transmits downlink data and / or downlink control signaling to the UE in a time unit.

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

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

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

[0159] FIG. 7 illustrates a flowchart of a method 700 performed by a UE according to an example embodiment of the disclosure.

[0160] Referring to FIG. 7, in operation S710, the UE may receive downlink (DL) data (e.g., downlink data carried by PDSCH(s)) 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.

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

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

[0163] [HARQ / scheduling general timing]

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

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

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

[0167] Some examples of uplink transmission timing will be described below with reference to FIGS. 8A-8C.

[0168] 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 (e.g., 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 disclosure, "the UE receives a DCI / DCI format" may refer to that "the UE detects the DCI / DCI format."

[0169] In an 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 (e.g., 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 the disclosure, unless otherwise specified, the PUSCH may be a dynamically scheduled PUSCH (e.g., scheduled by DCI) (e.g., which may be referred to as DG (dynamic grant) PUSCH in the disclosure) and / or a PUSCH not scheduled by DCI (e.g., CG PUSCH).

[0170] In an 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 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.

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

[0172] In 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, where the PDSCH reception may be a PDSCH reception providing a transport block (TB) with enabled HARQ-ACK information). Or, for example, HARQ-ACK may be HARQ-ACK for a DCI format without scheduling PDSCH.

[0173] In an 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.

[0174] In some implementations, the UE may report (or signal / transmit) a UE capability to the base station or indicate the UE capability in operation S720. For example, the UE reports (or signals / transmits) the UE capability to the base station by transmitting a PUSCH. In this case, the PUSCH transmitted by the UE includes the UE capability information. A UE capability may be a UE capability parameter, or a value of a UE capability parameter.

[0175] In some implementations, the base station may configure higher layer signaling for the UE based on a UE capability received from the UE.

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

[0177] [Two levels of priorities]

[0178] 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 parameterPUCCH-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.

[0179] 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 for 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 the time domain may include multiplexing UCI of the PUCCHs in a PUCCH or PUSCH. It should be noted that, in the disclosure, "resolving the overlapping for the physical channels" may also be used interchangeably with "determining the overlapping for 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 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 the 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. In the disclosure, unless otherwise indicated, "resolving the overlapping for physical channels" may be understood as resolving the overlapping for physical channels with the same physical layer priority.

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

[0181] 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; for example, the first priority is the higher priority, and the second priority is the lower priority. In an example, the first priority may be lower than the second priority. However, the disclosure is 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 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 the disclosure, the terms "first priority", "higher priority", "greater priority index" and "priority index 1" may be used interchangeably. In the disclosure, the terms "second priority", "lower priority", "smaller priority index" and "priority index 0" may be used interchangeably.

[0182] [Subslot]

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

[0184] 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, the number of symbols included in the slot of the PUCCH transmission is indicated by the subslot length parameter.

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

[0186] [Multicast service (MBS)]

[0187] In 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 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 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 disclosure, "multicast" may also be replaced by "broadcast".

[0188] [HARQ-ACK codebook]

[0189] In the example embodiment as shown in FIG. 7, in operation S710, the UE may receive downlink data (e.g., downlink data carried by PDSCH(s)) and / or downlink control signaling (e.g., DCI format(s) carried by PDCCH(s)) from the base station.

[0190] In operation S720, the UE may determine HARQ-ACK information bits transmitted in an uplink slot based on the downlink data and / or the downlink control signaling. For example, determining the HARQ-ACK information bits transmitted in the uplink slot includes at least one of the following:

[0191] determining values of the HARQ-ACK information bits;

[0192] determining the order of the HARQ-ACK information bits;

[0193] determining a total number of the HARQ-ACK information bits.

[0194] In operation S730, the UE transmits the HARQ-ACK information bits to the base station. Here, the UE may transmit the HARQ-ACK information bits in a PUCCH or PUSCH.

[0195] In some implementations, a HARQ-ACK codebook may include HARQ-ACK information (in the disclosure, which may also be called HARQ-ACK information bits) for one or more PDSCH receptions and / or DCI format(s) (e.g., DCI format without scheduling PDSCH reception). HARQ-ACK information for a PDSCH reception may be understood as HARQ-ACK information for transport block(s) (TB(s)) included in the PDSCH reception. In case that the UE is configured with PDSCH CBG (code block group) transmission (for example, the parameterPDSCH-CodeBlockGroupTransmissionis configured), or in case that one PDSCH reception includes one or more CBGs, HARQ-ACK information for a PDSCH reception may be understood as HARQ-ACK information for the CBGs included in the PDSCH reception. If HARQ-ACK information for one or more PDSCH receptions and / or DCI(s) is multiplexed in a time unit (e.g., uplink time unit) for transmission (e.g., transmission in a PUCCH in a same time unit), the UE may generate the HARQ-ACK codebook based on a predefined rule. The UE generating the HARQ-ACK codebook may include ordering the HARQ-ACK information bits and / or compressing (e.g., bundling) the HARQ-ACK information bits. 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 reception 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 of the HARQ-ACK processes of all of 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 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 the time domain and / or 'A' overlaps with 'B' in frequency domain.

[0196] 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 the 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 parametern1PUCCH-AN).

[0197] 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 reception (e.g., a PDSCH reception 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 reception 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 HARQ-ACK codebook configuration parameter for a PDSCH reception (e.g., the higher layer parameter pdsch-HARQ-ACK-Codebook). For example, if the UE is configured with the HARQ-ACK codebook configuration parameter (e.g., higher layer parameter pdsch-HARQ-ACK-Codebook) as semi-static, the UE may generate a semi-static HARQ-ACK codebook. If the UE is configured with the HARQ-ACK codebook configuration parameter (e.g., higher layer parameter pdsch-HARQ-ACK-Codebook) as dynamic, the UE may generate a dynamic 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 the 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.

[0198] 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 PDSCH receptions (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).

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

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

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

[0202] MA,cmay be determined by at least one of the following:

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

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

[0205] c) , where μDLis the configuration of a downlink subcarrier spacing (SCS) of the downlink active BWP, and μULis the configuration of an uplink subcarrier spacing of the active uplink BWP.

[0206] d) a semi-static uplink and downlink frame structure configuration, such as the parametertdd-UL-DL-ConfigurationCommonand the parametertdd-UL-DL-ConfigurationDedicated.

[0207] e) a downlink slot offset parameter (e.g., the higher layer parameter ) for the serving cellcand its corresponding slot offset SCS (e.g., the higher layer parameter μoffset,DL,c), 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 μoffset,UL).

[0208] In 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 the 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 the time domain. It should be noted that, in the disclosure, a starting symbol may be used interchangeably with a starting position, and an ending symbol may be used interchangeably with an ending position. In some implementations, the starting symbol may be replaced by the ending symbol, and / or the ending symbol may be replaced by the starting symbol.

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

[0210] 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}.

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

[0212] 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 disclosure is 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.

[0213] In some implementations, the DAI may include at least one of a first DAI and a second DAI.

[0214] In some examples, the first DAI may be a C-DAI (Counter-DAI), and the first DAI may be the cumulative number of the downlink assignment index. The value of the first DAI field in a DCI format is the cumulative number of {serving cell, PDCCH monitoring occasion (MO)}-pair(s) up to the current serving cell and the current time unit, where the time unit may be a time unit of the PDCCH reception, for example, PDCCH monitoring occasion. The {serving cell, PDCCH MO}-pairs may include DCI formats scheduling PDSCH receptions and / or DCI formats having associated / corresponding HARQ-ACK information bits without scheduling PDSCH receptions. The first DAI may be included in a downlink DCI format. HARQ-ACK information for a PDSCH reception scheduled by a DCI format and / or a DCI format without scheduling PDSCH reception is transmitted in a same time unit (for example, transmitted in a same PUCCH in a same time unit). The second DAI may be T-DAI (Total-DAI). The second DAI may be a total number of the downlink assignment index. The value of the second DAI field in a DCI format may be a total number of {serving cell, PDCCH MO}-pair(s) up to 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 an uplink DCI format may be also called UL DAI.

[0215] In some implementations, the first DAI may be sorted in the following order:

[0216] first in ascending order of serving cell index (e.g., scheduled serving cell index), and

[0217] second in ascending order of PDCCH MO index.

[0218] In some implementations, the first DAI may also be sorted in the following order. For example, if the UE reports a capability to support more than one PDSCH reception on a serving cell scheduled from a PDCCH MO (e.g., PDSCH receptions scheduled by more than one PDCCH), the first DAI may be sorted in the following order:

[0219] - first in increasing order of the PDSCH reception starting time (e.g., the PDSCH reception starting time for the same {serving cell, PDCCH MO}-pair),

[0220] - second in ascending order of serving cell index (e.g., scheduled serving cell index), and

[0221] - third in ascending order of PDCCH MO index.

[0222] In some examples, the first DAI may be a C-DAI (Counter-DAI). The first DAI may indicate the accumulative number of at least one of DCI scheduling PDSCH reception(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: the 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 the number of PDCCHs (e.g., PDCCHs indicating SPS release and / or PDCCHs indicating secondary cell dormancy)); or the accumulative number of PDCCH(s) up to the current time unit; or the accumulative number of PDSCH transmission(s) up to the current time unit; or the 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 the 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 the 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 the 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.

[0223] In some examples, 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 the 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.

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

[0225] Tables 1 and 2 show a correspondence between the DAI field and VT-DAI,mor VC-DAI,c,mor . Numbers of bits of the C-DAI and T-DAI are limited.

[0226] 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 format may be determined by equations in Table 1. VT-DAI,mor is the value of the T-DAI in the DCI format received in a PDCCH Monitoring Occasion (MO) m, and VC-DAI,c,mis the value of the C-DAI in the DCI format for a serving cellcreceived in the PDCCH monitoring occasionm. Both VT-DAI,mand VC-DAI,c,mare related to the number of bits of the DAI field in the DCI format. MSB is the most significant bit and LSB is the least significant bit.

[0227] [Table 1]

[0228]

[0229]

[0230] 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 VT-DAI,mor VC-DAI,c,mis represented as "1" by the equation in Table 1. Y may represent the value of the DAI corresponding to the number of DCI formats actually transmitted by the base station (the value of the DAI before conversion by the equation in the table).

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

[0232] [Table 2]

[0233]

[0234]

[0235] In some implementations, the UE may generate HARQ-ACK information bits in a PUCCH according to pseudo code 1. For example, if the UE transmits HARQ-ACK information in a PUCCH (e.g., a PUCCH for any PUCCH format) in slot n, the UE determines HARQ-ACK information bits according to pseudo code 1, where OACKis the total number of HARQ-ACK information bits.

[0236] [Pseudo code 1]

[0237]

[0238]

[0239]

[0240]

[0241] 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 or 2.

[0242] [HARQ feedback mode]

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

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

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

[0246] For the PDSCH reception of a HARQ process, if the UE is configured not to feed back HARQ-ACK information, the HARQ-ACK codebook does not include HARQ-ACK information for the PDSCH reception.

[0247] [Channel collision]

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

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

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

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

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

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

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

[0255] - 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 the time domain with other PUSCH(s) on a same serving cell;

[0256] - 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 the time domain with another PDSCH on a same serving cell with a same value of the CORESET pool index parameter (e.g., coresetPoolIndex); or

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

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

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

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

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

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

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

[0264] In 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. The channel may also include one or more PDCCHs and / or one or more PDSCHs.

[0265] It should be noted that, in 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. "Resolving overlapping channels," "resolving the overlapping for / among channels," "determining the overlapping for / among channels," and "determining the overlapping channels" may be used interchangeably.

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

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

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

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

[0270] It should be noted that, in the disclosure, "configured with and / or indicated a transmission with repetitions" may be understood that the 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 the 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 "the number of the repetitions of the PUCCH transmission is equal to 1". For example, the UE may be configured with a parameter related to the 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 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).

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

[0272] It should be noted that, in the disclosure, multiple approaches / methods can be combined in any order. In a combination, an approach / method may be performed one or more times, or an approach / method may not be performed. In addition, at least one step / operation of one of the approaches / methods may be combined with one or more steps / operations of other approach(s) / method(s) in the example embodiments of the disclosure to form new embodiments. The steps / operations in combination may be performed one or more times. When performing one approach / method or one approach / method combination, one or more steps / operations of the approach / method or approach / method combination may be omitted, or other associated steps / operations (e.g., other associated one or more steps / operations) may additionally be performed.

[0273] It should be noted that multiple steps in the method of the disclosure may be implemented in any order.

[0274] It should be noted that, in 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. "Canceling a transmission" may be used interchangeably with "not transmitting".

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

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

[0277] It should be noted that, in the disclosure, "slot" may be replaced by "subslot" or "time unit".

[0278] It should be noted that, in the disclosure, a time interval (or time unit interval) between a first physical channel and a second physical channel may be understood as the time interval (or time unit interval) between the ending position (or ending symbol) of the first physical channel and the starting position (or starting symbol) of the second physical channel, where the first physical channel is earlier than the second physical channel. The following descriptions may be used interchangeably: "the time interval between the first physical channel and the second physical channel is less than a predefined time"; "the second physical channel starts before the predefined time after the first physical channel"; and "the first physical channel is earlier than the second physical channel by no more than the predefined time". The following descriptions may be used interchangeably: "the time interval between the first physical channel and the second physical channel is greater than a predefined time"; "the second physical channel starts after the predefined time after the first physical channel"; and "the first physical channel is earlier than the second physical channel by more than the predefined time". Or, a time interval (or time unit interval) between a first physical channel and a second physical channel may be understood as the time interval (or time unit interval) between a time unit where the first physical channel is located and a time unit where the second channel is located. The time unit in which the physical channel is located may be understood as a time unit that overlaps with the ending position (or ending symbol) of the physical channel or a time unit that overlaps with the starting position (or starting symbol) of the physical channel.

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

[0280] It should be noted that, in the disclosure, "configured with a parameter (or information) ", "provided with a parameter (or information)", "configured with a parameter of a specific value (e.g., 'enable')" and "receiving a parameter (or information) " may be used interchangeably. Being configured with one or more parameters may refer to being configured with a parameter list in an IE, the parameter list including one or more parameters. Being configured with multiple parameters may also mean that the parameters are configured in multiple IEs, respectively.

[0281] It should be noted that, in the disclosure, "PUCCH with HARQ-ACK information" and "PUCCH including HARQ-ACK information" may be used interchangeably.

[0282] It should be noted that, in the disclosure, "HARQ-ACK", "HARQ-ACK feedback", "HARQ-ACK information", "HARQ-ACK information bit" and "HARQ-ACK codebook" may be used interchangeably.

[0283] It should be noted that, in the disclosure, "determining HARQ-ACK information bits" and "generating HARQ-ACK information bits" may be used interchangeably.

[0284] It should be noted that, in the 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. "PUCCH" and "PUCCH resource" may be used interchangeably, and "PUSCH" and "PUSCH resource" may be used interchangeably.

[0285] It should be noted that, in the disclosure, "the starting time of a resource (or channel)" and "the first symbol of the resource (or channel)" and "the starting time of the first symbol of the resource (or channel)" may be used interchangeably.

[0286] It should be noted that, in the disclosure, "the ending time of a resource (or channel)" and "the last symbol of the resource (or channel)" and "the ending time of the last symbol of the resource (or channel)" may be used interchangeably.

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

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

[0289] It should be noted that the embodiments of the disclosure may be applied to one serving cell or multiple serving cells.

[0290] It should be noted that the embodiments of the disclosure may be applied to one BWP or multiple BWPs.

[0291] It should be noted that, in the disclosure, "first and second" and "two" may be used interchangeably. For example, "a first channel and a second channel" may mean two channels. In the disclosure, "first and second" may also mean two or more than two. For example, "a first channel and a second channel" may also mean two or more channels.

[0292] It should be noted that, in the disclosure, the behavior of the UE (or base station) and the corresponding conditions of the behavior of the UE (or base station) may be used interchangeably. For example, "the UE receives (or is configured with) first information (or parameter)" and "if the UE is configured with the first information (or parameter)" may be used interchangeably.

[0293] It should be noted that, in the disclosure, receiving information carried by a DCI format may be understood as detecting a DCI format that carries the information.

[0294] It should be noted that, in the disclosure, the terms "index", "identification", "identifier", and "number" may be used interchangeably.

[0295] In the disclosure, a resource (which may also be referred to as a physical resource) may include a time domain resource (also referred to as a time resource) and / or a frequency domain resource (also referred to as a frequency resource).

[0296] In the disclosure, "time-domain resource" or "time resource" may refer to or be used interchangeably with at least one of symbol(s) (e.g., OFDM symbol(s)), slot(s), subslot(s), mini-slot(s), or subframe(s).

[0297] In the disclosure, "frequency domain resource" or "frequency resource" may refer to or be used interchangeably with at least one of: channel(s), subchannel(s), carrier(s), subcarrier(s), resource block(s) (RB(s)), resource element(s) (RE(s)), physical resource block(s) (PRB(s)), or physical resource block group(s) (RBG(s)).

[0298] It should be noted that satisfying a condition in the disclosure may be understood as at least satisfying the condition. That is, this condition and other conditions may be satisfied simultaneously. For example, "satisfying a specific condition" in the embodiments of the disclosure may be replaced with "at least satisfying the specific condition".

[0299] It should be noted that the UE may report a capability to support the method described in the embodiments of the disclosure through capability reporting, and / or the method described in the embodiments of the disclosure may be enabled through higher layer parameter configuration.

[0300] It should be noted that, in 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 the disclosure, the following descriptions may be used interchangeably:

[0301] - beam;

[0302] - spatial filter;

[0303] - spatial domain filter;

[0304] - spatial domain transmission filter;

[0305] - spatial setting;

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

[0307] - QCL parameter (QCL-type (e.g., type D) parameter / reference signal);

[0308] - TCI state;

[0309] - unified TCI state;

[0310] - spatial relationship;

[0311] - RS (reference signal);

[0312] - information related to sounding reference signal (SRS) (e.g., SRS resource indication (SRI)).

[0313] In some implementations, the RS may be an RS corresponding to a beam. For example, the RS may be CSI-RS or synchronization signal (SS) / physical broadcast channel (PBCH) block (SSB).

[0314] In some examples, the UE may be configured or provided with 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 (the SRS resource set index parameter value is equal to 0) may correspond to a CORESET pool index parameter with a value of 0, and the other SRS resource set (SRS resource set index parameter value is equal to 1) may correspond to the CORESET pool index parameter with a value of 1.

[0315] In the disclosure, the term "panel" may refer to a group of antenna ports or an antenna group. 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 the indicated reference signal ID. An SRS set ID may be used to indicate the antenna panel ID, where each antenna panel is associated with one SRS set.

[0316] In some cases, the base station may enhance coverage or reduce delay of a communication system through duplex. Duplex may include subband non-overlapping full duplex (SBFD). For example, a subband non-overlapping full duplex approach may be employed in a time division multiplexing (TDD) band (e.g., in unpaired spectrum). Subband non-overlapping duplex may refer to dividing the bandwidth (e.g., carrier bandwidth) of a communication node (e.g., base station) into more than one subband (e.g., there is no overlapping between each subband), and uplink and downlink communications can be performed simultaneously on different subbands.

[0317] In the disclosure, the term "time division duplex (TDD) configuration information" may be used interchangeably with the term "TDD uplink / downlink configuration information" or "information for configuring a slot format."

[0318] In the disclosure, the term "SBFD configuration information" may be used interchangeably with the term "configuration information for SBFD" or "configuration information for SBFD" or "configuration information for SBFD operation" or "configuration information for SBFD operation of the base station".

[0319] In the disclosure, the term "subband non-overlapping duplex" may be used interchangeably with "subband full duplex".

[0320] In the disclosure, the term "frequency domain resource corresponding to an uplink subband" may be used interchangeably with the term "frequency domain location corresponding to the uplink subband", or "frequency domain resource of the uplink subband", or "frequency domain resource for uplink", or "frequency domain location for uplink", or "frequency domain resource for uplink transmission", or "frequency domain location for uplink transmission".

[0321] In the disclosure, the term "frequency domain resource corresponding to a downlink subband" may be used interchangeably with the term "frequency domain location corresponding to the downlink subband", or, "frequency domain resource of the downlink subband", or "frequency domain resource for downlink", or "frequency domain location for downlink", or "frequency domain resource for downlink reception", or "frequency domain location for downlink reception".

[0322] In the disclosure, the term "frequency domain resource corresponding to a guardband" may be used interchangeably with the term "frequency domain location corresponding to the guardband", or "frequency domain resource of the guardband", or "frequency domain resource between (boundaries of) an uplink subband and a downlink subband", or "frequency domain location between (boundaries of) an uplink subband and a downlink subband", or "frequency domain resource for protecting / isolating between an uplink subband and a downlink subband".

[0323] In the disclosure, the term "SBFD cell" may be used interchangeably with the term "first cell", but the disclosure does not limit the naming of the "SBFD cell".

[0324] In some cases, the UE may obtain / receive / be configured with SBFD configuration information. Optionally, the UE may receive / obtain / be configured with the SBFD configuration information via common signaling (e.g., common RRC signaling) or specific signaling (e.g., specific RRC signaling). Optionally, the SBFD configuration information may be configuration information related to the SBFD. For example, the SBFD configuration information may be configuration information for SBFD. For example, the SBFD configuration information may be configuration information related to SBFD operation (of the base station). For example, the SBFD configuration information may be configuration information indicating a time domain resource and / or a frequency domain resource related to the SBFD operation. Optionally, the UE receives the SBFD configuration information in RRC_CONNECTED state. Optionally, the UE may receive the SBFD configuration information in RRC_IDLE / RRC_INACTIVE state.

[0325] > Optionally, a cell (e.g., serving cell) corresponding to / associated with the SBFD configuration information / where the SBFD configuration information is located / for may be called an SBFD cell.

[0326] >> Optionally, the cell corresponding to / associated with the SBFD configuration information may be a cell that performs the SBFD operation associated with the SBFD configuration. Optionally, the cell corresponding to / associated with the SBFD configuration information may be a primary cell (e.g., PCell) or a special cell (e.g., a SpCell). Optionally, the cell corresponding to / associated with the SBFD configuration information may be a secondary cell (e.g., SCell). Optionally, the cell corresponding to / associated with the SBFD configuration information may be a cell where the time domain resource and / or the frequency domain resource associated with the SBFD configuration information are located / correspond to. Optionally, the cell corresponding to / associated with the SBFD configuration information may be a cell where the time domain resource and / or the frequency domain resource associated with the SBFD configuration information are applied / used. Optionally, the cell corresponding to / associated with the SBFD configuration information may be a cell where the SBFD configuration information is received, or a cell where the SBFD configuration information is configured.

[0327] > Optionally, the SBFD configuration information may indicate / correspond to / be associated with the frequency domain resource and / or the (corresponding / associated) time domain resource. Optionally, the time domain resource corresponding to / associated with the frequency domain resource refer to the time domain resource on which the frequency domain resource configured by the SBFD configuration information is applicable / effective / workable. Optionally, the time domain resource corresponding to / associated with the frequency domain resource refers to the time domain resource on which the frequency domain resource configured by the SBFD configuration information is applied / used (by the UE).

[0328] >> Optionally, the SBFD configuration information may indicate the frequency domain resource (associated with / corresponding to the SBFD time domain resource). The frequency domain resource indicated by / configured by / associated with the SBFD configuration information may be referred as the SBFD frequency domain resource. Optionally, the SBFD configuration information may indicate at least one of a frequency domain resource corresponding to an uplink subband, a frequency domain resource corresponding to a downlink subband, and a frequency domain resource corresponding to a guardband. Optionally, the SBFD frequency domain resource may include at least one of the frequency domain resource corresponding to the uplink subband, the frequency domain resource corresponding to the downlink subband, and the frequency domain resource corresponding to the guardband. The frequency domain units included in the frequency domain resource are described below by taking PRB as an example. Optionally, the frequency domain resource corresponding to the uplink subband may include one or more consecutive PRBs, or a group of consecutive PRBs. Optionally, the frequency domain resource corresponding to the downlink subband may include one or more PRBs, or one or two groups of consecutive PRBs. Optionally, the frequency domain resource corresponding to the guardband may include one PRB or a group of consecutive PRBs or two groups of consecutive PRBs. Optionally, the uplink subband may be a subband for uplink (e.g., uplink transmission). Optionally, the uplink subband may be a frequency domain resource for uplink (e.g., uplink transmission). Optionally, the downlink subband may be a subband for downlink (e.g., downlink reception). Optionally, the downlink subband may be a frequency domain resource for downlink (e.g., downlink reception). Optionally, the UE may determine the frequency domain resource corresponding to the guardband based on the frequency domain resource corresponding to the uplink subband and / or the frequency domain resource corresponding to the downlink subband (and the carrier bandwidth of the SBFD cell). Optionally, the UE may determine the frequency domain resource corresponding to the downlink subband based on the frequency domain resource corresponding to the uplink subband and / or the frequency domain resource corresponding to the guardband (and the carrier bandwidth of the SBFD cell). Optionally, the frequency domain resource corresponding to the downlink subband may include one or more PRBs, or one or two groups of consecutive PRBs.

[0329] >>> Optionally, the SBFD frequency domain resource is determined based on the SBFD configuration information and a reference subcarrier spacing parameter indicated by the TDD configuration information (e.g., the reference subcarrier spacing parameter referenceSubcarrierSpacing included in the TDD configuration information) (for the cell). For example, the SBFD frequency domain resource is determined based on (the parameter associated with the frequency domain indicated by) the SBFD configuration information and the reference subcarrier spacing parameter (e.g., referenceSubcarrierSpacing) included in the TDD configuration information (for the cell). The method may reuse the parameter indicated by the TDD configuration information to determine the SBFD frequency domain resource, saving signaling overhead and improving the efficiency of the communication system.

[0330] >>> Optionally, the SBFD frequency domain resource is determined based on the reference subcarrier spacing parameter indicated by the SBFD configuration information (e.g., the reference subcarrier spacing parameter referenceSubcarrierSpacing included in the SBFD configuration information). For example, the SBFD time domain resource is determined based on the reference subcarrier spacing parameter (e.g., referenceSubcarrierSpacing) included in the SBFD configuration information. The method may utilize the SBFD configuration information to determine the SBFD frequency domain resource, which facilitates the base station to flexibly perform the SBFD operation, improving the efficiency of the communication system.

[0331] >>> Optionally, on the SBFD frequency domain resource, the part of the uplink BWP within the frequency domain resource corresponding to the uplink subband associated with the SBFD frequency domain resource may be / is allowed for uplink transmission. Optionally, on the SBFD time domain resource, the part of the uplink BWP not within the frequency domain resource corresponding to the uplink subband associated with the SBFD frequency domain resource may not be / is not allowed for uplink transmission. The method defines the scheduling restriction based on the SBFD configuration, which facilitates the base station to schedule flexibly, improving the efficiency of the communication system.

[0332] >>> Optionally, on the SBFD frequency domain resource, the part of the downlink BWP within the frequency domain resource corresponding to the downlink subband associated with the SBFD frequency domain resource may be / is allowed for downlink reception. Optionally, on the SBFD time domain resource, the part of the downlink BWP not within the frequency domain resource corresponding to the downlink subband associated with the SBFD frequency domain resource may not be / is not allowed for downlink reception. The method defines the scheduling restriction based on the SBFD configuration, which facilitates the base station to schedule flexibly, improving the efficiency of the communication system.

[0333] >> Optionally, the SBFD configuration information may indicate / configure / be associated with time domain resource. The time domain resource indicated by / configured by / associated with the SBFD configuration information may be referred as the SBFD time domain resource. The time domain resource other than the SBFD time domain resource (or a part of the time domain resource other than the SBFD time domain resource) may be referred as a non-SBFD time domain resource; or the time domain resource that is not the SBFD time domain resource may be referred as the non-SBFD time domain resource; or the time domain resource outside the SBFD time domain resource and within the downlink slot / downlink symbol and / or flexible slot / flexible symbol indicated / configured by the base station are referred as the non-SBFD time domain resource, or the time domain resource within the uplink slot / uplink symbol indicated / configured by the base station are referred as the non-SBFD time domain resource. The SBFD time domain resource may include several time domain units. Optionally, the SBFD time domain resource is not on the uplink slot and / or uplink symbol indicated by common information. Optionally, the SBFD time domain resource is on the downlink slot and / or downlink symbol indicated by the base station, and / or the SBFD time domain resource is on the flexible slot and / or flexible symbol indicated / configured by the base station. Optionally, the non-SBFD time domain resource is not on the uplink slot or uplink symbol indicated by the common information. Optionally, the non-SBFD time domain resource is on the downlink slot and / or downlink symbol indicated by the base station, and / or the non-SBFD time domain resource is on the flexible slot and / or flexible symbol indicated / configured by the base station. Optionally, the UE may obtain at least one of the uplink symbol, the uplink slot, the downlink symbol, the downlink slot, the flexible symbol, and the flexible slot indicated by the base station via the TDD configuration information. The TDD configuration information includes the TDD configuration information for the cell (e.g., TDD-UL-DL-ConfigurationCommon) and / or the TDD configuration information for the UE (tdd-UL-DL-ConfigurationDedicated).

[0334] >>> Optionally, the SBFD time domain resource is determined based on the SBFD configuration information and the reference subcarrier spacing parameter indicated by the TDD configuration information (e.g., the reference subcarrier spacing parameter referenceSubcarrierSpacing included in the TDD configuration information) (for the cell). For example, the SBFD time domain resource is determined based on (the parameter associated with the time domain resource indicated by) the SBFD configuration information and the reference subcarrier spacing parameter (e.g., referenceSubcarrierSpacing) included in the TDD configuration information (for the cell). The method may reuse the parameter indicated by the TDD configuration information to determine the SBFD time domain resource, saving signaling overhead and improving the efficiency of the communication system.

[0335] >>> Optionally, the SBFD time domain resource is determined based on the reference subcarrier spacing parameter indicated by the SBFD configuration information (e.g., the reference subcarrier spacing parameter referenceSubcarrierSpacing included in the SBFD configuration information). For example, the SBFD time domain resource is determined based on the reference subcarrier spacing parameter (e.g., referenceSubcarrierSpacing) included in the SBFD configuration information. The method may utilize the SBFD configuration information to determine the SBFD time domain resource, which facilitates the base station to flexibly perform the SBFD operation, improving the efficiency of the communication system.

[0336] Optionally, on a BWP, if a symbol / slot partially overlaps with the SBFD time domain resource, the symbol / slot may not be / is not allowed for transmission / reception. Optionally, on a BWP, if a symbol / slot fully overlaps with the SBFD time domain resource, the symbol / slot may be / is allowed for transmission / reception. The method defines the scheduling restriction based on the SBFD configuration, which facilitates the base station to schedule flexibly, improving the efficiency of the communication system.

[0337] Referring back to FIG. 7, in operation S710, the UE may receive configuration information of a first CG PUSCH for a serving cell from a base station, where the first CG PUSCH transmission overlaps in the time domain with a PUCCH transmission with UCI.

[0338] In operation S720, the UE may receive a PDCCH from the base station, where the PDCCH carries a DCI format that indicates the reception of a physical downlink channel or physical downlink signal on the serving cell. For example, the physical downlink channel may include at least one of the following: PDSCH, PDCCH, or physical broadcast channel (PBCH). The physical downlink signal may include at least one of the following: demodulation reference signal (DM-RS), phase tracking reference signal (PT-RS), positioning reference signal (PRS), CSI-RS, primary synchronization signal (PSS), or secondary synchronization signal (SSS).

[0339] In operation S730, if the first CG PUSCH transmission does not overlap in the time domain with the physical downlink channel reception or the physical downlink signal reception, the UE may multiplex the UCI in the first CG PUSCH, the UE may transmit the first CG PUSCH, and / or the UE may not transmit the PUCCH. Additionally or alternatively, if the first CG PUSCH transmission overlaps in the time domain with the physical downlink channel or the physical downlink signal, the UE may not multiplex the UCI in the first CG PUSCH, and / or the UE may transmit the PUCCH, and / or the UE may not transmit the first CG PUSCH. Optionally, the interval between the ending symbol the PDCCH reception and the starting symbol of the PUCCH transmission may not be less than (or may be greater than, or greater than or equal to) a first time. That is, the interval from the ending symbol of the PDCCH reception to the starting symbol of the PUCCH transmission may not be less than (or may be greater than, or greater than or equal to) the first time. The first time may be a predefined time, may be specified through a protocol, or may be reported through a UE capability. For example, the first time may be Tproc,2 which is the preparation time for canceling the PUSCH transmission. It should be noted that if the physical downlink channel reception or the physical downlink signal reception overlaps in the time domain with a first physical uplink channel on the serving cell, where the first physical uplink channel is a physical uplink channel in a set of overlapping physical uplink channels (or the first physical uplink channel belongs to the set of overlapping physical uplink channels), the interval between the ending symbol of the PDCCH reception and the earliest starting symbol in the set of overlapping physical uplink channels (e.g., the starting symbol of the earliest physical uplink channel in the set of overlapping physical uplink channels) may not be less than (or may be greater than, or greater than or equal to) the first time. This method can ensure that the UE has sufficient processing time to resolve the collision), thereby improving the reliability of uplink transmission.

[0340] Or, in operation S730, after resolving the overlapping (or collision) for CG PUSCH transmissions and physical downlink channel receptions or physical downlink signal receptions, if the first CG PUSCH transmission overlaps with the PUCCH transmission in the time domain, the UE may multiplex the UCI in the first CG PUSCH, the UE may transmit the first CG PUSCH, and / or the UE may not transmit the PUCCH.

[0341] Or, in operation S730:

[0342] The UE resolves the overlapping (or collision) for multiple physical downlink channel receptions or signal receptions;

[0343] The UE resolves the overlapping (or collision) for CG PUSCH transmissions and physical downlink channel receptions or physical downlink signal receptions;

[0344] The UE resolves the overlapping (or collision) for multiple physical uplink channel transmissions. For example, if the first CG PUSCH transmission overlaps in the time domain with the PUCCH transmission, the UE may multiplex the UCI in the first CG PUSCH, the UE may transmit the first CG PUSCH, and / or the UE may not transmit the PUCCH.

[0345] The UE resolves the overlapping (or collision) for physical uplink channel transmissions and physical downlink channel receptions or physical downlink signal receptions.

[0346] It should be noted that each of the above steps of resolving the overlapping (or collision) is optional, and the order of each step may be changed.

[0347] This method can increase the opportunity of the UCI transmission, thereby increasing the reliability of uplink transmission.

[0348] It should be noted that, in the disclosure, "CG PUSCH" may be replaced by "PUCCH with CSI", and "UCI" may be replaced by "SR and / or HARQ-ACK information for SPS PDSCH". Alternatively, in the disclosure, "CG PUSCH" may be replaced by "PUCCH with HARQ-ACK information for SPS PDSCH", and "UCI" may be replaced by "SR".

[0349] It should be noted that, in the disclosure, "CG PUSCH transmission" may be replaced by "PUCCH repetition transmission" or "CG PUSCH transmission and / or PUCCH repetition transmission".

[0350] This method can ensure that the UE has sufficient processing time to resolve collision, thereby improving the reliability of uplink transmission.

[0351] It should be noted that the first CG PUSCH transmission not overlapping in the time domain with the physical downlink channel reception or the physical downlink signal reception on the serving cell indicated by the DCI format may refer to that the time when the UE transmit the first CG PUSCH transmission does not overlap with the time when the UE receives the physical downlink channel reception or the physical downlink signal reception. The first CG PUSCH transmission overlapping in the time domain with the physical downlink channel reception or the physical downlink signal reception on the serving cell indicated by the DCI format may refer to that the time when the UE transmits the first CG PUSCH transmission overlaps with the time when the UE receives the physical downlink channel reception or the physical downlink signal. The time to transmit the first CG PUSCH transmission may be a transmission time considering TA (time advance).

[0352] In some implementations, if the first CG PUSCH transmission does not overlap with a first symbol, the UE multiplexes the UCI in the first CG PUSCH, the UE does not transmit the PUCCH; and / or if the first CG PUSCH transmission overlaps with the first symbol, the UE may not multiplex the UCI in the first CG PUSCH, and / or the UE may transmit the PUCCH. This method can increase the opportunity of the UCI transmission, thereby increasing the reliability of uplink transmission. In the embodiments of the disclosure, the first symbol may be at least one of the following:

[0353] - downlink symbols and / or flexible symbols configured or indicated by higher layer signaling (e.g., parameter tdd-UL-DL-ConfigurationCommon and parameter tdd-UL-DL-ConfigurationDedicated),

[0354] - SBFD symbols, e.g., higher layer configured SBFD symbols,

[0355] - symbols of SSB.

[0356]

[0357] In some implementations, if the first CG PUSCH transmission overlaps with a first symbol (or at least one first symbol) and all frequency domain resources of the first CG PUSCH on the first symbol (or the at least one first symbol) are frequency domain resources of the uplink subband, the UE multiplexes the UCI in the first CG PUSCH, and the UE does not transmit the PUCCH; and / or if the first CG PUSCH transmission overlaps with a first symbol (or at least one first symbol) and not all frequency domain resources of the first CG PUSCH on the first symbol (or the at least one first symbol) are frequency domain resources of the uplink subband, the UE may not multiplex the UCI in the first CG PUSCH, and / or the UE may transmit the PUCCH. This method can increase the opportunity of the UCI transmission, thereby increasing the reliability of uplink transmission.

[0358] It should be noted that all frequency domain resources of the first CG PUSCH being frequency domain resources of the uplink subband may be understood as that all PRBs of the first CG PUSCH are PRBs of the uplink subband. Not all frequency domain resources of the first CG PUSCH being frequency domain resources of the uplink subband may be understood as that part or all of the frequency domain resources of the first CG PUSCH are located in the downlink subband. For example, at least one of PRBs of the first CG PUSCH is a PRB of the downlink subband.

[0359] In some implementations, the first CG PUSCH transmission may be a CG PUSCH transmission that overlaps with a first symbol (or at least one first symbol) and not all frequency domain resources of the first CG PUSCH on the first symbol (or the at least one first symbol) are frequency domain resources of the uplink subband. The second CG PUSCH transmission may be a CG PUSCH transmission that does not overlap with first symbols. If a PUCCH overlaps in the time domain with both the first CG PUSCH transmission and the second CG PUSCH transmission, the UE multiplexes UCI of the PUCCH in the second CG PUSCH transmission. This method can increase the opportunity of the UCI transmission, thereby increasing the reliability of uplink transmission.

[0360] In some implementations, the first CG PUSCH transmission may be a CG PUSCH transmission on an SBFD cell. The second CG PUSCH transmission may be a CG PUSCH transmission on a non-SBFD cell. If a PUCCH overlaps in the time domain with both the first CG PUSCH transmission and the second CG PUSCH transmission, the UE multiplexes UCI of the PUCCH in the second CG PUSCH transmission. This method can increase the opportunity of the UCI transmission, thereby increasing the reliability of uplink transmission.

[0361] It should be noted that the second CG PUSCH and the first CG PUSCH may be on a same serving cell or on different serving cells.

[0362] In some implementations, the UE may be configured with higher layer signaling to indicate that when a semi-statically configured uplink channel or signal overlaps with a semi-statically configured downlink channel or signal on a serving cell, the UE transmits the uplink channel or signal. After resolving the overlapping for multiple uplink channels and / or signals, if a semi-statically configured downlink channel or signal overlaps with a semi-statically configured uplink channel or signal on a serving cell, the UE transmits the semi-statically configured uplink channel or signal, and the UE does not receive the semi-statically configured downlink channel or signal. In this way, the order for the UE to resolve the overlapping can be clarified and the reliability of uplink transmission can be improved. If a semi-statically configured uplink channel or signal overlaps with a semi-statically configured downlink channel or signal and a downlink channel or signal indicated by a DCI format (e.g., a PDSCH reception scheduled by a DCI format) or SSB transmission on a serving cell, the UE does not transmit the semi-statically configured uplink channel or signal, and the UE receives the semi-statically configured downlink channel or signal. In this way, the reliability of downlink transmission can be improved.

[0363] In some implementations, the overlapping for channels or signals can be resolved in the following ways:

[0364] First, the UE resolves the overlapping for multiple uplink channels and / or signals.

[0365] Second, the UE resolves the overlapping for uplink channels and / or signals and downlink channels or signals indicated by DCI formats or SSB transmission.

[0366] Third, the UE resolves the overlapping for uplink channels and / or signals and semi-statically configured downlink channels or signals.

[0367] The above method can be applicable in a case where the UE is configured with higher layer signaling to indicate that when a semi-statically configured uplink channel or signal overlaps with a semi-statically configured downlink channel or signal on a serving cell, the UE transmits the uplink channel or signal. In this way, the reliability of downlink transmission can be improved.

[0368] In some implementations, the overlapping for channels or signals can be resolved in the following ways:

[0369] First, the UE resolves the overlapping for multiple uplink channels and / or signals.

[0370] Second, the UE resolves the overlapping for downlink channels and / or signals and uplink channels indicated by DCI formats.

[0371] Third, the UE resolves the overlapping for downlink channels and / or signals and semi-statically configured uplink channels or signals.

[0372] The above method can be applicable in a case where the UE is configured with higher layer signaling to indicate that when a semi-statically configured uplink channel or signal overlaps with a semi-statically configured downlink channel or signal on a serving cell, the UE transmits the uplink channel or signal. In this way, the reliability of downlink transmission can be improved.

[0373] In some implementations, the UE may not be configured with higher layer signaling to indicate that when a semi-statically configured uplink channel or signal overlaps with a semi-statically configured downlink channel or signal on a serving cell, the UE transmits the uplink channel or signal. After resolving the overlapping for multiple uplink channels and / or signals, if a semi-statically configured downlink channel or signal overlaps with a semi-statically configured uplink channel or signal and an uplink channel or signal indicated by a DCI format (for example, PUSCH or PUCCH scheduled by a DCI format) on a serving cell, the UE does not receive the semi-statically configured downlink channel or signal, and the UE transmits the semi-statically configured uplink channel or signal. In this way, the reliability of uplink transmission can be improved.

[0374] In some implementations, when an uplink channel or signal (e.g., dynamically scheduled (or indicated) uplink channel or signal and / or semi-statically configured uplink channel or signal) overlaps with dynamically scheduled (or indicated) downlink channel or signal on one serving cell, if a first timing condition is satisfied, the UE cancels (or does not transmit) the uplink channel or signal and / or receives the downlink channel or signal. Otherwise, if the first timing condition is not satisfied, the UE transmits the uplink channel or signal and / or the UE does not receive the downlink channel or signal. The first timing condition may be that the end of the PDCCH reception scheduling (or indicating) the downlink channel or signal is earlier than T_proc,2 before the start of the uplink channel or signal transmission, where T_proc,2 is the preparation time for canceling the uplink channel or signal. This method can clarify the behavior of the UE and improve the reliability of downlink reception and uplink transmission.

[0375] In case that the uplink channel or signal is a dynamically scheduled (or indicated) uplink channel or signal, the above behavior can be enabled through higher layer signaling (for example, RRC parameter). If the higher layer signaling is not configured, the UE transmits the uplink channel or signal and / or the UE does not receive the downlink channel or signal. The UE can support the above behavior through capability reporting.

[0376] In some implementations, when a downlink channel or signal (for example, a dynamically scheduled (or indicated) downlink channel or signal and / or a semi-static configured downlink channel or signal) overlaps with a dynamically scheduled (or indicated) uplink channel or signal on one serving cell, if a second timing condition is satisfied, the UE cancels (or does not receive) the downlink channel or signal and / or transmits the uplink channel or signal. Otherwise, if the second timing condition is not satisfied, the UE receives the downlink channel or signal and / or the UE does not transmit (or cancels) the uplink channel or signal. The second timing condition may be that the end of the PDCCH reception scheduling (or indicating) the uplink channel or signal is earlier than T_proc before the start of the downlink channel or signal transmission, where T_proc is the preparation time for canceling the downlink channel or signal. This method can clarify the behavior of the UE and improve the reliability of downlink reception and uplink transmission.

[0377] In case that the downlink channel or signal is a dynamically scheduled (or indicated) downlink channel or signal, the above behavior can be enabled through higher layer signaling (for example, RRC parameter). If the higher layer signaling is not configured, the UE receives the downlink channel or signal and / or does not transmit the uplink channel or signal. The UE can support the above behavior through capability reporting.

[0378] FIG. 10 illustrates a flowchart of a method 1000 performed by a terminal according to an example embodiment of the disclosure.

[0379] Referring to FIG. 10, in operation S1010, the terminal receives configuration information of a first CG PUSCH for a first serving cell, where the first CG PUSCH overlaps in the time domain with a PUCCH with UCI. For example, the terminal may receive the configuration information from a base station.

[0380] Next, in operation S1020, the terminal receives a PDCCH that carries a DCI format, where the DCI format indicates a reception of a physical downlink channel or a physical downlink signal on the first serving cell. For example, the terminal may receive the PDCCH from the base station.

[0381] Then, in operation S1030, in case that the first CG PUSCH does not overlap in the time domain with the physical downlink channel or the physical downlink signal, the UE multiplexes the UCI in the first CG PUSCH, and / or in case that the first CG PUSCH overlaps in the time domain with the physical downlink channel or the physical downlink signal, the UE does not multiplex the UCI in the first CG PUSCH, where the interval between the ending symbol of the PDCCH reception and the starting symbol of the PUCCH transmission is greater than or equal to a first time.

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

[0383] In some implementations, the method 1000 may omit one or more of operations S1010 through S1030, or may include additional operations, such as operations that may be performed by the terminal (e.g., UE) according to various embodiments of the disclosure (e.g., the embodiments described in connection with FIGS. 4-7, and the various methods described above).

[0384] FIG. 11 illustrates a flowchart of a method performed by a base station according to an example embodiment of the disclosure.

[0385] Referring to FIG. 11, in operation S1110, the base station transmits configuration information of a first CG PUSCH for a first serving cell to a terminal, where the first CG PUSCH overlaps in a time domain with a PUCCH with UCI.

[0386] Next, in operation S1120, the base station transmits a PDCCH that carries a DCI format to the terminal, where the DCI format indicates a transmission of a physical downlink channel or a physical downlink signal on the first serving cell, where in case that the first CG PUSCH does not overlap in the time domain with the physical downlink channel or the physical downlink signal, the UCI is multiplexed in the first CG PUSCH, and / or in case that the first CG PUSCH overlaps in the time domain with the physical downlink channel or the physical downlink signal, the UCI is not multiplexed in the first CG PUSCH, where the interval between the ending symbol of the PDCCH and the starting symbol of the PUCCH is greater than or equal to the first time.

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

[0388] In some implementations, the method 1100 may omit one or more of operations S1110 to S1120, or may include additional operations, such as operations that may be performed by the base station according to various embodiments of the disclosure (e.g., the embodiments described in connection with FIGS. 4-7, and the various methods described above).

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

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

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

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

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

[0394] The above description is only an exemplary implementation of the disclosure, and is not intended to limit the scope of protection of the disclosure, 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:identifying that a downlink channel or signal based on an indication by a first downlink control information (DCI) format and an uplink channel or signal based on an indication by a second DCI format overlap at least partly on a serving cell;in case that a timing condition is satisfied, receiving the downlink channel or signal; andin case that the timing condition is not satisfied, transmitting the uplink channel or signal.2.The method of claim 1, wherein the timing condition includes:a start of the uplink channel or signal not being within Tproc,2 with respect to a last of a physical downlink control channel (PDCCH) associated with the first DCI format.3.The method of claim 2, wherein the Tproc,2 is a preparation time associated with the uplink channel or signal.4.The method of claim 1, wherein receiving the downlink channel or signal includes:in case that a higher layer parameter associated with a collision between the downlink channel or signal and the uplink channel or signal is not configured, receiving the downlink channel or signal.5.The method of claim 1, wherein in case that the timing condition is satisfied, the uplink channel or signal is not transmitted, andwherein in case that the timing condition is not satisfied, the downlink channel or signal is not received.6.The method of claim 1, wherein the downlink channel or signal includes at least one of a physical downlink shared channel (PDSCH) or a channel state information reference signal (CSI-RS), andwherein the uplink channel or signal includes at least one of a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).7.A user equipment (UE) comprising:memory storing instructions; andprocessing circuitry coupled to the memory and configured, based at least partially on execution of the instructions, to cause the UE to perform the method of any one of claims 1 to 6.8.A method performed by a base station in a wireless communication system, the method comprising:identifying that a downlink channel or signal based on an indication by a first downlink control information (DCI) format and an uplink channel or signal based on an indication by a second DCI format overlap at least partly on a serving cell;in case that a timing condition is satisfied, transmitting the downlink channel or signal; andin case that the timing condition is not satisfied, receiving the uplink channel or signal.9.The method of claim 8, wherein the timing condition includes:a start of the uplink channel or signal not being within Tproc,2 with respect to a last of a physical downlink control channel (PDCCH) associated with the first DCI format.10.The method of claim 9, wherein the Tproc,2 is a preparation time associated with the uplink channel or signal.11.The method of claim 8, wherein transmitting the downlink channel or signal includes:in case that a higher layer parameter associated with a collision between the downlink channel or signal and the uplink channel or signal is not configured, transmitting the downlink channel or signal.12.The method of claim 8, wherein in case that the timing condition is satisfied, the uplink channel or signal is not received, andwherein in case that the timing condition is not satisfied, the downlink channel or signal is not transmitted.13.The method of claim 8, wherein the downlink channel or signal includes at least one of a physical downlink shared channel (PDSCH) or a channel state information reference signal (CSI-RS), andwherein the uplink channel or signal includes at least one of a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).14.A base station comprising:memory storing instructions; andprocessing circuitry coupled to the memory and configured, based at least partially on execution of the instructions, to cause the base station to perform the method of any one of claims 8 to 13.

Images