Techniques for hybrid automatic repeat request state drop

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a first physical downlink control channel (PDCCH) communication having a new data indicator (NDI) value for a hybrid automatic repeat request (HARQ) process. The UE may start a HARQ state drop timer based at least in part on receiving the first PDCCH communication, wherein a duration of the HARQ state drop timer is based at least in part on one or more conditions. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 368,466, filed on July 14, 2022, entitled “TECHNIQUES FOR HYBRID AUTOMATIC REPEAT REQUEST STATE DISCARDING” and U.S. Non-Provisional Patent Application No. 18 / 352,047, filed on July 13, 2023, entitled “TECHNIQUES FOR HYBRID AUTOMATIC REPEAT REQUEST STATE DISCARDING” and assigned to the assignee of this application. The disclosures of these prior applications are considered part of and incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for hybrid automatic repeat request (HARQ) state discarding. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, or global level. New Radio (NR), which may also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink, using CP-OFDM or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM) on the uplink, and supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving a first physical downlink control channel (PDCCH) communication having a new data indicator (NDI) value for a hybrid automatic repeat request (HARQ) process. The method may include starting a HARQ state discard timer based at least in part on receiving the first PDCCH communication, wherein a duration of the HARQ state discard timer is based at least in part on one or more conditions.

[0008] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a first PDCCH communication having an NDI value for a HARQ process. The one or more processors may be configured to start a HARQ state discard timer based at least in part on receiving the first PDCCH communication, wherein the duration of the HARQ state discard timer is based at least in part on one or more conditions.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a first PDCCH communication having an NDI value for a HARQ process. The instruction set, when executed by one or more processors of the UE, may cause the UE to start a HARQ state discard timer based at least in part on receiving the first PDCCH communication, wherein a duration of the HARQ state discard timer is based at least in part on one or more conditions.

[0010] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a first PDCCH communication having an NDI value for a HARQ process. The apparatus may include means for starting a HARQ state discard timer based at least in part on receiving the first PDCCH communication, wherein a duration of the HARQ state discard timer is based at least in part on one or more conditions.

[0011] The various aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0012] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for the same purpose of achieving the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and methods of operation) and the associated advantages will be better understood according to the following description. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of limitations to the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0014] Figure 1 is a diagram illustrating an example of a wireless network.

[0015] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network.

[0016] Figure 3A and Figure 3B is a diagram illustrating an example associated with a hybrid automatic repeat request (HARQ) state discard according to the present disclosure.

[0017] Figure 3Bis a diagram illustrating an example in which a UE processes a shared channel communication as a new transmission based at least in part on receiving a second physical downlink control channel (PDCCH) communication after expiration of a HARQ state discard timer.

[0018] Figure 4 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0019] Figure 5 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0020] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or structures and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0021] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0022] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0023] Figure 11 is a diagram illustrating an example of a wireless network 100. The wireless network 100 may be a 5G (e.g., NR) network or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), or other entities. The network node 110 is an example of a network node that communicates with the UE 120. As shown, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). As another example, the network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0024] In some examples, the network node 110 is or includes a network node (such as an RU) that communicates with the UE 120 via a radio access link. In some examples, the network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, the network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. For example, the network node 110 may include an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network.

[0025] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 or a network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several thousand meters) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. The network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0026] In some aspects, the term "base station" or "network node" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with the network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.

[0027] The wireless network 100 may include one or more relay stations. A relay station is a network node that receives transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmits transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown, a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communications between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, or a relay, etc.

[0028] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, or different effects on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0029] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0030] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station, or a subscriber unit. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, or a satellite radio), a vehicle-mounted component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node, or any other suitable device configured to communicate via a wireless or wired medium.

[0031] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, or location tags, which may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices, or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, or electrically coupled.

[0032] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may also be referred to as a radio technology or air interface. Frequency may also be referred to as a carrier or frequency channel. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0033] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by network node 110.

[0034] Devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, or channels by frequency or wavelength. For example, devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0035] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics or FR2 characteristics, and thus the features of FR1 or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0036] With these examples in mind, unless otherwise specifically stated, if the term "sub-6 GHz" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, frequencies that may be within FR1, or frequencies that may include mid-band frequencies. Additionally, unless otherwise specifically stated, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, frequencies that may be within FR2, FR4, FR4-a, FR4-1, or FR5, or frequencies that may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) may be modified, and that the techniques described herein are applicable to those modified frequency ranges.

[0037] In some aspects, the UE 120 may include a communications manager 140. As described in greater detail elsewhere herein, the communications manager 140 may receive a first physical downlink control channel (PDCCH) communication having a new data indicator (NDI) value for a hybrid automatic repeat request (HARQ) process; and start a HARQ state discard timer based at least in part on receiving the first PDCCH communication, wherein a duration of the HARQ state discard timer is based at least in part on one or more conditions. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0038] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 Different than described.

[0039] Figure 22 is a diagram illustrating an example 200 in which a network node 110 communicates with a UE 120 in a wireless network 100. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0040] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may use one or more channel quality indicators (CQIs) received from the UE 120 to select one or more modulation and coding schemes (MCSs) for the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 using the MCS selected for the UE 120 and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0041] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 or other network nodes 110, and a set of received signals (e.g., R received signals) may be provided to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0042] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0043] One or more antennas (e.g., antennas 234a to 234t or antennas 252a to 252r) may include or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. An antenna panel, set of antennas, set of antenna elements, or antenna array may include one or more antenna elements (in a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or a plurality of antenna elements coupled to one or more transmit or receive components (such as antennas). Figure 2 One or more antenna elements of one or more components).

[0044] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by a TX MIMO processor 266, where applicable, further processed by a modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, or a TX MIMO processor 266. The transceiver may be used by a processor (e.g., the controller / processor 280) and a memory 282 to perform operations described herein (e.g., reference 1). Figures 3A to 5 )Aspects of any of the processes described.

[0045] At the network node 110, uplink signals from the UE 120 or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232, shown as DEMOD), detected by the MIMO detector 236 where applicable, and further processed by the receive processor 238 to obtain decoded data and control information transmitted via the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and provide the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform the functions described herein (e.g., reference 2 Figures 3A to 5 )Aspects of any of the processes described.

[0046] In some aspects, the controller / processor 280 may be a component of a processing system. A processing system may generally be a system or series of machines or components that receives inputs and processes the inputs to produce a set of outputs that may be communicated to other systems or components, such as the UE 120. For example, the processing system of the UE 120 may be a system that includes various other components or subcomponents of the UE 120.

[0047] The processing system of UE 120 may interface with one or more other components of UE 120, may process information (such as input or signal) received from one or more other components, or may output information to one or more other components. For example, a chip or modem of UE 120 may include: a processing system, a first interface for receiving or obtaining information, and a second interface for outputting, sending, or providing information. In some examples, the first interface may be an interface between a processing system and a receiver of the chip or modem, so that UE 120 may receive information or signal input, and may pass information to the processing system. In some examples, the second interface may be an interface between a processing system and a transmitter of the chip or modem, so that UE 120 may send information output from the chip or modem. A person of ordinary skill in the art will readily recognize that the second interface may also obtain or receive information or signal input, and the first interface may also output, send, or provide information.

[0048] In some aspects, controller / processor 240 may be a component of a processing system. A processing system may generally be a system or series of machines or components that receives inputs and processes the inputs to produce a set of outputs that may be passed to other systems or components, such as network node 110. For example, a processing system of network node 110 may be a system that includes various other components or subcomponents of network node 110.

