CN115707132A

CN115707132A - User equipment in wireless communication system and method performed by the same

Info

Publication number: CN115707132A
Application number: CN202210474348.9A
Authority: CN
Inventors: 张飒; 王轶; 吴敏; 孙霏菲
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2021-08-03
Filing date: 2022-04-29
Publication date: 2023-02-17

Abstract

A User Equipment (UE) in a wireless communication system and a method performed by the same are provided. The method comprises the following steps: receiving a Downlink (DL) signal, the DL signal including a Physical Downlink Control Channel (PDCCH) and/or a Physical Downlink Shared Channel (PDSCH); and/or transmitting an Uplink (UL) signal including a Physical Uplink Control Channel (PUCCH) and/or a Physical Uplink Shared Channel (PUSCH), wherein the PDCCH is monitored when the UE is in an active time of a Discontinuous Reception (DRX) mode. The invention can reduce the power consumption of the UE.

Description

User equipment in wireless communication system and method performed by the same

Technical Field

The present disclosure relates generally to the field of wireless communications, and more particularly, to a user equipment for use 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. Accordingly, the 5G or quasi-5G communication system is also referred to as a "super 4G network" or a "post-LTE 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 antenna, analog beamforming, massive antenna technology are discussed in the 5G communication system.

Further, in the 5G communication system, development of improvement of a system network is ongoing based on advanced small cells, cloud Radio Access Network (RAN), ultra dense network, device-to-device (D2D) communication, wireless backhaul, mobile network, cooperative communication, coordinated multipoint (CoMP), reception side interference cancellation, and the like.

In 5G systems, hybrid FSK and QAM modulation (FQAM) and Sliding Window Superposition Coding (SWSC) have been developed as Advanced Coding Modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and Sparse Code Multiple Access (SCMA) as advanced access techniques.

Disclosure of Invention

In accordance with at least one embodiment of the present disclosure, a method performed by a User Equipment (UE) in a wireless communication system is provided. The method comprises the following steps: receiving a Downlink (DL) signal including a Physical Downlink Control Channel (PDCCH) and/or a Physical Downlink Shared Channel (PDSCH); and/or transmitting an Uplink (UL) signal including a Physical Uplink Control Channel (PUCCH) and/or a Physical Uplink Shared Channel (PUSCH), wherein the PDCCH is monitored when the UE is in an active time of a Discontinuous Reception (DRX) mode.

According to some embodiments of the present disclosure, there is also provided a User Equipment (UE) in a wireless communication system. The UE includes: a transceiver configured to transmit and receive signals; and a controller coupled with the transceiver and configured to: receiving a Downlink (DL) signal, the DL signal including a Physical Downlink Control Channel (PDCCH) and/or a Physical Downlink Shared Channel (PDSCH); and/or transmitting an Uplink (UL) signal including a Physical Uplink Control Channel (PUCCH) and/or a Physical Uplink Shared Channel (PUSCH), wherein the PDCCH is monitored when the UE is in an active time of a Discontinuous Reception (DRX) mode.

There is also provided, according to some embodiments of the present disclosure, a computer-readable storage medium having one or more computer programs stored thereon, wherein any of the above-described methods 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 to be expressly understood that the drawings described below are directed to only some embodiments of the disclosure and are not intended as a definition of the limits of the disclosure. In the drawings:

fig. 1 illustrates a schematic diagram of an example wireless network, in accordance with some embodiments of the present disclosure;

fig. 2A and 2B illustrate example wireless transmit and receive paths, in accordance with 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 in accordance with some embodiments of the present disclosure;

figure 4 illustrates a block diagram of a second type of transceiving node, in accordance with some embodiments of the present disclosure;

fig. 5 illustrates a flow diagram of a method performed by a UE in accordance with some disclosed embodiments;

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

figure 7 illustrates a schematic diagram of a DRX mechanism, according to some embodiments of the present disclosure;

fig. 8 illustrates a flow diagram of a method performed by a UE in accordance with some embodiments of the present disclosure;

figure 9 illustrates a block diagram of a first type of transceiving node, in accordance with some embodiments of the present disclosure; and

fig. 10 shows a flow chart of a method performed by a base station in accordance with some embodiments of the present disclosure.

Detailed Description

The following description with reference to the accompanying drawings is provided to facilitate a thorough understanding of various embodiments of the present disclosure as defined by the claims and equivalents thereof. This description includes various specific details to facilitate understanding but should be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Moreover, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

The terms and phrases used in the following specification and claims are not limited to their dictionary meanings but are used only by the inventor to enable a clear and consistent understanding of the present disclosure. Accordingly, it should be apparent to those skilled in the art that the following descriptions of the various embodiments of the present disclosure are provided for illustration only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

Herein, reference to any action or element based on any information, action, or element may include an implementation in which the action or element is based, at least in part, on any information, action, or element. For example, "determine B based on a (a can be any information, action, or element) (B can be any information, action, or element)" may mean "determine B based on at least a.

The terms "comprises" or "comprising" refer to the presence of the respective disclosed functions, operations, or components that may be used in various embodiments of the present disclosure, and do not limit the presence of one or more additional functions, operations, or features. Furthermore, the terms "comprises" or "comprising" may be interpreted as referring to certain features, integers, steps, operations, elements, components, or groups thereof, but should not be interpreted as excluding the possibility of one or more other features, integers, steps, operations, elements, components, or groups thereof.

The term "or" as used in various embodiments of the present disclosure includes any and all combinations of any of the listed terms. For example, "a or B" may include a, may include B, or may include both a and B.

It should be understood that the use of "first," "second," and similar terms in the present disclosure are not intended to indicate any order, quantity, or importance, but rather are used to distinguish one element from another.

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 may be used and only one item in the list may be required. For example, "at least one of A, B and C" includes any of the following combinations: A. b, C, A and B, A and C, B and C, and a and B and C. For example, "A, B or at least one of C" includes any of the following combinations: A. b, C, A and B, A and C, B and C, and a and B and C.

The term "couple" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms "transmit," "receive," and "communicate," as well as derivatives thereof, encompass both direct and indirect communication. The phrase "associated with," and derivatives thereof, means including, included within, connected to, interconnected with, contained within, connected to or connected with, coupled to or coupled with, communicable with, cooperative with, interleaved, juxtaposed, proximate, bound to or bound with, having,. Properties, having,. Relationships, or having relationships with. The term "controller" or "processor" means any device, system, or part thereof that controls at least one operation. Such a controller or processor 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.

As used herein, any reference to "one example" or "an example," "one embodiment" or "an implementation," "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 an example" in various places in the specification are not necessarily all referring to the same embodiment.

Unless otherwise defined, all terms (including technical or scientific terms) used in this disclosure have the same meaning as understood by one of ordinary skill in the art to which this disclosure belongs. General terms, as defined in dictionaries, are to be interpreted as having a meaning that is consistent with their context in the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

Furthermore, the various functions described below may be implemented or supported by one or more computer programs, each computer program formed from computer readable program code and embodied in a computer readable medium. The terms "application" and "program" refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in suitable computer-readable program code. The phrase "computer readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer readable medium" includes any type of medium capable of being accessed by a computer, such as Read-Only Memory (ROM), random Access Memory (RAM), a hard disk drive, a Compact Disc (CD), a Digital Video Disc (DVD), or any other type of Memory. A "non-transitory" computer-readable medium excludes wired, wireless, optical, or other communication links that 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 a rewritable optical disk or an erasable memory device.

