CN116437490A

CN116437490A - Terminal in wireless communication system and method performed by the same

Info

Publication number: CN116437490A
Application number: CN202211406895.XA
Authority: CN
Inventors: 张飒; 孙霏菲
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2022-01-07
Filing date: 2022-11-10
Publication date: 2023-07-14

Abstract

A terminal in a wireless communication system and a method performed thereby are provided. The method comprises the following steps: a Physical Uplink Shared Channel (PUSCH) is transmitted from and/or a Physical Downlink Shared Channel (PDSCH) is received from one or more PUSCH. The one or more PUSCHs include dynamically scheduled PUSCHs and/or Configuration Grant (CG) PUSCHs, and the one or more PDSCH includes dynamically scheduled PDSCH and/or semi-persistent scheduling (SPS) PDSCH. The invention can improve communication efficiency.

Description

Terminal in wireless communication system and method performed by the same

Technical Field

The present disclosure relates generally to the field of wireless communications, and in particular, to a terminal in a wireless communication system and a method performed thereby.

Background

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

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

Further, in the 5G communication system, development of system network improvement is being performed based on advanced small cells, cloud Radio Access Networks (RANs), ultra dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, cooperative multipoint (CoMP), receiving-end interference cancellation, and the like.

In 5G systems, hybrid FSK and QAM modulation (FQAM) and Sliding Window Superposition Coding (SWSC) as Advanced Code 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.

Disclosure of Invention

In accordance with at least one embodiment of the present disclosure, a method performed by a terminal in a wireless communication system is provided. The method comprises the following steps: a Physical Uplink Shared Channel (PUSCH) is transmitted from and/or a Physical Downlink Shared Channel (PDSCH) is received from one or more PUSCH. The one or more PUSCHs include dynamically scheduled PUSCHs and/or Configuration Grant (CG) PUSCHs, and the one or more PDSCH includes dynamically scheduled PDSCH and/or semi-persistent scheduling (SPS) PDSCH.

There is also provided, in accordance with at least one embodiment of the present disclosure, a terminal in a wireless communication system. The terminal comprises: a transceiver configured to transmit and receive signals; and a controller coupled to the transceiver and configured to perform operations in the method performed by the terminal.

There is also provided, in accordance with at least one embodiment of the present disclosure, a method performed by a base station in a wireless communication system. The method comprises the following steps: transmitting one or more Physical Downlink Shared Channels (PDSCH), and/or receiving PUSCH from one or more Physical Uplink Shared Channels (PUSCH). The one or more PUSCHs include dynamically scheduled PUSCHs and/or Configuration Grant (CG) PUSCHs, and the one or more PDSCH includes dynamically scheduled PDSCH and/or semi-persistent scheduling (SPS) PDSCH.

There is also provided, in accordance with at least one embodiment of the present disclosure, a base station in a wireless communication system. The base station includes: a transceiver configured to transmit and receive signals; and a controller coupled to the transceiver and configured to perform operations in the method performed by the base station.

According to some embodiments of the present disclosure, there is also provided a computer-readable storage medium having stored thereon one or more computer programs, wherein any of the methods described above may be implemented when the one or more computer programs are executed by one or more processors.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings of the embodiments of the present disclosure will be briefly described below. It is apparent that the figures described below relate only to some embodiments of the present disclosure and are not limiting of the present disclosure. In the accompanying drawings:

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

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

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

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

fig. 4 illustrates a block diagram of a second transceiving node according to some embodiments of the present disclosure;

fig. 5 illustrates a flow chart of a method performed by a UE in accordance with some embodiments of the disclosure;

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

fig. 7A and 7B illustrate examples of time domain resource allocation Tables (TDRA) according to some embodiments of the present disclosure;

FIG. 8 illustrates a flow chart of a method performed by a terminal in accordance with some embodiments of the disclosure;

fig. 9 illustrates a block diagram of a first transceiving node according to some embodiments of the present disclosure; and

fig. 10 illustrates a flow chart of a method performed by a base station according to some embodiments of the present disclosure.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present disclosure more apparent, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present disclosure. It will be apparent that the described embodiments are some, but not all, of the embodiments of the present disclosure. All other embodiments, which can be made by one of ordinary skill in the art without the need for inventive faculty, are within the scope of the present disclosure, based on the described embodiments of the present disclosure.

Before proceeding with the description of the detailed description that follows, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term "couple" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms "transmit," "receive," and "communicate," and derivatives thereof, encompass both direct and indirect communication. The terms "include" and "comprise," as well as derivatives thereof, are intended to be inclusive and not limited to. The term "or" is inclusive, meaning and/or. The phrase "associated with" and its derivatives are intended to include, be included within, be connected to, be interconnected with, be included within, be connected to or be connected with, be coupled to or be coupled with, be able to communicate with, be co-operative with, be interwoven with, be juxtaposed with, be proximate to, be bound to or be in relation to, be bound to, be provided with an · attribute, be provided with an · relationship or be provided with a relationship with the · and the like. The term "controller" means any device, system, or portion thereof that controls at least one operation. Such a controller may be implemented in hardware, or in a combination of hardware and software and/or firmware. The functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. At least one of the phrases "..when used with a list of items means that different combinations of one or more of the listed items can be used and that only one item in the list may be required. For example, "at least one of A, B and C" includes any one of the following combinations: A. b, C, A and B, A and C, B and C, and a and B and C. For example, "at least one of A, B or C" includes any one of the following combinations: A. b, C, A and B, A and C, B and C, and a and B and C.

Furthermore, the various functions described below may be implemented or supported by one or more computer programs, each 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 portions 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 (Random Access Memory, RAM), a hard disk drive, a Compact Disc (CD), a Digital Video Disc (DVD), or any other type of Memory. "non-transitory" computer-readable media exclude wired, wireless, optical, or other communication links that transmit transitory electrical or other signals. Non-transitory computer readable media include media that can permanently store data and media that can store and later rewrite data, such as rewritable optical disks or erasable memory devices.

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

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

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

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

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

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

It will be further understood that the terms "comprises" and "comprising," and the like, when used in this specification, specify the presence of stated features and advantages, but do not preclude the presence of other features and advantages, and that the terms "comprising" and "include" specify the presence of stated features and advantages, but rather than preclude the presence of other features and advantages. The terms "connected" or "connected," and the like, are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "upper", "lower", "left", "right", etc. are used merely to indicate relative positional relationships, which may also be changed when the absolute position of the object to be described is changed.

The various embodiments discussed below for describing the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged wireless communication system. For example, although the following detailed description of embodiments of the present disclosure will be directed to LTE and 5G communication systems, it will be appreciated by those skilled in the art that the main gist of the present disclosure may be applied to other communication systems having similar technical contexts and channel formats with slight modifications without substantially departing from the scope of the present disclosure. The technical solution of the embodiments of the present application may be applied to various communication systems, for example, the communication systems may include a global system for mobile communications (global system for mobile communications, GSM) system, a code division multiple access (code division multiple access, CDMA) system, a wideband code division multiple access (wideband code division multiple access, WCDMA) system, a general packet radio service (general packet radio service, GPRS), a long term evolution (long term evolution, LTE) system, an LTE frequency division duplex (frequency division duplex, FDD) system, an LTE time division duplex (time division duplex, TDD), a general mobile communication system (universal mobile telecommunication system, UMTS), a worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX) communication system, a fifth generation (5th generation,5G) system, or a New Radio (NR), etc. In addition, the technical scheme of the embodiment of the application can be applied to future-oriented communication technologies. In addition, the technical scheme of the embodiment of the application can be applied to future-oriented communication technologies.

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

Fig. 1-3B below describe various embodiments implemented in a wireless communication system using orthogonal frequency division multiplexing (orthogonal frequency division multiplexing, OFDM) or orthogonal frequency division multiple access (orthogonal frequency division multiple access, OFDMA) communication techniques. The description of fig. 1-3B is not meant to imply architectural or physical implications with respect to the manner in which different embodiments may be implemented. The various embodiments of the present disclosure may be implemented in any suitably arranged communication system.

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 this disclosure.

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

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

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

The dashed lines illustrate the approximate extent of

coverage areas

120 and 125, which are shown as approximately circular for illustration and explanation purposes only. It should be clearly understood that coverage areas associated with the gnbs, such as

coverage areas

120 and 125, can have other shapes, including irregular shapes, depending on the configuration of the gnbs and the variations in the radio environment associated with natural and man-made obstructions.

As described in more detail below, one or more of gNB 101, gNB 102, and gNB 103 includes 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 shows one example of a wireless network 100, various changes can be made to fig. 1. For example, the wireless network 100 can include any number of gnbs and any number of UEs in any suitable arrangement. Also, the gNB 101 is capable of communicating directly with any number of UEs and providing those UEs with wireless broadband access to the network 130. Similarly, each gNB 102-103 is capable of communicating directly with the network 130 and providing direct wireless broadband access to the network 130 to the UE. Furthermore, the

gnbs

101, 102, and/or 103 can provide access to other or additional external networks (such as external telephone networks or other types of data networks).