[0049] The processing system of the network node 110 may interface with one or more other components of the network node 110, may process information (such as input or signal) received from one or more other components, or may output information to one or more other components. For example, a chip or modem of the network node 110 may include: a processing system, a first interface for receiving or obtaining information, and a second interface for outputting, sending, or providing information. In some examples, the first interface may be an interface between a processing system and a receiver of the chip or modem, so that the network node 110 may receive information or signal input, and may pass information to the processing system. In some examples, the second interface may be an interface between a processing system and a transmitter of the chip or modem, so that the network node 110 may send information output from the chip or modem. A person of ordinary skill in the art will readily recognize that the second interface may also obtain or receive information or signal input, and the first interface may also output, send, or provide information.

[0050] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or Figure 2 Any other component in the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or the like may perform one or more techniques associated with HARQ state discarding, as described in more detail elsewhere herein. Figure 2 Any other component (or combination of components) in may perform or direct, for example Figure 4 400 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and memory 282 may include non-transitory computer-readable media storing one or more instructions (e.g., code or program code) for wireless communication. For example, one or more instructions, when executed (e.g., directly, or after compilation, conversion, or interpretation) by one or more processors of network node 110 or UE 120, may cause one or more processors, UE 120, or network node 110 to perform or direct, for example, Figure 4 The process 400 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0051] In some aspects, a UE (e.g., UE 120) includes means for receiving a first PDCCH communication having an NDI value for a HARQ process; and / or means for starting a HARQ state discard timer based at least in part on receiving the first PDCCH communication, wherein a duration of the HARQ state discard timer is based at least in part on one or more conditions. Means for the UE to perform operations described herein may include, for example, one or more of the following: a communications manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0052] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0053] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Different than described.

[0054] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5GNR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0055] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0056] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0057] HARQ refers to a retransmission protocol in which a receiver wireless communication device checks for errors in received data, and if an error is detected, the receiver wireless communication device buffers the received data and requests a retransmission from a transmitter wireless communication device. The HARQ receiver is then able to combine the buffered received data with the retransmitted data before channel decoding and error detection, which improves the performance of the retransmission. The HARQ protocol may be implemented at the medium access control (MAC) layer.

[0058] The HARQ protocol relies on the transmitter wireless communication device receiving an acknowledgement (e.g., an acknowledgement (ACK) or a negative acknowledgement (NACK)) from the receiver wireless communication device. The round trip time, which includes both the processing time of the transmitter wireless communication device and the processing time of the receiver wireless communication device as well as propagation delays, means that such acknowledgements are not received instantly.

[0059] Generally speaking, a transmitter wireless communication device becomes inactive (with respect to communicating with a receiver wireless communication device) while waiting for an acknowledgment or waiting for a scheduling opportunity, which means that the average throughput may be relatively low. This corresponds to a single HARQ process (also referred to as a stop-and-wait (SAW) process). The HARQ process stops and waits for an acknowledgment before continuing to transmit additional data. Multiple HARQ processes may be used to avoid the impact of round-trip time on throughput. That is, other HARQ processes may transmit data while a given HARQ process is waiting for an acknowledgment. The HARQ entity within the MAC layer manages multiple HARQ processes. In operation, the transmitter wireless communication device buffers the transmitted data until a positive acknowledgment has been received (in the event that a retransmission is required). Once a positive acknowledgment has been received or the maximum number of retransmissions allowed has been reached, the data is cleared from the transmit buffer. Once the transmit buffer of a given HARQ process has been cleared, new data may be transmitted by the given HARQ process.

[0060] The HARQ protocol may be used on the downlink or on the uplink. "Downlink HARQ" may refer to the transmission of downlink data on a physical downlink shared channel (PDSCH) with a HARQ confirmation returned on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). "Uplink HARQ" may refer to the transmission of uplink data on a PUSCH with a HARQ confirmation returned on a PDCCH. For both downlink HARQ and uplink HARQ, each serving cell has its own HARQ entity and its own set of HARQ processes. In addition, both downlink HARQ and uplink HARQ are asynchronous, which means that there is no fixed timing pattern for each HARQ process. Instead, the network node must signal the identity of the associated HARQ process with each downlink resource allocation. It is worth noting that although asynchronous HARQ increases signaling overhead, asynchronous HARQ increases flexibility because retransmissions do not have to be scheduled during specific time slots.

[0061] Downlink control information (DCI) (e.g., DCI format 1_0, DCI format 1_1) may be used to provide dynamic downlink resource allocation on the PDCCH. The DCI associated with dynamic downlink resource allocation may include information for implementing downlink HARQ operations, such as information indicating a HARQ process number, NDI, redundancy version (RV), PDSCH to HARQ feedback timing indicator, PUCCH resource indicator, downlink assignment index (DAI), code block group (CBG) transmission information (CBGTI), CBG refresh information (CBGFI), MCS information, or frequency resource allocation information (e.g., resource block allocation information), etc. Similarly, dynamic uplink resource allocation may be provided on the PDCCH using DCI (e.g., DCI format 0_0, DCI format 0_1). The DCI associated with dynamic uplink resource allocation may include information for implementing uplink HARQ operations, such as information indicating a HARQ process number, NDI, RV, or CBGTI.

[0062] With respect to downlink HARQ, NDI may be communicated via a single bit used to inform the UE whether the network node is sending a new transmission (e.g., a new transport block (TB)) or a retransmission of a previous transmission. Switching the NDI value relative to a previous NDI value for the same HARQ process (e.g., from 0 to 1, from 1 to 0) indicates that a new transmission (rather than a retransmission) is being sent. Conversely, maintaining (i.e., not switching) the NDI value relative to a previous NDI value for the same HARQ process indicates that a retransmission (rather than a new transmission) is being sent.

[0063] With respect to uplink HARQ, NDI may be a one-bit flag that acts as a HARQ acknowledgment for a previously transmitted message associated with a specified HARQ process number. For example, switching the NDI value relative to the previous NDI value for a specified HARQ process is used to indicate that the UE is initiating a new transmission (which corresponds to a positive acknowledgment of a previously transmitted message). Conversely, using the same NDI value for a specified HARQ process (i.e., not switching the NDI value relative to the previous NDI value) is used to indicate that the UE is performing a retransmission of a previously transmitted message (which corresponds to a negative acknowledgment of a previously transmitted message).

[0064] The state of a given HARQ process (referred to herein as a HARQ state) is defined by the NDI value and may include other information associated with performing HARQ transmission / reception, such as the MCS associated with the HARQ process at a given time, resource block (RB) allocations, timing information, etc. Thus, it can be said that a switch in an NDI value relative to a previous NDI value switches the HARQ state of the HARQ process from one HARQ state to another HARQ state (e.g., from state 0 when the NDI value is 0 to state 1 when the NDI value is 1, and vice versa).

[0065] According to the 3GPP specification, the UE may not discard the HARQ state of a given HARQ process in some deployments. That is, the UE may maintain the HARQ state for an indefinite amount of time. It is worth noting that this operation does not take into account the possibility that the UE and the network node may be relatively easily out of sync with each other, because the NDI can be a single bit (for both downlink HARQ and uplink HARQ). Therefore, since there are only two HARQ states (e.g., state 0 and state 1), the UE may easily miss the HARQ state change. For example, in the case of downlink HARQ, the UE may receive a first NDI indicating that the HARQ process is changing from a second state (e.g., state 1) to a first state (e.g., state 0). Therefore, the UE identifies the upcoming communication associated with the HARQ process as a new transmission. In this example, the UE receives the new transmission (e.g., as scheduled by a PDCCH communication carrying a DCI including the first NDI) and successfully decodes it. However, in this example, the UE fails to receive the second NDI that changes the state of the HARQ process from the first state to the second state, but later receives a third NDI indicating that the HARQ process is in the first state. In this scenario, the UE processes the communication associated with the third NDI as if the HARQ process remains in the first state, rather than operating as if the HARQ process transitions from the first state to the second state and back to the first state. This causes the UE to incorrectly identify another new transmission as a retransmission (of the previous new transmission), and the new transmission is discarded by the UE.