The various embodiments discussed below are illustrative of the principles of the present disclosure in this patent document 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/or 5G, those skilled in the art will appreciate that the primary subject matter of the present disclosure is applicable to other communication systems with similar technical background and channel format, with slight modifications, without substantially departing from the scope of the present disclosure. For example, the technical solution of the embodiment of the present application can be applied to various communication systems. For example, the communication system may include a global system for mobile communications (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a General Packet Radio Service (GPRS), a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a universal microwave access (WiMAX) communication system, a fifth generation (5 g) or New Radio (NR) system, and the like. In addition, the technical scheme of the embodiment of the application can be applied to future-oriented communication technology.

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

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 figures 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 (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA) communication techniques. The descriptions of fig. 1-3B are not meant to imply physical or architectural implications for the manner in which different embodiments may be implemented. The different embodiments of the present disclosure may be implemented in any suitably arranged communication system.

Fig. 1 illustrates an example wireless network 100 in accordance with some embodiments of the present disclosure. The embodiment of the wireless network 100 shown in fig. 1 is for illustration only. Other embodiments of wireless network 100 can be used without departing from the scope of this disclosure.

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

Depending on the network type, other well-known terms can be used instead of "gnnodeb" or "gNB", such as "base station" or "access point". For convenience, the terms "gNodeB" and "gNB" are used in this patent document to refer to network infrastructure components that provide wireless access for remote terminals. 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 network type. 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 a gNB, whether the UE is a mobile device (such as a mobile phone or smartphone) or what is commonly considered a stationary device (such as a desktop computer or vending machine).

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

The dashed lines illustrate the approximate extent of

coverage areas

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

coverage areas

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

As described in more detail below, one or more of gNB 101, gNB 102, and gNB 103 include a 2D antenna array as described in embodiments of the present disclosure. In some embodiments, one or more of gNB 101, gNB 102, and gNB 103 support codebook design and structure 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, wireless network 100 can include any number of gnbs and any number of UEs in any suitable arrangement. Also, the gNB 101 can communicate directly with any number of UEs and provide those UEs with wireless broadband access to the network 130. Similarly, each of gnbs 102-103 can communicate directly with network 130 and provide UEs direct wireless broadband access to network 130. Further, 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 being implemented in a gNB (such as gNB 102), while receive path 250 can be described as being 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 design and structure 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 N-point Inverse 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. 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 decode 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 the 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 in order to generate N parallel symbol streams, where N is the number of IFFT/FFT points used in the gNB 102 and the UE 116. N-point IFFT block 215 performs IFFT operations 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. Add cyclic prefix block 225 inserts a cyclic prefix into the time domain signal. Upconverter 230 modulates (such as upconverts) the output of add cyclic prefix block 225 to an RF frequency for transmission over a wireless channel. The signal can also be filtered at baseband before conversion to RF frequency.

The RF signal transmitted from the gNB 102 reaches the UE 116 after passing through the radio channel, and the reverse operation to that at the gNB 102 is performed at the UE 116. Downconverter 255 downconverts 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 parallel time-domain signals. The N-point FFT block 270 performs an FFT algorithm to generate N parallel frequency domain signals. The parallel-to-serial block 275 converts the parallel frequency domain signals to a sequence of modulated data symbols. Channel decode and demodulation block 280 demodulates and decodes the modulated symbols to recover the original input data stream.

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

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

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

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 in accordance with some embodiments of the present 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 configurations. However, UEs have a wide variety of configurations, and fig. 3A does not limit the scope of the disclosure to any particular implementation of a UE.

The 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. The UE 116 also includes a speaker 330, a processor/controller 340, an input/output (I/O) interface 345, input device(s) 350, a display 355, and a memory 360. Memory 360 includes an Operating System (OS) 361 and one or more applications 362.

RF transceiver 310 receives incoming RF signals from antenna 305 that are transmitted by the gNB of wireless network 100. The RF transceiver 310 down-converts an incoming RF signal to generate an Intermediate Frequency (IF) or baseband signal. The IF or baseband signal is sent to the RX processing circuitry 325, where the RX processing circuitry 325 generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. RX processing circuit 325 sends the processed baseband signals to speaker 330 (such as for voice data) or to 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, e-mail, 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 the outgoing processed baseband or IF signals from TX processing circuitry 315 and upconverts the baseband or IF signals to RF signals, which are transmitted via antenna 305.

The processor/controller 340 can include one or more processors or other processing devices and executes the OS 361 stored in the memory 360 in order to control overall operation of the 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 circuitry 325, and TX processing circuitry 315 in accordance with well-known principles. In some embodiments, processor/controller 340 includes at least one microprocessor or microcontroller.

The processor/controller 340 is also capable of executing other processes and programs resident in the 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 a process. In some embodiments, processor/controller 340 is configured to execute applications 362 based on OS 361 or in response to signals received from the gNB or the operator. The processor/controller 340 is also coupled to an I/O interface 345, where the I/O interface 345 provides 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 input device(s) 350 and a display 355. The operator of the UE 116 can input data into the UE 116 using the 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). A memory 360 is coupled to the processor/controller 340. A portion of memory 360 can include Random Access Memory (RAM) while another portion of memory 360 can include flash memory or other Read Only Memory (ROM).

Although fig. 3A shows one example of the 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 fixed devices.

Fig. 3B illustrates an example gNB 102, according to some embodiments of the present disclosure. The embodiment of the gNB 102 shown in fig. 3B is for illustration only, and the other gnbs of fig. 1 can have the same or similar configurations. However, the gNB has a wide variety of configurations, and fig. 3B does not limit the scope of the present disclosure to any particular implementation of the gNB. Note that gNB 101 and gNB 103 can include the same or similar structure 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 some 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, 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 the antennas 370a-370 n. 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 circuitry 376, where the RX processing circuitry 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 the controller/processor 378 for further processing.

TX processing circuitry 374 receives analog or digital data (such as voice data, network data, e-mail, 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. RF transceivers 372a-372n receive outgoing processed baseband or IF signals from TX processing circuitry 374 and upconvert the baseband or IF signals into RF signals for transmission via antennas 370a-370 n.

Controller/processor 378 can include one or more processors or other processing devices that control the overall operation of gNB 102. For example, the controller/processor 378 may be capable of controlling the reception of forward channel signals and the transmission of reverse channel signals by the RF transceivers 372a-372n, the RX processing circuitry 376, and the TX processing circuitry 374 in accordance with well-known principles. The controller/processor 378 can also support additional functions, such as higher-level wireless communication functions. For example, the controller/processor 378 can perform a Blind Interference Sensing (BIS) process, such as by performing a BIS algorithm, and decode the received signal with the interference signal subtracted. Controller/processor 378 may support any of a wide variety of other functions in the 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 resident in memory 380, such as a base OS. The controller/processor 378 can also support channel quality measurement and reporting for systems with 2D antenna arrays as described in embodiments of the present disclosure. In some embodiments, controller/processor 378 supports communication between entities such as a web RTC. Controller/processor 378 can move data into and out of memory 380 as needed to perform a process.

Controller/processor 378 is also coupled to a backhaul or network interface 382. Backhaul or network interface 382 allows gNB 102 to communicate with other devices or systems over a backhaul connection or over a network. Backhaul or network interface 382 can support communication via any suitable wired or wireless connection(s). For example, when 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), backhaul or network interface 382 can allow gNB 102 to communicate with other gnbs over wired or wireless backhaul connections. When gNB 102 is implemented as an access point, backhaul or network interface 382 can allow gNB 102 to communicate with a larger network (such as the internet) via a wired or wireless local area network or via a wired or wireless connection. Backhaul or network interface 382 includes any suitable structure that supports communication over a wired or wireless connection, such as an ethernet or RF transceiver.

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 a BIS algorithm, 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 at least one interfering signal determined by a BIS algorithm.

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

Although fig. 3B shows one example of a 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 backhauls or network interfaces 382 and the controller/processor 378 can support routing functions to route data between different network addresses. As another particular example, although shown as including a single instance of TX processing circuitry 374 and a single instance of RX processing circuitry 376, gNB 102 can include multiple instances of each (such as one for each RF transceiver).

Exemplary embodiments of the present disclosure are further described below in conjunction with the appended drawings.

With the rapid development of the information industry, especially the growing demand from the mobile internet and internet of things (IoT), the future mobile communication technology is challenged with unprecedented challenges. For example, according to the International Telecommunications Union (ITU) report ITU-R M [ imt. Beyond 2020.Traffic ], it is expected that the mobile traffic will increase nearly 1000 times in 2020 compared to 2010 (era 4G), the number of UE connections will also exceed 170 billion, and the number of connected devices will be more striking as the vast number of IoT devices gradually infiltrates into the mobile communication network. To address this unprecedented challenge, the communications industry and academia have developed extensive fifth generation mobile communications technology (5G) research to target the 2020. Future 5G frameworks and overall goals are currently discussed in ITU's report ITU-RM [ imt.vision ], wherein 5G demand prospects, application scenarios and various important performance indicators are specified. For the new requirements in 5G, ITU's report ITU-R M [ imt. User TECHNOLOGY tree ] provides information related to the technical trend of 5G, aiming at solving significant problems of significant improvement of system throughput, consistency of user experience, scalability to support IoT, latency, energy efficiency, cost, network flexibility, support of emerging services, and flexible spectrum utilization. In 3GPP (3 rd Generation Partnership Project), the first phase of work for 5G has been ongoing. To support more flexible scheduling, the 3GPP decides to support variable Hybrid Automatic Repeat request-Acknowledgement (HARQ-ACK) feedback delay in 5G. In an existing Long Term Evolution (LTE) system, an uplink transmission Time of receiving HARQ-ACK from downlink data is fixed, for example, in a Frequency Division Duplex (FDD) system, a Time delay is 4 subframes, and in a Time Division Duplex (TDD) system, an HARQ-ACK feedback Time delay is determined for a corresponding downlink subframe according to uplink and downlink configuration. In a 5G system, whether FDD or TDD, the uplink time unit for which HARQ-ACK can be fed back is variable for a certain downlink time unit (e.g., downlink timeslot or downlink mini-timeslot). For example, the HARQ-ACK feedback delay may be dynamically indicated through physical layer signaling, or different HARQ-ACK delays may be determined according to different services or user capabilities and other factors.

The 3GPP defines three major directions of 5G application scenarios — eMBB (enhanced mobile broadband), mtc (massive machine-type communication), URLLC (ultra-reliable and low-latency communication). The eMBB scene aims to further improve the data transmission rate on the basis of the existing mobile broadband service scene so as to improve the user experience, and thus the extremely communication experience between people is pursued. mMTC and URLLC are application scenarios of the Internet of things, but the respective emphasis points are different: mMTC is mainly information interaction between people and objects, and URLLC mainly embodies the communication requirements between the objects and the objects.

In 5G, the UE may support flexible parameter set (numerology), larger bandwidth, more flexible scheduling, more terminal antennas so that the UE achieves increased complexity and power consumption. Some UEs (e.g., wearable devices) have higher requirements for energy saving, and how to reduce the power consumption of the UE is an urgent problem to be solved. For the UE supporting the URLLC service, how to reduce the power consumption of the UE on the premise of ensuring the reliability of the service is an urgent problem to be solved.

In order 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 the embodiments of the present disclosure, for convenience of description, a first type transceiving node and a second type transceiving node are defined. For example, the first type of transceiving node may be a base station and the second type of transceiving node may be a UE. In the following examples, the base station is taken as an example (but not limited to) to describe the first type of transceiving node, and the UE is taken as an example (but not limited to) to describe the second type of transceiving node.

