WO2024172448A1

WO2024172448A1 - Method and apparatus for transmitting and receiving uplink channel

Info

Publication number: WO2024172448A1
Application number: PCT/KR2024/002005
Authority: WO
Inventors: Sa ZHANG; Feifei SUN
Original assignee: Samsung Electronics Co., Ltd.
Priority date: 2023-02-15
Filing date: 2024-02-13
Publication date: 2024-08-22
Also published as: CN118509143A

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method and an apparatus for transmitting and receiving an uplink channel are provided. The method includes: receiving first information for enabling the terminal to report unused occasions for a configured grant (CG) physical uplink shared channel (PUSCH); and transmitting second information for indicating whether one or more CG PUSCH occasions are unused based on the first information, wherein in case that a CG PUSCH occasion is not indicated as unused by the second information, a configured uplink grant corresponding to the CG PUSCH and HARQ information associated with the CG PUSCH are delivered to a hybrid automatic repeat request (HARQ) entity of the terminal. The invention can enhance the spectrum efficiency.

Description

METHOD AND APPARATUS FOR TRANSMITTING AND RECEIVING UPLINK CHANNEL

The disclosure relates to the technical field of wireless communication, and more specifically, to a method and an apparatus for transmitting and receiving an uplink channel.

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

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

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

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

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

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

The present invention has been made to address at least the above problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention provides a method and apparatus for transmitting and receiving uplink channel.

According to at least one embodiment of the disclosure, a method performed by a base station in a wireless communication system is provided. The method includes: transmitting first information for enabling a terminal to report unused occasions for a configured grant (CG) physical uplink shared channel (PUSCH) to the terminal; receiving second information for indicating whether one or more CG PUSCH occasions are unused from the terminal; and receiving the CG PUSCH in a CG PUSCH occasion based on the second information, wherein the CG PUSCH occasion is not indicated as unused by the second information.

In some implementations, for example, the method further includes scheduling a PUSCH on a serving cell through a physical downlink control channel (PDCCH), wherein the PUSCH overlaps with a CG PUSCH on the serving cell corresponding to a CG PUSCH occasion that is indicated as unused, wherein the CG PUSCH occasion that is indicated as unused is determined based on the second information.

In some implementations, for example, the method further includes scheduling a PUSCH on a serving cell through a PDCCH, wherein the PUSCH has a same HARQ process as a CG PUSCH on the serving cell corresponding to a CG PUSCH occasion that is indicated as unused, wherein the CG PUSCH occasion that is indicated as unused is determined based on the second information.

According to at least one embodiment of the disclosure, a terminal in a wireless communication system is also provided. The terminal includes: a transceiver; and a controller coupled with the transceiver and configured to perform one or more of the operations in the above-mentioned methods performed by the terminal.

According to at least one embodiment of the disclosure, a base station in a wireless communication system is also provided. The base station includes: a transceiver; and a controller coupled with the transceiver and configured to perform one or more of the operations in the above-mentioned method performed by the base station.

According to at least one embodiment of the disclosure, a computer-readable storage medium having one or more computer programs stored thereon is also provided, wherein the one or more computer programs, when executed by one or more processors, can implement any of the above-described methods.

Advantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention. For more enhanced communication system, there is a need for method and network for transmitting and receiving uplink channel.

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

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

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

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

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

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

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

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

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

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

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

FIGS. 8B illustrates some examples of uplink transmission timing according to some embodiments of the disclosure;

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

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

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

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

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

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".

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.

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.

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.

According to at least one embodiment of the disclosure, a method performed by a terminal in a wireless communication system is provided. The method includes: receiving first information for enabling the terminal to report unused occasions for a configured grant (CG) physical uplink shared channel (PUSCH); and transmitting second information for indicating whether one or more CG PUSCH occasions are unused based on the first information, wherein in case that a CG PUSCH occasion is not indicated as unused by the second information, a configured uplink grant corresponding to the CG PUSCH and HARQ information associated with the CG PUSCH are delivered to a hybrid automatic repeat request (HARQ) entity of the terminal.

In some implementations, for example, in case that the CG PUSCH occasion is not indicated as unused by the second information:

- not transmitting the CG PUSCH corresponding to the CG PUSCH occasion, or transmitting the CG PUSCH corresponding to the CG PUSCH occasion; and/or

- based on receiving indication information for enabling the terminal not to transmit the CG PUSCH corresponding to the CG PUSCH occasion, not transmitting the CG PUSCH corresponding to the CG PUSCH occasion or transmitting the CG PUSCH corresponding to the CG PUSCH occasion; and/or

- based on not receiving the indication information, transmitting the CG PUSCH corresponding to the CG PUSCH occasion; and/or

- generating a medium access control (MAC) protocol data unit (PDU) for the configured uplink grant corresponding to the CG PUSCH occasion.

In some implementations, for example, the first information is used to enable the terminal to report one or more of: information regarding the unused occasions for the CG PUSCH; a number of the unused occasions for the CG PUSCH; or CG PUSCH configuration indexes corresponding to the unused occasions for the CG PUSCH.

In some implementations, for example, the first information is included in one or more of: a CG PUSCH configuration; DCI for activating a CG PUSCH configuration; an uplink BWP configuration; or a cell group configuration for a cell group.

In some implementations, for example, one or more CG PUSCH occasions indicated by the second information include one or more of: one or more CG PUSCH occasions after an uplink channel carrying the second information; one or more CG PUSCH occasions corresponding to a CG PUSCH configuration; one or more CG PUSCH occasions with a same priority; or one or more CG PUSCH occasions in a period of the CG PUSCH configuration.

In some implementations, for example, the one or more CG PUSCHs includes one or more of:

- CG PUSCH occasions that do not overlap with a first predefined symbol;

- subsequent CG PUSCH occasions of a PUSCH carrying the second information;

- CG PUSCH occasions that are later than N7 time units after an end position of the PUSCH carrying the second information, where N7 is a positive rational number;

- CG PUSCH occasions that are in a same period as a CG PUSCH carrying the second information;

- CG PUSCH occasions that are in N3 periods after a period in which the CG PUSCH carrying the second information is located, where N3 is a positive rational number;

- CG PUSCH occasions that correspond to a same CG PUSCH configuration as the CG PUSCH carrying the second information;

- CG PUSCH occasions that are in a same serving cell or uplink BWP as the CG PUSCH carrying the second information; or

- CG PUSCH occasions that have a same priority as the PUSCH carrying the second information.

In some implementations, for example, the first predefined symbol includes one or more of:

- a semi-statically configured downlink symbol;

- a symbol of a synchronization signal block (SSB);

- a symbol of a control resource set 0 (CORESET0);

- a symbol indicated as pdcch-ConfigSIB1 by an MIB of a CORESET associated with a Type0-PDCCH common search space (CSS) set;

- an unavailable symbol configured by higher layer signaling; or

- X symbols after the SSB, where X is a positive rational number.

In some implementations, for example, for each of one or more CG PUSCH occasions that are indicated as unused by the second information:

- not transmitting a CG PUSCH corresponding to the CG PUSCH occasion; and/or

- not transmitting a CG PUSCH between a start time and an end time of the CG PUSCH occasion; and/or

- not transmitting a first predetermined number of CG PUSCHs after a start time of the CG PUSCH; and/or

- not transmitting a second predetermined number of CG PUSCHs before a reception time of the CG PUSCH; and/or

- not delivering the configured uplink grant corresponding to the CG PUSCH and the HARQ information associated with the CG PUSCH to the HARQ entity of the terminal; and/or

- not generating a MAC PDU for the configured uplink grant corresponding to the CG PUSCH.

In some implementations, for example, the second information is transmitted in one or more of a PUCCH, a PUSCH, a CG PUSCH or a dynamically scheduled PUSCH.

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

Before undertaking the DETAILED DESCRIPTION below, it 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.

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.

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

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

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

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

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

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

It will be further understood that similar words such as the term "include" or "comprise" mean that elements or objects appearing before the word encompass the listed elements or objects appearing after the word and their equivalents, but other elements or objects are not excluded. Similar words such as "connect" or "connected" are not limited to physical or mechanical connection, but 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.

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

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

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

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

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

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

Depending on a type of the network, other well-known terms such as "base station (BS)" or "access point" 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).