[0066] It is worth noting that in some deployments, the downlink HARQ entity may maintain the HARQ state of a given HARQ process for 256 time slots (e.g., 256 milliseconds (ms) for NR 5G with a 15 kilohertz (kHz) subcarrier spacing (SCS)), after which the downlink HARQ entity may discard the HARQ state (e.g., if the HARQ state has not changed during the 256 time slot period). After discarding the HARQ state, any transmission is considered a new transmission. As described above, before discarding the HARQ state, determining whether a given transmission is a new transmission or a retransmission is based on the value of the NDI. However, for periodic services with a periodicity of less than 256 time slots (e.g., such as Voice over NR (VoNR) services with a periodicity of 40 ms; or VR services that may have a periodicity of 16.6 ms), this configuration may still result in scenarios where new transmissions are discarded.

[0067] As an example, at a first point in time, the UE receives a first PDCCH communication carrying a DCI including an NDI indicating a first state of a HARQ process (e.g., state 0). In this example, the UE subsequently receives a new transmission (e.g., a first PDSCH communication) scheduled by the first PDCCH communication and successfully decodes it. Here, the UE starts a HARQ state discard timer of 256ms duration after, for example, successfully decoding the new transmission. Next, the UE fails to receive a second PDCCH communication sent at a second point (e.g., 40ms after the first point in time), the second PDCCH communication carrying a DCI including an NDI indicating a second state of the HARQ process (e.g., state 1). That is, the UE misses the HARQ state change and therefore misses the new transmission associated with the HARQ process (e.g., the second PDSCH communication). Here, due to the discontinuous reception (DRX) configuration, it is assumed that because the UE fails to respond to the second PDCCH communication, the UE does not wake up from the sleep state, and the network may not attempt any retransmission of the second PDCCH communication or the second PDSCH communication indicating the second state (e.g., NDI=1). Next, at a third time point (e.g., 80ms after the first time point), the UE receives a third PDCCH communication carrying a DCI, which includes an NDI indicating the first state of the HARQ process. Here, the HARQ state has been maintained by the UE since the first time point (because the 256 slot timer has not expired). Therefore, the UE mistakenly identifies the new transmission (e.g., the third PDSCH communication scheduled by the third PDCCH communication) as a retransmission. Therefore, because the UE receives and decodes the new transmission associated with the first PDCCH communication, the UE discards the third PDSCH communication scheduled by the third PDCCH communication, even if the third PDSCH communication is a new transmission (not a retransmission). It is worth noting that in a scenario where the UE fails to successfully decode the first PDSCH communication, the UE may attempt to combine the first PDSCH communication and the third PDSCH communication. (For example, if the DCI parameters permit the combination) because the UE has incorrectly identified the third PDSCH communication as a retransmission. However, because the third PDSCH communication is a new transmission (rather than a retransmission), such a combination is guaranteed to never succeed. In either scenario, the result is that the UE incorrectly processes the third PDSCH communication.

[0068] Some aspects described herein provide techniques and devices for HARQ state discard. In some aspects, a UE may receive a first PDCCH communication having an NDI value for a HARQ process. In some aspects, the UE may start a HARQ state discard timer based at least in part on receiving the first PDCCH communication, wherein the duration of the HARQ state discard timer is based at least in part on one or more conditions. The one or more conditions may include, for example, the duration of the DRX cycle of the UE (e.g., the long DRX cycle of the UE, the short DRX cycle of the UE, etc.), the behavior of the network node regarding communication with the UE, the service mode associated with the UE, the HARQ round trip time (RTT) associated with the network node, the sleep state of the UE, the SCS associated with the UE, the cell type associated with the network node, the application type associated with the UE service, the quality of service (QoS) feature set associated with the UE service or the QoS identifier associated with the UE service, etc. In some aspects, the techniques and devices for HARQ state discard described herein can improve the performance and reliability of HARQ operations. For example, the techniques and apparatus described herein for HARQ state discarding can prevent new transmissions associated with periodic traffic from being erroneously discarded or decoded due to being erroneously identified as retransmissions.Additional details are provided below.

[0069] Figure 3A and Figure 3B is a diagram illustrating an example 300 associated with HARQ state discarding according to the present disclosure. Figure 3A As shown, example 300 includes communications between a network node 110 and a UE 120. In some aspects, the network node 110 and the UE 120 may be included in a wireless network, such as the wireless network 100. The network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

[0070] like Figure 3A As shown by reference numeral 302, the network node 110 may send a PDCCH communication with an NDI for a HARQ process, and the UE 120 may receive the PDCCH communication. For example, as described herein, the network node 110 may send a PDCCH carrying a DCI including an NDI value associated with a HARQ process of the UE 120, and the UE 120 may receive the PDCCH.

[0071] As indicated by reference numeral 304, UE 120 may start a HARQ state discard timer based at least in part on receiving the PDCCH communication. For example, a PDCCH communication may schedule a PDSCH communication. Here, UE 120 may attempt to receive and decode a PDSCH communication scheduled by a PDCCH communication having an NDI value. In one example, UE 120 may fail to decode a PDSCH communication and may start a HARQ state discard timer based at least in part on failing to decode the PDSCH communication. In another example, UE 120 may successfully decode a PDSCH communication and may start a PDSCH communication based at least in part on successfully decoding the PDSCH communication. In this way, in some aspects, UE 120 may start a HARQ discard timer after receiving a PDCCH communication having an NDI value associated with a HARQ process.

[0072] In some aspects, the duration of the HARQ discard timer is based at least in part on one or more conditions. In some aspects, the one or more conditions include the duration of the DRX cycle of the UE 120 (e.g., the long DRX cycle of the UE, the short DRX cycle of the UE, etc.). That is, in some aspects, the duration of the HARQ state discard timer may be based at least in part on the DRX cycle of the UE 120. In some specific implementations, the UE 120 may determine the DRX cycle based at least in part on the following: The duration of the HARQ discard time (e.g., long DRX cycle or short DRX cycle) will be determined at least in part based on, for example, the service type or the relative length of the DRX cycle.

[0073] In operation, the UE 120 is awake (e.g., not in a sleep state) during a portion of each DRX cycle to enable PDCCH communications to be received by the UE 120. Here, by remaining awake for several DRX cycles, the UE 120 provides the network node 110 with an opportunity to schedule the UE 120 in the next DRX cycle (e.g., if the UE 120 fails to successfully receive or successfully decode an earlier transmission). If the DRX on-duration timer associated with the DRX cycle of the UE 120 is relatively short (e.g., shorter than the HARQ RTT), the network node 110 has only one opportunity to schedule the UE 120 with PDCCH communications and receive an acknowledgement that the UE 120 successfully received the PDCCH communications (e.g., via UE HARQ ACK / NACK feedback in the case of PDSCH, or via PUSCH). Successful reception of PDCCH communications extends the DRX awake time, which provides an opportunity for HARQ retransmissions. In some aspects, the duration of the HARQ state discard timer is approximately equal to twice the duration of the UE's DRX cycle minus a delay period. As a specific example, if the duration of the DRX cycle of UE 120 is 40 ms (e.g., when UE 120 is using VoNR services) and the delay period is 10 ms, the duration of the HARQ state discard timer is 70 ms (e.g., (2×40 ms)−10 ms=70 ms).

[0074] In some aspects, the duration of the HARQ state discard timer is longer than the duration of the DRX cycle of the UE. In some aspects, the duration of the HARQ state discard timer is shorter than N times the duration of the DRX cycle of the UE, where N is greater than or equal to 2. In some aspects, the duration of the HARQ state discard timer is greater than or equal to the duration of the DRX cycle of the UE plus the delay period. For example, if the duration of the DRX cycle of the UE 120 is 40 ms (e.g., when the UE 120 is using VoNR services) and the delay period is 10 ms, the duration of the HARQ state discard timer may be longer than 50 ms (e.g., at least 40 ms + 10 ms = at least 50 ms).