The text and drawings are provided as examples only to assist the reader in understanding the disclosure. They are not intended, nor should they be construed, as limiting the scope of the disclosure in any way. While certain embodiments and examples have been provided, it will be apparent to those skilled in the art, based on the disclosure herein, that changes can be made in the embodiments and examples shown without departing from the scope of the disclosure.

Fig. 4 shows a block diagram of a second type of transceiving node according to embodiments of the present disclosure.

Referring to fig. 4, a second type of transceiving node 400 may comprise a transceiver 401 and a controller 402.

The transceiver 401 may be configured to receive first type data and/or first type control signaling from a first type transceiving node and to transmit second type data and/or second type control signaling to the first type transceiving 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 type of transceiving node, as well as to control the second type of transceiving node to implement the methods set forth in embodiments of the present disclosure. For example, the controller 402 may be configured to determine, based on the first type of data and/or the first type of control signaling, the second type of data and/or the second type of control signaling and a time unit for transmitting the second type of data and/or the second type of control signaling, and to control the transceiver 401 to transmit the second type of data and/or the second type of control signaling to the first type of transceiving node at the determined time unit.

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

In some embodiments, the first type of data may be data that is transmitted by the first type of transceiving node to the second type of transceiving node. In the following examples, the first type of data is exemplified by (but not limited to) Downlink data carried by a PDSCH (Physical Downlink Shared Channel).

In some embodiments, the second type of data may be data transmitted by the second type of transceiving node to the first type of transceiving node. In the following examples, the second type of data is exemplified by (but not limited to) Uplink data carried by a PUSCH (Physical Uplink Shared Channel).

In some embodiments, the first type of control signaling may be control signaling sent by the first type of transceiving node to the second type of transceiving node. In the following examples, the first type of control signaling is illustrated by taking downlink control signaling as an example (but not limited to). The Downlink Control signaling may be DCI (Downlink Control information) carried by a PDCCH (Physical Downlink Control Channel) and/or Control signaling carried by a PDSCH (Physical Downlink Shared Channel). For example, the DCI may be UE specific DCI, the DCI may also be common DCI, the common DCI may be DCI common to some UEs, for example, group common DCI, and the common DCI may also be DCI common to all UEs. The DCI may be an uplink DCI (e.g., a DCI scheduling a PUSCH) and/or a downlink DCI (e.g., a DCI scheduling a PDSCH).

In some embodiments, the second type of control signaling may be control signaling sent by the second type of transceiving node to the first type of transceiving node. In the following examples, the second type of control signaling is illustrated by taking uplink control signaling as an example (but not limited to). The Uplink Control signaling may be UCI (Uplink Control Information) carried through PUCCH (Physical Uplink Control Channel) and/or Control signaling carried through PUSCH (Physical Uplink Shared Channel). The type of UCI may include one or more of: HARQ-ACK Information, SR (Scheduling Request), LRR (Link Recovery Request), CSI (channel State Information), or CG (Configured grant) UCI.

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

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

In some embodiments, the first type time unit is a time unit in which the first type transceiving node transmits the first type data and/or the first type control signaling. In the following examples, the first class time units are illustrated by taking the following line time units as an example (but not limited to).

In some embodiments, the second type time unit is a time unit for the second type transceiving node to transmit the second type data and/or the second type control signaling. In the following examples, the second type of time cell is illustrated by taking the line time cell as an example (but not limited to).

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

Depending on the network type, 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 (TP), a 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. The base station may provide wireless access according to one or more wireless communication protocols, e.g., 5G3GPP 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.

Fig. 5 shows a flow diagram of a method 500 performed by a UE according to an embodiment of the invention.

Referring to fig. 5, the UE receives downlink data and/or downlink control signaling from the base station at step S510. For example, the UE may receive downlink data and/or downlink control signaling from the base station based on predefined rules and/or already received configuration parameters.

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

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

In step S510, the UE may determine a time unit and/or frequency domain resources for receiving downlink data (e.g., PDSCH) and/or downlink control signaling (e.g., PDCCH) according to the received downlink control signaling (e.g., higher layer signaling). For example, a parameter of DRX (Discontinuous Reception) may be configured via higher layer signaling, and the UE may determine whether to receive (e.g., monitor) a PDCCH according to the parameter of DRX.

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

In some embodiments, the downlink control signaling may include DCI carried over a PDCCH and/or control signaling carried over a PDSCH. For example, the DCI may be used to schedule transmission of a PUSCH or reception of a PDSCH. Some examples of uplink transmission timing will be described below with reference to 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 indicate a time interval between a DCI-scheduled PDSCH and a DCI-carrying PDCCH, and the unit of K0 may be a time slot. For example, fig. 6A gives an example of K0= 1. In the example shown in fig. 6A, the time interval from the DCI scheduled PDSCH to the PDCCH carrying the DCI is 1 slot.

In another example, the UE receives DCI and transmits PUSCH according to time domain resources indicated in the DCI. For example, a time interval between a PUSCH for DCI scheduling and a PDCCH carrying DCI may be represented using a parameter K2, and a 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.

In yet another example, the UE receives the PDSCH and may send HARQ-ACK information for the PDSCH on the PUCCH in the uplink time unit. For example, a time interval between a PUCCH for transmitting HARQ-ACK information of a PDSCH and the PDSCH may be represented using a parameter K1, and a unit of K1 may be an uplink time unit such as a slot or a sub-slot. When the unit of K1 is a slot, the time interval is a PUCCH for feeding back HARQ-ACK information of the PDSCH and a slot offset value of the PDSCH. For example, fig. 6A gives an example of K1= 3. In the example shown in fig. 6A, a PUCCH for transmitting HARQ-ACK information of a PDSCH is spaced 3 slots apart from the PDSCH.

In yet another example, the UE receives DCI (e.g., DCI indicating SPS (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 parameter K1, and a unit of K1 may be an uplink time unit such as a slot or a 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 HARQ-ACK information of DCI and the DCI is 3 slots. For example, a parameter K1 may be used to indicate a time interval between SPS PDSCH reception and PUCCH whose HARQ-ACK is fed back, where K1 is indicated in DCI activating the SPS PDSCH. In some embodiments, the UE may report (or send (signal/transmit)) the UE capability to the base station or indicate the UE capability at step S520. For example, the UE reports (or sends) the UE capability to the base station by sending a PUSCH. In this case, the PUSCH transmitted by the UE includes the UE capability information.

In some embodiments, the base station may configure the UE with higher layer signaling based on the UE capabilities previously received from the UE (e.g., in step S510 of a previous downlink-uplink transmission procedure). For example, the base station configures higher layer signaling for the UE by sending 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 compared to physical layer signaling, for example, the higher layer signaling may include RRC signaling and/or MAC CE, for example.

In some embodiments, the UE may be configured with two levels of priority for uplink transmissions. For example, the two levels of priority may include a first priority and a second priority that are 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., the UE may be configured with more than two levels of priority. For convenience, in the embodiments of the present disclosure, the description is made in consideration that the first priority is higher than the second priority. It should be noted that all embodiments of the present disclosure are applicable to the case that the first priority may be higher than the second priority; all embodiments of the present disclosure are applicable to situations where the first priority may be lower than the second priority; all embodiments of the disclosure are applicable to the case where the first priority may be equal to the second priority.

In the embodiments of the present disclosure, unicast may refer to a manner in which a network communicates with one UE, and multicast/broadcast may refer to a manner in which a network communicates with a plurality of UEs. For example, the unicast PDSCH may be one PDSCH received by one UE, and the scrambling of the PDSCH may be based on a Radio Network Temporary Identifier (RNTI) specific to the UE, such as a C-RNTI. The multicast/broadcast PDSCH may be one PDSCH received simultaneously by more than one UE, and the scrambling of the multicast/broadcast PDSCH may be based on an RNTI common to the group of UEs. For example, the RNTI common to the scrambled UE group for the multicast/broadcast PDSCH may include an RNTI (referred to as G-RNTI in embodiments of the disclosure) scrambled for a dynamically scheduled multicast/broadcast transmission (e.g., PDSCH) or an RNTI (referred to as GS-RNTI in embodiments of the disclosure) scrambled for a multicast/broadcast SPS transmission (e.g., SPS PDSCH). The GS-RNTI and the G-RNTI can be different RNTIs or the same RNTI. The UCI of the unicast PDSCH may include HARQ-ACK information, SR, or CSI of the unicast PDSCH. UCI of multicast (groupcast or multicast)/broadcast PDSCH may include HARQ-ACK information of multicast/broadcast PDSCH. In an embodiment of the present disclosure, "multicast/broadcast" may refer to at least one of multicast or broadcast.

In some embodiments, the HARQ-ACK codebook may include HARQ-ACK information for one or more PDSCHs and/or DCIs. If the HARQ-ACK information of one or more PDSCHs and/or DCIs is transmitted in the same uplink time unit, the UE may generate a HARQ-ACK codebook according to a predefined rule. For example, if one PDSCH is successfully decoded, the HARQ-ACK information of this PDSCH is a positive ACK. For example, a positive ACK may be represented 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 the HARQ-ACK codebook. For example, the UE may generate the HARQ-ACK codebook according to a pseudo-code specified by a protocol. In one example, if the UE receives a DCI format indicating SPS PDSCH release (deactivation), the UE transmits HARQ-ACK information 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 for the DCI format. In yet another example, if the UE receives a DCI format indicating HARQ-ACK information for transmitting all HARQ-ACK processes (e.g., one shot HARQ-ACK codebook, which is also, for example, type-3 HARQ-ACK codebook (Type-3 HARQ-ACK codebook) in 3GPP (e.g., TS 38.213)), the UE transmits HARQ-ACK information for all HARQ-ACK processes. In yet another example, if the UE receives a DCI format, wherein the DCI format schedules a PDSCH, the UE transmits HARQ-ACK information for the PDSCH. In yet another example, the UE receives the SPS PDSCH, and the UE transmits HARQ-ACK information for the SPS PDSCH. In yet another example, if the UE is configured by higher layer signaling to receive the SPS PDSCH, the UE transmits HARQ-ACK information for the SPS PDSCH. If the UE is configured by higher layer signaling to receive the SPS PDSCH, the SPS PDSCH may be cancelled 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 the semi-static frame structure configured by higher layer signaling overlaps with a symbol of the SPS PDSCH. In yet another example, the UE transmits HARQ-ACK information for the SPS PDSCH if the UE is configured to receive the SPS PDSCH by higher layer signaling according to a predefined rule.

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

In some embodiments, if the HARQ-ACK information transmitted for the same uplink time unit includes HARQ-ACK information for any DCI format, and/or dynamically scheduled PDSCH (e.g., PDSCH scheduled by one DCI format) and/or DCI HARQ-ACK information, the UE may generate HARQ-ACK information according to rules that produce a dynamically scheduled PDSCH and/or DCI HARQ-ACK codebook. 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 3GPP (e.g., TS 38.213)) or a dynamic HARQ-ACK Codebook (e.g., type-2 HARQ-ACK Codebook (Type-2 HARQ-ACK Codebook) in 3GPP (e.g., TS 38.213)) according to PDSCH HARQ-ACK Codebook configuration parameters (e.g., the parameter pdcsch-HARQ-ACK-Codebook in 3 GPP), the dynamic HARQ-ACK Codebook may also be a packet (grouping) and HARQ-ACK retransmission Codebook (Type-2 HARQ-ACK Codebook) in 3GPP (e.g., TS 38.213).

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). In the following embodiments, the allocation index is described as DAI as an example. However, embodiments of the present disclosure are not limited thereto, and any other suitable allocation index may be employed.

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