gNB 102 provides wireless broadband access to the network 130 for a first plurality of User Equipments (UEs) within a coverage area 120 of gNB 102. The first plurality of UEs include a UE 111, which may be located in a Small Business (SB); a UE 112, which may be located in an enterprise (E); a UE 113, which may be located in a WiFi Hotspot (HS); a UE 114, which may be located in a first residence (R); a UE 115, which may be located in a second residence (R); a UE 116, which may be a mobile device (M), such as a cellular phone, a wireless laptop computer, a wireless PDA, etc. GNB 103 provides wireless broadband access to network 130 for a second plurality of UEs within a coverage area 125 of gNB 103. The second plurality of UEs include a UE 115 and a UE 116. In some embodiments, one or more of gNBs 101-103 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.

The dashed lines show approximate ranges of the

coverage areas

120 and 125, and the ranges are shown as approximate circles merely for illustration and explanation purposes. It should be clearly understood that the coverage areas associated with the gNBs, such as the

coverage areas

120 and 125, may have other shapes, including irregular shapes, depending on configurations of the gNBs and changes in the radio environment associated with natural obstacles and man-made obstacles.

As will be described in more detail below, one or more of gNB 101, gNB 102, and gNB 103 include a 2D antenna array as described in embodiments of the disclosure. In some embodiments, one or more of gNB 101, gNB 102, and gNB 103 support codebook designs and structures for systems with 2D antenna arrays.

Although FIG. 1 illustrates an example of the wireless network 100, various changes 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.

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 embodiments, the reception path 250 is configured to support codebook designs and structures for systems with 2D antenna arrays as described in embodiments of the disclosure.

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

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

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

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

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

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.).

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.

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.

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

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

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

The processor/controller 340 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 embodiments, the processor/controller 340 includes at least one microprocessor or microcontroller.

The processor/controller 340 is also capable of executing other processes and programs residing in the memory 360, such as operations for channel quality measurement and reporting for systems with 2D antenna arrays as described in embodiments of the disclosure. The processor/controller 340 can move data into or out of the memory 360 as required by an execution process. In some embodiments, the processor/controller 340 is configured to execute the application 362 based on the OS 361 or in response to signals received from the gNB or the operator. The processor/controller 340 is also coupled to an I/O interface 345, where the I/O interface 345 provides UE 116 with the 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.

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).

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.

In some implementations, two or more UEs 116 may communicate directly using one or more sidelink channels (for example, without using a base station as a medium for communication with each other). For example, the UE 116 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocol (which, for example, may include vehicle-to-vehicle (V2V) protocol, vehicle-to-infrastructure (V2I) protocol, etc.), mesh network, etc. In this case, the UE 116 may perform scheduling operations, resource selection operations, and/or other operations performed by the base station as described elsewhere herein. For example, the base station may configure the UE 116 via downlink control information (DCI), radio resource control (RRC) signaling, medium access control-control element (MAC-CE) or via system information (e.g., system information block (SIB)). FIG. 3B illustrates an example gNB 102 according to some embodiments of the disclosure. The embodiment of gNB 102 shown in FIG. 3B is for illustration only, and other gNBs of FIG. 1 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.

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

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

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

The controller/processor 378 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 embodiments, the controller/processor 378 includes at least one microprocessor or microcontroller.

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

The controller/processor 378 is also coupled to the backhaul or network interface 382. The backhaul or network interface 382 allows gNB 102 to communicate with other devices or systems through a backhaul connection or through a network. The backhaul or network interface 382 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.

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.

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

Although FIG. 3B illustrates an example of gNB 102, various changes may be made to FIG. 3B. For example, gNB 102 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).

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.

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.

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

In some cases, in order to reduce the delay, a base station can configure CG (Configured Grant) PUSCH resources for a UE. Before receiving the CG PUSCH, the base station is not sure whether a CG PUSCH resource is used by the UE, and the base station cannot allocate a CG PUSCH resource that is unused by the UE to other UEs in advance, which may cause a waste of time-frequency resources. Therefore, an enhanced UE downlink signal receiving method or uplink signal transmitting method is needed to improve the system spectrum efficiency.

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

In embodiments of the disclosure, for the convenience of description, a first transceiving node and a second transceiving node are defined. For example, the first transceiving node may be a base station, and the second transceiving node may be a UE. For another example, the embodiments of the disclosure may be applicable to the scenario of sidelink communication, in which case, the first transceiver node may be a UE, and the second transceiver node may be another UE. Therefore, the first transceiving node and the second transceiving node may each be any suitable communication node. In the following description, the base station is taken as an example (but not limited thereto) to illustrate the first transceiving node, and the UE is taken as an example (but not limited thereto) to illustrate the second transceiving node.

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

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

- MIB (master information block)

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

- RRC signaling

- MAC CE

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

- PDCCH (physical downlink control channel)

- DCI (downlink control information)

- UE-specific DCI

- group common DCI

- common DCI

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

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

- PUCCH (physical uplink control channel)

- UCI (uplink control information)

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

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

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

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

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

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

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

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

Herein, depending on the network type, the term "base station" or "BS" 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 wirelessly enabled devices. Base stations may provide wireless access in accordance with one or more wireless communication protocols, e.g., 5G 3GPP new radio (NR) interface/access, Long Term Evolution (LTE), LTE advanced (LTE-A), High Speed Packet Access (HSPA), Wi-Fi 802.11a/b/g/n/ac, etc.

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

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

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

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

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

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

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

In implementations described in connection with FIG. 4 or 5, the first control signaling may be control signaling transmitted by the first transceiving node to the second transceiving node. In the following examples, downlink control signaling is taken as an example (but not limited thereto) to illustrate the first control signaling. The downlink control signaling may be DCI (downlink control information) carried by a PDCCH (Physical Downlink Control Channel) and/or control signaling carried by a PDSCH (Physical Downlink Shared Channel). For example, the DCI may be UE specific DCI, and the DCI may also be common DCI. The common DCI may be DCI common to a part of UEs, such as group common DCI, and the common DCI may also be DCI common to all of the UEs. The DCI may be uplink DCI (e.g., DCI for scheduling a PUSCH) and/or downlink DCI (e.g., DCI for scheduling a PDSCH).

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

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

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

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

In implementations described in connection with FIG. 4 or 5, a second time unit is a time unit in which the second transceiving node transmits the second data and/or the second control signaling. In the following examples, an uplink time unit or uplink slot or PUCCH slot or PCell (Primary Cell) slot or PUCCH slot on PCell is taken as an example (but not limited thereto) to illustrate the second time unit. The "PUCCH slot" may be understood as a PUCCH transmission slot.

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

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

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

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

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

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

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

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

In operation S720, the UE determines uplink data and/or uplink control signaling and a second time unit based on the downlink data and/or downlink control signaling.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

For example, if the UE is configured with the subslot length parameter, and 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 a PDSCH reception), then HARQ-ACK information for the PDSCH reception or PDCCH reception is transmitted in an uplink subslot n+k, where k is determined by the timing parameter K1 (the definition of the timing parameter K1 may refer to the previous description). For another example, if the UE is not configured with the subslot length parameter, and 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.

In embodiments of the disclosure, unicast may refer to a manner in which a network communicates with a UE, and multicast (or groupcast) may refer to a manner in which a network communicates with multiple UEs. For example, a unicast PDSCH may be a PDSCH received by one UE, and the 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 the scrambling of the multicast PDSCH may be based on a UE-group common RNTI. For example, the UE-group common RNTI for scrambling the multicast PDSCH may include an RNTI (which may be referred to as Group RNTI (G-RNTI) in embodiments of the disclosure) for scrambling of a dynamically scheduled multicast transmission (e.g., PDSCH) or an RNTI (which may be referred to as group configured scheduling RNTI (G-CS-RNTI) in embodiments of the disclosure) for scrambling of a multicast SPS transmission (e.g., SPS PDSCH). UCI(s) of the unicast PDSCH may include HARQ-ACK information, SR, or CSI of the unicast PDSCH reception. UCI(s) of the multicast PDSCH may include HARQ-ACK information for the multicast PDSCH reception. In embodiments of the disclosure, "multicast" may also be replaced by "broadcast".

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

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

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

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

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 bits according to a semi-statically configured parameter (e.g., a parameter configured by higher layer signaling). For a serving cell c, an active downlink BWP (bandwidth part) and an active uplink BWP, the UE determines a set of

occasions for candidate PDSCH receptions for which the UE can transmit corresponding HARQ-ACK information in a PUCCH in an uplink slot

.

may be determined by at least one of:

a) HARQ-ACK slot timing values K1 of the active uplink BWP;

b) a downlink time domain resource allocation (TDRA) table;

c) an uplink SCS configuration and a downlink SCS configuration;