[0075] In some aspects, UE 120 may calculate the duration of the HARQ state discard timer. For example, UE 120 may determine the duration of the DRX cycle of UE 120 and may calculate the duration of the HARQ state discard timer based at least in part on the duration of the DRX cycle of UE 120 (e.g., in the manner described in the above examples).

[0076] In some aspects, the duration of the HARQ state discard timer may be a fixed value. For example, in a scenario where the UE 120 is not configured with a DRX cycle or when the UE is configured to communicate using a specific SCS (e.g., a 120kHz SCS), the duration of the HARQ discard timer may be a fixed value of X ms. In some aspects, the value of X may be based at least in part on a delay associated with one or more previous transmissions sent or received by the UE 120.

[0077] In some aspects, the duration of the HARQ state discard timer may be based at least in part on one or more conditions other than the duration of the DRX cycle of the UE 120. For example, in some aspects, the one or more conditions may include the behavior of the network node 110 with respect to communicating with the UE 120. For example, the UE 120 may be configured with a relatively long duration of the HARQ state discard timer. Here, when the corresponding PDCCH is received before the HARQ state discard timer expires, the UE 120 may attempt to decode the shared channel communication as a retransmission. If the decoding fails (indicating that the duration of the HARQ state discard timer is too long), the UE 120 may reprocess the shared channel communication as a new transmission. If the UE 120 subsequently successfully decodes the shared channel communication, the UE 120 may shorten the duration of the HARQ state discard timer (e.g., shorten the configured amount of time). In this way, the duration of the HARQ state discard timer may be dynamically adjusted over time until an appropriate value for a particular network node 110 is reached.

[0078] As another example, in some aspects, one or more conditions may include a traffic pattern associated with UE 120. For example, if UE 120 has a relatively full buffer, UE 120 may use a relatively short duration for the HARQ state discard timer, and conversely, if UE 120 has a relatively empty buffer, the UE may use a relatively long duration for the HARQ state discard timer. Here, a relatively full buffer may prevent UE 120 from entering a sleep state, and thus network node 110 has an opportunity to perform a retransmission, which means that a relatively short duration may be used. Conversely, a relatively empty buffer may allow UE 120 to enter a sleep state, and thus, network node 110 may have less chance of having a retransmission successfully received by UE 120, and thus a longer duration may be used. In some aspects, the duration of the HARQ state discard timer may be based at least in part on the traffic periodicity. For example, in some aspects, the duration of the HARQ state discard timer may be selected to be a value equal to a multiple of the traffic periodicity (e.g., minus a delay period).

[0079] As another example, in some aspects, the one or more conditions may include a HARQ RTT associated with the network node 110. For example, as mentioned above, HARQ is asynchronous, and how a given HARQ retransmission is performed depends on the given network node 110 (e.g., a first network node 110 may be able to send a retransmission within 8 time slots after an initial transmission, while a second network node 110 may need 14 time slots after the initial transmission before being able to send a retransmission). In some aspects, the UE 120 may measure the HARQ RTT or determine the HARQ RTT configured by the radio resource control (RRC) for DRX (e.g., drx-HARQ-RTT-TimerDL and drx-HARQ-RTT-TimerUL), and then set the duration of the HARQ state discard timer according to the HARQ RTT. In some aspects, if the DRX on duration timer (i.e., the amount of time that the UE 120 is awake in each DRX cycle regardless of whether the UE 120 is scheduled) is longer than the HARQ RTT, the UE 120 may determine that there is sufficient opportunity for retransmission within the first DRX awake period that occurs at the time of the first PDCCH communication. In this scenario, the UE may select N as a value of 1. If the network is determined to be under a relatively heavy load, the network node 110 may not be able to schedule the UE 120 in the next DRX cycle, and therefore the UE 120 may select N as a value greater than 1.

[0080] As another example, in some aspects, one or more conditions may include a sleep state of UE 120. For example, the first opportunity for retransmission is within the HARQ RTT. Thus, if UE 120 is not in the sleep state at the HARQ RTT and network node 110 does not transmit to UE 120, this means that network node 110 had an opportunity to send a retransmission to UE 120, but did not do so. Here, if UE 120 enters the sleep state after the HARQ RTT, it may be determined that network node 110 does not want to schedule UE 120 with retransmissions. Thus, in some aspects, the duration of the HARQ state discard timer may be based at least in part on whether UE 120 is in the sleep state. In fact, in such a scenario, the duration of the HARQ state discard timer is set to zero. In contrast, the HARQ state is based at least in part on whether UE 120 has entered the sleep state after the HARQ RTT.

[0081] As another example, in some aspects, the one or more conditions may include an SCS associated with the UE 120. That is, in some aspects, the duration of the HARQ state discard timer may be based at least in part on the SCS used by the UE 120. Notably, latency decreases as the SCS increases (time slots become shorter in time). Thus, if the value of the HARQ state discard timer is expressed in milliseconds, the value of the HARQ state discard timer becomes smaller as the SCS increases. Conversely, if the units of the HARQ state discard timer are expressed in time slots, the duration of the HARQ state discard timer may remain the same regardless of the SCS used by the UE 120.

[0082] As another example, in some aspects the one or more conditions may include a cell type associated with network node 110. That is, in some aspects the duration of the HARQ state discard timer may be based at least in part on the type of cell in which network node 110 is communicating with UE 120.

[0083] As another example, in some aspects, the one or more conditions may include an application type associated with the UE traffic. That is, in some aspects, the duration of the HARQ state discard timer may be based at least in part on the application type associated with the traffic of UE 120. For example, if UE 120 is using a VoNR application, the duration of the HARQ state discard timer may be based at least in part on a DRX cycle duration used by UE 120 in association with the VoNR application.

[0084] As another example, in some aspects, the one or more conditions may include a set of QoS characteristics associated with the UE traffic. That is, in some aspects, the duration of the HARQ state discard timer may be based at least in part on the QoS characteristics of the traffic associated with the UE 120.

[0085] As another example, in some aspects, the one or more conditions may include a QoS identifier associated with the UE traffic (e.g., a 5G NR QoS identifier (5QI) associated with a traffic flow of UE 120). That is, in some aspects, the duration of the HARQ state discard timer may be based at least in part on the QoS identifier associated with the UE traffic.

[0086] As another example, in some aspects, the one or more conditions may include a network type associated with the network node 110. That is, in some aspects, the duration of the HARQ state discard timer may be based at least in part on the network type associated with the network node 110. For example, in a scenario where the network node 110 is included in a terrestrial network (TN), the RTT (and therefore the latency) may be relatively short, and thus the duration of the HARQ state discard timer may be relatively short. Conversely, in a scenario where the network node 110 is included in a non-terrestrial network (NTN), the RTT (and therefore the latency) may be relatively long, and thus the duration of the HARQ state discard timer may be relatively long.

[0087] In some aspects, as mentioned above, the duration of the HARQ state discard timer is also based at least in part on the delay period. The delay period can be used to take into account network characteristics or UE characteristics that may cause delays in the transmission and reception of communications between the network node 110 and the UE 120. For example, the delay period can be used to take into account scheduling delays, UE wake-up delays, jitter, or semi-persistent scheduling (SPS) grant periods. Therefore, in some aspects, the delay period can be based at least in part on scheduling delays (e.g., expected or estimated scheduling delays), UE wake-up delays (e.g., expected or estimated UE wake-up delays), jitter (e.g., expected or estimated jitter), or SPS grant periods.

[0088] In some aspects, the UE 120 may determine the duration of the HARQ state discard timer based at least in part on comparing a first HARQ state discard timer value (e.g., a HARQ state discard timer value calculated by the UE 120) with a second HARQ state discard timer value (e.g., a HARQ state discard timer value configured on the UE 120 by the network node 110). For example, as described herein, the UE 120 may determine the first HARQ state discard timer duration value based at least in part on one or more conditions. In one example, the UE 120 determines the first HARQ state discard timer value to be 70 ms (e.g., based at least in part on the DRX cycle duration of the UE 120). Next, the UE 120 determines whether the first HARQ state discard timer duration value is less than or equal to the second HARQ state discard timer duration value. In this example, the second HARQ state discard timer value is 256 ms (e.g., a HARQ state discard timer value configured on the UE 120 by the network node 110). Here, the UE 120 may identify the duration of the HARQ state as the first HARQ state discard timer duration value (e.g., 70 ms) based at least in part on determining that the first HARQ state discard timer duration value is less than or equal to the second HARQ state discard timer duration value (e.g., 256 ms). Thus, in some aspects, the UE 120 may identify a minimum of the first HARQ state discard timer value and the second HARQ state discard timer value and determine the HARQ state discard timer value as the minimum of the first HARQ state discard timer value and the second HARQ state discard timer value.

[0089] In some aspects, the UE 120 may set the HARQ state discard timer according to the duration of the HARQ state discard timer. That is, the UE 120 may determine the duration of the HARQ state discard timer and may set the HARQ state discard timer so that the HARQ state discard timer is configured to use the HARQ state discard timer value determined by the UE 120.

[0090] In some aspects, UE 120 may receive a configuration indicating the duration of the HARQ state discard timer from network node 110. That is, in some aspects, one or more conditions include a configuration received from network node 110. In other words, in some aspects, network node 110 may configure UE 120 with a value for the HARQ state discard timer. In some aspects, UE 120 may be configured with separate (e.g., different) values ​​for uplink HARQ and downlink HARQ. In some aspects, the configuration of UE 120 by network node 110 may enable the value best suited for the specific operation of the network to be used for the HARQ state discard timer.

[0091] In some aspects, the UE 120 may discard the HARQ state in association with the HARQ state discard timer and in association with checking the RV. For example, the UE 120 may check the expiration of the HARQ state discard timer only when the RV is zero (RV=0), the NDI is the same as the previous NDI, and the non-reserved MCS meets the MCS threshold. In some aspects, the UE 120 may discard the HARQ state in association with the HARQ state discard timer and in association with a previously received DCI having a non-reserved MCS and an NDI value equal to the current NDI value. In some aspects, the UE 120 may discard the HARQ state in association with the HARQ state discard timer and in association with a network node 110 that has previously used a RV value not equal to zero (RV!=0) for new transmission.

[0092] In some aspects, the UE 120 may discard the HARQ state in association with checking one or more parameters (e.g., MCS, RV, etc.) from the received DCI and one or more other resource allocation parameters (such as the number of symbols or the number of RBs). For example, if the RV is 0 or if the RV! = 0, but the MCS fails to meet (e.g., is lower than) a threshold, and the resource allocation parameter meets the threshold, the UE 120 may determine that the transport block (TB) is self-decodable and may discard the HARQ state in association with the HARQ state discard timer. In an alternative example, if the RV! = 0 and the MCS meets (e.g., is equal to or higher than) a threshold, the UE 120 may determine that the TB is not self-decodable and may avoid discarding the HARQ state.

[0093] In some aspects, UE 120 may selectively discard the HARQ state in association with the DCI misdetection information. The DCI misdetection information may indicate a likelihood that UE 120 did not receive the first DCI from network node 110. For example, in association with UE 120 determining that the likelihood is high (e.g., greater than a threshold), UE 120 may determine to discard the HARQ state. Alternatively, in association with UE 120 determining that the likelihood is low (e.g., not greater than a threshold), UE 120 may determine not to discard the HARQ state.

[0094] In some aspects, the DCI misdetection information may be associated with a PDCCH decoding metric, such as an energy parameter (e.g., detected energy), a cyclic redundancy check (CRC) parameter (e.g., CRC failure), or a pruning parameter, etc. In some aspects, the DCI misdetection information may be associated with a measurement gap. For example, the UE 120 may determine whether a measurement gap has occurred, and may determine whether the network node 110 is performing scheduling during the measurement gap. In some aspects, the DCI misdetection information may be associated with a pattern of one or more previous RVs. For example, the UE 120 may determine whether a transmission will be a retransmission or a new transmission in association with a pattern of one or more previous RVs.

[0095] In some aspects, after receiving a first PDCCH communication (e.g., a PDCCH communication received as indicated by reference numeral 302) and starting a HARQ state discard timer, the UE 120 may receive a second PDCCH communication having an NDI value for a HARQ process (e.g., the same NDI value, such as 0 or 1). In some aspects, if the second PDCCH communication is received before the HARQ state discard timer expires, the UE 120 may process a shared channel communication (e.g., a PDSCH communication) scheduled by the second PDCCH communication as a retransmission. That is, the UE 120 may process the shared channel communication as a retransmission based at least in part on receiving the second PDCCH communication before the HARQ state discard timer expires.

[0096] Conversely, if a second PDCCH communication is received after the HARQ state discard timer expires, the UE 120 may process the shared channel communication scheduled by the second PDCCH communication as a new transmission. That is, the UE 120 may process the shared channel communication as a new transmission based at least in part on receiving the second PDCCH communication after the HARQ state discard timer expires.

[0097] Figure 3B 3 is a diagram illustrating an example 350 in which UE 120 processes a shared channel communication as a new transmission based at least in part on receiving a second PDCCH communication after expiration of a HARQ state discard timer. Figure 3BAs shown by reference numeral 352, at a first point in time (eg, 0 ms), UE 120 receives a first PDCCH communication (eg, a new downlink grant) having a first NDI value (eg, NDI 0) for a HARQ process (eg, HARQ process 1).

[0098] As indicated by reference numeral 354, UE 120 starts a HARQ state discard timer based at least in part on receiving the first PDCCH communication. Figure 3B , the duration of the HARQ state discard timer is 70 ms (e.g., twice the 40 ms duration of the DRX cycle duration of UE 120 minus a 10 ms delay period). As shown by reference numeral 356, at a second point in time (e.g., 40 ms), UE 120 misses a PDCCH communication (e.g., a new downlink grant) having a second NDI value (e.g., NDI 1) for the HARQ process.

[0099] As indicated by reference numeral 358, at a third point in time (e.g., 80 ms), UE 120 receives a second PDCCH communication (e.g., a new downlink grant) having a first NDI value (e.g., NDI 0) for the HARQ process. Figure 3B , the HARQ state discard timer expired before the second PDCCH communication was received, and therefore, the UE 120 processes the PDSCH communication associated with the second PDCCH communication as a new transmission based at least in part on receiving the second PDCCH communication after the expiration of the HARQ state discard timer. Notably, in this example, if the duration of the HARQ state discard timer is longer than twice the DRX cycle duration (or if the UE 120 maintains the HARQ state indefinitely), the UE 120 erroneously discards the PDSCH communication associated with the second PDCCH communication.

[0100] As indicated above, Figure 3A and Figure 3B are provided as examples. Other examples can be found in the Figure 3A and Figure 3B Different than described.

[0101] Figure 4 is a diagram illustrating an example process 400 performed, for example, by a UE in accordance with the present disclosure. Example process 400 is an example of a UE (eg, UE 120) performing operations associated with techniques for HARQ state discard.

[0102] like Figure 4As shown, in some aspects, process 400 may include receiving a first PDCCH communication having an NDI value for a HARQ process (block 410). For example, as described above, a UE (e.g., using Figure 5 The communication manager 140 and / or receiving component 502 depicted in FIG. 5 may receive a first PDCCH communication having an NDI value for a HARQ process.

[0103] like Figure 4 As further shown, in some aspects, process 400 may include starting a HARQ state discard timer based at least in part on receiving the first PDCCH communication, wherein a duration of the HARQ state discard timer is based at least in part on one or more conditions (block 420). For example, as described above, a UE (e.g., using Figure 5 The communication manager 140 and / or HARQ component 508 depicted in FIG. 1 may start a HARQ state discard timer based at least in part on receiving the first PDCCH communication, wherein a duration of the HARQ state discard timer is based at least in part on one or more conditions.

[0104] Process 400 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0105] In a first aspect, the one or more conditions include a duration of a DRX cycle of the UE.

[0106] In a second aspect, alone or in combination with the first aspect, a duration of a HARQ state discard timer is longer than the duration of the DRX cycle of the UE.

[0107] In a third aspect, alone or in combination with one or more of the first and second aspects, the duration of the HARQ state discard timer is shorter than N times the duration of the DRX cycle of the UE, where N is greater than or equal to 2.

[0108] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the duration of the HARQ state discard timer is approximately equal to twice the duration of the DRX cycle of the UE minus a delay period.

[0109] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, a duration of the HARQ state discard timer is greater than or equal to a duration of a DRX cycle of the UE plus a delay period.

[0110] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 400 includes: determining the duration of the DRX cycle of the UE; and calculating the duration of the HARQ state discard timer based at least in part on the duration of the DRX cycle of the UE.

[0111] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the duration of the DRX cycle of the UE is 40 ms, and the duration of the HARQ state discard timer is 70 ms.

[0112] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the duration of the HARQ state discard timer is also based at least in part on a delay period.

[0113] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the duration of the delay period is based at least in part on at least one of: scheduling delay, UE wake-up delay, jitter, or SPS grant period.

[0114] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 400 includes: receiving a second PDCCH communication having the NDI value for the HARQ process, the second PDCCH communication being received before the expiration of the HARQ state discard timer; and processing a shared channel communication scheduled by the second PDCCH communication as a retransmission based at least in part on receiving the second PDCCH communication before the expiration of the HARQ state discard timer.

[0115] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 400 includes: receiving a second PDCCH communication having the NDI value for the HARQ process, the second PDCCH communication being received after the HARQ state discard timer expires; and processing a shared channel communication scheduled by the second PDCCH communication as a new transmission based at least in part on receiving the second PDCCH communication after the HARQ state discard timer expires.

[0116] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, process 400 includes: determining a first HARQ state discard timer duration value based at least in part on the one or more conditions; determining that the first HARQ state discard timer duration value is less than or equal to a second HARQ state discard timer duration value; and identifying the duration of the HARQ state as the first HARQ state discard timer duration value based at least in part on the determination that the first HARQ state discard timer duration value is less than or equal to the second HARQ state discard timer duration value.

[0117] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, process 400 includes: setting the HARQ state discard timer according to the duration of the HARQ state discard timer.

[0118] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the one or more conditions include behavior of the network node with respect to communicating with the UE.

[0119] In a fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, the one or more conditions include a traffic pattern associated with the UE.

[0120] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the one or more conditions include a HARQ RTT associated with the network node.

[0121] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the one or more conditions include a sleep state of the UE.

[0122] In an eighteenth aspect, either alone or in combination with one or more of the first to seventeenth aspects, the one or more conditions include a subcarrier spacing associated with the UE.

[0123] In a nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the one or more conditions include a cell type associated with the network node.

[0124] In a twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, the one or more conditions include an application type associated with the UE service.

[0125] In a twenty-first aspect, either alone or in combination with one or more of the first to twentieth aspects, the one or more conditions include a set of quality of service characteristics associated with the UE traffic.

[0126] In a twenty-second aspect, either alone or in combination with one or more of the first to twenty-first aspects, the one or more conditions include a quality of service identifier associated with the UE traffic.

[0127] In a twenty-third aspect, either alone or in combination with one or more of the first to twenty-second aspects, the one or more conditions comprise a configuration received from a network node.

[0128] although Figure 4 An example block diagram of process 400 is shown, but in some aspects, process 400 may include Figure 4 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 400. Additionally or alternatively, two or more of the blocks in the process 400 may be performed in parallel.

[0129] Figure 5 5 is a diagram of an example apparatus 500 for wireless communication according to the present disclosure. Apparatus 500 may be a UE, or a UE may include apparatus 500. In some aspects, apparatus 500 includes a receiving component 502 and a transmitting component 504, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 500 may communicate with another apparatus 506 (such as a UE, a base station, or another wireless communication device) using receiving component 502 and transmitting component 504. As further shown, apparatus 500 may include a communication manager 140. Communication manager 140 may include a HARQ component 508, etc.

[0130] In some aspects, the apparatus 500 may be configured to perform Figure 3A and Figure 3B Additionally or alternatively, the apparatus 500 may be configured to perform one or more processes described herein, such as Figure 4 In some aspects, the apparatus 500 and / or Figure 5 One or more of the components shown may include a combination of Figure 2 Additionally or alternatively, Figure 5 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0131] The receiving component 502 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 506. The receiving component 502 may provide the received communications to one or more other components of the device 500. In some aspects, the receiving component 502 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 500. In some aspects, the receiving component 502 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0132] Transmit component 504 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 506. In some aspects, one or more other components of device 500 may generate communications and may provide the generated communications to transmit component 504 for transmission to device 506. In some aspects, transmit component 504 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 506. In some aspects, transmit component 504 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 504 can be co-located with the receive component 502 in a transceiver.

[0133] Receiving component 502 can receive a first PDCCH communication having an NDI value for a HARQ process. HARQ component 508 can start a HARQ state discard timer based at least in part on receiving the first PDCCH communication, wherein a duration of the HARQ state discard timer is based at least in part on one or more conditions.

[0134] The HARQ component 508 can determine a duration of a DRX cycle for the UE. The HARQ component 508 can calculate the duration of the HARQ state discard timer based at least in part on the duration of the DRX cycle for the UE.

[0135] The receiving component 502 may receive a second PDCCH communication having the NDI value for the HARQ process, the second PDCCH communication being received before the HARQ state discard timer expires. The HARQ component 508 may process a shared channel communication scheduled by the second PDCCH communication as a retransmission based at least in part on receiving the second PDCCH communication before the HARQ state discard timer expires.

[0136] The receiving component 502 may receive a second PDCCH communication having the NDI value for the HARQ process, the second PDCCH communication being received after the HARQ state discard timer expires. The HARQ component 508 may process a shared channel communication scheduled by the second PDCCH communication as a new transmission based at least in part on receiving the second PDCCH communication after the HARQ state discard timer expires.

[0137] The HARQ component 508 may determine a first HARQ state discard timer duration value based at least in part on the one or more conditions. The HARQ component 508 may determine that the first HARQ state discard timer duration value is less than or equal to a second HARQ state discard timer duration value. The HARQ component 508 may identify the duration of the HARQ state as the first HARQ state discard timer duration value based at least in part on the determination that the first HARQ state discard timer duration value is less than or equal to the second HARQ state discard timer duration value.

[0138] The HARQ component 508 can set the HARQ state discard timer according to the duration of the HARQ state discard timer.

[0139] Figure 5 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 5 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 5 Two or more components shown may be implemented in a single component, or Figure 5 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 5 The component set (one or more components) shown may be described as being executable by Figure 5 Another component shown is a collection of one or more functions performed.

[0140] The following provides an overview of some aspects of the disclosure:

[0141] Aspect 1: A method of wireless communication performed by a UE, the method comprising: receiving a first PDCCH communication having an NDI value for a HARQ process; and starting a HARQ state discard timer based at least in part on receiving the first PDCCH communication, wherein the duration of the HARQ state discard timer is based at least in part on one or more conditions.

[0142] Aspect 2: The method according to aspect 1, wherein the one or more conditions include the duration of the DRX cycle of the UE.

[0143] Aspect 3: The method according to aspect 2, wherein the duration of the HARQ state discard timer is longer than the duration of the DRX cycle of the UE.

[0144] Aspect 4: The method according to any one of Aspects 2 to 3, wherein the duration of the HARQ state discard timer is shorter than N times the duration of the DRX cycle of the UE, where N is greater than or equal to 2.

[0145] Aspect 5: The method according to any one of aspects 2 to 4, wherein the duration of the HARQ state discard timer is approximately equal to twice the duration of the DRX cycle of the UE minus a delay period.

[0146] Aspect 6: The method according to any one of aspects 2 to 5, wherein the duration of the HARQ state discard timer is greater than or equal to the duration of the DRX cycle of the UE plus a delay period.

[0147] Aspect 7: According to the method described in any one of Aspects 2 to 6, the method also includes: determining the duration of the DRX cycle of the UE; and calculating the duration of the HARQ state discard timer based at least in part on the duration of the DRX cycle of the UE.

[0148] Aspect 8: The method according to any one of aspects 2 to 7, wherein the duration of the DRX cycle of the UE is 40 ms, and the duration of the HARQ state discard timer is 70 ms.

[0149] Aspect 9: The method according to any one of aspects 1 to 8, wherein the duration of the HARQ state discard timer is also based at least in part on a delay period.

[0150] Aspect 10: The method according to aspect 9, wherein the duration of the delay period is based at least in part on at least one of: scheduling delay, UE wake-up delay, jitter, or SPS grant period.

[0151] Aspect 11: According to the method described in any one of Aspects 1 to 10, the method further includes: receiving a second PDCCH communication having the NDI value for the HARQ process, the second PDCCH communication being received before the expiration of the HARQ state discard timer; and processing the shared channel communication scheduled by the second PDCCH communication as a retransmission based at least in part on receiving the second PDCCH communication before the expiration of the HARQ state discard timer.

[0152] Aspect 12: According to the method described in any one of Aspects 1 to 10, the method further includes: receiving a second PDCCH communication having the NDI value for the HARQ process, the second PDCCH communication being received after the HARQ state discard timer expires; and processing the shared channel communication scheduled by the second PDCCH communication as a new transmission based at least in part on receiving the second PDCCH communication after the HARQ state discard timer expires.

[0153] Aspect 13: According to the method described in any one of Aspects 1 to 12, the method further includes: determining a first HARQ state discard timer duration value based at least in part on the one or more conditions; determining that the first HARQ state discard timer duration value is less than or equal to a second HARQ state discard timer duration value; and identifying the duration of the HARQ state as the first HARQ state discard timer duration value based at least in part on determining that the first HARQ state discard timer duration value is less than or equal to the second HARQ state discard timer duration value.

[0154] Aspect 14: According to the method according to any one of aspects 1 to 13, the method further includes: setting the HARQ state discard timer according to the duration of the HARQ state discard timer.

[0155] Aspect 15: The method according to any one of aspects 1 to 14, wherein the one or more conditions include a behavior of a network node with respect to communicating with the UE.

[0156] Aspect 16: The method according to any one of aspects 1 to 15, wherein the one or more conditions include a traffic pattern associated with the UE.

[0157] Aspect 17: The method according to any one of aspects 1 to 16, wherein the one or more conditions include a HARQ RTT associated with the network node.

[0158] Aspect 18: The method according to any one of aspects 1 to 17, wherein the one or more conditions include a sleep state of the UE.

[0159] Aspect 19: A method according to any one of Aspects 1 to 18, wherein the one or more conditions include a subcarrier spacing associated with the UE.

[0160] Aspect 20: The method according to any one of aspects 1 to 19, wherein the one or more conditions include a cell type associated with the network node.

[0161] Aspect 21: A method according to any one of aspects 1 to 20, wherein the one or more conditions include an application type associated with the UE service.

[0162] Aspect 22: The method according to any one of aspects 1 to 21, wherein the one or more conditions include a set of quality of service characteristics associated with UE traffic.

[0163] Aspect 23: A method according to any one of aspects 1 to 22, wherein the one or more conditions include a quality of service identifier associated with the UE traffic.

[0164] Aspect 24: The method according to any one of aspects 1 to 23, wherein the one or more conditions include a configuration received from a network node.

[0165] Aspect 25: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 24.

[0166] Aspect 26: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 24.

[0167] Aspect 27: An apparatus for wireless communication, the apparatus comprising: at least one component for performing the method according to one or more of aspects 1 to 24.

[0168] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 24.

[0169] Aspect 29: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 24.

[0170] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0171] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, or a combination of hardware and software. As used herein, the phrase "based on" is intended to be broadly interpreted as "based at least in part on". As used herein, depending on the context, "satisfying a threshold value" may refer to a value greater than a threshold value, greater than or equal to a threshold value, less than a threshold value, less than or equal to a threshold value, equal to a threshold value, not equal to a threshold value, etc. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of these items (including a single member). As an example, "at least one of a, b, or c" is intended to cover: a, b, c, a+b, a+c, b+c, and a+b+c.

[0172] In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the term "group" and "group" are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items), and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" and similar terms are intended to be open terms that do not limit the elements (e.g., element "including" A can also contain B) that they modify. In addition, as used herein, the term "or" is intended to be inclusive when used in a sequence, and can be used interchangeably with "and / or", unless otherwise expressly stated (e.g., in the case of being used in combination with "any one of" or "only one of").

[0173] The various illustrative logics, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the various aspects disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been generally described in terms of functionality and is illustrated in the various illustrative components, blocks, modules, circuits, and processes described herein. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0174] The hardware and data processing devices for implementing the various illustrative logics, logic blocks, modules and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed using a general purpose single-chip or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic component, a discrete hardware component or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration. In some aspects, specific processes and methods may be performed by circuits dedicated to a given function.

[0175] In one or more aspects, the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed in this specification and their structural equivalents, or any combination thereof. Aspects of the subject matter described in this specification may also be implemented as one or more computer programs (e.g., one or more modules of computer program instructions) encoded on computer storage media to be executed by a data processing apparatus or to control the operation of the data processing apparatus.

[0176] If implemented in software, the function may be stored as one or more instructions or codes on a computer-readable medium or sent via a computer-readable medium. The process of the method or algorithm disclosed herein may be implemented in a processor executable software module that may reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, and communication media include any medium that can realize the transfer of a computer program from one place to another. Storage media can be any available medium that a computer can access. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of an instruction or data structure and can be accessed by a computer. In addition, any connection may be appropriately referred to as a computer-readable medium. Disks and optical disks as used herein include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks and blue-ray disks, wherein disks generally reproduce data magnetically, and optical disks reproduce data optically with lasers. The combination of media described herein should also be included in the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as a code and instruction set, or any combination of code and instruction sets, on a machine-readable medium or computer-readable medium, which may be incorporated into a computer program product.

[0177] Various modifications to the various aspects described in this disclosure may be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the spirit or scope of the disclosure. Therefore, the claims are not intended to be limited to the aspects shown herein, but should be granted the broadest scope consistent with the disclosure, the principles and novel features disclosed herein.

[0178] Additionally, one of ordinary skill in the art will readily recognize that the terms "upper" and "lower" are sometimes used for ease of describing the drawings and indicate relative positions on a correctly oriented page corresponding to the orientation of the drawings, and may not reflect the correct orientation of any device as implemented.

[0179] Certain features described in this specification in the context of independent aspects may also be implemented in combination in a single aspect. Conversely, various features described in the context of a single aspect may also be implemented in multiple aspects individually or in any suitable subcombination. In addition, although features may be described as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination may be removed from the combination in some cases, and a claimed combination may be directed to a subcombination, or a variation of a subcombination.