In some examples, the first type of DAI may be a C-DAI (Counter-DAI). The first type of DAI may indicate an accumulated count of at least one of DCI for a scheduled PDSCH, or DCI for SPS PDSCH release (deactivation), or DCI for secondary cell dormancy. For example, the cumulative count may be a cumulative count to the current serving cell and/or the current time unit. For example, C-DAI may refer to: the cumulative number of { serving cell, time unit } pairs scheduled by the PDCCH until the current time unit within the time window (which may also include the number of PDCCHs (e.g., PDCCH indicating SPS release, and/or PDCCH indicating secondary cell dormancy); or the cumulative number of PDCCHs until the current time unit; or the cumulative number of PDSCH transmissions until the current time unit; or the cumulative number of { serving cell, time unit } pairs for which there is PDSCH transmission related to the PDCCH (e.g., scheduled by the PDCCH) and/or for which there is a PDCCH (e.g., a PDCCH indicating SPS release, and/or a PDCCH indicating secondary cell dormancy) until the current serving cell and/or current time unit; or the cumulative number of PDSCHs and/or PDCCHs (e.g., PDCCHs indicating SPS release, and/or PDCCHs indicating secondary cell dormancy) for which the corresponding PDCCH exists, which have been scheduled by the base station, to the current serving cell and/or the current time unit; or the cumulative number of PDSCHs scheduled by the base station to the current serving cell and/or the current time unit (the PDSCH is the PDSCH with the corresponding PDCCH); or the cumulative number of time units with PDSCH transmission scheduled by the base station to the current serving cell and/or the current time unit (the PDSCH is the PDSCH with the corresponding PDCCH). The ordering of 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 a time including a first type of DAI and first type of DAI information. The first type of DAI may be included in a downlink DCI format.

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

In the following examples, the first type of DAI is C-DAI and the second type of DAI is T-DAI, but not limited thereto.

Tables 1 and 2 show the DAI field and V _T-DAI,m Or V _C-DAI,c，m The corresponding relationship of (2). The number of bits of the C-DAI and T-DAI is limited.

For example, in the case where the C-DAI or T-DAI is expressed with 2 bits, the value of the C-DAI or T-DAI in the DCI may be determined by the formula in Table 1. V _T-DAI,m Is the value of T-DAI in DCI received at PDCCH monitoring occasion (monitoring interference) m, V _C-DAI,c，m Is the value of C-DAI in the DCI for serving cell C received at PDCCH monitoring occasion m. V _T-DAI,m And V _C-DAI,c，m Is 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 expressed by the formula in Table 1 _T-DAI,m Or V _C-DAI,c，m The value of (d) is represented as "1". Y may represent a value of DAI (a value of DAI before conversion by a formula in a table) corresponding to the number of DCIs actually transmitted by the base station.

For example, in the case where 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 dictates otherwise, all or one or more of the methods, steps or operations described by the embodiments of the present disclosure may be configured and/or indicated by protocol provisions and/or higher layer signaling. The dynamic signaling may be PDCCH and/or DCI format. For example, for SPS PDSCH and/or CG PUSCH, the indication may be dynamically indicated in its activation 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, e.g., parameter X, is not configured), the UE performs another mode (e.g., mode B).

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

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

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

It should be noted that in the method of the present disclosure, the number of times that the repeated transmission is configured and/or indicated may be understood as the repeated transmission is greater than 1. For example, a PUCCH that is "configured and/or indicated for repeated transmission" may be replaced with a "PUCCH that is repeatedly transmitted on more than one slot/sub-slot. Not configured and/or indicating that the repeated transmission may be understood as a number of repeated transmissions equal to 1. For example, a PUCCH which is "not configured and/or indicates a repetitive transmission" may be replaced with a "PUCCH transmission whose number of repetitive transmissions is 1". For example, the UE may be configured with a parameter related to the number of PUCCH repetition transmissions

When the parameter is

Greater than 1, may mean that the UE is configured with PUCCH repetition transmission, and the UE may be in

Repeat PUCCH transmission over a time unit (e.g., slot); when the parameter is equal to 1, it may mean that the UE is not configured with PUCCH repetition transmission. For example, a repeatedly transmitted PUCCH may contain only one type of UCI. If the PUCCH is configured with repetition transmission, in the embodiments of the present disclosure, one of multiple repetition transmissions of the PUCCH may be regarded as one PUCCH (or PUCCH resource), or all of the repetition transmissions of the PUCCH may be regarded as one PUCCH (or PUCCH resource), or a specific one of the multiple repetition transmissions of the PUCCH may be regarded as one PUCCH (or PUCCH resource).

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

It should be noted that the various aspects described in this disclosure can be combined in any order. In one combination, a mode may be performed one or more times.

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

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

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

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

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

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

In some communication systems (e.g., NR), reduction of UE unnecessary PDCCH monitoring behavior by employing DRX techniques is supported to reduce UE energy consumption. The base station may configure DRX cycles for the UE, each DRX cycle consisting of an Active Time (Active Time) and an Inactive Time (Inactive Time), as shown in fig. 7. During active time (also referred to as active state) of the DRX mode, the UE monitors the DCI or the PDCCH carrying the DCI (e.g., predefined PDCCH such as PDCCH for data scheduling), and during inactive time (also referred to as inactive state) of the DRX mode, the UE does not monitor the DCI or the PDCCH carrying the DCI (e.g., predefined PDCCH such as PDCCH for data scheduling) to save UE power consumption. For example, the PDCCH may include at least one of: PDCCH scrambled with C-RNTI, PDCCH scrambled with CI-RNTI (Cancellation Indication RNTI), PDCCH scrambled with CS-RNTI (coordinated Scheduling RNTI), PDCCH scrambled with INT-RNTI (interrupt RNTI), PDCCH scrambled with SFI-RNTI (Slot Format Indication RNTI), PDCCH scrambled with SP-CSI-RNTI (Semi-Persistent CSI), PDCCH scrambled with TPC-PUCCH-RNTI (Transmit Power Control-PUCCH-RNTI), PDCCH scrambled with TPC-PUSCH-RNTII (Transmit Power Control-PUSCH-RNTI), PDCCH scrambled with TPC-SRS-RNTI (Transmit Power Control-PUSCH-TPC), PDCCH-SRS-RNTI (Transmit Power Control-downlink Reference RNTI), RNTI scrambled with a Transmit Power-Sounding Reference RNTI and AI.

When configured with a DRX cycle (DRX cycle), the active times of the serving cells in one DRX group (a DRX group may for example represent a group of serving cells with the same DRX active time) may include the following times (the time while):

-a DRX active duration timer (e.g. 3GPP parameter DRX-onDurationTimer) or a DRX inactivity timer (e.g. 3GPP parameter DRX-inactivity timer) configured for the DRX group is running; or

-a DRX downlink retransmission timer (e.g. 3GPP parameter DRX-retransmission timerdl) or a DRX uplink retransmission timer (e.g. 3GPP parameter DRX-retransmission timerll) of any serving cell in the DRX group is running; or

An initial access contention resolution timer (e.g., 3GPP parameter ra-ContentionResolutionTimer) or an msgB feedback window (e.g., 3GPP parameter msgB-ResponseWindow) is running; or

-scheduling request is sent on PUCCH and suspended (pending); or

-after successful reception of the random access response of the contention-based random access preamble selected by the non-MAC entity, the C-RNTI scrambling of the MAC entity indicates that the newly transmitted PDCCH has not been received.