d) a semi-static uplink and downlink frame structure configuration;

e) a downlink slot offset parameter (e.g., the higher layer parameter

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

), and a slot offset parameter (e.g., the higher layer parameter

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

).

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

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

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

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

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

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

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

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

Tables 1 and 2 show a correspondence between the DAI field and

or

. Numbers of bits of the C-DAI and T-DAI are limited.

For example, in case that a C-DAI or T-DAI in a DCI is represented with 2 bits, the value of the C-DAI or T-DAI in the DCI may be determined by equations in Table 1.

or

is the value of the T-DAI in the DCI received in a PDCCH Monitoring Occasion (MO) m, and

is the value of the C-DAI in the DCI for a serving cell c received in the PDCCH monitoring occasion m. Both

and

are related to a number of bits of the DAI field in the DCI. MSB is the Most Significant Bit and LSB is the Least Significant Bit.

[Table 1]

For example, when the C-DAI or T-DAI is 1, 5 or 9, as shown in Table 1, all of the DAI field are indicated with "00", and the value of

or

is represented as "1" by the equation in Table 1. Y may represent the value of the DAI corresponding to the number of DCIs actually transmitted by the base station (the value of the DAI before conversion by the equation in the table).

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

[Table 2]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

It should be noted that in methods of the disclosure, "configured with and/or indicated a transmission with repetitions" may be understood that a number of the repetitions of the transmission is greater than 1. For example, "configured with and/or indicated a PUCCH transmission with repetitions" may be understood that "the PUCCH transmission is repeated on more than one slot/sub-slot". "Not configured with and/or indicated a transmission with repetitions" may be understood that a number of the repetitions of the transmission is equal to 1. For example, "not configured with and/or indicated a PUCCH transmission with repetitions" may be understood that "a number of the repetitions of the PUCCH transmission is equal to 1". For example, the UE may be configured with a parameter

related to a number of repetitions of a PUCCH transmission; When the parameter

is greater than 1, it may mean that the UE is configured with a PUCCH transmission with repetitions, and the UE may repeat the PUCCH transmission on

time units (e.g., slots); when the parameter is equal to 1, it may mean that the UE is not configured with a PUCCH transmission with repetitions. For example, the PUCCH with repetitions may include only one type of UCI. If the PUCCH is configured with repetitions, in embodiments of the disclosure, a repetition of the multiple repetitions of the PUCCH may be used as a PUCCH (or a PUCCH resource), or all of the repetitions of the PUCCH may be used as a PUCCH (or a PUCCH resource), or a specific repetition of the multiple repetitions of the PUCCH may be used as a PUCCH (or a PUCCH resource).

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

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

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

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

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

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

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

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

In some cases, the UE may be configured with CG PUSCH resources. For example, a CG PUSCH configuration on an uplink BWP is configured by an information element (IE) ConfiguredGrantConfig. One or more CG PUSCH configurations on an uplink BWP can be configured by an IE configuredGrantConfigToAddModList. The UE may be configured with one or more CG PUSCH configurations for uplink BWPs corresponding to one or more serving cells, respectively. According to some embodiments of the disclosure, one or more of the methods described below may be used for transmitting an uplink channel, for example, a CG PUSCH.

Method MN1

In some implementations, a UE may be configured with first information by higher layer signaling. For example, the UE may receive the first information in operation S710. The first information can be used to indicate (for example, enable) the UE to report information related to unused CG PUSCH(s) and/or used CG PUSCH(s). After receiving the first information, the UE may report the information related to unused CG PUSCH(s) and/or used CG PUSCH(s). For example, the unused CG PUSCH(s) may be a CG PUSCH that is unused in a current time or in a time after the current time (in the future).

In operation S720, the UE may determine second information based on the first information, or the UE may determine whether to transmit or report the second information based on the first information, or the UE may transmit or report the second information based on the first information. The second information may indicate the information related to unused CG PUSCH(s) and/or used CG PUSCH(s). For example, when the UE is configured with the first information, the UE transmits or reports the second information.

In operation S720, if a CG PUSCH resource or CG PUSCH allocation or CG PUSCH occasion (occasion for CG PUSCH) or configured uplink grant

- is indicated as unused by the second information, or

- is not indicated as used by the second information, or

- is determined as unused by the first information and/or the second information, or

- is not determined as used by the first information and/or the second information, or

- overlaps with a third time unit that is indicated as unused by the second information,

then the UE does not transmit a PUSCH in the CG PUSCH resource or allocation or occasion, and/or the UE does not deliver the configured uplink grant and its associated HARQ information to a HARQ entity, and/or the UE does not generate a MAC PDU for the configured uplink grant or the UE does not obtain the MAC PDU to transmit from a multiplexing and assembly entity (if any).

Additionally or alternatively, in operation S720, if a CG PUSCH resource or CG PUSCH allocation or CG PUSCH occasion or configured uplink grant

- is not indicated as unused by the second information, or

- is not determined as unused by the first information and/or the second information, or

- is indicated as used by the second information, or

- is determined as used by the first information and/or the second information, or

- overlaps with the third time unit that is not indicated as unused by the second information,

then the UE may transmit the PUSCH in the CG PUSCH resource or allocation or occasion, and/or the UE may deliver the configured uplink grant and its associated HARQ information to the HARQ entity, and/or the UE may generate the MAC PDU for the configured uplink grant or the UE may obtain a MAC PDU to transmit from the Multiplexing and assembly entity (if any).

In operation S730, the UE may transmit or report the second information. For example, the UE may transmit or report the second information in a second time unit. For example, the second information may be carried by the CG PUSCH.

The method can enable the base station to reallocate CG PUSCH resources that will not be used by the UE, thereby improving the system spectrum efficiency. The UE does not generate a corresponding MAC PDU for unused CG PUSCH resources, which can avoid generating an invalid MAC PDU for data corresponding to a logical channel, which cannot be retransmitted through HARQ, thereby improving uplink transmission performance.

It should be noted that in embodiments of the disclosure, "CG PUSCH", "CG PUSCH occasion", "CG PUSCH resource", "CG PUSCH allocation" and "configured uplink grant" may be used interchangeably.

It should be noted that in embodiments of the disclosure, "third time unit that is indicated as unused by second information" may be replaced by "third time unit that is not indicated as used by the second information" or "third time unit that is determined as unused by first information and/or second information" or "third time unit that is not determined as used by first information and/or second information".

It should be noted that in embodiments of the disclosure, "third time unit that is not indicated as unused by second information" may be replaced by "third time unit that is indicated as used by second information" or "third time unit that is determined as used by first information and/or second information", "third time unit that is not determined as unused by first information and/or second information".

It should be noted that the first information may be used to indicate (for example, enable) the UE to report the second information for a CG PUSCH configuration in a CG list (e.g., a parameter allowedCG-List) allowed by a logical channel (for example, allowed for transmitting data of the logical channel).

Method MN2

In some implementations, the first information may also indicate (for example, enable) at least one of:

- the UE to report unused CG PUSCH occasion(s); or, a maximum value N8_max of the unused CG PUSCH occasion(s).

- the number of unused CG PUSCH occasions reported by the UE; or, a maximum value N9_max of the number of unused CG PUSCH occasions.

- the UE to report CG PUSCH configuration index(es) corresponding to the unused CG PUSCH occasion(s).

- the UE to report the first (or last) unused CG PUSCH occasion; or, a maximum value N10_max of the first (or last) unused CG PUSCH occasion.

- the UE to report used CG PUSCH occasion(s); or, a maximum value N11_max of the used CG PUSCH occasion(s).

- the UE to report a number of used CG PUSCH occasions; or, a maximum value N12_max of the number of used CG PUSCH occasions.

- the UE to report CG PUSCH configuration index(es) corresponding to the used CG PUSCH occasion(s).

- the UE to report the last (or first) used CG PUSCH occasion; or, a maximum value N13_max of the last (or first) used CG PUSCH occasion.

- a maximum value N20_max of the CG PUSCH occasion.

- dynamically indicating whether the UE reports the second information. For example, in a DCI format for activating a Type-2 CG PUSCH, a field may be used to indicate whether the UE reports the second information. For example, the field may be 1 bit. For example, "1" (or "0") in the DCI format for activating indicates a CG PUSCH configuration activated by the DCI format, and the UE reports the second information; "0" (or "1") indicates a CG PUSCH configuration activated by the DCI format, and the UE does not report the second information.

- third information, which may be time information of the unused CG PUSCH;

- the UE to report unused third time unit(s); or, a maximum value N14_max of the unused third time unit(s).