[0180] Similarly, although the operations are depicted in a specific order in the accompanying drawings, this should not be understood as requiring such operations to be performed in the specific order shown or in a sequential order, or to perform all illustrated operations to achieve the desired result. In addition, the accompanying drawings can schematically depict one or more example processes in the form of a flow chart. However, other operations not depicted can be incorporated into the example processes schematically illustrated. For example, one or more additional operations can be performed before, after, at the same time, or between any operations in the illustrated operations. In some environments, multitasking and parallel processing are advantageous. In addition, the separation of various system components in the various aspects described should not be understood as requiring such separation in all aspects, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, other aspects also fall within the scope of the appended claims. In some cases, the actions recorded in the claims can be performed in different orders and still achieve the desired result.

Claims

1. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a first physical downlink control channel (PDCCH) communication having a new data indicator (NDI) value for a hybrid automatic repeat request (HARQ) process; as well as starting a HARQ state discard timer based at least in part on receiving the first PDCCH communication, Wherein a duration of the HARQ state discard timer is based at least in part on one or more conditions.

2. The method of claim 1, wherein the one or more conditions include a duration of a discontinuous reception (DRX) cycle of the UE. 3 . The method according to claim 2 , wherein the duration of the HARQ state discard timer is longer than the duration of the DRX cycle of the UE. 4 . The method of claim 2 , wherein the duration of the HARQ state discard timer is shorter than N times the duration of the DRX cycle of the UE, wherein N is greater than or equal to 2.

5. The method of claim 2, wherein the duration of the HARQ state discard timer is approximately equal to twice the duration of the DRX cycle of the UE minus a delay period.

6. The method of claim 2, wherein the duration of the HARQ state discard timer is greater than or equal to the duration of the DRX cycle of the UE plus a delay period.

7. The method according to claim 2, further comprising: determining the duration of the DRX cycle of the UE; as well as The duration of the HARQ state discard timer is calculated based at least in part on the duration of the DRX cycle of the UE.

8. The method of claim 2, wherein the duration of the DRX cycle of the UE is 40 milliseconds (ms), and the duration of the HARQ state discard timer is 70 ms.

9. The method of claim 1 , wherein the duration of the HARQ state discard timer is also based at least in part on a delay period, wherein the duration of the delay period is based at least in part on at least one of: a scheduling delay, a UE wake-up delay, jitter, or a semi-persistent scheduling (SPS) grant period.

10. The method according to claim 1, further comprising: receiving a second PDCCH communication having the NDI value for the HARQ process, the second PDCCH communication being received before expiration of the HARQ state discard timer, and A shared channel communication scheduled by the second PDCCH communication is processed as a retransmission based at least in part on receiving the second PDCCH communication prior to expiration of the HARQ state discard timer.

11. The method according to claim 1, further comprising: receiving a second PDCCH communication having the NDI value for the HARQ process, the second PDCCH communication being received after expiration of the HARQ state discard timer, and A shared channel communication scheduled by the second PDCCH communication is processed as a new transmission based at least in part on receiving the second PDCCH communication after expiration of the HARQ state discard timer.

12. The method according to claim 1, further comprising: determining a first HARQ state discard timer duration value based at least in part on the one or more conditions; Determining that the first HARQ state discard timer duration value is less than or equal to the second HARQ state discard timer duration value; and The duration of the HARQ state is identified as the first HARQ state discard timer duration value based at least in part on determining that the first HARQ state discard timer duration value is less than or equal to a second HARQ state discard timer duration value.

13. The method according to claim 1, further comprising: The HARQ state discard timer is set according to the duration of the HARQ state discard timer.

14. The method of claim 1, wherein the one or more conditions include at least one of the following: the behavior of the network node with respect to communicating with the UE, a service mode associated with the UE, a HARQ round trip time (RTT) associated with the network node, the sleep state of the UE, a subcarrier spacing associated with the UE, a cell type associated with the network node, The application type associated with the UE service, a set of quality of service characteristics associated with the UE service, a quality of service identifier associated with the UE service, or A configuration is received from the network node.

15. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a first physical downlink control channel (PDCCH) communication having a new data indicator (NDI) value for a hybrid automatic repeat request (HARQ) process; as well as A HARQ state discard timer is started based at least in part on receiving the first PDCCH communication, wherein a duration of the HARQ state discard timer is based at least in part on one or more conditions.

16. The UE of claim 15, wherein the one or more conditions include a duration of a discontinuous reception (DRX) cycle of the UE.

17. The UE of claim 16, wherein the duration of the HARQ state discard timer is longer than the duration of the DRX cycle of the UE. 18 . The UE of claim 16 , wherein the duration of the HARQ state discard timer is shorter than N times the duration of the DRX cycle of the UE, wherein N is greater than or equal to 2.

19. The UE of claim 16, wherein the duration of the HARQ state discard timer is approximately equal to twice the duration of the DRX cycle of the UE minus a delay period.

20. The UE of claim 16, wherein the duration of the HARQ state discard timer is greater than or equal to the duration of the DRX cycle of the UE plus a delay period.

21. The UE of claim 16, wherein the one or more processors are further configured to: determining the duration of the DRX cycle of the UE; and The duration of the HARQ state discard timer is calculated based at least in part on the duration of the DRX cycle of the UE.

22. The UE of claim 16, wherein the duration of the DRX cycle of the UE is 40 milliseconds (ms), and the duration of the HARQ state discard timer is 70 ms.

23. The UE of claim 15, wherein the duration of the HARQ state discard timer is also based at least in part on a delay period, wherein the duration of the delay period is based at least in part on at least one of: a scheduling delay, a UE wake-up delay, jitter, or a semi-persistent scheduling (SPS) grant period.

24. The UE of claim 15, wherein the one or more processors are further configured to: receiving a second PDCCH communication having the NDI value for the HARQ process, the second PDCCH communication being received before expiration of the HARQ state discard timer, and A shared channel communication scheduled by the second PDCCH communication is processed as a retransmission based at least in part on receiving the second PDCCH communication prior to expiration of the HARQ state discard timer.

25. The UE of claim 15, wherein the one or more processors are further configured to: receiving a second PDCCH communication having the NDI value for the HARQ process, the second PDCCH communication being received after expiration of the HARQ state discard timer, and A shared channel communication scheduled by the second PDCCH communication is processed as a new transmission based at least in part on receiving the second PDCCH communication after expiration of the HARQ state discard timer.

26. The UE of claim 15, wherein the one or more processors are further configured to: determining a first HARQ state discard timer duration value based at least in part on the one or more conditions; Determining that the first HARQ state discard timer duration value is less than or equal to the second HARQ state discard timer duration value; and The duration of the HARQ state is identified as the first HARQ state discard timer duration value based at least in part on determining that the first HARQ state discard timer duration value is less than or equal to a second HARQ state discard timer duration value.

27. The UE of claim 15, wherein the one or more processors are further configured to set the HARQ state discard timer according to the duration of the HARQ state discard timer.

28. The UE of claim 15, wherein the one or more conditions include at least one of the following: the behavior of the network node with respect to communicating with the UE, a service mode associated with the UE, a HARQ round trip time (RTT) associated with the network node, the sleep state of the UE, a subcarrier spacing associated with the UE, a cell type associated with the network node, The application type associated with the UE service, a set of quality of service characteristics associated with the UE service, a quality of service identifier associated with the UE service, or A configuration is received from the network node.

29. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: receiving a first physical downlink control channel (PDCCH) communication having a new data indicator (NDI) value for a hybrid automatic repeat request (HARQ) process; as well as A HARQ state discard timer is started based at least in part on receiving the first PDCCH communication, wherein a duration of the HARQ state discard timer is based at least in part on one or more conditions.

30. An apparatus for wireless communication, the apparatus comprising: means for receiving a first physical downlink control channel (PDCCH) communication having a new data indicator (NDI) value for a hybrid automatic repeat request (HARQ) process; and means for starting a HARQ state discard timer based at least in part on receiving the first PDCCH communication, Wherein a duration of the HARQ state discard timer is based at least in part on one or more conditions.

Images