In some embodiments, the active time or the inactive time of the UE may be determined based on a timer (alternatively referred to as a DRX related timer). That is, the timer may be used to control the active time or inactive time of the UE. For example, the timer may include one or more of an active duration (ON duration) timer (or referred to as a timer related to an active duration of the DRX mode) (e.g., a 3GPP parameter DRX-onDurationTimer), an inactive timer (e.g., a 3GPP parameter DRX-InactivityTimer), a Round-Trip Time (RTT) timer (or referred to as a timer related to a Round-Trip Time of the HARQ process), and a retransmission timer (or referred to as a timer related to a retransmission). In some embodiments, the UE may support other timers (e.g., predefined or preset timers, or any suitable timers now in existence) for DRX mode.

For example, an active duration timer may be used to determine a default duration for which the UE may be active (e.g., during an active duration (ON duration) of a DRX cycle). For example, the inactivity timer may be used to determine a duration to remain in the active time after receiving the PDCCH (or DCI). For example, the RTT timer may be used to determine a minimum duration before a DL allocation or UL retransmission grant of a retransmission may be received. For example, a retransmission timer may be used to determine a maximum duration before a grant of retransmission may be received.

In some examples, the RTT timer may include a DRX downlink hybrid automatic repeat request round trip time timer and/or a DRX uplink hybrid automatic repeat request round trip time timer. The retransmission timer may include a DRX downlink retransmission timer and/or a DRX uplink retransmission timer.

In some embodiments, one or more of the above-described timers (DRX-related timers) may be activated (e.g., started or restarted) or deactivated (e.g., stopped or expired). When a timer is activated, the timer is in run; when a timer is deactivated, the timer is not in operation (stopped or expired). For example, when at least one of an active duration timer, an inactive timer, a retransmission timer (a retransmission timer for UL or a retransmission timer for DL) or an initial access contention resolution timer is running, the UE may be in an active time and may listen to DCI or a PDCCH carrying DCI. For example, the type of PDCCH may refer to the previous description.

In the embodiments of the present disclosure, the use of DRX downlink hybrid automatic repeat request round trip time timer is exemplified (but not limited) by DRX-HARQ-RTT-TimerDL; the use of DRX uplink hybrid automatic repeat request round trip time timer is illustrated by taking DRX-HARQ-RTT-timerll as an example (but not limited to); the DRX downlink retransmission timer usage is exemplified by (but not limited to) DRX-retransmission timerdl; the use of the DRX uplink retransmission timer is illustrated by, but not limited to, DRX-retransmission timerll. For example, a DRX downlink hybrid automatic repeat request round trip time timer (e.g., DRX-HARQ-RTT-TimerDL) may represent a minimum duration before a DL allocation for which the MAC entity expects HARQ retransmissions. For example, the DRX uplink hybrid automatic repeat request round trip time timer may represent a minimum duration before the MAC entity expects a UL HARQ retransmission grant. For example, drx-retransmission timerdl may represent the maximum duration before receiving a grant for a DL retransmission. For example, drx-retransmission timerll may represent the maximum duration before a grant of UL retransmission is received.

When configured with DRX cycle, the MAC entity will:

1> if a MAC PDU (Packet Data Unit) is received in the configured downlink allocation:

2> starting drx-HARQ-RTT-TimerDL for the corresponding HARQ process at the first symbol (in the first symbol after the end of the corresponding transmission carrying DL HARQ feedback);

2> stop drx-retransmission timerdl for the corresponding HARQ process.

1> if drx-HARQ-RTT-TimerDL expires (expire):

2> if the data of the corresponding HARQ process is not successfully decoded:

3> starting drx-retransmission TimerDL for the corresponding HARQ process at the first symbol after drx-HARQ-RTT-TimerDL expires.

When configured with DRX cycle, the MAC entity will:

1> if DRX group is active time:

2> monitoring the PDCCH of the serving cell in the DRX group, for example, the PDCCH can be monitored according to a method specified by 3GPP TS 38.213;

2> if the PDCCH indicates DL transmission:

3> starting drx-HARQ-RTT-TimerDL for the corresponding HARQ process at the first symbol after the corresponding transmission for bearing DL HARQ feedback is finished;

3> stop drx-retransmission timerdl for the corresponding HARQ process.

For one HARQ process, if the corresponding transmission carrying the DL HARQ feedback is cancelled (e.g., the lower priority uplink transmission is cancelled by the higher priority uplink transmission; and for another example, the HARQ-ACK transmission for the SPS PDSCH is semi-statically configured as the downlink symbol cancellation), the UE may enter an inactive time (e.g., other DRX related timers may not satisfy the condition for entering an active time) since the UE has stopped DRX-retransmission timerdl for the corresponding HARQ process, at which point the UE may not receive the retransmission of the HARQ process scheduled by the base station and/or the retransmission of the DL HARQ feedback.

In some embodiments, for one HARQ process, if the corresponding transmission carrying the DL HARQ feedback is cancelled and/or delayed from being transmitted, it may be performed at a predetermined time in at least one of the following manners a _1 to a _3, by protocol specification and/or higher layer signaling configuration.

Mode a _1: a predetermined timer (referred to as a first predetermined timer for convenience of description) is started for the corresponding HARQ process. For example, if the predetermined timer is running, the UE is considered (e.g., determined) to be in active time. In some examples, whether the UE is in active time may be defined for one DRX group. For example, the UE being active time may refer to all of one or more serving cells in one DRX group being active time. In other examples, whether the UE is active time may be defined for one serving cell. For example, the UE being in the active time may refer to the serving cell corresponding to this HARQ process being in the active time.

Mode a _2: a drx-retransmission timerdl is started for the corresponding HARQ process.

Mode a _3: if the data of the corresponding HARQ process is not successfully decoded, a drx-retransmission TimerDL is started for the corresponding HARQ process.

For example, the predetermined time may be at least one of the following times as specified by a protocol and/or configured by higher layer signaling:

the first symbol after the end of the respective transmission carrying the DL HARQ feedback (for convenience of description, referred to as "first time" in the embodiments of the present disclosure);

-a starting point of a subframe or slot or sub-slot or symbol after the end of the corresponding transmission carrying the DL HARQ feedback (for convenience of description, referred to as "second time" in the embodiments of the present disclosure);

the first symbol after PDCCH reception ends (referred to as "third time" in the embodiments of the present disclosure for convenience of description);

-drx-HARQ-RTT-first symbol after timeout of TimerDL (referred to as "fourth time" in the embodiments of the present disclosure for convenience of description);

-drx-HARQ-RTT-first symbol after timer ul expiration (for convenience of description, referred to as "fifth time" in the embodiments of the present disclosure);

the first symbol after the end of the first or last repeated transmission in the respective transmissions carrying DL HARQ feedback (referred to as "sixth time" in the embodiments of the present disclosure for convenience of description);

the first symbol (for convenience of description, referred to as "seventh time" in the embodiments of the present disclosure) after the UE successfully receives the random access response of the contention based random access preamble selected by the non-MAC entity;

the starting point of a subframe or slot or subslot or symbol after the UE successfully receives the random access response of the contention-based random access preamble selected by the non-MAC entity (for convenience of description, referred to as "eighth time" in the embodiments of the present disclosure).

By starting the corresponding one or more timers for the corresponding HARQ processes in at least one of the above-described times, the UE can receive the retransmission of the HARQ process and/or the retransmission of the DL HARQ feedback scheduled by the base station in time, thereby reducing the user plane delay and improving the reliability of transmission.

It should be noted that the predetermined time may be other times defined by the protocol. For example, the time when DRX-inactivity timer expires (DRX group expires) for one DRX group defined by 3gpp TS 38.321.

It should be noted that, in the embodiment of the present disclosure, the corresponding transmission carrying the DL HARQ feedback may be a cancelled and/or delayed corresponding transmission carrying the DL HARQ feedback. Alternatively, the corresponding transmission carrying the DL HARQ feedback in the embodiment of the present disclosure may be a corresponding transmission carrying the DL HARQ feedback that has been actually transmitted. The corresponding transmission may be a PUCCH transmission and/or a PUSCH transmission.

The method prescribes the action of the UE when the corresponding transmission for bearing the DL HARQ feedback is cancelled and/or is sent in a delayed mode, and the UE can timely receive the retransmission of the HARQ process and/or the retransmission of the DL HARQ feedback scheduled by the base station, so that the time delay of a user plane is reduced, and the transmission reliability is improved.

If the UE is configured with the dynamic HARQ-ACK codebook, the UE may determine (e.g., detect) DCI missed detection (omission of DCI; or presence of undetected DCI) through the DAI. For example, the base station schedules DCI #1 and DCI #2 to the UE, both of which indicate that HARQ-ACK is transmitted in the same uplink time unit (e.g., slot n), where DCI #1 schedules PDSCH #1 with one HARQ process of 1, and indicates that C-DAI is 1, DCI #2 schedules PDSCH #2 with one HARQ process of 2, and indicates that C-DAI is 2. The UE only receives DCI #2 and PDSCH #2, the PDSCH #2 is successfully decoded, and the HARQ-ACK codebook sent by the UE in the uplink time unit (for example, time slot n) is { NACK, ACK }. Since the UE does not restart the drx-retransmission timerdl for HARQ process 1, the UE may enter an inactive time and the UE may not be able to receive a retransmission of that HARQ process scheduled by the base station.

In some embodiments, at least one of the following modes B _1 to B _4 may be performed at a predetermined time if the UE detects DCI missing (e.g., omission of DCI) or the UE determines that there is undetected DCI, through protocol specification and/or higher layer signaling configuration.

Mode B _1: a predetermined timer (referred to as a second predetermined timer for convenience of description) is started. For example, the predetermined timer, if running, considers (e.g., determines) that the UE is in active time. It should be noted that the active time of the UE may be defined for all DRX groups. For example, the predetermined timer is a common timer for different DRX groups. It should be noted that the second predetermined timer may be the same timer as the first predetermined timer, or may be a different timer.