- the UE to report a number of unused third time units; or, a maximum value N15_max of the number of unused third time units.

- the UE to report CG PUSCH configuration index(es) corresponding to the unused third time unit(s).

- the UE to report the first (or last) unused third time unit; or, a maximum value N16_max of the first (or last) unused third time unit.

- the UE to report used third time unit(s); or, a maximum value N17_max of the used third time unit(s).

- the UE to report a number of used third time units; or, a maximum value N18_max of the number of the used third time units.

- the UE to report CG PUSCH configuration index(s) corresponding to the used third time unit(s).

- the UE to report the last (or first) used third time unit; or, a maximum value N19_max of the last (or first) used third time unit.

- a maximum value N21_max of the third time unit(s).

In some implementations, the first information may be configured in at least one of the following ways.

The first information may be configured in a CG PUSCH configuration (e.g., IE ConfiguredGrantConfig). At this time, the first information may indicate that the second information reported by the UE is used to indicate one or more CG PUSCH occasions corresponding to the CG PUSCH configuration. For example, the second information may be used to indicate whether one or more CG PUSCH occasions corresponding to the CG PUSCH configuration are unused and/or whether they are used. This configuration is more flexible.

The first information may be configured in an uplink BWP configuration (e.g., IE BWP-UplinkDedicated). At this time, the first information may indicate that the second information reported by the UE is used to indicate one or more CG PUSCH occasions corresponding to one or more CG PUSCH configurations on the uplink BWP. For example, the second information may be used to indicate whether one or more CG PUSCH occasions corresponding to one or more CG PUSCH configurations on the uplink BWP are unused and/or whether they are used. This can save signaling overhead.

The first information may be configured uniformly for all CG PUSCH configurations in a cell group (e.g., a PUCCH cell group), for example, configured in an IE CellGroupConfig. This can minimize the signaling overhead.

The first information may be configured in a logical channel configuration IE (e.g., LogicalChannelConfig). For another example, the first information may be configured in a radio link control (RLC) bearer configuration IE (e.g., RLC-BearerConfig). If the UE receives the first information, the UE may report the second information in the CG PUSCH of the CG configuration (CG PUSCH configuration) in the CG list that is allowed for the logical channel (for example, allowed for transmitting data of the logical channel). This can avoid configuring each CG PUSCH configuration associated with the logical channel, thereby reducing the configuration signaling overhead.

Method MN3

In some implementations, the second information may be at least one of:

- whether N1 CG PUSCH occasions are unused CG PUSCH occasions and/or used CG PUSCH occasions. N1 may be a positive integer. For example, N1 is equal to 1. For another example, N1 may be configured by higher layer signaling. For example, N1 may be configured by the method of configuring the first information in Method MN2. A number of bits of the second information may be N1. Each bit corresponds to a CG PUSCH occasion respectively. For example, the first bit corresponds to the first CG PUSCH occasion, the second bit corresponds to the second CG PUSCH occasion, ..., and the N1-th bit corresponds to the N1-th CG PUSCH occasion. The number of bits of the second information may also be configured by higher layer signaling, for example, the number of bits of the second information may be configured by the method of configuring the first information in Method MN2. In some implementations, bit "1" (or "0") indicates that the CG PUSCH occasion corresponding to this bit is an unused CG PUSCH occasion; "0" (or "1") indicates that the CG PUSCH occasion corresponding to this bit is not an unused CG PUSCH occasion.

- N8: index(es) of the unused CG PUSCH occasion(s);

- N9: a number (e.g., maximum number) of unused CG PUSCH occasions;

- CG PUSCH configuration index(es) corresponding to the unused CG PUSCH occasion(s);

- N10: the first (or last) unused CG PUSCH occasion;

- N11: index(es) of the used CG PUSCH occasion(s);

- N12: a number (e.g., maximum number) of used CG PUSCH occasions;

- a CG PUSCH configuration index(es) corresponding to the used CG PUSCH occasion(s).

- N13: the last (or first) used CG PUSCH occasion; a time (e.g., duration) of the unused CG PUSCH occasion. For example, time information of the unused CG PUSCH occasion may be a start time and/or an end time of the unused CG PUSCH occasion.

- a time (e.g., duration) of the used CG PUSCH occasion(s). For example, time information of the used CG PUSCH occasion may be a start time and/or an end time of the used CG PUSCH occasion. It may be indicated that whether N4 third time units are unused third time units and/or are used third time units. N4 may be a positive integer. For example, N4 is equal to 1. For another example, N4 may be configured by higher layer signaling. For example, N4 may be configured by the method of configuring the first information in Method MN2. A number of bits of the second information may also be N4. Each bit corresponds to a third time unit respectively. A length (or duration) of a third time unit may be configured by higher layer signaling, for example, the length (or duration) of a third time unit may be configured by the method of configuring the first information in Method MN2.

- N14: index(es) of the unused third time unit(s);

- N15: a number (e.g., maximum number) of the unused third time unit(s);

- N16: the first (or last) unused third time unit;

- N17: index(es) of the used third time unit(s);

- N18: a number (e.g., maximum number) of the used third time units;

- N19: the last (or first) used third time unit.

In an example, N1 may be configured in a CG PUSCH configuration, and at this time, the second information may be carried by a CG PUSCH of the CG PUSCH configuration, and the second information may indicate whether N1 CG PUSCH occasions of the CG PUSCH configuration are indicated as unused. In another example, N1 may be configured in an uplink BWP configuration. At this time, the second information may be carried by a CG PUSCH in the uplink BWP (or a serving cell, for example, a serving cell where the uplink BWP is located), and the second information may indicate whether N1 CG PUSCH occasions of the uplink BWP (or the serving cell) are indicated as unused. In another example, N1 may be uniformly configured for all CG PUSCH configurations in a cell group (e.g., a PUCCH cell group). At this time, the second information may be carried by the CG PUSCH in the cell group, and the second information may indicate whether N1 CG PUSCH occasions of the cell group are indicated as unused. This can improve the flexibility of scheduling.

In an example, N4 may be configured in an uplink BWP configuration, and at this time, the second information may be carried by the CG PUSCH in the uplink BWP (or the serving cell, for example, the serving cell where the uplink BWP is located), and the second information may indicate whether N4 third time units of the uplink BWP (or the serving cell) are indicated as unused. In another example, N4 may be configured in a parameter of a cell group (e.g., a PUCCH cell group). At this time, the second information may be carried by a CG PUSCH in the cell group, and the second information may indicate whether N4 third time units of the cell group are indicated as unused. A reference SCS or a reference serving cell may be configured for the third time unit; for example, the reference SCS is 15kHz or an SCS of the reference serving cell is 15kHz, and the third time unit is 1 slot, and at this time, a slot of the third time unit is 15kHz, that is, a slot with a length of 1ms. This can reduce the number of UCI bits and improve the uplink transmission efficiency.

In some implementations, the CG PUSCH occasion(s) indicated in the second information may be CG PUSCH occasions satisfying a first predefined condition. The third time unit(s) indicated in the second information may be third time units satisfying a second predefined condition.

In some implementations, the CG PUSCH occasion(s) and/or the third time unit(s) indicated by the second information or its contents may be CG PUSCH occasions and/or third time units satisfying the first predefined condition and/or the second predefined condition. As an example, when the second information includes information indicating whether N1 CG PUSCH occasions are unused CG PUSCH occasions and/or are used CG PUSCH occasions, the N1 CG PUSCH occasions may be determined based on the first predefined condition and/or the second predefined condition. For example, the N1 CG PUSCH occasions may be N1 CG PUSCH occasions satisfying the first predefined condition and/or satisfying the second predefined condition. As another example, when the second information includes information indicating the unused CG PUSCH occasion, the unused CG PUSCH occasion may be determined based on the first predefined condition and/or the second predefined condition. For example, the determined unused CG PUSCH occasion(s) may be CG PUSCH occasions satisfying the first predefined condition and/or satisfying the second predefined condition. As yet another example, when the second information includes information indicating the unused third time unit(s), the unused third time unit(s) may be determined based on the first predefined condition and/or the second predefined condition. For example, the determined unused third time unit(s) may be third time units satisfying the first predefined condition and/or satisfying the second predefined condition.

It should be noted that in embodiments of the disclosure, "CG PUSCH occasion" may be replaced by "CG PUSCH occasion group". A CG PUSCH occasion group may contain one or more CG PUSCH occasions. A number of CG PUSCH occasions in a CG PUSCH occasion group may be configured by higher layer signaling. For example, it may be configured by the method of configuring the first information in Method MN2.

It should be noted that N8, N9, ... , N19 may all be integers, and their maximum values are N8_max, N9_max, 쪋, N19_max, respectively. N8, N9, ... , and N19, and N8_max, N9_max, ... , and N19_max may all be configured by a method similar to that of configuring N1.

It should be noted that N20_max and N21_max may both be integers, and they can all be configured by a method similar to that of configuring N1.

Method MN4

In some implementations, the first predefined condition may be at least one of the following:

- the indicated CG PUSCH occasions do not overlap with a first predefined symbol. The first predefined symbol may be specified by protocols and/or configured by higher layer signaling.

- the indicated CG PUSCH occasions are later than a PUSCH carrying the second information. That is, the indicated CG PUSCH occasions are subsequent to the PUSCH carrying the second information.

- the indicated CG PUSCH occasions are later than N7 symbols (or time units) after an end position (symbol) of the PUSCH carrying the second information. That is, the indicated CG PUSCH occasions are after N7 symbols (or time units) after the end position (symbol) of the PUSCH carrying the second information. N7 is a positive integer or a positive rational number. N7 may be configured by higher layer signaling. For example, N7 may be configured by the method of configuring the first information in Method MN2. N7 may also be reported through UE capabilities.

- the indicated CG PUSCH occasions are in the same period as the CG PUSCH carrying the second information.

- the indicated CG PUSCH occasions are in N3 periods after a period in which the CG PUSCH carrying the second information is located. N3 is a positive integer or a positive rational number. N3 may be configured by higher layer signaling. For example, N3 may be configured by the method of configuring the first information in Method MN2. N3 may also be reported through UE capabilities. For example, N3 may be 1, that is, the indicated CG PUSCH occasions are in the next period after the period in which the CG PUSCH carrying the second information is located.

- the indicated CG PUSCH occasions correspond to the same CG PUSCH configuration as the CG PUSCH carrying the second information.

- the indicated CG PUSCH occasions are in the same serving cell or uplink BWP as the CG PUSCH carrying the second information.

- the indicated CG PUSCH occasions have the same priority (e.g., physical layer priority) as the PUSCH carrying the second information.

- a configured grant timer (e.g., a parameter configuredGrantTimer) of a HARQ process corresponding to the indicated CG PUSCH occasions is not running in a start symbol (or position) of the indicated CG PUSCH occasions.

For example, the first predefined symbol may be at least one of.

- semi-statically configured downlink symbol(s) (configured by higher layer signaling) (e.g., downlink symbol(s) configured by a 3GPP parameter tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated).

- symbol(s) of an SSB (Synchronization Signal Block).

- symbol(s) of CORESET0.

- unavailable symbol(s) configured by higher layer signaling.

- X symbols after an SSB. X is a positive integer or a positive rational number, which may be specified by protocols and/or configured by higher layer signaling.

The method can improve the validity of the second information indication, and can exclude the CG PUSCH that does not need to be indicated, thereby reducing the number of UCI bits and improving the uplink transmission efficiency.

It should be noted that in embodiments of the disclosure, "indicated CG PUSCH occasion" may be replaced by "indicated third time unit".

Method MN5

In some implementations, CG PUSCH occasions indicated by the second information may be ordered in at least one of the following orders:

- a time order, for example, in chronological order.

- an order of indexes of CG PUSCH configurations, for example, in an ascending (or descending order) order of indexes of CG PUSCH configurations.

- an order of serving cell indexes, for example, in an ascending (or descending order) order of serving cell indexes).

The method specifies the specific ordering method of the second information, which can keep the understanding of the second information consistent between the UE and the base station, improve the reliability of uplink transmission and reduce the blind detection of the base station.

Method MN6

In some implementations, the UE may also report fourth information. The fourth information is used to indicate a number of bits of the second information. The second information and the fourth information may be carried by the same PUSCH. The fourth information may indicate the number of bits of the second information in the PUSCH carrying the fourth information. The fourth information and the second information may be encoded separately. A number of bits of the fourth information may be specified by protocols or configured by higher layer signaling. For example, the fourth information may be configured by the method of configuring the first information in Method MN2. The method can improve the flexibility of scheduling.

Method MN7

In some implementations, the UE may determine one or more CG PUSCH resources or allocations or occasions or configured uplink grants as unused (or used) through the first information and/or the second information. For example, it may be determined by the maximum value N20_max of the CG PUSCH occasion and the last (or first) used CG PUSCH occasion N13. For example, the last N20_max-N13 CG PUSCH occasions are unused.

In some implementations, if a CG PUSCH resource or allocation or occasion or configured uplink grant is not indicated as unused by the second information, or is not determined as unused, the UE may not transmit the CG PUSCH corresponding to the CG PUSCH resource or allocation or occasion, and/or the UE transmits the CG PUSCH corresponding to the CG PUSCH resource or allocation or occasion, that is, the UE is not capable of not transmitting (is not allowed to not transmit) the CG PUSCH corresponding to the CG PUSCH resource or allocation or occasion.

In some implementations, the UE may be configured with fifth information by higher layer signaling. For example, the UE receives the fifth information in operation S710. The fifth information may be used to indicate whether the UE is capable of not transmitting (is allowed to not transmit) a PUSCH on a CG PUSCH occasion that is not indicated as unused. The fifth information may be used to indicate (for example, enable) that the UE is capable of not transmitting (is allowed to not transmit) the PUSCH on the CG PUSCH occasion that is not indicated as unused.

In an example, if the UE is configured with the fifth information, the UE may not transmit the CG PUSCH corresponding to the CG PUSCH resource or allocation or occasion. If the UE is not configured with the fifth information, the UE is not capable of not transmitting (is not allowed to not transmit) the CG PUSCH corresponding to the CG PUSCH resource or allocation or occasion, that is, the UE transmits the CG PUSCH corresponding to the CG PUSCH resource or allocation or occasion.

The fifth information may be configured by higher layer signaling, for example, the fifth information may be configured by a method similar to that of configuring the first information in Method MN2.

The method can keep the understanding of the second information consistent between the UE and the base station, improve the reliability of uplink transmission, and improve the flexibility of uplink transmission through the configuration of the fifth information.

Method MN8

The UE does not expect that a CG PUSCH occasion is indicated as unused by a first second information and is not indicated as used by a second second information. For example, a first PUSCH carrying the first second information precedes a second PUSCH carrying the second second information. For example, the start symbol (or position) of the first PUSCH precedes the start symbol (or position) of the second PUSCH. This can avoid that the UE and the base station have different understandings of the second information when the base station misses the detection of the CG PUSCH, and the reliability of uplink transmission can be improved.

Method MN9

The second information may also be carried by a DG PUSCH and/or PUCCH, and whether it can be carried by the DG PUSCH and/or PUCCH may be configured by a higher layer signaling parameter. For example, the higher layer signaling parameter may be configured by the method of configuring the first information in Method MN2. Whether the second information can be carried by the PUSCH or PUCCH may be dynamically indicated in DCI that schedules or indicates the PUSCH or PUCCH. This can increase the transmission occasion of the second information, thereby increasing the flexibility of uplink scheduling.

Method MN10

If a configured grant transmission occasion is determined or indicated as unused or is not determined or indicated as used on a serving cell, the UE is allowed to be scheduled by a PDCCH to transmit a PUSCH that overlaps in time with the configured grant transmission occasion on the serving cell, that is, the PUSCH scheduled by the PDCCH that overlaps in time with the configured grant transmission occasion in the serving cell does not need to satisfy a timing condition for a DG PUSCH to cancel a CG PUSCH. The timing condition for a DG PUSCH to cancel a CG PUSCH may be that when a PDCCH ending in symbol i schedules the transmission of a PUSCH on a given serving cell overlapping in time with a configured grant transmission occasion starting in symbol j, the end of symbol i is at least

symbols before the beginning of symbol j.

The UE is not expected to be scheduled by a PDCCH ending in symbol i to transmit a PUSCH on a given serving cell overlapping in time with a transmission occasion, where the UE is allowed to transmit a PUSCH with configured grant, starting in symbol j on the same serving cell if the end of symbol i is not at least

symbols before the beginning of symbol j, if the UE is not provided with a low-priority DG-high-priority CG parameter (e.g., prioLowDG-HighCG) or a high-priority DG-low-priority CG parameter (e.g., prioHighDG-LowCG), or the UE is provided with the low-priority DG-high-priority CG parameter (e.g., prioLowDG-HighCG) or the high-priority DG-low-priority CG parameter (e.g., prioHighDG-LowCG) and the two PUSCHs have the same priority index, except that the transmission occasion is indicated as unused or is not indicated as used by the second information, or is determined as unused or is not determined as used.