Fig. 2A and 2B illustrate example wireless transmit and receive paths according to some embodiments of the present disclosure. In the following description, transmit path 200 can be described as implemented in a gNB (such as gNB 102), while receive path 250 can be described as implemented in a UE (such as UE 116). However, it should be understood that the receive path 250 can be implemented in the gNB and the transmit path 200 can be implemented in the UE. In some embodiments, receive path 250 is configured to support codebook designs and structures for systems with 2D antenna arrays as described in embodiments of the present disclosure.

The transmit path 200 includes a channel coding and modulation block 205, a serial-to-parallel (S-to-P) block 210, an inverse N-point fast fourier transform (IFFT) block 215, a parallel-to-serial (P-to-S) block 220, an add cyclic prefix block 225, and an up-converter (UC) 230. The receive path 250 includes a down-converter (DC) 255, a remove cyclic prefix block 260, a serial-to-parallel (S-to-P) block 265, an N-point Fast Fourier Transform (FFT) block 270, a parallel-to-serial (P-to-S) block 275, and a channel decoding and demodulation block 280.

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

The RF signal transmitted from the gNB 102 reaches the UE 116 after passing through the wireless channel, and an operation inverse to that at the gNB 102 is performed at the UE 116. Down-converter 255 down-converts the received signal to baseband frequency and remove cyclic prefix block 260 removes the cyclic prefix to generate a serial time domain baseband signal. Serial-to-parallel block 265 converts the time-domain baseband signal to a parallel time-domain signal. The N-point FFT block 270 performs an FFT algorithm to generate N parallel frequency domain signals. Parallel-to-serial block 275 converts the parallel frequency domain signals into a sequence of modulated data symbols. The channel decoding and demodulation block 280 demodulates and decodes the modulation symbols to recover the original input data stream.

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

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

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

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

Fig. 3A illustrates an example UE 116 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, the UE has a variety of configurations, and fig. 3A does not limit the scope of the present disclosure to any particular implementation of the UE.

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

RF transceiver 310 receives an incoming RF signal from antenna 305 that is transmitted by the gNB of wireless network 100. 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 sent to RX processing circuit 325, where 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 sends the processed baseband signals to a speaker 330 (such as for voice data) or to a processor/controller 340 (such as for web-browsing data) for further processing.

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

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

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

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

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

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

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

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

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

The controller/processor 378 can include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, controller/processor 378 may be capable of controlling the reception of forward channel signals and the transmission of backward channel signals via RF transceivers 372a-372n, RX processing circuit 376, and TX processing circuit 374 in accordance with well-known principles. The controller/processor 378 is also capable of supporting 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 by a BIS algorithm and decode the received signal from which the interference signal is subtracted. Controller/processor 378 may support any of a variety of other functions in gNB 102. In some embodiments, controller/processor 378 includes at least one microprocessor or microcontroller.

Controller/processor 378 is also capable of executing programs and other processes residing in memory 380, such as a basic OS. Controller/processor 378 is also capable of supporting channel quality measurements and reporting for systems having 2D antenna arrays as described in embodiments of the present disclosure. In some embodiments, the controller/processor 378 supports communication between entities such as web RTCs. Controller/processor 378 is capable of moving data into and out of memory 380 as needed to perform the process.

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

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

As described in more detail below, the transmit and receive paths of the gNB 102 (implemented using the RF transceivers 372a-372n, TX processing circuitry 374, and/or RX processing circuitry 376) support aggregated communications with FDD and TDD cells.

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

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

With the rapid development of the information industry, especially the growing demand from the mobile internet and internet of things (IoT, internet of things), the future mobile communication technology is challenged unprecedented. As per the international telecommunications union (International Telecommunication Union, ITU) report ITU-R M [ imt. Beyond 2020.Traffic ], it can be expected that in 2020, mobile traffic will increase approximately 1000 times as compared to 2010 (4G age), UE connections will also exceed 170 billions, and the number of connected devices will be even more dramatic as massive IoT devices gradually penetrate mobile communication networks. To address this unprecedented challenge, the communications industry and academia have developed extensive fifth generation mobile communication technology (5G) research to face the 2020 s. The framework and overall goals of future 5G have been discussed in ITU report ITU-R M [ imt.vision ], where the requirements expectations, application scenarios and important performance metrics of 5G are specified. For new demands in 5G, ITU report ITU-R M [ imt.future TECHNOLOGY TRENDS ] provides information about technical trends for 5G, aiming at solving significant problems of significant improvement of system throughput, user experience consistency, scalability to support IoT, latency, energy efficiency, cost, network flexibility, support of emerging services, flexible spectrum utilization, etc. In 3GPP (3 rd Generation Partnership Project, third generation partnership project), work on the first phase of 5G is already underway. To support more flexible scheduling, 3GPP decides to support variable hybrid automatic repeat request-Acknowledgement (HARQ-ACK) feedback delay in 5G. In existing long term evolution (Long Term Evolution, LTE) systems, the time of uplink transmission from the reception of HARQ-ACK of downlink data is fixed, for example, in frequency division duplex (Frequency Division Duplex, FDD) systems, the delay is 4 subframes, and in time division duplex (Time Division Duplex, TDD) systems, one HARQ-ACK feedback delay is determined for the corresponding downlink subframe according to the uplink and downlink configuration. In a 5G system, whether FDD or TDD, the uplink time unit in which HARQ-ACKs can be fed back is variable for one determined downlink time unit (e.g., downlink time slot or downlink mini-slot). For example, the time delay of the HARQ-ACK feedback may be dynamically indicated by the physical layer signaling, or different HARQ-ACK time delays may be determined according to different services or factors such as user capability.

The 3GPP defines three major directions for 5G application scenarios-eMBB (enhanced mobile broadband ), mMTC (massive machine-type communication), URLLC (ultra-reliable and low-latency communication), ultra-reliable and low-latency communications. The eMBB scene aims at further improving the data transmission rate on the basis of the existing mobile broadband service scene so as to improve the user experience, thereby seeking the extreme communication experience among people. mctc and URLLC are application scenarios such as internet of things, but each emphasis is different: mctc is mainly information interaction between people and objects, and URLLC mainly reflects the communication requirement between objects.

As described above, various services can be provided according to the development of wireless communication systems, and thus a method for easily providing such services is required.

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

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

Exemplary embodiments of the present disclosure are further described below with reference to the accompanying drawings.

The text and drawings are provided as examples only to assist the reader in understanding the present disclosure. They are not intended, nor should they be construed, to limit the scope of the present disclosure in any way. While certain embodiments and examples have been provided, it will be apparent to those of ordinary skill in the art from this disclosure that variations can be made to the embodiments and examples shown without departing from the scope of the disclosure.

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

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

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

The controller 402 may be an application specific integrated circuit or at least one processor. The controller 402 may be configured to control the overall operation of the second transceiving node, as well as to control the second transceiving node to implement the methods presented in the embodiments of the present disclosure. For example, the controller 402 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 to control the transceiver 401 to transmit the second data and/or the second control signaling to the first transceiving node at the determined time unit.

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

In some embodiments, the first data may be data that the first transceiving node transmits to the second transceiving node. In the following examples, the first data is described by taking downlink data carried by PDSCH (Physical Downlink Shared Channel ) as an example, but not limited to.

In some embodiments, the second data may be data transmitted by the second transceiving node to the first transceiving node. In the following example, the second data is described by taking uplink data carried by PUSCH (Physical Uplink Shared Channel ) as an example (but not limited to).

In some embodiments, the first control signaling may be control signaling sent by the first transceiver node to the second transceiver node. In the following examples, the first control signaling is illustrated by way of example (but not limitation) with respect to the downlink control signaling. The downlink control signaling may be DCI (Downlink control information ) carried over PDCCH (Physical Downlink Control Channel, physical downlink control channel) and/or control signaling carried over PDSCH (Physical Downlink Shared Channel ). For example, the DCI may be a UE-specific (UE specific) DCI, and the DCI may also be a common DCI, which may be a DCI common to some UEs, for example, a group common (group common) DCI, and the common DCI may also be a DCI common to all UEs. The DCI may be uplink DCI (e.g., DCI scheduling PUSCH) and/or downlink DCI (e.g., DCI scheduling PDSCH).

In some embodiments, the second control signaling may be control signaling sent by the second transceiver node to the first transceiver node. In the following examples, the second control signaling is illustrated by way of example (but not limitation) with respect to the uplink control signaling. The uplink control signaling may be UCI (Uplink Control Information ) carried over PUCCH (Physical Uplink Control Channel, physical uplink control channel) and/or control signaling carried over PUSCH (Physical Uplink Shared Channel ). The type of UCI may include one or more of the following: HARQ-ACK information, SR (Scheduling Request ), LRR (Link Recovery Request, link recovery request), CSI (Chanel State Information, channel state information), or CG (Configured grant) UCI. In embodiments of the present disclosure, UCI may be used interchangeably with PUCCH when UCI is carried by PUCCH.

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

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