Mode B _2: the drx-inactivytytytimer is started or restarted. For example, DRX-inactivity timer is started or restarted for each DRX group. As another example, a DRX-inactivity timer is started or restarted for a certain DRX group.

Mode B _3: drx-HARQ-RTT-TimerDL is started or restarted for a predetermined HARQ process.

Mode B _4: drx-retransmission timerdl is started or restarted for a predetermined HARQ process.

By executing at least one of the modes B _1 to B _4 at a predetermined time (e.g., one of the first time to the eighth time), the UE can receive the retransmission of the HARQ process scheduled by the base station in time, thereby reducing the user plane delay and improving the reliability of transmission.

In one example, the predetermined HARQ process may be a HARQ process without feedback HARQ information. For example, in the present embodiment, the predetermined HARQ process may be a HARQ process other than HARQ process 2. In another example, the predetermined HARQ process may also be all HARQ processes. In yet another example, the predetermined HARQ process may also be a certain HARQ process, e.g., a HARQ process corresponding to an expired drx-HARQ-RTT-TimerDL.

In some examples, at least one of the above modes B _1 to B _4 may be performed at the predetermined time if the UE detects DCI missed detection and satisfies a predefined condition, which may be specified by a protocol and/or higher layer signaling configuration. For example, the predefined condition may be at least one of the following conditions C _1 to C _3:

condition C _1: drx-HARQ-RTT-TimerDL for one HARQ process expires.

Condition C _2: missed detection may occur for the PDSCH corresponding to one HARQ process, for example, scheduling DCI for the PDSCH corresponding to one HARQ process is not detected.

Condition C _3: the HARQ-ACK information corresponding to one HARQ process is NACK.

For example, the predetermined time may be a time defined in other embodiments of the present disclosure, for example, one of the first time to the eighth time. As another example, the predetermined time may be other times as defined by the protocol.

The method prescribes the behavior of the UE when the UE detects the DCI missing detection, can avoid the UE from entering the inactive time due to the missing detection of the DCI, and can enable the UE to receive the retransmission of the HARQ process scheduled by the base station in time, thereby reducing the time delay of a user plane, improving the reliability of transmission and improving the frequency spectrum efficiency of a system.

In some embodiments, the UE may be configured with PUCCH repetition transmission. For example, the HARQ-ACK information may be repeatedly transmitted. The MAC entity, when configured with the DRX cycle, may, via protocol provisions and/or higher layer signaling configuration:

1> if a MAC PDU (Packet Data Unit, protocol Data Unit) is received in the configured downlink allocation:

and 2> starting drx-HARQ-RTT-TimerDL for the corresponding HARQ process at the preset time.

Alternatively, the MAC entity may, via protocol provisions and/or higher layer signaling configuration, when configured with the DRX cycle:

1> if DRX group is active time:

2> if the PDCCH indicates DL transmission:

and 3> starting drx-HARQ-RTT-TimerDL for the corresponding HARQ process at the preset time.

For example, the predetermined time may be the first symbol after the end of the first or last repeated transmission in the corresponding transmission carrying the DL HARQ feedback. For another example, the predetermined time may also be a time defined in other embodiments of the present disclosure, for example, one of the first time to the eighth time. As another example, the predetermined time may be other times as defined by the protocol.

The method prescribes the behavior of the UE when the HARQ-ACK is repeatedly transmitted, can reduce the time for scheduling retransmission by the base station, and can ensure that the UE can timely receive the retransmission of the HARQ process scheduled by the base station, thereby reducing the time delay of a user plane, improving the reliability of transmission and improving the frequency spectrum efficiency of a system.

In some embodiments, the UE may be in an active time if the C-RNTI scrambling of the MAC entity indicates that a newly transmitted PDCCH has not been received after the UE successfully receives a random access response of a contention-based random access preamble selected by a non-MAC entity. For some specific services, the base station may transmit data (e.g., SPS PDSCH) or receive data (e.g., CG PUSCH) in a schedule-free manner. For activation and retransmission of SPS PDSCH and CG PUSCH, a base station scrambles PDCCH (DCI) by using CS-RNTI, and at the moment, if the UE does not receive PDCCH which is scrambled by C-RNTI and indicates new transmission, the UE is always in active time, so that the power consumption of the UE is increased.

The UE may be configured by protocol provisions and/or higher layer signaling if the UE is in an active time when at least one of the following conditions D _1 and D _2 is met after successfully receiving a random access response of a contention-based random access preamble selected by a non-MAC entity:

condition D _1: the UE does not receive the PDCCH indicating the new transmission with the C-RNTI scrambling and the UE does not receive the PDCCH with the CS-RNTI scrambling.

It should be noted that the PDCCH scrambled by the CS-RNTI may be at least one of the following: activating PDCCH of SPS PDSCH, activating PDCCH of CG PUSCH, scheduling PDCCH retransmitted by SPS PDSCH, and scheduling PDCCH retransmitted by CG PUSCH.

Condition D _2: a predetermined timer (referred to as a third predetermined timer for convenience of description) is running.

It should be noted that the predetermined timer may be started or restarted at a predetermined time. The predetermined time may be a time defined in other embodiments of the present disclosure, for example, one of the first time to the eighth time. As another example, the predetermined time may be other times as defined by the protocol. The predetermined timer may be one of the timers in various embodiments of the present disclosure.

The method can reduce the time of the UE in the activity time, thereby reducing the power consumption of the UE and increasing the battery endurance time of the UE.

In some embodiments, the UE receives a PDCCH indicating SPS PDSCH activation, and the UE starts drx-inactivity timer to make the UE enter active time. For some services, the base station may only use a scheduling-free approach. For example, the UE transmits with only one SPS PDSCH configuration, and after the SPS PDSCH configuration is activated, the base station transmits the SPS PDSCH to the UE, and the base station does not transmit the PDCCH to the UE to schedule the newly transmitted PDSCH. At this time, if the UE continues to monitor the PDCCH, the power consumption of the UE increases.

A predetermined timer (referred to as a fourth predetermined timer for convenience of description) may be started at a predetermined time if the UE receives one PDCCH activating one SPS PDSCH and/or type-2 scheduling-free PUSCH (e.g., UL grant type 2 PUSCH) through protocol provisioning and/or higher layer signaling configuration.

It should be noted that the predetermined timer may be started or restarted at a predetermined time. The predetermined time may be a time defined in other embodiments of the present disclosure, for example, one of the first time to the eighth time. For another example, the predetermined time may be other times defined by the protocol.

The predetermined timer may be applicable for all SPS PDSCH configurations and/or all type-2 scheduling free PUSCH configurations. The predetermined timer may be applicable for a certain SPS PDSCH configuration and/or type-2 scheduling-free PUSCH configuration. For example, the predetermined timer may be configured in an SPS PDSCH configuration. The predetermined timer may also reuse the drx-inactivity timer. For example, a different drx-inactivytytimer value may be configured for the SPS PDSCH.

The method can reduce the time of the UE in the active time, thereby reducing the power consumption of the UE and increasing the battery endurance time of the UE.

In some embodiments, the data packet may have a transmission delay requirement. If the packet is not transmitted correctly within the required transmission time, it may not be necessary to continue transmitting the packet. A packet (e.g., a packet of a higher layer) may be divided into a plurality of TBs (Transport blocks). If any TB is not properly transmitted during the required transmission time, it may not be necessary to continue transmitting any TB of the data packet. At this point, the UE does not need to continue receiving the PDCCH that schedules this packet.

One predetermined timer (e.g., timer parameter; referred to as a fifth predetermined timer for convenience of description) may be configured through protocol provisioning and/or higher layer signaling. If the UE receives a data packet or a traffic PDSCH and/or a PDCCH scheduling a traffic PDSCH, and/or the UE transmits a data packet or transmits a traffic PUSCH and/or receives a PDCCH scheduling a traffic PUSCH, the UE starts the predetermined timer at a predefined time. If the predetermined timer expires, at least one of a timer (e.g., drx-retransmission TimerDL, drx-retransmission timerll, drx-HARQ-RTT-TimerDL, or drx-HARQ-RTT-timerll) or drx-InactivityTimer for the packet or all HARQ processes associated with the service is stopped.

The predetermined time may be a time defined in other embodiments of the present disclosure, for example, one of the first time to the eighth time. For another example, the predetermined time may be other times defined by the protocol.

The predetermined timer parameter may be configured for traffic. For example, the predetermined timer parameters may be configured separately for logical channels and/or logical channel groups. The predetermined timer parameters may also be configured separately for an SPS PDSCH configuration (or configuration group) and/or a CG PUSCH configuration (or configuration group). The predetermined timer parameter may also be configured separately for the serving cell (or group of serving cells).

In some embodiments, when configured with a DRX cycle, the MAC entity will:

1> if the MAC PDU is transmitted in the configured uplink grant and no LBT (Listen Before Talk) failure indication (LBT failure indication) is received from the lower layers:

2> start drx-HARQ-RTT-timerll for the corresponding HARQ process at the first symbol after the end of the first transmission of the corresponding PUSCH transmission (e.g., the first transmission in a bundle of repeated transmissions);

2> the drx-retransmission timerll of the corresponding HARQ process is stopped at the first transmission of the corresponding PUSCH transmission (e.g., the first transmission in a bundle of repeated transmissions).

1> if DRX group is active time:

2> if PDCCH indicates UL transmission

3> stop drx-retransmission timerll for the corresponding HARQ process.

1> if drx-HARQ-RTT-timerll expires:

2> start drx retransmission timerll for the corresponding HARQ process at the first symbol after drx-HARQ-RTT-timerll expires.

If the PUSCH only contains HARQ-ACK information (e.g., does not contain uplink data and/or CSI), the base station does not schedule retransmission of the PUSCH, and the UE does not need to continue to monitor the uplink scheduling PDCCH of the HARQ process.

Through protocol specification and/or higher layer signaling configuration, if only HARQ-ACK information is contained in an uplink transmission, at least one of the following timers of HARQ processes associated with the uplink transmission is stopped at a predetermined time (e.g., a first symbol after a first transmission (e.g., a first transmission in a bundle) of a corresponding PUSCH transmission ends): drx-retransmission timerll, and drx-HARQ-RTT-timerll.

In some cases, data scheduling has a delay requirement, and if the delay requirement is exceeded, the base station may not schedule retransmission, and at this time, the UE continues to monitor the PDCCH and does not receive DCI for scheduling data retransmission, which may consume UE power consumption. In order to save UE power consumption, the UE may be instructed to start or stop a predefined timer through protocol specification and/or signaling, and stop a specific timer when the UE determines that data is not to be retransmitted, thereby reducing the time to monitor the PDCCH. For example, at least one of the following ways MN1 to MN3 may be employed.

Mode MN1

In some embodiments, whether it is possible to schedule retransmission of data may be dynamically indicated in one DCI format. For example, an indication that may be shown with 1 bit in one DCI format, "1" indicates that retransmission may be scheduled, and "0" indicates that retransmission is not scheduled. As another example, this may be indicated by implicit means.

In one example, whether it is possible to schedule a retransmission of the DCI-format-scheduled PDSCH may be indicated in DCI format 1_1 or 1_2, and if the DCI format indicates that a retransmission of the PDSCH is not scheduled, the UE stops the predefined timers (e.g., drx-retransmission timerls and drx-HARQ-RTT-timerls) of the HARQ process associated with the PDSCH transmission for a predetermined time may be times defined by embodiments of the present disclosure, e.g., the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback. If the DCI format does not indicate that a retransmission of the PDSCH will not be scheduled, the UE starts a predefined timer (e.g., drx-HARQ-RTT-TimerDL) for the HARQ process associated with the PDSCH transmission at a predetermined time.

In one example, whether it is possible to schedule retransmission of the PUSCH scheduled by the DCI format 0_1 or 0_2, if the DCI format indicates that retransmission of the PUSCH is not scheduled, the predefined timer (e.g., drx-retransmission timer ul and drx-HARQ-RTT-timer ul) for which the UE stops the uplink transmission associated HARQ process for a predefined time may be a time defined by embodiments of the present disclosure, e.g., the first symbol after the end of the first transmission of the corresponding PUSCH transmission (e.g., the first transmission in a repeat transmission bundle (bundle)). If the DCI format does not indicate that retransmission of the PUSCH will not be scheduled, the UE starts a predefined timer (e.g., drx-HARQ-RTT-timerll) for the HARQ process associated with the uplink transmission at a predetermined time.

It should be noted that "whether it is possible to schedule retransmission of PDSCH scheduled by the DCI format" may be replaced with "whether to stop (or start) a predefined timer (e.g., drx-retransmission timer dl and/or drx-HARQ-RTT-timer dl) after feeding back HARQ-ACK"; "whether it is possible to schedule a retransmission of the DCI format scheduled PUSCH" may also be replaced with "whether to stop (or start) a predefined timer (e.g., drx-retransmission timer ul and/or drx-HARQ-RTT-timer ul) at the first symbol after the end of the first transmission of the PUSCH transmission (e.g., the first transmission in a bundle of repeated transmissions)".

The method can reduce the time of the UE for the PDCCH blind detection and reduce the power loss of the UE.

Mode MN2