may be a rational number and

may be determined by UE capability reporting and the SCS for the PUSCH.

If for a given HARQ process on a serving cell, a configured grant transmission occasion is determined as unused or is not determined as used, or the configured grant transmission occasion is not determined as used or is determined as unused, the UE is allowed to be scheduled by a PDCCH to transmit a PUSCH with the same HARQ process on the serving cell, and it is not required to satisfy a timing condition that a PDCCH of the same HARQ process schedules a PUSCH. The timing condition that a PDCCH of the same HARQ process schedules a PUSCH may be that when a PDCCH ending in symbol i schedules the transmission of a PUSCH with the same HARQ process on a given serving cell, the gap between the end of the PDCCH and the beginning of symbol j is not less than

symbols.

The UE is not expected to be scheduled by a PDCCH ending in symbol i to transmit a PUSCH on a given serving cell for a given HARQ process, if there is a transmission occasion where the UE is allowed to transmit a PUSCH with configured grant with the same HARQ process on the same serving cell starting in symbol j after symbol i, and if the gap between the end of the PDCCH and the beginning of symbol j is less than

symbols except that the transmission occasion is indicated as unused or is not indicated as used by the second information, or is determined as unused or is not determined as used.

may be a rational number and

may be determined by UE capability reporting and the SCS of the PUSCH.

The method can improve the flexibility of dynamic scheduling and reduce the delay of scheduling the PUSCH.

Method MN11

In some implementations, the second predefined condition may be at least one of the following:

- not all symbols in the indicated third time unit overlap with the first predefined symbol. That is, at least one symbol in the indicated third time unit does not overlap with the first predefined symbol.

- the indicated third time unit is later than a PUSCH carrying the second information. That is, the indicated third time unit is after the PUSCH carrying the second information.

- the indicated third time unit is later than N5 symbols or time units (e.g., the third time unit) after an end position (symbol) of the PUSCH carrying the second information. That is, the indicated third time unit is after N5 symbols (e.g., the third time unit) after the end position (symbol) of the PUSCH carrying the second information. N5 is a positive integer or a positive rational number. N5 may be configured by higher layer signaling. For example, N5 may be configured by the method of configuring the first information in Method MN5. N5 may also be reported through UE capabilities.

- the indicated third time unit is in the same period (e.g., a period of a CG PUSCH) as a CG PUSCH carrying the second information.

- the indicated third time unit is in N6 time units (e.g., the third time unit) after a time unit (e.g., the third time unit) in which the CG PUSCH carrying the second information is located. N6 is a positive integer or a positive rational number. N6 may be configured by higher layer signaling. For example, N6 may be configured by the method of configuring the first information in Method MN5. N6 may also be reported through UE capabilities. For example, N6 may be 1, that is, the indicated third time unit is in the next period after the period in which the CG PUSCH carrying the second information is located.

- the indicated third time unit is in the same serving cell or uplink BWP as the CG PUSCH carrying the second information.

- a priority corresponding to the indicated third time unit is the same as that (e.g., a physical layer priority) of the PUSCH carrying the second information.

Method MN12

In some implementations, the UE may determine that one or more third time units are unused (or used) through the first information and/or the second information. For example, it may be determined by the maximum value N21_max of the third time units and the used third time unit index N17. For example, the last N21_max-N17 third time units are unused.

In some implementations, if a third time unit is not indicated as unused by the second information, or is not determined as unused, the UE may not transmit a CG PUSCH overlapping with the third time unit, or the UE may transmit the CG PUSCH overlapping with the third time unit, that is, the UE is not capable of not transmitting (is not allowed to not transmit) the CG PUSCH overlapping with the third time unit.

In some implementations, the UE may be configured with sixth information by higher layer signaling. For example, the UE receives the sixth information in operation S710. The sixth information may be used to indicate whether the UE is capable of not transmitting (is allowed to not transmit) the CG PUSCH overlapping with a third time unit that is not indicated as unused by the second information. The sixth information may be used to indicate (for example, enable) that the UE is capable of not transmitting (is allowed to not transmit) the CG PUSCH overlapping with the third time unit that is not indicated as unused by the second information.

In an example, if the UE is configured with the sixth information, the UE may not transmit the CG PUSCH overlapping with the third time unit that is not indicated as unused by the second information. If the UE is not configured with the sixth information, the UE is not capable of not transmitting the CG PUSCH overlapping with the third time unit that is not indicated as unused by the second information, that is, the UE transmits the CG PUSCH overlapping with the third time unit that is not indicated as unused by the second information.

The sixth information may be configured by higher layer signaling, for example, the sixth information may be configured by the method of configuring the first information in Method MN2.

The method can keep the understanding of the second information consistent between the UE and the base station, improve the reliability of uplink transmission, and improve the flexibility of uplink transmission through the configuration of the sixth information.

Method MN13

In some implementations, for each serving cell and each configured uplink grant, if a third predefined condition is not satisfied, the UE may not set the HARQ process ID as the HARQ process ID associated with the PUSCH duration, and/or may not deliver the configured uplink grant and the associated HARQ information to the HARQ entity.

For example, the third predefined condition may be at least one of the following:

- a configured grant transmission occasion is determined or indicated as used.

- a configured grant transmission occasion is not determined or indicated as unused.

In an example, for each serving cell and each configured uplink grant, if configured and activated, the MAC entity shall:

1> if the PUSCH duration of the configured uplink grant does not overlap with the PUSCH duration of an uplink grant received on the PDCCH or in a Random Access Response for this Serving Cell and the third predefined condition is satisfied:

　　2> set the HARQ Process ID to the HARQ Process ID associated with this PUSCH duration;

　　2> if a configured grant timer (e.g., a parameter configuredGrantTimer) for the corresponding HARQ process is not running:

　　　　3> consider the NDI bit for the corresponding HARQ process to have been toggled;

　　　　3> deliver the configured uplink grant and the associated HARQ information to the HARQ entity.

1> if the PUSCH duration of the configured uplink grant does not overlap with the PUSCH duration of an uplink grant received on the PDCCH or in a Random Access Response for this Serving Cell:

　　2> if a configured grant timer (e.g., a parameter configuredGrantTimer) for the corresponding HARQ process is not running and the third predefined condition is satisfied:

1> if the MAC entity is configured with the logical channel (LCH) based priority parameter (e.g., the parameter lch-basedPrioritization), and the PUSCH duration of the configured uplink grant does not overlap with the PUSCH duration of an uplink grant received in a Random Access Response or with the PUSCH duration of an uplink grant addressed to Temporary C-RNTI or the PUSCH duration of a MSGA (e.g., Message A for the random access procedure) payload for this Serving Cell and the third predefined condition is satisfied; or

1> if the MAC entity is not configured with the logical channel (LCH) based priority parameter (e.g., the parameter lch-basedPrioritization), and the PUSCH duration of the configured uplink grant does not overlap with the PUSCH duration of an uplink grant received on the PDCCH or in a Random Access Response or the PUSCH duration of a MSGA payload for this Serving Cell and the third predefined condition is satisfied

　　2> if, for the corresponding HARQ process, the configured grant timer (e.g., the parameter configuredGrantTimer) is not running and the CG retransmission timer (e.g., the parameter cg-RetransmissionTimer) is not configured and the CG-SDT (small data transmission) retransmission timer (e.g., the parameter cg-SDT-RetransmissionTimer) is not configured (i.e. new transmission).

　　　　3> if there is an on-going CG-SDT procedure and PDCCH addressed to the MAC entity's C-RNTI has been received; or

　　　　3> if there is no on-going CG-SDT procedure:

　　　　　　4> consider the NDI bit for the corresponding HARQ process to have been toggled;

　　　　　　4> deliver the configured uplink grant and the associated HARQ information to the HARQ entity.

1> if the MAC entity is configured with the logical channel (LCH) based priority parameter (e.g., the parameter lch-basedPrioritization), and the PUSCH duration of the configured uplink grant does not overlap with the PUSCH duration of an uplink grant received in a Random Access Response or with the PUSCH duration of an uplink grant addressed to Temporary C-RNTI or the PUSCH duration of a MSGA (e.g., Message A for the random access procedure) payload for this Serving Cell; or

1> if the MAC entity is not configured with the logical channel (LCH) based priority parameter (e.g., the parameter lch-basedPrioritization), and the PUSCH duration of the configured uplink grant does not overlap with the PUSCH duration of an uplink grant received on the PDCCH or in a Random Access Response or the PUSCH duration of a MSGA payload for this Serving Cell

　　2> if, for the corresponding HARQ process, the configured grant timer (e.g., the parameter configuredGrantTimer) is not running and the CG retransmission timer (e.g., the parameter cg-RetransmissionTimer) is not configured and the CG-SDT (small data transmission) retransmission timer (e.g., the parameter cg-SDT-RetransmissionTimer) is not configured (i.e. new transmission) and the third predefined condition is satisfied.

　　　　3> if there is no on-going CG-SDT procedure:

In an example, for each uplink grant, the HARQ entity shall:

1> identify the HARQ process associated with this grant, and for each identified HARQ process:

　　2> if the uplink grant is part of a bundle of the configured uplink grant, and may be used for initial transmission, and if no MAC PDU has been obtained for this bundle and the third predefined condition is satisfied:

　　　　3> if there is a MAC PDU in the Msg3 (e.g., Message 3 for the random access procedure) buffer and the uplink grant was received in a Random Access Response; or:

　　　　3> if there is a MAC PDU in the Msg3 (e.g., Message 3 for the random access procedure) buffer and the uplink grant was received on PDCCH for the C-RNTI in the response window (ra-ResponseWindow) and this PDCCH successfully completed the Random Access procedure initiated for beam failure recovery:

　　　　　　4> obtain the MAC PDU to transmit from the Msg3 buffer.

　　　　3> else

　　　　　　4> obtain the MAC PDU to transmit from the Multiplexing and assembly entity, if any;

In an example, for each uplink grant, the HARQ entity shall:

　　　　3> if this uplink grant is a prioritized uplink grant

The method can avoid the UE from generating corresponding MAC PDU for unused CG PUSCH resources, and can avoid generating invalid MAC PDU for data corresponding to logical channels, which cannot be retransmitted through HARQ, thereby improving the uplink transmission performance.

Method MN14

In some implementations, the second information may be carried by a PUSCH, for example, a CG PUSCH. The second information may be encoded separately from other UCI. If the UE is to multiplex the second information and HARQ-ACK, part 1 CSI and part 2 CSI in the PUSCH, the UE discards the part 2 CSI. For example, if a PUCCH carrying HARQ-ACK, part 1 CSI and part 2 CSI overlaps with a PUSCH carrying the second information in time domain, the UE multiplexes the HARQ-ACK and part 1 CSI in the PUSCH. The UE does not transmit the part 2 CSI.

In some implementations, if the UE can multiplex the second information in a PUSCH, the configuration parameters of UCI on a PUSCH (e.g., uci-OnPUSCH) may be configured through the higher layer signaling second parameter. The second parameter may be used to indicate a beta offset parameter (e.g., betaOffset, which may be selected from dynamic or semiStatic) and/or a scaling parameter (e.g., scaling or alpha, which indicates a scaling factor limiting the number of resources (e.g., resource element (RE)) allocated to UCI on the PUSCH) for UCI multiplexing in the PUSCH. If the UE is configured with the second parameter, when the UE multiplexes the second information in the PUSCH, the UE may determine the number of REs occupied by the second information according to the second parameter.

In this way, different beta offset parameters and/or scaling parameters can be configured separately for different UCI information, and the scheduling flexibility can be improved.

Method MN15

In some implementations, the second information may be carried by a PUSCH, for example, a CG PUSCH. The second information may be encoded jointly with other UCI. For example, the second information may be encoded jointly with HARQ-ACK, and the second information may be located before or after the HARQ-ACK. For another example, the second information may be jointly encoded with part 1 CSI. This can avoid discarding part 1 CSI and improve the reliability of CSI transmission.

In some implementations, it may be specified by protocols that the first information and a CG PUSCH transmission with repetitions cannot be configured at the same time. Alternatively, if the first information is configured, it is considered that the CG PUSCH is not transmitted with repetitions. This can reduce the implementation complexity.

In some implementations, if the CG PUSCH is configured with repetitions, the CG PUSCH occasion indicated by the second information is the first CG PUSCH occasion of the CG PUSCH repetitions. This can improve the efficiency of the second information indication.

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

Referring to FIG. 10, in operation S1010, the terminal may receive first information for enabling the terminal to report unused occasions for a CG PUSCH.

Next, in operation S1020, the terminal may transmit second information for indicating whether one or more CG PUSCH occasions are unused based on the first information. in case that a CG PUSCH occasion is not indicated as unused by the second information, a configured uplink grant corresponding to the CG PUSCH and HARQ information associated with the CG PUSCH are delivered to a hybrid automatic repeat request (HARQ) entity of the terminal.

In some implementations, operations S1010 and/or S1020 may be performed based on the methods described according to various embodiments (e.g., various methods described above, such as Methods MN1-MN15) of the disclosure.

In some implementations, the method 1000 may omit one or more of operations S1010 to S1020, or may include additional operations, for example, the operations performed by the terminal (e.g., a UE) that are described according to various embodiments (e.g., various methods described above, such as Methods MN1-MN15) of the disclosure.

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

Referring to FIG. 11, in operation S1110, the base station transmits first information for enabling a terminal to report unused occasions for a CG PUSCH to the terminal.

Next, in operation S1120, the base station receives second information for indicating whether one or more CG PUSCH occasions are unused from the terminal.

In operation S1130, the base station receives a CG PUSCH in a CG PUSCH occasion based on the second information, wherein the CG PUSCH occasion is not indicated as unused by the second information.

In some implementations, operations S1110 and/or S1120 and/or S1130 may be performed based on the methods described according to various embodiments (e.g., various methods described above, such as methods MN1-MN15) of the disclosure.

In some implementations, the method 1100 may omit one or more of operations S1110 to S1130, or may include additional operations, for example, the operations performed by the base station that are described according to various embodiments (e.g., various methods described above, such as Methods MN1-MN15) of the disclosure.

Those skilled in the art will understand that the above illustrative embodiments are described herein and are not intended to be limiting. It should be understood that any two or more of the embodiments disclosed herein may be combined in any combination. Furthermore, other embodiments may be utilized and other changes may be made without departing from the spirit and scope of the subject matter presented herein. It will be readily understood that aspects of the invention of the disclosure as generally described herein and shown in the drawings may be arranged, replaced, combined, separated and designed in various different configurations, all of which are contemplated herein.

Those skilled in the art will understand that the various illustrative logical 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 functional sets in different ways for each specific application, but such design decisions should not be interpreted as causing a departure from the scope of this application.

The various illustrative logic blocks, modules, and circuits described in this application may be implemented or performed by a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic devices, discrete gates or transistor logics, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

The steps of the method or algorithm described in this application may be embodied directly in hardware, in a software module executed by a processor, or in a combination thereof. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, register, hard disk, 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 media. 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 user terminal. In an alternative, the processor and the storage medium may reside in the user terminal as discrete components.

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

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

Claims

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

receiving first information for enabling the terminal to report unused occasions for a configured grant (CG) physical uplink shared channel (PUSCH); and

based on the first information, transmitting second information for indicating whether one or more CG PUSCH occasions are unused,

wherein in case that a CG PUSCH occasion is not indicated as unused by the second information, a configured uplink grant corresponding to the CG PUSCH and HARQ information associated with the CG PUSCH are delivered to a hybrid automatic repeat request (HARQ) entity of the terminal.
The method of claim 1, wherein in case that the CG PUSCH occasion is not indicated as unused by the second information:

not transmitting the CG PUSCH corresponding to the CG PUSCH occasion, or transmitting the CG PUSCH corresponding to the CG PUSCH occasion;

based on receiving indication information for enabling the terminal not to transmit the CG PUSCH corresponding to the CG PUSCH occasion, not transmitting the CG PUSCH corresponding to the CG PUSCH occasion or transmitting the CG PUSCH corresponding to the CG PUSCH occasion;

based on not receiving the indication information, transmitting the CG PUSCH corresponding to the CG PUSCH occasion; or

generating a medium access control (MAC) protocol data unit (PDU) for the configured uplink grant corresponding to the CG PUSCH occasion.
The method of claim 1,

wherein the first information is used to enable the terminal to report at least one information regarding the unused occasions for the CG PUSCH, a number of the unused occasions for the CG PUSCH, or CG PUSCH configuration indexes corresponding to the unused occasions for the CG PUSCH.
The method of claim 1,

wherein the first information is included in at least one a CG PUSCH configuration, DCI for activating a CG PUSCH configuration, an uplink BWP configuration; or a cell group configuration for a cell group,

wherein the second information is transmitted in at least one PUCCH, a PUSCH, a CG PUSCH or a dynamically scheduled PUSCH,

wherein one or more CG PUSCH occasions indicated by the second information include at least one one or more CG PUSCH occasions after an uplink channel carrying the second information, one or more CG PUSCH occasions corresponding to a CG PUSCH configuration, one or more CG PUSCH occasions with a same priority, or one or more CG PUSCH occasions in a period of the CG PUSCH configuration, and

wherein the one or more CG PUSCHs includes at least one CG PUSCH occasions that do not overlap with a first predefined symbol, subsequent CG PUSCH occasions of a PUSCH carrying the second information, CG PUSCH occasions that are later than N7 time units after an end position of the PUSCH carrying the second information, where N7 is a positive rational number, CG PUSCH occasions that are in a same period as a CG PUSCH carrying the second information, CG PUSCH occasions that are in N3 periods after a period in which the CG PUSCH carrying the second information is located, where N3 is a positive rational number, CG PUSCH occasions that correspond to a same CG PUSCH configuration as the CG PUSCH carrying the second information, CG PUSCH occasions that are in a same serving cell or uplink BWP as the CG PUSCH carrying the second information, or CG PUSCH occasions that have a same priority as the PUSCH carrying the second information, and

wherein the first predefined symbol includes at least one a semi-statically configured downlink symbol, a symbol of a synchronization signal block (SSB), a symbol of a control resource set 0 (CORESET0), an unavailable symbol configured by higher layer signaling, or X symbols after the SSB, where X is a positive rational number.
The method of claim 1, wherein for each CG PUSCH occasion of one or more CG PUSCH occasions that are indicated as unused by the second information:

not transmitting a CG PUSCH corresponding to the CG PUSCH occasion; and/or

not transmitting a CG PUSCH between a start time and an end time of the CG PUSCH occasion; or

not transmitting a first predetermined number of CG PUSCHs after a start time of the CG PUSCH; or

not transmitting a second predetermined number of CG PUSCHs before a reception time of the CG PUSCH; or

not delivering the configured uplink grant corresponding to the CG PUSCH and the HARQ information associated with the CG PUSCH to the HARQ entity of the terminal; or

not generating a MAC PDU for the configured uplink grant corresponding to the CG PUSCH.
A method performed by a base station in a wireless communication system, the method comprising:

transmitting, to a terminal, first information for enabling the terminal to report unused occasions for a configured grant (CG) physical uplink shared channel (PUSCH);

receiving, from the terminal, second information for indicating whether one or more CG PUSCH occasions are unused; and

receiving the CG PUSCH in a CG PUSCH occasion based on the second information, wherein the CG PUSCH occasion is not indicated as unused by the second information.
The method of claim 6, further comprising:

scheduling a PUSCH on a serving cell through a physical downlink control channel (PDCCH),

wherein the PUSCH overlaps with a CG PUSCH on the serving cell corresponding to a CG PUSCH occasion that is indicated as unused, and

wherein the CG PUSCH occasion that is indicated as unused is determined based on the second information.
The method of claim 6, further comprising:

scheduling a PUSCH on a serving cell through a PDCCH,

wherein the PUSCH has a same HARQ process as a CG PUSCH on the serving cell corresponding to a CG PUSCH occasion that is indicated as unused, and

wherein the CG PUSCH occasion that is indicated as unused is determined based on the second information.
A terminal in a wireless communication system, the terminal comprising:

a transceiver; and

a controller configured to:

receive, first information for enabling the terminal to report unused occasions for a configured grant (CG) physical uplink shared channel (PUSCH), and

based on the first information, transmit second information for indicating whether one or more CG PUSCH occasions are unused,

wherein in case that a CG PUSCH occasion is not indicated as unused by the second information, a configured uplink grant corresponding to the CG PUSCH and HARQ information associated with the CG PUSCH are delivered to a hybrid automatic repeat request (HARQ) entity of the terminal.
The terminal of claim 9, wherein the controller is further configured to:

not transmit the CG PUSCH corresponding to the CG PUSCH occasion, or transmitting the CG PUSCH corresponding to the CG PUSCH occasion,

based on receiving indication information for enabling the terminal not to transmit the CG PUSCH corresponding to the CG PUSCH occasion, not transmit the CG PUSCH corresponding to the CG PUSCH occasion or transmitting the CG PUSCH corresponding to the CG PUSCH occasion,

based on not receiving the indication information, transmit the CG PUSCH corresponding to the CG PUSCH occasion, or

generate a medium access control (MAC) protocol data unit (PDU) for the configured uplink grant corresponding to the CG PUSCH occasion.
The terminal of claim 9,

wherein the first information is used to enable the terminal to report at least one information regarding the unused occasions for the CG PUSCH, a number of the unused occasions for the CG PUSCH, or CG PUSCH configuration indexes corresponding to the unused occasions for the CG PUSCH,

wherein the first information is included in at least one a CG PUSCH configuration, DCI for activating a CG PUSCH configuration, an uplink BWP configuration; or a cell group configuration for a cell group,

wherein the second information is transmitted in at least one PUCCH, a PUSCH, a CG PUSCH or a dynamically scheduled PUSCH,

wherein one or more CG PUSCH occasions indicated by the second information include at least one one or more CG PUSCH occasions after an uplink channel carrying the second information, one or more CG PUSCH occasions corresponding to a CG PUSCH configuration, one or more CG PUSCH occasions with a same priority, or one or more CG PUSCH occasions in a period of the CG PUSCH configuration, and

wherein the one or more CG PUSCHs includes at least one CG PUSCH occasions that do not overlap with a first predefined symbol, subsequent CG PUSCH occasions of a PUSCH carrying the second information, CG PUSCH occasions that are later than N7 time units after an end position of the PUSCH carrying the second information, where N7 is a positive rational number, CG PUSCH occasions that are in a same period as a CG PUSCH carrying the second information, CG PUSCH occasions that are in N3 periods after a period in which the CG PUSCH carrying the second information is located, where N3 is a positive rational number, CG PUSCH occasions that correspond to a same CG PUSCH configuration as the CG PUSCH carrying the second information, CG PUSCH occasions that are in a same serving cell or uplink BWP as the CG PUSCH carrying the second information, or CG PUSCH occasions that have a same priority as the PUSCH carrying the second information, and

wherein the first predefined symbol includes at least one a semi-statically configured downlink symbol, a symbol of a synchronization signal block (SSB), a symbol of a control resource set 0 (CORESET0), an unavailable symbol configured by higher layer signaling, or X symbols after the SSB, where X is a positive rational number.
The terminal of claim 9, wherein the controller is further configured to:

not transmit a CG PUSCH corresponding to the CG PUSCH occasion,

not transmit a CG PUSCH between a start time and an end time of the CG PUSCH occasion,

not transmit a first predetermined number of CG PUSCHs after a start time of the CG PUSCH,

not transmit a second predetermined number of CG PUSCHs before a reception time of the CG PUSCH,

not deliver the configured uplink grant corresponding to the CG PUSCH and the HARQ information associated with the CG PUSCH to the HARQ entity of the terminal. or

not generate a MAC PDU for the configured uplink grant corresponding to the CG PUSCH.
A base station in a wireless communication system, the base station comprising:

a transceiver; and

a controller configured to:

transmit, to a terminal, first information for enabling the terminal to report unused occasions for a configured grant (CG) physical uplink shared channel (PUSCH),

receive, from the terminal, second information for indicating whether one or more CG PUSCH occasions are unused, and

receive the CG PUSCH in a CG PUSCH occasion based on the second information, wherein the CG PUSCH occasion is not indicated as unused by the second information.
The base station of claim 13, wherein the controller is further configured to:

schedule a PUSCH on a serving cell through a physical downlink control channel (PDCCH),

wherein the PUSCH overlaps with a CG PUSCH on the serving cell corresponding to a CG PUSCH occasion that is indicated as unused, and

wherein the CG PUSCH occasion that is indicated as unused is determined based on the second information.
The base station of claim 13, wherein the controller is further configured to:

schedule a PUSCH on a serving cell through a PDCCH,

wherein the PUSCH has a same HARQ process as a CG PUSCH on the serving cell corresponding to a CG PUSCH occasion that is indicated as unused, and

wherein the CG PUSCH occasion that is indicated as unused is determined based on the second information.