In some embodiments, the first time unit is a time unit when the first transceiving node transmits the first data and/or the first control signaling. In the following example, the first time unit is described taking the following time unit as an example (but not limited to).

In some embodiments, the second time unit is a time unit when the second transceiving node transmits the second data and/or the second control signaling. In the following example, the second time cell is illustrated with the above row time cell as an example (but not limited to).

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

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

In describing the wireless communication system and in the present disclosure described below, the higher layer signaling or higher layer signals are signaling methods for transferring information from the base station to the terminal through a downlink data channel of the physical layer or transferring information from the terminal to the base station through an uplink data channel of the physical layer, and examples of the signaling methods may include signaling methods for transferring information through radio resource control (radio resource control, RRC) signaling, packet data convergence protocol (packet data convergence protocol, PDCP) signaling, or medium access control (medium access control, MAC) control elements (MAC control element, MAC CE).

Fig. 5 shows a flowchart of a method performed by a UE according to an embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

In some embodiments, the UE may report (or send) or indicate the UE capability to the base station at step S520. For example, the UE reports (or transmits) UE capabilities to the base station by transmitting PUSCH. In this case, the PUSCH transmitted by the UE includes UE capability information.

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

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

In some embodiments, the UE may be configured with two levels of priority for uplink transmissions. For example, the two-level priority may include a first priority and a second priority different from each other. In one example, the first priority may be higher than the second priority. In another example, the first priority may be lower than the second priority. However, embodiments of the present disclosure are not limited thereto, e.g., a UE may be configured with priorities of more than two levels. For convenience, in embodiments of the present disclosure, description is made taking into account that the first priority is higher than the second priority. It should be noted that all embodiments of the present disclosure are applicable to a case where the first priority may be higher than the second priority; all embodiments of the present disclosure apply to situations where the first priority may be lower than the second priority; all embodiments of the present disclosure apply to the case where the first priority may be equal to the second priority.

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

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

For example, if the UE is configured with a sub-slot length parameter, sub-slot n is the last uplink sub-slot overlapping with PDSCH reception or PDCCH reception (e.g., SPS PDSCH release, and/or indicating secondary cell dormancy, and/or trigger type-3 HARQ-ACK codebook reporting and no scheduled PDSCH reception), HARQ-ACK information for that PDSCH reception or PDCCH reception is transmitted in uplink sub-slot n+k, where K is determined by timing parameter K1 (for definition of timing parameter K1, reference may be made to the previous description). For another example, if the UE is not configured with a sub-slot length parameter, slot n is the last uplink slot overlapping with the downlink slot where the PDSCH or PDCCH is received, HARQ-ACK information for the PDSCH or PDCCH is transmitted in uplink slot n+k, where K is determined by timing parameter K1.

In embodiments of the present disclosure, unicast may refer to a manner in which a network and one UE communicate, and multicast (multicast) may refer to a manner in which a network and multiple UEs communicate. For example, the unicast PDSCH may be a PDSCH received by one UE, and scrambling of the PDSCH may be based on a UE-specific radio network temporary identifier (RNTI, radio Network Temporary Identifier), such as a cell-RNTI (C-RNTI). The multicast PDSCH may be PDSCH that more than one UE receives at the same time, and scrambling of the multicast PDSCH may be based on RNTI common to the UE group. For example, the common RNTI for the scrambled UE group of the multicast PDSCH may include an RNTI (in the embodiments of the present disclosure, referred to as G-RNTI) for the scrambling of the dynamically scheduled multicast transmission (e.g., PDSCH) or an RNTI (in the embodiments of the present disclosure, referred to as G-CS-RNTI) for the scrambling of the multicast SPS transmission (e.g., SPS PDSCH). The G-CS-RNTI and the G-RNTI may be different RNTIs or the same RNTI. UCI of the unicast PDSCH may include HARQ-ACK information, SR, or CSI of the unicast PDSCH. UCI of the multicast PDSCH may include HARQ-ACK information of the multicast PDSCH. In embodiments of the present disclosure, "multicast" may also be replaced with "broadcast".

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

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

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

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

A semi-static HARQ-ACK codebook (e.g., 3gpp TS 38.213 type-1 HARQ-ACK codebook) may determine the size of the HARQ-ACK codebook and the ordering of HARQ-ACK bits according to semi-statically configured parameters (e.g., parameters of higher layer signaling configuration). For a certain serving cell c, a downlink with part (BWP), an uplink with BWP, the UE determines M for candidate PDSCH reception (candidate PDSCH reception) _A,c Set of individual occasions (occasin), UE uplink slot n _U Corresponding HARQ-ACK information received by the candidate PDSCH is transmitted on one PUCCH in (a).

M _A,c May be determined by at least one of the following:

a) The HARQ-ACK slot timing value K1 of the activated uplink BWP;

b) A downlink Time Domain Resource Allocation (TDRA) table;

c) Configuring an uplink and downlink subcarrier spacing (SCS);

d) Semi-static uplink and downlink frame structure configuration;

e) Downlink slot offset parameters for serving cell c (e.g., 3GPP parameters

) And its corresponding SCS parameters (e.g., 3GPP parameters μ _offset,DL,c ) The slot offset parameter of the primary serving cell (e.g., 3GPP parameters +.>

) And its corresponding SCS parameters (e.g., 3GPP parameters μ _offset,UL )。

The parameter K1 is used to determine a candidate uplink timeslot, and then determine a candidate downlink timeslot according to the candidate uplink timeslot. The candidate downlink slot satisfies at least one of the following conditions: (i) If the time unit of the PUCCH is a sub-time slot, at least one candidate PDSCH receiving end position in the candidate downlink time slot overlaps with the candidate uplink time slot in the time domain; or (ii) if the time unit of the PUCCH is a slot, the end position of the candidate downlink slot overlaps with the candidate uplink slot in the time domain. It should be noted that, in the embodiments of the present disclosure, the start symbol and the start position may be used interchangeably, and the end symbol and the end position may be used interchangeably. In some implementations, the start symbol may be replaced with an end symbol, and/or the end symbol may be replaced with a start symbol.

The number of PDSCHs in a candidate downlink slot that need feedback HARQ-ACKs may be determined by the maximum of the number of valid PDSCHs in the downlink slot that do not overlap (e.g., valid PDSCH may be PDSCH that do not overlap with semi-statically configured uplink symbols). The time domain resources occupied by PDSCH may be determined by (i) configuring a time domain resource allocation table (in embodiments of the present disclosure, also referred to as a table associated with time domain resource allocation) by higher layer signaling and (ii) dynamically indicating a certain row in the time domain resource allocation table by DCI. Each row in the time domain resource allocation table may define information related to time domain resource allocation. For example, for a time domain resource allocation table, the indexed rows define timing values (e.g., time unit (e.g., slot) offset (e.g., K0)) of PDCCH and PDSCH, start and Length Indicators (SLIVs), or directly define start symbols and allocation lengths. For example, for the first row of the time domain resource allocation table, the starting OFDM symbol is 0 and the 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; 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 scheduling the PDSCH may indicate any one row in the time domain resource allocation table. When the OFDM symbols in the downlink slot are all downlink symbols, the maximum value of the number of valid PDSCH without overlap in the downlink slot is 2. At this time, the type-1 HARQ-ACK codebook may require feedback of HARQ-ACK information for 2 PDSCH in the downlink slot of the serving cell.

Fig. 7A and 7B illustrate examples of time domain resource allocation tables. Specifically, fig. 7A shows a time domain resource allocation table scheduling one PDSCH in one row, and fig. 7B shows a time domain resource allocation table scheduling a plurality of PDSCH in one row. Referring to fig. 7A, each row corresponds to a timing parameter K0 value, a value of S indicating a start symbol, a value of L indicating a length, wherein the value of S and the value of L may determine a SLIV. Referring to fig. 7B, each row corresponds to a plurality of sets of values of { K0, S, L }, unlike fig. 7A.

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

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

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

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

In the following examples, the first DAI is a C-DAI and the second DAI is a T-DAI is illustrated, but not limited to.

Tables 1 and 2 show the DAI field and V _T-DAI,m Or V _C-DAI,c,m Corresponding relation of (3). The number of bits for C-DAI and T-DAI is limited.

For example, in the case where the C-DAI or the T-DAI is represented by 2 bits, the value of the C-DAI or the T-DAI in DCI can be determined by the formula in Table 1. V (V) _T-DAI,m V for the value of T-DAI in DCI received at PDCCH listening occasion (Monitoring Occasion, MO) m _C-DAI,c,m Is the value of C-DAI in the DCI received on serving cell C at PDCCH listening occasion m. V (V) _T-DAI,m And V _C-DAI,c,m Are related to the number of bits of the DAI field in the DCI. MSB is the most significant bit (Most Significant Bit), LSB is the least significant bit (Least Significant Bit).

TABLE 1

For example, if C-DAI or T-DAI is 1, 5 or 9, as shown in Table 1, each is indicated by "00" in the DAI field, and V is determined by the formula in Table 1 _T-DAI,m Or V _C-DAI,c,m The value of (2) is denoted as "1". Y may represent a value of DAI (a value of DAI before conversion by a formula in the table) corresponding to the number of DCI actually transmitted by the base station.

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

TABLE 2

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

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

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

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

In the method of the present disclosure, one DCCH and/or DCI format schedules multiple PDSCH/PUSCH, which may be multiple PDSCH/PUSCH of the same serving cell and/or multiple PDSCH/PUSCH of different serving cells.

It should be noted that the various ways described in this disclosure may be combined in any order. In one combination, an approach may be performed one or more times.

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

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

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

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

It should be noted that, in the method of the present disclosure, if the number of terms is not limited, the method of the present disclosure may be applied to one and/or more of the terms. "a" or "an" may be replaced with "a plurality" or "more than one" or "a plurality" or "more than one" may be replaced with "one".

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

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

It should be noted that the time slots in the embodiments of the present disclosure may be replaced by other time units.

It should be noted that, in the embodiments of the present disclosure, "predefined conditions are satisfied, predefined methods (or steps) are performed" and "predefined conditions are not satisfied, predefined methods (or steps) are not performed" may be used instead. "predefined conditions are satisfied, predefined methods (or steps) are not performed" and "predefined conditions are not satisfied, predefined methods (or steps) are performed" may be used instead.

It should be noted that, in the embodiments of the present disclosure, parameters, information, or configurations may be preconfigured or predefined or configured by a base station. Thus, in some cases, a parameter, information, or configuration may be referred to as a predefined parameter, predefined information, or predefined configuration, respectively. In embodiments of the present disclosure, the meaning of pre-configuring certain information or parameters in the UE may be interpreted as default information or parameters embedded in the UE at the time of manufacturing the UE, or information or parameters pre-acquired and stored in the UE by higher layer signaling (e.g., RRC) configuration, or information or parameters acquired and stored from the base station.

It should be noted that, in the embodiments of the present disclosure, the 'solution overlapping channel' or the 'solution overlapping channel' may be understood as a solution to a collision of overlapping channels, and/or a solution to a collision of a set of overlapping channels. For example, when one PUCCH overlaps with one PUSCH, resolving the overlap or collision may include multiplexing UCI in the PUCCH to PUSCH, or may include transmitting a higher priority PUCCH or PUSCH. For another example, when one PUCCH overlaps with one or another PUCCH, resolving the overlap or collision may include multiplexing UCI into one PUCCH, or may include transmitting a higher priority PUCCH. For another example, when two PUSCHs of the same serving cell overlap, resolving the overlap or collision may include transmitting a PUSCH having a higher priority among the two PUSCHs.

It should be noted that, in the embodiments of the present disclosure, a "set of overlapping channels" may be understood as each channel in the set of overlapping channels overlapping at least one channel in the set of channels other than the channel. The channel 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 the first PUCCH overlaps at least one of the second PUCCH and the third PUCCH, the second PUCCH overlaps at least one of the first PUCCH and the third PUCCH, and the third PUCCH overlaps 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 both the second PUCCH and the third PUCCH, and the second PUCCH and the third PUCCH do not overlap.

It should be noted that, the collision between PUSCH and other uplink physical channels and/or downlink physical channels may be at least one of the following:

the PUSCH overlaps with other PUSCH and/or PUCCH and/or PDSCH and/or PDCCH of the same serving cell in the time domain.

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

The first PUCCH overlaps with the second PUCCH in the time domain.

The PUCCH overlaps with the PDSCH of the same serving cell in the time domain.

It should be noted that, the collision between PDSCH and other uplink physical channels and/or downlink physical channels may be at least one of the following:

the PDSCH overlaps with other PUSCH and/or PUCCH and/or PDSCH and/or PDCCH of the same serving cell in the time domain.

The PDSCH overlaps with the PUCCH in the time domain.

In some cases, the UE does not expect more than N (e.g., N is an integer greater than 0, such as n=1) PUSCHs to be scheduled in one time unit (e.g., slot). For example, for a single TRP, for SCS of 480/960kHz, the UE does not expect more than N (e.g., N is an integer greater than 0, such as n=1) PUSCHs to be scheduled in one time unit (e.g., slot). The PUSCH to be transmitted may be determined in at least one of the following manners MN1 to MN 7. For example, for a single TRP, for 480/960kHz SCS, the PUSCH to be transmitted may be determined in at least one of the following ways MN1 to MN 7. For another example, if the UE reporting capability indicates that at most N PUSCHs are scheduled in one slot of one serving cell, at least one of the following ways may be employed to determine the PUSCH to be transmitted.

Mode MN1

In the mode MN1, the UE does not expect to be configured with more than N CG PUSCHs in one time unit of one serving cell. Alternatively, the UE does not expect to be configured with more than N active CG PUSCHs in one time unit of one serving cell.

In some examples, for a single TRP, the UE does not expect to be configured with more than N CG PUSCHs in one time unit of one serving cell for SCS of 480/960 kHz.

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

Mode MN2

In the mode MN2, if more than N active CG PUSCHs are configured in one time unit of one serving cell, the UE transmits only up to N CG PUSCHs. For example, if more than N active CG PUSCHs are configured in one time unit of one serving cell, the UE transmits at most N higher priority CG PUSCHs. For another example, if at least one activated higher priority CG PUSCH is configured in one time unit of one serving cell, the UE transmits one higher priority CG PUSCH.

In some examples, for a single TRP, for SCS of 480/960kHz, the UE only transmits up to N CG PUSCHs if more than N active CG PUSCHs are configured in one time unit of one serving cell.

Mode MN3

In the mode MN3, the PUSCH to be transmitted may be determined according to one or more of the following steps.

Step one: it is determined to transmit up to N CG PUSCHs. For example, assuming that there is no DG PUSCH, it is determined to transmit up to N CG PUSCHs. As another example, methods according to other embodiments of the present disclosure determine to transmit up to N CG PUSCHs.

Step two: it is determined to transmit up to N DG PUSCHs and/or CG PUSCHs.

In some examples, for a single TRP, for an SCS of 480/960kHz, the PUSCH to be transmitted may be determined as per one or more of the above steps

The method can improve the flexibility of dynamic scheduling.

Mode MN4

In the mode MN4, a UE does not expect a PUSCH scheduled by DCI/PDCCH and a CG PUSCH to overlap in time domain within a time unit (e.g., slot) of a serving cell, through protocol specification and/or higher layer signaling configuration. Alternatively, the UE does not expect a PUSCH scheduled by DCI/PDCCH to overlap with a CG PUSCH in time domain for the same TRP (e.g., 3GPP parameters coresetpooolindex are the same) within one time unit (e.g., slot) of one serving cell.

In some examples, for a single TRP, for SCS at 480/960kHz, the UE may not expect a PUSCH scheduled by DCI/PDCCH to overlap in time domain with a CG PUSCH within a time unit (e.g., slot) of a serving cell, through protocol specification and/or higher layer signaling configuration.

Mode MN5

In mode MN5, if a DCI/PDCCH scheduled PUSCH meets a first predefined timing condition with a predefined CG PUSCH and/or all CG PUSCHs within a time unit (e.g., slot) of a serving cell, the UE transmits the DCI/PDCCH scheduled PUSCH and/or the UE does not transmit or cancel transmitting the predefined CG PUSCH and/or all CG PUSCHs. Alternatively, for the same TRP (e.g., the same 3GPP parameter coresetpoolndex) within one time unit (e.g., time slot) of one serving cell, if one DCI/PDCCH scheduled PUSCH meets a first predefined timing condition with a predefined CG PUSCH and/or all CG PUSCHs, the UE transmits the DCI/PDCCH scheduled PUSCH and/or the UE does not transmit or cancel the transmission of the predefined CG PUSCH and/or all CG PUSCHs. For example, the PUSCH scheduled by DCI may not overlap with the CG PUSCH in the time domain.

For example, the predefined CG PUSCH may be the CG PUSCH with the earliest starting time/symbol. For another example, the predefined CG PUSCH may also configure the CG PUSCH with the smallest (or largest) index for CG PUSCH.

For example, the first predefined timing condition may be that a time interval between an end (or start) position (or symbol) of the PDCCH (or CORESET where the DCI is located) and a start position (or symbol) of the CG PUSCH is greater than a predefined time.

In some examples, for a single TRP, for SCS of 480/960kHz, if one DCI/PDCCH scheduled PUSCH meets a first predefined timing condition with a predefined CG PUSCH and/or all CG PUSCHs within one time unit (e.g., slot) of one serving cell, the UE transmits the DCI/PDCCH scheduled PUSCH and/or the UE does not transmit or cancel transmitting the predefined CG PUSCH and/or all CG PUSCHs.

The method can improve the flexibility of dynamic scheduling.

Mode MN6

In mode MN6, if the first PUSCH and the second PUSCH satisfy a predefined condition within one time unit (e.g., slot) of one serving cell, the UE transmits the first PUSCH and/or the UE does not transmit or cancel transmitting the second PUSCH. Alternatively, for the same TRP (e.g., the same 3GPP parameter coresetpoolndex) within one time unit (e.g., time slot) of one serving cell, if a PUSCH meets a second predefined timing condition with a second PUSCH, the UE transmits the first PUSCH and/or the UE does not transmit or cancel the transmission of the second PUSCH. For example, the first PUSCH and the second PUSCH may not overlap in the time domain. For another example, the first PUSCH overlaps with the second PUSCH in the time domain.

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

-the first PUSCH has a higher priority than the second PUSCH;

-the first PUSCH has the same priority as the second PUSCH, the first PUSCH being DG PUSCH and the second PUSCH being CG PUSCH;

-scheduling the PDCCH of the first PUSCH and the second PUSCH to meet a second predefined timing condition.

In some examples, the second predefined timing condition may be that a time interval of an ending (or starting) position (or symbol) of the PDCCH (or CORESET in which the DCI is located) and a starting position (or symbol) of the second PUSCH is greater than a predefined time.

It should be noted that, since the number of PUSCHs transmitted in one time unit (e.g., slot) of one serving cell is limited, the UE does not transmit the second PUSCH or cancels transmission (e.g., partially cancels transmission) of the second PUSCH may be based on different UE capabilities. For example, when the UE reports UE capability-indicates that the number of PUSCHs transmitted in one time unit (e.g., slot) of one serving cell is N (e.g., N is equal to 1), when two PUSCHs of one serving cell overlap in the time domain, the UE transmits one of the PUSCHs (e.g., higher priority PUSCH) and the UE transmits the other PUSCH (e.g., lower priority PUSCH). For another example, when the UE reporting UE capability indicates that the number of PUSCHs transmitted in one time unit (e.g., slot) of one serving cell is N (e.g., N is equal to 1), when two PUSCHs of one serving cell overlap in the time domain, the UE transmits one of the PUSCHs (e.g., higher priority PUSCH), and the UE may cancel transmitting the other PUSCH (e.g., lower priority PUSCH).

In some examples, for a single TRP, for SCS of 480kHz or 960kHz, the UE transmits the first PUSCH and/or the UE does not transmit the second PUSCH within one slot of one serving cell if a predefined condition (e.g., a predefined condition in the manner MN 6) is met when the first PUSCH overlaps the second PUSCH in the time domain.

The method can improve the flexibility of dynamic scheduling.

Mode MN7

In the manner MN7, it is possible to configure, by protocol specification and/or higher layer signaling, that the number of PUSCHs that the UE expects to transmit (or can transmit) in one time unit of one serving cell is not more than N (e.g., N is an integer greater than zero, such as n=1), and/or that the number of PUSCHs that the UE does not expect to transmit (e.g., scheduled to transmit/expected to transmit/can transmit) is more than N.

For example, the PUSCH that the UE expects to transmit (or may transmit) may be determined by at least one of:

PUSCH without overlapping with symbols configured as downlink symbols and/or flexible symbols by higher layer signaling (e.g. 3GPP parameters tdd-UL-DL-configuration command and/or tdd-UL-DL-configuration de-tected);

-there is no PUSCH (e.g. CG PUSCH) with an overlap with the symbols indicated as downlink symbols and/or flexible symbols by dynamic signaling (e.g. dynamic SFI (slot format indicator, slot format indication), information carrying dynamic SFI by DCI format 2_0);

PUSCH (e.g., CG PUSCH) with no dynamic scheduling with the same serving cell (e.g., valid PDSCH, PDSCH without overlapping with higher layer signaling configured as uplink symbols) with overlap in time domain;

PUSCH without overlapping in time domain with PUSCH and/or PUCCH of higher priority with the same serving cell;

PUSCH without overlapping with symbols indicated by an uplink cancellation indication (CI, cancellation indication) (e.g. a CI carried by DCI format 2_4), e.g. CI may be used to inform the UE to cancel the physical resource block(s) (PRB) and symbol(s) of the corresponding UL transmission;

PUSCH without overlap in time domain with higher priority PUCCH.

For example, when the PUSCH satisfies at least one of the following conditions, it may be determined that the PUSCH is a PUSCH that the UE expects to transmit (or may transmit).

Condition COND1: there is no overlap with symbols configured as downlink symbols and/or flexible symbols by higher layer signaling (e.g., 3GPP parameters tdd-UL-DL-configuration Common and/or tdd-UL-DL-configuration Dedio). For example, when the condition COND1 is satisfied, a collision between PUSCH and a symbol indicated as a downlink symbol and/or a flexible symbol by higher layer signaling may be resolved.

Condition COND2: there is no overlap with the symbols indicated as downlink symbols and/or flexible symbols by dynamic signaling (e.g., dynamic SFI, carried by DCI format 2_0). For example, when the condition COND2 is satisfied, a collision between the PUSCH and the symbol indicated as a downlink symbol and/or a flexible symbol by dynamic signaling may be resolved.

Condition COND3: PDSCH not dynamically scheduled with the same serving cell (e.g., valid PDSCH, PDSCH not overlapping higher layer signaling configured as uplink symbols) overlaps in the time domain. For example, when the condition COND3 is satisfied, a collision between PUSCH and PDSCH may be resolved.

Condition COND4: there is no overlap in time domain with the PUSCH and/or PUCCH of higher priority with the same serving cell. For example, when the condition COND4 is satisfied, a collision between PUSCH and other higher priority PUSCH and/or PUCCH may be resolved.

Condition COND5: there is no overlap with the symbols indicated by the upstream CI (e.g., CI carried over DCI format 2_4). For example, when the condition COND5 is satisfied, a collision between the PUSCH and the symbol indicated by the uplink CI may be resolved.

For example, after resolving symbols indicated as downlink symbols and/or flexible symbols with higher layer signaling and/or dynamic signaling, and/or other PUSCH and/or PUCCH and/or PDSCH collisions, in one time unit of one serving cell, the number of PUSCHs that the UE expects to transmit (e.g., scheduled to transmit/expected to transmit/can transmit) is not more than N (e.g., n=1), and/or the number of PUSCHs that the UE does not expect to transmit (e.g., scheduled to transmit/expected to transmit/can transmit) is more than N.

It should be noted that the mode NM6 may be limited to the same TRP (e.g. 3GPP parameters coresetpoinlindex are the same).

In some examples, for a single TRP, for SCS of 480/960kHz, the number of PUSCHs that the UE expects to transmit (or can transmit) in one time unit of one serving cell may be specified by a protocol and/or higher layer signaling configuration is no more than N (e.g., N is an integer greater than zero, such as n=1), and/or the number of PUSCHs that the UE does not expect to transmit (e.g., scheduled/expected/can transmit) is greater than N.

The method can improve the flexibility of dynamic scheduling and reduce the time delay of the uplink user plane.

In some cases, the UE does not expect more than M (e.g., M is an integer greater than zero, such as m=1) PDSCH to be scheduled in one time unit (e.g., slot) of one serving cell. For example, for a SCS of 480/960kHz, for a single TRP scenario, the UE does not expect more than M (e.g., M is an integer greater than zero, such as m=1) PDSCH scheduled in one time unit (e.g., slot) of one serving cell. In these cases, PDSCH to be received may be determined in at least one of the following ways MN8 to MN 10. For example, for a single TRP, SCS 480/960kHz, the PDSCH to be received may be determined in at least one of the following ways MN 8-MN 10. For another example, if the UE reporting capability indicates that at most M PDSCH are received in one slot of one serving cell, PDSCH to be received may be determined in at least one of the following ways.

Mode MN8

In the MN8, a UE does not expect a DCI/PDCCH scheduled PDSCH to overlap with an SPS PDSCH in the time domain within a time unit (e.g., slot) of a serving cell, which may be specified by a protocol and/or higher layer signaling configuration. Alternatively, the UE does not expect a PDSCH scheduled by DCI/PDCCH to overlap with an SPS PDSCH in time domain for the same TRP (e.g., the same 3GPP parameter coresetpoolndex) in one time unit (e.g., slot) of one serving cell.

In some examples, for a single TRP, for SCS of 480/960kHz, a UE may not expect a DCI/PDCCH scheduled PDSCH to overlap in the time domain with an SPS PDSCH within one time unit (e.g., slot) of one serving cell, through protocol specification and/or higher layer signaling configuration.

Mode MN9

In mode MN9, if a DCI/PDCCH scheduled PDSCH meets a third predefined timing condition with a predefined SPS PDSCH and/or all SPS PDSCH within a time unit (e.g., slot) of a serving cell, the UE receives the DCI/PDCCH scheduled PDSCH and/or does not receive or expect to receive the predefined SPS PDSCH and/or all SPS PDSCH. Alternatively, for the same TRP (e.g., the same 3GPP parameter coresetpoolndex) within one time unit (e.g., time slot) of one serving cell, if one DCI/PDCCH scheduled PDSCH meets a third predefined timing condition with a predefined SPS PDSCH and/or all SPS PDSCH, the UE receives the DCI/PDCCH scheduled PDSCH and/or the UE does not receive or does not expect to receive the predefined SPS PDSCH and/or all SPS PDSCH. For example, the PDSCH scheduled by DCI and the SPS PDSCH may not overlap in the time domain.

For example, the predefined SPS PDSCH may be the earliest starting time/symbol SPS PDSCH. For another example, the predefined SPS PDSCH may also configure the SPS PDSCH with the smallest (or largest) index for the SPS PDSCH.

For example, the third predefined timing condition may be that the time interval of the ending (or starting) position (or symbol) of the PDCCH (or CORESET where the DCI is located) and the starting position (or symbol) of the SPS PDSCH is greater than a predefined time.

In some examples, for a single TRP, for 480/960kHz SCS, if a DCI/PDCCH scheduled PDSCH meets a third predefined timing condition with a predefined SPS PDSCH and/or all SPS PDSCH within a time unit (e.g., slot) of a serving cell, the UE receives the DCI/PDCCH scheduled PDSCH and/or the UE does not receive or does not expect to receive the predefined SPS PDSCH and/or all SPS PDSCH

The method can improve the flexibility of dynamic scheduling.

Mode MN10

In the MN10, the number of PDSCH that the UE expects to receive (or can receive) is not more than M (e.g., m=1) and/or the number of PDSCH that the UE does not expect to receive (or can not receive) is more than M in one time unit of one serving cell may be configured by protocol specification and/or higher layer signaling. For example, the PDSCH that the UE expects to receive (or may receive) may be determined for at least one of:

PDSCH without overlap with higher layer signaling (e.g., 3GPP parameters tdd-UL-DL-configuration command and/or tdd-UL-DL-configuration de-configured) configured as uplink symbols and/or flexible symbols;

PDSCH (e.g., SPS PDSCH) without overlap with symbols indicated as uplink symbols and/or flexible symbols by dynamic signaling (e.g., slot Format Indicator (SFI), carried by DCI format 2_0);

PDSCH (e.g., SPS PDSCH) that has no overlap in time domain with PUSCH dynamically scheduled by the same serving cell (e.g., a valid PUSCH, e.g., a PUSCH that has no overlap with higher layer signaling configured as uplink symbols);

PDSCH that has no overlap in time domain with PDSCH of higher priority to the same serving cell;

PDSCH without overlap in time domain with dynamically scheduled PUCCH (e.g., SPS PDSCH).

For example, when the PDSCH satisfies at least one of the following conditions, it may be determined that the PUSCH is a PUSCH that the UE expects to transmit (or may transmit).

Condition COND6: there is no overlap with higher layer signaling (e.g., 3GPP parameters tdd-UL-DL-configuration Common and/or tdd-UL-DL-configuration de-configured) configured as uplink symbols and/or flexible symbols. For example, when the condition COND6 is satisfied, a collision between the PDSCH and a symbol indicated as an uplink symbol and/or a flexible symbol by higher layer signaling may be resolved.

Condition COND7: there is no overlap with symbols indicated as uplink symbols and/or flexible symbols by dynamic signaling (e.g., SFI). When the condition COND7 is satisfied, a collision between the PDSCH and the symbols indicated as uplink symbols and/or flexible symbols by the dynamic signaling may be resolved.

Condition COND8: there is no overlap in the time domain with the PUSCH dynamically scheduled by the same serving cell (e.g., a valid PUSCH, e.g., a PUSCH that does not overlap with higher layer signaling configured as uplink symbols). For example, when the condition COND8 is satisfied, a collision between the PDSCH and the PUSCH may be resolved.

Condition COND9: there is no overlap in the time domain with PDSCH of higher priority than the same serving cell. For example, when the condition COND9 is satisfied, a collision between the PDSCH and another PDSCH may be resolved.

Condition COND10: there is no overlap in time domain with the dynamically scheduled PUCCH. For example, when the condition COND10 is satisfied, a collision between the PDSCH and the PUCCH may be resolved.

For example, after resolving symbols indicated as uplink symbols and/or flexible symbols with higher layer signaling and/or dynamic signaling, and/or other PDSCH and/or PUCCH and/or PUSCH collisions, the UE does not receive (e.g., is scheduled to receive/expects to receive/can receive) more than M (e.g., m=1) of PDSCH in one time unit of one serving cell, and/or does not expect to receive (or can not receive) more than M of PDSCH.

Note that NM9 may be limited to the same TRP (e.g., 3GPP parameters coresetpolindex are the same).

In some examples, for a single TRP, for an SCS of 480/960kHz, the SCS may be specified by a protocol and/or configured by higher layer signaling, the number of PDSCH that the UE expects to receive (or may receive) is no more than M (e.g., m=1) and/or the number of PDSCH that the UE does not expect to receive (or may not expect to receive) is more than M in one time unit of one serving cell

Mode MN11

In mode MN11, the MAC entity will

1> if the buffer status reporting procedure determines that at least one BSR (Buffer Status Report ) has been triggered and not cancelled:

2> if the regular BSR has been triggered and the logical channel SR delay timer (e.g., parameter l ogica l Channe l SR-De l ayTimer) is not running:

3> if there is no UL-SCH (Up l I nk Shared Channe l ) resource available for new transmission and no PUSCH carrying SP-CSI is activated (or no PUSCH resource carrying SP-CS I) (e.g., the PUSCH overlaps with PUCCH carrying SR in time domain);

4> trigger Scheduling Request (SR)

The method can avoid overlapping of the PUCCH bearing the SR and the PUSCH bearing the SP-CSI in the time domain, and can reduce the complexity of UE realization.

In some cases, the UE may transmit and/or receive multiple (e.g., for two) overlapping channels, and at least one of the MNs 12-13 may receive and/or transmit channels in the following manner.

Mode MN12

In the mode MN12, the UE first solves a plurality of PUSCHs overlapping on the same serving cell, and then solves the overlapping PUCCH and PUSCH. For example, the UE first solves a plurality of PUSCHs (e.g., a plurality of PUSCHs having the same priority) overlapped on the same serving cell, and then solves the overlapped PUCCH and PUSCH (e.g., PUCCH and PUSCH having the same priority).

The plurality of PUSCHs overlapping on the same serving cell may include at least one of:

one PUSCH carrying SP-CSI (semi-persistent CSI) (e.g., PUSCH carrying SP-CSI without PDCCH scheduling) overlaps with one PUSCH scheduled by DCI/PDCCH.

-one CG PUSCH overlaps one PUSCH scheduled by DCI/PDCCH.

One PUSCH carrying SP-CSI (semi-persistent CSI) (e.g., PUSCH carrying SP-CSI without PDCCH scheduling) overlaps with one CG PUSCH.

In some embodiments, if one PUSCH carrying SP-CSI (e.g., PUSCH carrying SP-CSI without PDCCH scheduling) overlaps both the first PUSCH and the second CG PUSCH scheduled by DCI/PDCCH, the UE does not transmit PUSCH carrying SP-CSI (or the UE does not transmit CSI report. E.g., PUSCH carrying SP-CSI is cancelled by CG PUSCH), the DCI/PDCCH scheduling the first PUSCH and PUSCH carrying SP-CSI do not need to satisfy timing conditions, which may improve scheduling flexibility and reduce scheduling delay.

In some embodiments, it may be specified by a protocol that the UE does not expect one PUSCH carrying SP-CSI (e.g., PUSCH carrying SP-CSI without PDCCH scheduling) to overlap with both the first PUSCH and the second CG PUSCH scheduled by DCI/PDCCH. This may reduce UE implementation complexity.

If the CG PUSCH and/or the PUSCH carrying the SP-CSI are canceled from being transmitted by the PUSCH scheduled by the DCI/PDCCH, the UE does not multiplex UCI in the PUCCH to the CG PUSCH and/or the PUSCH carrying the SP-CSI, so that the transmission probability of the UCI can be increased, and the reliability of UCI transmission can be improved.

Mode MN13

In the mode MN13, the UE first solves a plurality of PUSCHs and/or PDSCH overlapping on the same serving cell, and then solves the overlapping PUCCH and PUSCH and/or PDSCH.

In some embodiments, if one PUSCH carrying SP-CSI (e.g., PUSCH carrying SP-CSI without PDCCH scheduling) overlaps with both PDSCH and CG PUSCH scheduled by DCI/PDCCH, UE does not transmit PUSCH carrying SP-CSI (or UE does not transmit CSI report. E.g., PUSCH carrying SP-CSI is cancelled by CG PUSCH), DCI/PDCCH scheduling PDSCH and PUSCH carrying SP-CSI do not need to satisfy timing conditions, which may improve scheduling flexibility and reduce scheduling delay.

In some embodiments, it may be specified by the protocol that the UE does not expect one PUSCH carrying SP-CSI (e.g., PUSCH carrying SP-CSI without PDCCH scheduling) to overlap with both PDSCH and CG PUSCH scheduled by DCI/PDCCH. This may reduce UE implementation complexity.

If CG PUSCH and/or PUSCH carrying SP-CSI are/is canceled from being transmitted by PDSCH scheduled by DCI/PDCCH, UE does not multiplex UCI in PUCCH to CG PUSCH and/or PUSCH carrying SP-CSI, so that the transmission probability of UCI can be increased, and the reliability of UCI transmission is improved.

Mode MN14

In mode MN14, the UE first resolves lower priority overlapping PUCCH and/or PUSCH transmissions, then if one lower priority PUCCH or PUSCH transmission overlaps with a semi-statically configured higher priority PUCCH or PUSCH transmission (e.g., no PDCCH/DCI scheduled PUCCH or PUSCH transmission), the UE does not send the lower priority PUCCH or PUSCH transmission, at which time the PDCCH reception scheduling the higher priority PUCCH or PUSCH transmission does not need to satisfy the timing condition if the higher priority PUCCH or PUSCH transmission scheduled by one PDCCH/DCI overlaps with the lower priority PUCCH or PUSCH transmission in the time domain.

It should be noted that, in the embodiments of the present disclosure, the PUCCH or PUSCH without PDCCH/DCI scheduling may be CG PUSCH and/or PUSCH carrying SP-CSI.

The manner MN14 may be used in a scenario where the UE determines overlapping PUCCHs and/or PUSCHs of different priorities when the UE is not configured to indicate different priority multiplexing parameters (e.g., parameters uci-muxwith diffprio).

The method can increase the flexibility of scheduling and reduce the scheduling time delay.

Mode MN15

In mode MN15, the UE first addresses overlapping PUCCH and/or PUSCH transmissions of lower priority, then the UE addresses overlapping PUSCH of the same serving cell (if present, e.g., does not send lower priority PUSCH transmissions), and the UE then addresses overlapping PUCCH transmissions of different priorities with PUSCH transmissions. For example, the UE cancels lower priority PUCCH transmissions starting from the first overlapping symbol. At this time, the UE expects the higher priority PUSCH not earlier than T after its scheduled PDCCH reception _proc,2 Time, T _proc,2 Is a predefined time.

The manner MN15 may be used in a scenario where the UE determines overlapping PUCCHs and/or PUSCHs of different priorities when the UE is not configured to indicate different priority multiplexing parameters (e.g., parameter uci-muxwith diffprio).

Mode MN16

In the mode MN16, if one PUCCH carrying SR overlaps with PUSCH carrying SP-CSI in the time domain (for example, PUCCH has the same priority as PUSCH), the UE transmits the PUCCH carrying SR, and the UE does not transmit the PUSCH carrying SP-CSI. Therefore, the probability of SR transmission can be increased, and the uplink transmission time domain can be reduced. Or, the UE does not transmit PUCCH carrying SR, and the UE transmits PUSCH carrying SP-CSI. Therefore, the probability of SP-CSI transmission can be increased, and the reliability of uplink transmission is improved.

In some embodiments, it may be specified by the protocol that the UE does not expect that one PUCCH carrying SR overlaps with the PUSCH carrying SP-CSI in the time domain (e.g., the PUCCH carrying SR is the same priority as the PUSCH carrying SP-CSI), which may reduce UE implementation complexity.

In some embodiments, if one PUCCH overlaps PUSCH carrying SP-CSI in the time domain (e.g., PUCCH is the same priority as PUSCH), the UE transmits PUCCH and the UE does not transmit PUSCH carrying SP-CSI. This may increase the probability of UCI transmission in PUCCH.

In some embodiments, if one PUSCH carrying SP-CSI overlaps one PUCCH carrying SR and one PUCCH carrying HARQ-ACK and/or CSI in the time domain (e.g., PUCCH is the same priority as PUSCH), the UE does not transmit PUSCH carrying SP-CSI, and/or the UE transmits PUCCH carrying SR and/or PUCCH carrying HARQ-ACK and/or CSI. This may increase the probability of UCI transmission in PUCCH.

In some embodiments, it may be specified by a protocol that the UE does not expect that one PUSCH carrying SP-CSI overlaps one PUCCH carrying SR and one PUCCH carrying HARQ-ACK and/or CSI in the time domain (e.g., PUSCH overlaps both PUCCHs), which may reduce UE implementation complexity.

It should be noted that, in the embodiment of the present disclosure, 'determine to receive' may be replaced with 'receive', 'determine to transmit' may be replaced with 'transmit'.

It should be noted that, the method applied to CG PUSCH (or PUSCH without PDCCH/DCI scheduling) in the embodiments of the present disclosure is also applied to PUSCH carrying SP-CSI (semi-persistent CSI) (e.g., PUSCH carrying SP-CSI without PDCCH scheduling). For example, CG PUSCH in embodiments of the present disclosure may be replaced with PUSCH carrying SP-CSI (semi-persistent CSI) (e.g., PUSCH carrying SP-CSI without PDCCH scheduling).

Fig. 8 illustrates a flow chart of a method 800 performed by a terminal (e.g., UE) according to some embodiments of the present disclosure.

Referring to fig. 8, in operation S810, a Physical Uplink Shared Channel (PUSCH) is transmitted from one or more PUSCH and/or a Physical Downlink Shared Channel (PDSCH) is received. The one or more PUSCHs include dynamically scheduled PUSCHs and/or Configuration Grant (CG) PUSCHs, and the one or more PDSCH includes dynamically scheduled PDSCH and/or semi-persistent scheduling (SPS) PDSCH.

In some embodiments, when the maximum value of the number of PUSCHs that can be transmitted in the time unit of the serving cell is N, the PUSCH is transmitted from one or more physical uplink shared channels, PUSCHs, where N is a positive integer.

In some examples, PUSCH may be transmitted based on at least one of:

-the terminal does not expect to be configured with more than N CG PUSCHs in the time unit of the serving cell;

-in case more than N active CG PUSCHs are configured in a time unit of a serving cell, transmitting up to N CG PUSCHs;

-transmitting up to N CG PUSCHs;

-transmitting up to N dynamically scheduled PUSCHs and/or CG PUSCHs;

-in the time unit of the serving cell, the dynamically scheduled PUSCH and CG PUSCH are not expected by the terminal to overlap in the time domain;

-in a time unit of the serving cell, if the dynamically scheduled PUSCH and the predefined CG PUSCH and/or all CG PUSCHs meet a predefined timing condition, transmitting the dynamically scheduled PUSCH and/or not transmitting the predefined CG PUSCH and/or all CG PUSCHs; or (b)

In the time unit of the serving cell, the number of PUSCHs that the terminal expects to transmit is not more than N, and/or the number of PUSCHs that the terminal does not expect to transmit is more than N _。

In some sub-examples, the PUSCH that the terminal expects to transmit may be determined based on at least one of:

PUSCH without overlap with symbols indicated as downlink and/or flexible by higher layer signaling;

-PUSCH without overlap with symbols indicated as downlink and/or flexible by dynamic signaling;

-PUSCH without overlapping in time domain with PDSCH dynamically scheduled by the same serving cell;

-PUSCH without overlapping with a symbol indicated by the uplink cancellation indication; or (b)

PUSCH without overlap in time domain with higher priority PUCCH.

In some embodiments, when the maximum value of the number of PDSCH that can be received in the time unit of the serving cell is M, the PDSCH is received from the one or more PDSCH, where M is a positive integer.

In some examples, the PDSCH may be received based on at least one of:

-in the time unit of the serving cell, the PDSCH that the terminal does not expect dynamic scheduling does not overlap with the SPS PDSCH in the time domain;

-within a time unit of the serving cell, if the dynamically scheduled PDSCH meets a predefined timing condition with the predefined SPS PDSCH and/or all SPS PDSCH, receiving the dynamically scheduled PDSCH and/or not receiving or not expecting to receive the predefined SPS PDSCH and/or all SPS PDSCH;

The number of PDSCH that the terminal expects to receive is not more than M, and/or the number of PDSCH that the UE does not expect to receive is more than M.

In some sub-examples, the PDSCH that the terminal expects to transmit may be determined based on at least one of:

PDSCH without overlap with symbols indicated as uplink and/or flexible by higher layer signaling;

-PDSCH without overlap with symbols indicated as uplink and/or flexible by dynamic signaling;

-PDSCH with no overlap in time domain with PUSCH dynamically scheduled by the same serving cell;

PDSCH that has no overlap in time domain with PDSCH of higher priority to the same serving cell; or (b)

PDSCH without overlap in time domain with dynamically scheduled PUCCH.

In some embodiments, the UE may schedule more than one PDSCH (e.g., more than one PDSCH on one serving cell) by one DCI format, and the UE may be configured for HARQ-ACK bundling in the time domain (time domain bundling). For a semi-static HARQ-ACK codebook, the UE may determine its HARQ-ACK position in the HARQ-ACK codebook from the last PDSCH of multiple PDSCHs scheduled by one DCI format.

In some embodiments, the UE is configured with a semi-static HARQ-ACK codebook, the UE is configured with multiple PDSCH that may receive one DCI schedule at one serving cell (e.g., a row in the TDRA table contains multiple SLIVs). If the UE is configured with PDSCH Bundling (e.g., the UE is configured with 3GPP parameters enabletimedomain harq-Bundling), the UE may convert the TDRA table into a TDRA table that contains only one SLIV (the number of SLIVs in a row is 1), with the SLIV of each row in the converted TDRA table corresponding to the last SLIV of the row in the original TDRA table.

For example, let R' be the set of PDSCH time domain resource allocation TDRA tables. Let R be the set of the last SLIV of each row in set R'.

For serving cell c, if the UE is not configured with PDSCH repeated transmission parameters (e.g., 3GPP parameters PDSCH-aggregation factor and/or PDSCH-aggregation factor-R16, where PDSCH-aggregation factor is configured in parameter PDSCH-Config and PDSCH-aggregation factor-R16 is configured in parameter SPS-Config), the UE may determine whether the SLIV corresponding to row R in set R is a valid SLIV according to the corresponding row R in set R'. For example, if at least one symbol in each SLIV corresponding to a corresponding row R in set R' is configured (e.g., by higher layer signaling (e.g., 3GPP parameters tdd-UL-DL-configuration Common, and/or tdd-UL-DL-configuration de-directed)) as an uplink, the corresponding row in set R is deleted (at this point, the SLIV for which the action is invalid).

For serving cell c, if the UE is configured with PDSCH repeated transmission parameters (e.g., 3GPP parameters PDSCH-aggregation factor and/or PDSCH-aggregation factor-16, where PDSCH-aggregation factor is configured in parameter PDSCH-Config and PDSCH-aggregation factor-16 is configured in parameter SPS-Config), the UE may determine whether the SLIV corresponding to row R in set R is a valid SLIV according to corresponding rows R in set R' and set R. For example, if at least one of each SLIV corresponding to the corresponding row R in the set R' is configured as an uplink symbol by higher layer signaling (e.g., 3GPP parameters tdd-UL-DL-configuration Common, and/or tdd-UL-DL-configuration Dedic) and from a slot

To time slot n _0,k +n _D At least one symbol of the time domain resource of the PDSCH corresponding to row r is configured (e.g., by higher layer signaling (e.g., 3GPP parameters tdd-UL-DL-configuration command, and/or tdd-UL-DL-configuration de-directed)) for uplink, where K _1,k For set K ₁ Time slot n, time slot n _0,k Is the uplink time slot n _U -K _1,k Overlapping (or, upstream time slot n _U -K _1,k The lowest indexed downlink slot in the downlink slots in (a) is the corresponding row in set R is deleted (at this time, the row is the ineffective SLIV).

In one example, for a certain serving cell c, one downlink active BWP, one uplink active BWP, the UE determines M for candidate PDSCH reception _A,c A set of opportunities, wherein the UE is in uplink slot n _U Corresponding HARQ-ACK information received by the candidate PDSCH is transmitted on one PUCCH in (a). For a set K of slot timing values ₁ The UE may delete the row in the TDRA set corresponding to the invalid SLIV according to at least one of the pseudocode-1.

Pseudo code-1

/>

/>

Pseudo code-2

/>

It should be noted that the number of the substrates,

may be the maximum value of pdsch-Aggregation factor and pdsch-Aggregation factor-r 16. In the embodiment of the present disclosure, n _0,k And (3) with

Can be used interchangeably.

It should be noted that, in the embodiment of the present disclosure, "the UE is not configured with the PDSCH repeated transmission parameter" may be replaced with "the UE is not configured with the listening DCI format 1_2" and "the UE is configured with the PDSCH repeated transmission parameter" may be replaced with "the UE is configured with the listening DCI format 1_2".

The method can avoid that the PDSCH repeated transmission does not have corresponding bit positions in the HARQ-ACK codebook when the PDSCH repeated transmission and the PDSCH binding are configured at the same time, and can improve the reliability of the HARQ-ACK codebook.

In one example, for a certain serving cell c, one downlink active BWP and one uplink active BWP, the UE determines M for candidate PDSCH reception _A,c Opportunity set, UE (user Equipment) uplink time slot n _U Corresponding HARQ-ACK information received by the candidate PDSCH is transmitted on one PUCCH in (a). For a set of slot timing values _K1 The UE may determine M from the pseudocode-3 _A,c A set of individual opportunities.

Pseudo code-3

/>

/>

/>

/>

/>

/>

/>

It should be noted that the pseudocode-1 in the pseudocode-3 may be replaced with the pseudocode-2.

In some embodiments, method 800 may include transmitting PUSCH and/or receiving PDSCH based on one or more of manners MN 1-MN 16 described above.

In some implementations, the method 800 may include methods or operations in the various embodiments described above that may be performed by a terminal (e.g., UE).

Fig. 9 shows a block diagram of a first transceiving node 900 according to an embodiment of the present invention.

Referring to fig. 9, a first transceiving node 900 may include a transceiver 901 and a controller 902.

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

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

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

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

Fig. 10 shows a flow chart of a method 1000 performed by a base station according to one embodiment of the invention.

Referring to fig. 10, in step S1010, a base station transmits downlink data and/or downlink control information.

In step S1020, the base station receives second data and/or second control line information from the UE in time units.

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

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

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

The various illustrative logical blocks, modules, and circuits described herein may be implemented or performed with a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

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

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

The foregoing is merely exemplary embodiments of the present invention and is not intended to limit the scope of the invention, which is defined by the appended claims.

Claims

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

the PUSCH is transmitted from one or more physical uplink shared channels PUSCH and/or the PDSCH is received from one or more physical downlink shared channels PDSCH,

wherein the one or more PUSCHs include dynamically scheduled PUSCHs and/or configuration grant CG PUSCHs, the one or more PDSCH including dynamically scheduled PDSCH and/or semi-persistent scheduling SPS PDSCH.

2. The method of claim 1, wherein PUSCH is transmitted from one or more physical uplink shared channels, PUSCHs, when a maximum of a number of PUSCHs that can be transmitted in a time unit of a serving cell is N, where N is a positive integer.

3. The method of claim 2, wherein PUSCH is transmitted based on at least one of:

the terminal does not expect to be configured with more than N CG PUSCHs in the time cell of the serving cell;

in the case where more than N CG PUSCHs are configured in a time unit of a serving cell, transmitting up to N CG PUSCHs;

transmitting up to N CG PUSCHs;

transmitting at most N dynamically scheduled PUSCHs and/or CG PUSCHs;

in a time unit of a serving cell, a terminal does not expect that a dynamically scheduled PUSCH and a CG PUSCH are not overlapped in a time domain;

in a time unit of a serving cell, if a dynamically scheduled PUSCH meets a predefined timing condition with a predefined CG PUSCH and/or all CG PUSCHs, transmitting the dynamically scheduled PUSCH and/or not transmitting the predefined CG PUSCH and/or all CG PUSCHs; or (b)

In the time unit of the serving cell, the number of PUSCHs that the terminal expects to transmit is not more than N, and/or the number of PUSCHs that the terminal does not expect to transmit is more than N.

4. A method according to any one of claims 3, wherein the PUSCH that the terminal expects to transmit is determined based on at least one of:

PUSCH without overlap with symbols indicated as downlink and/or flexible by dynamic signaling;

PUSCH overlapping PDSCH dynamically scheduled by the same serving cell in time domain is not available;

PUSCH having no overlapping in time domain with PUSCH and/or PUCCH of higher priority with the same serving cell;

PUSCH without overlapping with the symbol indicated by the uplink cancellation indication; or (b)

There is no PUSCH overlapping in time domain with the higher priority PUCCH.

5. The method of any of claims 1-4, wherein PDSCH is received from one or more PDSCH when a maximum of a number of PDSCH that can be received in a time unit of a serving cell is M, where M is a positive integer.

6. The method of claim 5, wherein the PDSCH is received based on at least one of:

in a time unit of a serving cell, a PDSCH that the terminal does not expect dynamic scheduling does not overlap with an SPS PDSCH in the time domain;

in a time unit of a serving cell, if the dynamically scheduled PDSCH meets a predefined timing condition with the predefined SPS PDSCH and/or all SPS PDSCH, receiving the dynamically scheduled PDSCH and/or not receiving or not expecting to receive the predefined SPS PDSCH and/or all SPS PDSCH;

The number of PDSCH that the terminal expects to receive is not more than M and/or the number of PDSCH that the UE does not expect to receive is more than M.

7. The method of claim 6, wherein the PDSCH expected to be transmitted by the terminal is determined based on at least one of:

PDSCH that does not overlap symbols configured as uplink and/or flexible by higher layer signaling;

PDSCH that does not overlap symbols that are indicated as uplink and/or flexible by dynamic signaling;

PDSCH that has no overlap in time domain with PUSCH dynamically scheduled by the same serving cell;

PDSCH that is not overlapped with PDSCH of higher priority of the same serving cell in time domain; or (b)

There is no PDSCH overlapping in time domain with the dynamically scheduled PUCCH.

8. A terminal in a wireless communication system, comprising:

a transceiver configured to transmit and receive signals; and

a controller coupled to the transceiver and configured to perform the operations of the method of any one of claims 1-7.