In some embodiments, one parameter may be configured in the SPS PDSCH configuration parameter (e.g., the 3GPP parameter SPS-Config) to indicate whether retransmission is supported (or whether a predefined timer (e.g., drx-retransmission timerls and/or drx-HARQ-timerls) is stopped (or started) at a predefined time (e.g., the first symbol after the end of the respective transmission carrying the DL HARQ feedback corresponding to the SPS PDSCH is transmitted), if this parameter indicates that retransmission is not supported (or the predefined timer is stopped after the feedback of the HARQ-ACK), the UE stops the predefined timer (e.g., drx-retransmission timerls and drx-HARQ-RTT-rtds) at the predefined time (e.g., the first symbol after the end of the respective transmission carrying the DL HARQ feedback corresponding to the SPS PDSCH is transmitted), otherwise, the UE starts the predefined timer (e.g., drx-retransmission-timerls).

In some embodiments, a parameter may be configured in a CG PUSCH configuration parameter (e.g., 3GPP parameter ConfiguredGrantConfig) to indicate whether retransmission is supported (or whether a predefined time (e.g., the first symbol after the first transmission in a bundle of repeated transmissions (e.g., bundle) ends)) is stopped (or started) for a predefined timer (e.g., timedrx-retransmission timerll and drx-HARQ-RTT-timerll), if the parameter indicates that retransmission is not supported (or the first symbol after the first transmission of the CG PUSCH transmission (e.g., the first transmission in a bundle of repeated transmissions (bundle) ends) is stopped for the predefined timer (e.g., timedrx-retransmission-timer and drx-HARQ-RTT-timer ul), the UE stops the predefined timer (e.g., the first symbol after the first transmission of the CG PUSCH transmission (e.g., the first transmission in a bundle of repeated transmissions (bundle) ends) for the first transmission of the CG transmission (e.g., bundle) and otherwise starts the predefined timer (e.g., the first symbol after the first transmission of the PUSCH transmission bundle (bundle) ends.

Mode MN3

In some embodiments, one parameter may be configured in the SPS PDSCH configuration parameter to indicate the number of transmissions N (N may indicate the total number of transmissions, or N may indicate the number of transmissions scheduled by the DCI format). Wherein, N can be a non-negative integer or a positive integer. The UE stops the predefined timers (e.g., drx-retransmission TimerDL and drx-HARQ-RTT-TimerDL) at a predefined time (e.g., the first symbol after the end of the respective transmission of the DL HARQ feedback corresponding to the nth transmission (or retransmission) carrying the SPS PDSCH). The UE starts a predefined timer (e.g., drx-HARQ-RTT-TimerDL) at the first symbol after the end of the respective transmission carrying the DL HARQ feedback corresponding to the non-nth retransmission of the SPS PDSCH.

In some embodiments, one parameter may be configured in a CG PUSCH configuration parameter (e.g., 3GPP parameter ConfiguredGrantConfig) to indicate the number of transmissions M (M may indicate the total number of transmissions, or M may indicate the number of transmissions scheduled by a DCI format). Wherein M may be a non-negative or positive integer. The UE stops the predefined timer (e.g., drx-retransmission timer ul and drx-HARQ-RTT-timer ul) for a predefined time (e.g., the first symbol after the end of the first transmission (e.g., the first transmission in a bundle of repeated transmissions) of the CG PUSCH mth transmission (or retransmission)). The UE starts a predefined timer (e.g., drx-HARQ-RTT-timerll) at the first symbol after the end of the first transmission (e.g., the first transmission in a bundle of repeated transmissions) of the CG PUSCH non-mth transmission (or duplicate transmission).

It should be noted that if N is equal to 0 or M is equal to 0, it is stated that retransmission is not scheduled, and the processing can be performed in the manner MN 2.

Fig. 8 shows a flow diagram of a method 800 performed by a UE in accordance with an embodiment of the disclosure.

Referring to fig. 8, a DL signal including a PDCCH and/or a PDSCH is received in operation S810.

In operation S820, a UL signal including a PUCCH and/or a PUSCH is transmitted.

In an embodiment, the PDCCH is monitored when the UE is in active time of DRX mode.

In some embodiments, for a HARQ process of a DL signal, in case the UL transmission carrying DL HARQ feedback is cancelled and/or delayed, at least one of the following may be performed at a first predetermined time: starting a first predetermined timer for the HARQ process, wherein the UE is in an active time of a DRX mode for PDCCH monitoring when the first predetermined timer is running; starting a retransmission timer for DL for the HARQ process; or if the data of the HARQ process is not successfully decoded, starting a retransmission timer for the DL for the HARQ process.

In some embodiments, where it is determined that there is undetected DCI, at least one of the following may be performed at a second predetermined time: starting a second predetermined timer, wherein the UE is in active time of DRX mode for PDCCH monitoring when the second predetermined timer is running; starting or restarting an inactivity timer; starting or restarting a round trip time RTT timer for DL for a predetermined HARQ process; or start or restart a retransmission timer for DL for a predetermined HARQ process.

In some embodiments, upon successful reception of a random access response of the contention-based random access preamble selected by the non-medium access control MAC entity, the UE may be determined to be in an active time based on at least one of: (i) The UE does not receive a PDCCH scrambled by a cell radio network temporary identifier C-RNTI and indicating new transmission and does not receive a PDCCH scrambled by a CS-RNTI configured and scheduled; or (ii) a third predetermined timer is running, wherein the UE is in active time of DRX mode for PDCCH monitoring while the third predetermined timer is running.

In some embodiments, a fourth predetermined timer may be started at a third predetermined time in case the received PDCCH activates SPS PDSCH and/or UL grant type 2PUSCH, wherein the UE is in active time of DRX mode for PDCCH monitoring while the fourth predetermined timer is running.

In some embodiments, the fifth predetermined timer may be started at the fourth predetermined time in case the UE receives a DL signal or transmits an UL signal. Upon expiration of the fifth predetermined timer, stopping at least one of an inactivity timer, a retransmission timer for DL, a retransmission timer for UL, an RTT timer for DL, or an RTT timer for UL for each of all HARQ processes associated with the downlink signal.

In some embodiments, in case that the uplink transmission of the uplink signal includes only DL HARQ feedback, at least one of a retransmission timer for UL or an RTT timer for UL of the HARQ process associated with the uplink transmission may be stopped at a fifth predetermined time.

In some embodiments, each of the first predetermined time, the second predetermined time, the third predetermined time, the fourth predetermined time, and the fifth predetermined time is based on at least one of:

a first time unit after the end of the UL transmission carrying the DL HARQ feedback;

a starting point of a time unit after the end of the UL transmission carrying the DL HARQ feedback;

a first time unit after the end of the reception of the PDCCH;

the first time unit after the round trip time RTT timer for DL expires;

a first time unit after expiration of the RTT timer for the UL;

a first time unit after the end of the first or last repetition in the UL transmission carrying the DL HARQ feedback, where the UL transmission comprises repetitions;

a first time unit after the UE successfully receives a random access response of a contention-based random access preamble selected by a non-MAC entity;

the UE is at a starting point of a time unit after successfully receiving a random access response of the contention-based random access preamble selected by the non-MAC entity.

For example, the time unit may be one of a subframe, a slot, a sub-slot, or a symbol.

In some embodiments, each of the first predetermined timer, the second predetermined timer, the third predetermined timer, the fourth predetermined timer, or the fifth predetermined timer may include at least one of: a retransmission timer for DL, a retransmission timer for UL, an inactive timer, an RTT timer for DL, an RTT timer for UL, an active duration timer, or a newly defined timer.

For example, the retransmission timer for the DL may include drx-retransmission timerdl.

For example, the retransmission timer for the UL may include drx-retransmission timerll.

For example, the inactivity timer may include a drx-inactivity timer.

For example, the RTT timer for DL may include drx-HARQ-RTT-TimerDL.

For example, the RTT timer for the UL may comprise drx-HARQ-RTT-timerll.

For example, the activity duration timer may include a drx-onDurationTimer.

Fig. 9 illustrates a block diagram of a first type of transceiving node 900 according to some embodiments of the present disclosure.

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

The transceiver 901 may be configured to transmit and receive second type data and/or second type control signaling from a second type transceiving 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 the overall operation of the first type of transceiving node, including controlling the transceiver 901 to transmit first type data and/or first type control signaling to the second type of transceiving node and to receive second type data and/or second type control signaling from the second type of transceiving node in time units.

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

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

Fig. 10 shows a flow diagram of a method 1000 performed by a base station, in accordance with some embodiments of the present disclosure.

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

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

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

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

In some embodiments, the base station may send the configuration information to a second type of transceiving node. For example, the configuration information may include parameters for one or more of the various timers described above. For example, the configuration information may be transmitted via higher layer signaling (e.g., RRC signaling or MAC CE).

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 disclosed invention, 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 would understand that the various illustrative logical blocks, modules, circuits, and steps described in this application 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 implementation 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 (DSP), an Application Specific Integrated Circuit (ASIC), a 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 this application 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 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 above description is intended to be illustrative of the present invention and not to limit the scope of the invention, which is defined by the claims appended hereto.

Claims

1. A method performed by a user equipment, UE, in a wireless communication system, comprising:

receiving a Downlink (DL) signal, wherein the DL signal comprises a Physical Downlink Control Channel (PDCCH) and/or a Physical Downlink Shared Channel (PDSCH); and/or

Transmitting an uplink, UL, signal comprising a physical uplink control channel, PUCCH, and/or a physical uplink shared channel, PUSCH,

wherein the PDCCH is monitored when the UE is in an active time of a Discontinuous Reception (DRX) mode.

2. The method according to claim 1, wherein for a hybrid automatic repeat request, HARQ, process of the DL signal, in case UL transmission carrying DL HARQ feedback is cancelled and/or delayed, at least one of the following is performed at a first predetermined time:

starting a first predetermined timer for the HARQ process, wherein the UE is in active time of DRX mode for PDCCH monitoring when the first predetermined timer is running;

starting a retransmission timer for DL for the HARQ process; or

And if the data of the HARQ process is not decoded successfully, starting a retransmission timer for DL for the HARQ process.

3. The method of claim 1, wherein in the event that DCI is not detected, performing at least one of the following at a second predetermined time:

starting a second predetermined timer, wherein the UE is in active time of DRX mode for PDCCH monitoring while the second predetermined timer is running;

starting or restarting an inactivity timer;

starting or restarting a round trip time RTT timer for DL for a predetermined HARQ process; or

A retransmission timer for DL is started or restarted for a predetermined HARQ process.

4. The method of claim 1, wherein the UE is determined to be in the active time based on at least one of:

the UE does not receive a PDCCH scrambled by a cell radio network temporary identifier C-RNTI and indicating new transmission and does not receive a PDCCH scrambled by a CS-RNTI configured and scheduled;

a third predetermined timer is running, wherein the UE is in active time of DRX mode for PDCCH monitoring while the third predetermined timer is running.

5. The method of claim 1, wherein a fourth predetermined timer is started at a third predetermined time on a condition that the received PDCCH activates SPS PDSCH and/or UL grant type 2PUSCH, wherein the UE is in active time of DRX mode for PDCCH monitoring while the fourth predetermined timer is running.

6. The method of claim 1, wherein the first and second light sources are selected from the group consisting of,

wherein a fifth predetermined timer is started at a fourth predetermined time in case that the UE receives the DL signal or transmits the UL signal,

wherein, on an expiration of the fifth predetermined timer, at least one of an inactivity timer, a retransmission timer for DL, a retransmission timer for UL, an RTT timer for DL, or an RTT timer for UL for each of all HARQ processes associated with the downlink signal is stopped.

7. The method of claim 1, wherein in the case that the transmission of the UL signal includes only DL HARQ feedback, stopping at least one of a retransmission timer for UL or an RTT timer for UL for a HARQ process associated with the transmission of the UL signal at a fifth predetermined time.

8. The method of any of claims 1-7, wherein each of the first, second, third, fourth, and fifth predetermined times is based on at least one of:

a first time unit after the end of the reception of the PDCCH;

the first time unit after the round trip time RTT timer for DL expires;

a first time unit after expiration of the RTT timer for the UL;

a first time unit after the end of a first or last repetition in an UL transmission carrying DL HARQ feedback, where the UL transmission comprises repetitions;

the first time unit after the UE successfully receives the random access response of the contention-based random access preamble selected by the non-MAC entity;

9. The method of claim 8, wherein:

each of the first, second, third, fourth, or fifth predetermined timers includes at least one of: a retransmission timer for DL, a retransmission timer for UL, an inactive timer, an RTT timer for DL, an RTT timer for UL, an active duration timer, or a newly defined timer.

10. A user equipment, UE, in a wireless communication system, comprising:

a transceiver configured to transmit and receive signals; and

a controller coupled with the transceiver and configured to:

receiving a Downlink (DL) signal, wherein the DL signal comprises a Physical Downlink Control Channel (PDCCH) and/or a Physical Downlink Shared Channel (PDSCH), and/or

11. The UE of claim 10, wherein the controller is configured to perform, for a HARQ process of the DL signal, in case UL transmission carrying DL HARQ feedback is cancelled and/or delayed, at a first predetermined time, at least one of:

starting a first predetermined timer for the HARQ process, wherein when the first predetermined timer is running, the UE is in active time of DRX mode for PDCCH monitoring;

starting a retransmission timer for DL for the HARQ process; or

12. The UE of claim 10, wherein the controller is configured to, if DCI is not detected, perform at least one of the following at a second predetermined time:

starting or restarting an inactivity timer;

13. The UE of claim 10, wherein the controller is configured to determine that the UE is in the active time based on at least one of the following after successfully receiving a random access response of a contention-based random access preamble selected by a non-medium access control, MAC, entity:

the UE does not receive a PDCCH (physical downlink control channel) which is scrambled by a cell radio network temporary identifier C-RNTI and indicates new transmission and does not receive the PDCCH scrambled by a configuration scheduling radio network temporary identifier CS-RNTI; or

14. The UE of claim 10, wherein the controller is configured to start a fourth predetermined timer at a third predetermined time on a condition that the received PDCCH activates SPS PDSCH and/or UL grant type 2PUSCH, wherein the UE is in active time of DRX mode for PDCCH monitoring while the fourth predetermined timer is running.

15. The UE of claim 10, wherein the controller is configured to start a fifth predetermined timer at a fourth predetermined time if the UE receives the DL signal or transmits the UL signal,

wherein the controller is configured to stop at least one of an inactivity timer, a retransmission timer for DL, a retransmission timer for UL, an RTT timer for DL, or an RTT timer for UL for each of all HARQ processes associated with the downlink signal if the fifth predetermined timer expires.

16. The UE of claim 10, wherein the controller is configured to stop at least one of a retransmission timer for UL or an RTT timer for UL for a HARQ process associated with the transmission of the UL signal at a fifth predetermined time if the transmission of the UL signal includes only DL HARQ feedback.

17. The UE of any of claims 10-16, wherein each of the first, second, third, fourth, and fifth predetermined times is based on at least one of:

a first time unit after the end of the reception of the PDCCH;

the first time unit after the round trip time RTT timer for DL expires;

a first time unit after expiration of the RTT timer for the UL;

a first time unit after the end of a first or last repetition in an UL transmission carrying DL HARQ feedback, if the UL transmission comprises repetitions;

18. The UE of claim 17, wherein: