WO2023043570A1 - Temporisateurs de demande de répétition automatique hybride (harq) à renvoi de harq d'un seul coup - Google Patents

Temporisateurs de demande de répétition automatique hybride (harq) à renvoi de harq d'un seul coup Download PDF

Info

Publication number
WO2023043570A1
WO2023043570A1 PCT/US2022/040811 US2022040811W WO2023043570A1 WO 2023043570 A1 WO2023043570 A1 WO 2023043570A1 US 2022040811 W US2022040811 W US 2022040811W WO 2023043570 A1 WO2023043570 A1 WO 2023043570A1
Authority
WO
WIPO (PCT)
Prior art keywords
harq
processes
condition
shot
satisfied
Prior art date
Application number
PCT/US2022/040811
Other languages
English (en)
Inventor
Ozcan Ozturk
Xiaoxia Zhang
Mostafa KHOSHNEVISAN
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US17/841,548 external-priority patent/US20230084318A1/en
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to CN202280060949.3A priority Critical patent/CN117917032A/zh
Publication of WO2023043570A1 publication Critical patent/WO2023043570A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling

Definitions

  • the present disclosure relates generally to wireless communications, and more specifically to hybrid automatic repeat request (HARQ) timers with one shot HARQ feedback.
  • HARQ hybrid automatic repeat request
  • Wireless communications systems are widely deployed to provide various telecommunications services such as telephony, video, data, messaging, and broadcasts.
  • Typical wireless communications systems may employ multiple-access technologies capable of supporting communications with multiple users by sharing available system resources (e.g., bandwidth, transmit power, and/or the like).
  • multipleaccess 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, singlecarrier frequency-division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE).
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency-division multiple access
  • OFDMA orthogonal frequency-division multiple access
  • SC-FDMA singlecarrier frequency-division multiple access
  • TD-SCDMA time division synchronous code division multiple access
  • LTE long term
  • 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).
  • UMTS universal mobile telecommunications system
  • 3GPP Third Generation Partnership Project
  • NB Narrowband (NB)-Intemet of things
  • eMTC enhanced machine-type communications
  • a wireless communications network may include a number of base stations (BSs) that can support communications for a number of user equipment (UEs).
  • UE user equipment
  • BS base station
  • BS base station
  • the downlink refers to the communications link from the BS to the UE
  • the uplink refers to the communications link from the UE to the BS.
  • a BS may be referred to as a Node B, an evolved Node B (eNB), a gNB, an access point (AP), a radio head, a transmit and receive point (TRP), a new radio (NR) BS, a 5G Node B, and/or the like.
  • New radio which may also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP).
  • 3GPP Third Generation Partnership Project
  • NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink (DL), using CP-OFDM and/or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
  • OFDM orthogonal frequency division multiplexing
  • SC-FDM e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)
  • MIMO multiple-input multiple-output
  • a method of wireless communication by a user equipment includes receiving, from a network entity, a request for one shot hybrid automatic repeat request (HARQ) feedback for multiple HARQ processes.
  • the method also includes transmitting, to the network entity, the one shot HARQ feedback in response to receiving the request.
  • the method further includes starting or restarting a discontinuous reception (DRX) HARQ round trip time (RTT) timer for one of the HARQ processes based at least on satisfying a condition, after transmitting the one shot HARQ feedback.
  • DRX discontinuous reception
  • RTT round trip time
  • a method of wireless communication by a network entity station includes transmitting a request for one shot hybrid automatic repeat request (HARQ) feedback for multiple HARQ processes.
  • the method also includes receiving the one shot HARQ feedback in response to receiving the request.
  • the method further includes refraining from scheduling data for a period of time for one of the plurality of HARQ processes based at least on satisfying a condition, after receiving the one shot HARQ feedback.
  • HARQ hybrid automatic repeat request
  • a user equipment having a memory and one or more processors coupled to the memory.
  • the processor(s) is configured to receive, from a network entity, a request for one shot hybrid automatic repeat request (HARQ) feedback for multiple HARQ processes.
  • the processor(s) is also configured to transmit, to the network entity, the one shot HARQ feedback in response to receiving the request.
  • the processor(s) is further configured to start or restart a discontinuous reception (DRX) HARQ round trip time (RTT) timer for one of the HARQ processes based at least on satisfying a condition, after transmitting the one shot HARQ feedback.
  • DRX discontinuous reception
  • RTT round trip time
  • a network entity station having a memory and one or more processors coupled to the memory.
  • the processor(s) is configured to transmit a request for one shot hybrid automatic repeat request (HARQ) feedback for multiple HARQ processes.
  • the processor(s) is also configured to receive the one shot HARQ feedback in response to receiving the request.
  • the processor(s) is further configured to refrain from scheduling data for a period of time for one of the HARQ processes based at least on satisfying a condition, after receiving the one shot HARQ feedback.
  • HARQ hybrid automatic repeat request
  • aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communications device, and processing system as substantially described with reference to and as illustrated by the accompanying drawings and specification.
  • FIGURE l is a block diagram conceptually illustrating an example of a wireless communications network, in accordance with various aspects of the present disclosure.
  • FIGURE 2 is a block diagram conceptually illustrating an example of a base station in communication with a user equipment (UE) in a wireless communications network, in accordance with various aspects of the present disclosure.
  • UE user equipment
  • FIGURE 3 is a block diagram illustrating an example disaggregated base station architecture, in accordance with various aspects of the present disclosure.
  • FIGURE 4 is a timing diagram illustrating a hybrid automatic repeat request (HARQ) process.
  • HARQ hybrid automatic repeat request
  • FIGURE 5 is a timing diagram illustrating a one shot HARQ process with an activity timer, in accordance with aspects of the present disclosure.
  • FIGURE 6 is a timing diagram illustrating a one shot HARQ process with a round trip time (RTT) timer starting when an activity timer is not running, in accordance with aspects of the present disclosure.
  • FIGURE 7 is a flow diagram illustrating an example process performed, for example, by a user equipment (UE), in accordance with various aspects of the present disclosure.
  • UE user equipment
  • FIGURE 8 is a flow diagram illustrating an example process performed, for example, by a network entity, in accordance with various aspects of the present disclosure.
  • Hybrid automatic repeat request (HARQ) processing improves communications reliability by acknowledging and negatively acknowledging packets transmitted across a wireless communications medium. If a receiver successfully decodes a packet, the receiver transmits an acknowledgement (ACK) to the sender confirming receipt. If the receiver unsuccessfully decodes the packet, the receiver transmits a negative acknowledgement (NACK). Upon receiving a NACK, the sender may retransmit the packet to improve the chances of successful decoding at the receiver.
  • ACK acknowledgement
  • NACK negative acknowledgement
  • the sender may retransmit the packet to improve the chances of successful decoding at the receiver.
  • Multiple HARQ processes may run in parallel for different data packets. For example, sixteen processes may run in parallel.
  • the media access control (MAC) layer of the protocol stack manages HARQ processing.
  • MAC entities start and stop various timers during the HARQ process. For example, a round trip time (RTT) timer starts when a physical downlink control channel (PDCCH) indicates a downlink transmission.
  • RTT timer controls a minimum duration before a downlink assignment for HARQ retransmission is expected by the MAC entity after a user equipment (UE) sends the HARQ feedback.
  • UE user equipment
  • the RTT timer may allow the UE to employ power savings techniques during this time.
  • the UE may receive a PDCCH without any downlink data transmission, e.g., a physical; downlink shared channel (PDSCH), but which includes a one shot HARQ-ACK request.
  • the one shot HARQ-ACK request triggers one shot (also referred to as Type-3) HARQ feedback.
  • One shot HARQ feedback includes the HARQ-ACK information for all HARQ processes at one time.
  • aspects of the present disclosure address options for UE behavior, such as which HARQ processes should start or restart the RTT timer when the UE receives a one shot HARQ feedback request.
  • the UE starts or restarts the RTT timer in the first symbol after the end of the corresponding transmission carrying the downlink HARQ feedback.
  • the RTT timer starts or restarts for a HARQ process if the RTT timer is already running.
  • the RTT timer starts or restarts for a HARQ process if a retransmission timer is already running. If the RTT timer starts or restarts due to the running retransmission timer, the UE stops the retransmission timer.
  • the UE starts or restarts the RTT timer for a HARQ process a pre-configured duration (e.g., gap) after the retransmission timer expires.
  • the UE starts or restarts the RTT timer for a HARQ process when an activity timer is not running.
  • the activity timer defines a period of time for when a HARQ process is active.
  • the UE starts or restarts the RTT timer for a HARQ process if a HARQ buffer for this process is not empty. According to further aspects of the present disclosure, the UE starts or restarts the RTT timer for the HARQ process including the downlink control information (DCI) for the one shot HARQ feedback request.
  • DCI downlink control information
  • FIGURE 1 is a diagram illustrating a network 100 in which aspects of the present disclosure may be practiced.
  • the network 100 may be a 5G or NR network or some other wireless network, such as an LTE network.
  • the wireless network 100 may include a number of BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 1 lOd) and other network entities.
  • a BS is an entity that communicates with user equipment (UEs) and may also be referred to as a base station, an NR BS, a Node B, a gNB, a 5G node B, an access point, a transmit and receive point (TRP), and/or the like.
  • Each BS may provide communications coverage for a particular geographic area.
  • the term “cell” can refer to a coverage area of a BS and/or a BS subsystem serving this coverage area, depending on the context in which the term is used.
  • a BS may provide communications coverage for a macro cell, a pico cell, a femto cell, and/or another type of cell.
  • a macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription.
  • a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription.
  • a femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a closed subscriber group (CSG)).
  • CSG closed subscriber group
  • a BS for a macro cell may be referred to as a macro BS.
  • a BS for a pico cell may be referred to as a pico BS.
  • a BS for a femto cell may be referred to as a femto BS or a home BS.
  • a BS 110a may be a macro BS for a macro cell 102a
  • a BS 110b may be a pico BS for a pico cell 102b
  • a BS 110c may be a femto BS for a femto cell 102c.
  • a BS may support one or multiple (e.g., three) cells.
  • the terms “eNB,” “base station,” “NR BS,” “gNB,” “AP,” “node B,” “5G NB,” “TRP,” and “cell” may be used interchangeably.
  • a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile BS.
  • the BSs may be interconnected to one another and/or to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces such as a direct physical connection, a virtual network, and/or the like using any suitable transport network.
  • the wireless network 100 may also include relay stations.
  • a relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send a transmission of the data to a downstream station (e.g., a UE or a BS).
  • a relay station may also be a UE that can relay transmissions for other UEs.
  • a relay station 1 lOd may communicate with macro BS 110a and a UE 120d in order to facilitate communications between the BS 110a and UE 120d.
  • a relay station may also be referred to as a relay BS, a relay base station, a relay, and/or the like.
  • the wireless network 100 may be a heterogeneous network that includes BSs of different types (e.g., macro BSs, pico BSs, femto BSs, relay BSs, and/or the like). These different types of BSs may have different transmit power levels, different coverage areas, and different impact on interference in the wireless network 100.
  • macro BSs may have a high transmit power level (e.g., 5 to 40 watts) whereas pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 watts).
  • the BSs 110 may exchange communications via backhaul links 132 (e.g., SI, etc.).
  • backhaul links 132 e.g., SI, etc.
  • Base stations 110 may communicate with one another over other backhaul links (e.g., X2, etc.) either directly or indirectly (e.g., through core network 130).
  • the core network 130 may be an evolved packet core (EPC), which may include at least one mobility management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW).
  • EPC evolved packet core
  • MME mobility management entity
  • S-GW serving gateway
  • PDN packet data network gateway
  • the MME may be the control node that processes the signaling between the UEs 120 and the EPC. All user IP packets may be transferred through the S-GW, which itself may be connected to the P-GW.
  • the P-GW may provide IP address allocation as well as other functions.
  • the P-GW may be connected to the network operator's IP services.
  • the operator's IP services may include the Internet, the Intranet, an IP multimedia subsystem (IMS), and a packet-switched (PS) streaming service.
  • IMS IP multimedia subsystem
  • PS packet-switched
  • the core network 130 may provide user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions.
  • One or more of the base stations 110 or access node controllers (ANCs) may interface with the core network 130 through backhaul links 132 (e.g., SI, S2, etc.) and may perform radio configuration and scheduling for communications with the UEs 120.
  • backhaul links 132 e.g., SI, S2, etc.
  • various functions of each access network entity or base station 110 may be distributed across various network devices (e.g., radio heads and access network controllers) or consolidated into a single network device (e.g., a base station 110).
  • UEs 120 may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile.
  • a UE may also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, and/or the like.
  • a UE may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communications device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, biometric sensors/devices, wearable devices (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicular component or sensor, smart meters/sensors, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.
  • a cellular phone e.g., a smart phone
  • PDA personal digital assistant
  • WLL wireless local loop
  • One or more UEs 120 may establish a protocol data unit (PDU) session for a network slice.
  • the UE 120 may select a network slice based on an application or subscription service. By having different network slices serving different applications or subscriptions, the UE 120 may improve its resource utilization in the wireless network 100, while also satisfying performance specifications of individual applications of the UE 120.
  • the network slices used by UE 120 may be served by an AMF (not shown in FIGURE 1) associated with one or both of the base station 110 or core network 130.
  • AMF access and mobility management function
  • the UEs 120 may include an RTT timer setting module 140.
  • the RTT timer setting module 140 may receive, from a base station, a request for one shot hybrid automatic repeat request (HARQ) feedback for multiple HARQ processes.
  • the RTT timer setting module 140 may also transmit, to the base station, the one shot HARQ feedback in response to receiving the request.
  • the RTT timer setting module 140 may also start or restart a discontinuous reception (DRX) HARQ round trip time (RTT) timer for one of the HARQ processes based at least on satisfying a condition, after transmitting the one shot HARQ feedback.
  • DRX discontinuous reception
  • RTT round trip time
  • the base stations 110 may include an RTT timer setting module 138.
  • the RTT timer setting module 138 may transmit, to a user equipment (UE), a request for one shot hybrid automatic repeat request (HARQ) feedback for multiple HARQ processes.
  • the RTT timer setting module 138 may also receive, from the UE, the one shot HARQ feedback in response to receiving the request.
  • the RTT timer setting module 138 may refrain from scheduling data for a period of time for the UE for one of the HARQ processes based at least on satisfying a condition, after receiving the one shot HARQ feedback.
  • Some UEs may be considered machine-type communications (MTC) or evolved or enhanced machine-type communications (eMTC) UEs.
  • MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, and/or the like, that may communicate with a base station, another device (e.g., remote device), or some other entity.
  • a wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communications link.
  • Some UEs may be considered Internet-of-Things (loT) devices, and/or may be implemented as NB-IoT (narrowband internet of things) devices. Some UEs may be considered a customer premises equipment (CPE).
  • UE 120 may be included inside a housing that houses components of UE 120, such as processor components, memory components, and/or the like.
  • any number of wireless networks may be deployed in a given geographic area.
  • Each wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies.
  • a RAT may also be referred to as a radio technology, an air interface, and/or the like.
  • a frequency may also be referred to as a carrier, a frequency channel, and/or the like.
  • Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
  • NR or 5G RAT networks may be deployed.
  • two or more UEs 120 may communicate directly using one or more sidelink channels (e.g., without using a base station 110 as an intermediary to communicate with one another).
  • the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, and/or the like), a mesh network, and/or the like.
  • P2P peer-to-peer
  • D2D device-to-device
  • V2X vehicle-to-everything
  • V2V vehicle-to-everything
  • the UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere as being performed by the base station 110.
  • the base station 110 may configure a UE 120 via downlink control information (DCI), radio resource control (RRC) signaling, a media access control-control element (MAC-CE) or via system information (e.g., a system information block (SIB).
  • DCI downlink control information
  • RRC radio resource control
  • MAC-CE media access control-control element
  • SIB system information block
  • FIGURE 1 is provided merely as an example. Other examples may differ from what is described with regard to FIGURE 1.
  • FIGURE 2 shows a block diagram of a design 200 of the base station 110 and UE 120, which may be one of the base stations and one of the UEs in FIGURE 1.
  • the base station 110 may be equipped with T antennas 234a through 234t
  • UE 120 may be equipped with R antennas 252a through 252r, where in general T > 1 and R > 1.
  • a transmit processor 220 may receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS(s) selected for the UE, and provide data symbols for all UEs. Decreasing the MCS lowers throughput but increases reliability of the transmission.
  • MCS modulation and coding schemes
  • the transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI) and/or the like) and control information (e.g., CQI requests, grants, upper layer signaling, and/or the like) and provide overhead symbols and control symbols.
  • the transmit processor 220 may also generate reference symbols for reference signals (e.g., the cell-specific reference signal (CRS)) and synchronization signals (e.g., the primary synchronization signal (PSS) and secondary synchronization signal (SSS)).
  • reference signals e.g., the cell-specific reference signal (CRS)
  • synchronization signals e.g., the primary synchronization signal (PSS) and secondary synchronization signal (SSS)
  • a transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t.
  • Each modulator 232 may process a respective output symbol stream (e.g., for OFDM and/or the like) to obtain an output sample stream.
  • Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal.
  • T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.
  • the synchronization signals can be generated with location encoding to convey additional information.
  • antennas 252a through 252r may receive the downlink signals from the base station 110 and/or other base stations and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively.
  • Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples.
  • Each demodulator 254 may further process the input samples (e.g., for OFDM and/or the like) to obtain received symbols.
  • a MIMO detector 256 may obtain received symbols from all R demodulators 254a through 254r, perform MEMO detection on the received symbols if applicable, and provide detected symbols.
  • a receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control information and system information to a controller/processor 280.
  • a channel processor may determine reference signal received power (RSRP), received signal strength indicator (RS SI), reference signal received quality (RSRQ), channel quality indicator (CQI), and/or the like.
  • RSRP reference signal received power
  • RS SI received signal strength indicator
  • RSRQ reference signal received quality
  • CQI channel quality indicator
  • one or more components of the UE 120 may be included in a housing.
  • a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports comprising RSRP, RSSI, RSRQ, CQI, and/or the like) from the controller/processor 280. Transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MEMO processor 266 if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, and/or the like), and transmitted to the base station 110.
  • modulators 254a through 254r e.g., for DFT-s-OFDM, CP-OFDM, and/or the like
  • the uplink signals from the UE 120 and other UEs may be received by the antennas 234, processed by the demodulators 254, detected by a MEMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120.
  • the receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller/processor 240.
  • the base station 110 may include communications unit 244 and communicate to the core network 130 via the communications unit 244.
  • the core network 130 may include a communications unit 294, a controller/processor 290, and a memory 292.
  • the controller/processor 240 of the base station 110, the controller/processor 280 of the UE 120, and/or any other component(s) of FIGURE 2 may perform one or more techniques associated with RTT timer setting as described in more detail elsewhere.
  • the controller/processor 240 of the base station 110, the controller/processor 280 of the UE 120, and/or any other component(s) of FIGURE 2 may perform or direct operations of, for example, the processes of FIGURES 7 and 8 and/or other processes as described.
  • Memories 242 and 282 may store data and program codes for the base station 110 and UE 120, respectively.
  • a scheduler 246 may schedule UEs for data transmission on the downlink and/or uplink.
  • the UE 120 and/or base station 110 may include means for receiving, means for transmitting, means for starting, means for restarting, and means for refraining.
  • Such means may include one or more components of the UE 120 or base station 110 described in connection with FIGURE 2.
  • FIGURE 2 is provided merely as an example. Other examples may differ from what is described with regard to FIGURE 2.
  • a network node a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station (BS), or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture.
  • RAN radio access network
  • BS base station
  • one or more units (or one or more components) performing base station functionality may be implemented in an aggregated or disaggregated architecture.
  • a BS such as a Node B (NB), an evolved NB (eNB), an NR BS, 5G NB, an access point (AP), a transmit and receive point (TRP), or a cell, etc.
  • NB Node B
  • eNB evolved NB
  • 5G NB 5G NB
  • AP access point
  • TRP transmit and receive point
  • a cell etc.
  • a BS may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.
  • An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node.
  • a disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).
  • CUs central or centralized units
  • DUs distributed units
  • RUs radio units
  • a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes.
  • the DUs may be implemented to communicate with one or more RUs.
  • Each of the CU, DU, and RU also can be implemented as virtual units (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).
  • VCU virtual central unit
  • VDU virtual distributed unit
  • VRU virtual radio unit
  • Base station-type operations or network designs may consider aggregation characteristics of base station functionality.
  • disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (0-RAN (such as the network configuration sponsored by the 0-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)).
  • IAB integrated access backhaul
  • 0-RAN such as the network configuration sponsored by the 0-RAN Alliance
  • vRAN virtualized radio access network
  • C-RAN cloud radio access network
  • Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design.
  • the various units of the disaggregated base station, or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit.
  • FIGURE 3 shows a diagram illustrating an example disaggregated base station 300 architecture.
  • the disaggregated base station 300 architecture may include one or more central units (CUs) 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated base station units (such as a near-real time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both).
  • a CU 310 may communicate with one or more distributed units (DUs) 330 via respective midhaul links, such as an Fl interface.
  • DUs distributed units
  • the DUs 330 may communicate with one or more radio units (RUs) 340 via respective fronthaul links.
  • the RUs 340 may communicate with respective UEs 120 via one or more radio frequency (RF) access links.
  • RF radio frequency
  • the UE 120 may be simultaneously served by multiple RUs 340.
  • Each of the units may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium.
  • Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units can be configured to communicate with one or more of the other units via the transmission medium.
  • the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units.
  • the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a radio frequency (RF) transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
  • a wireless interface which may include a receiver, a transmitter or transceiver (such as a radio frequency (RF) transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
  • RF radio frequency
  • the CU 310 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310.
  • the CU 310 may be configured to handle user plane functionality (e.g., central unit - user plane (CU-UP)), control plane functionality (e.g., central unit - control Plane (CU-CP)), or a combination thereof.
  • the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units.
  • the CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the El interface when implemented in an 0-RAN configuration.
  • the CU 310 can be implemented to communicate with the DU 330, as necessary, for network control and signaling.
  • the DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340.
  • the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the Third Generation Partnership Project (3GPP).
  • the DU 330 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.
  • Lower-layer functionality can be implemented by one or more RUs 340.
  • an RU 340 controlled by a DU 330, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split.
  • the RU(s) 340 can be implemented to handle over the air (OTA) communication with one or more UEs 120.
  • OTA over the air
  • real-time and non-real-time aspects of control and user plane communication with the RU(s) 340 can be controlled by the corresponding DU 330.
  • this configuration can enable the DU(s) 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
  • the SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements.
  • the SMO Framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (such as an 01 interface).
  • the SMO Framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-cloud) 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface).
  • a cloud computing platform such as an open cloud (O-cloud) 390
  • network element life cycle management such as to instantiate virtualized network elements
  • a cloud computing platform interface such as an 02 interface
  • Such virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, and near-RT RICs 325.
  • the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O- eNB) 311, via an 01 interface. Additionally, in some implementations, the SMO Framework 305 can communicate directly with one or more RUs 340 via an 01 interface.
  • the SMO Framework 305 also may include a non-RT RIC 315 configured to support functionality of the SMO Framework 305.
  • the non-RT RIC 315 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence/machine learning (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the near-RT RIC 325.
  • the non-RT RIC 315 may be coupled to or communicate with (such as via an Al interface) the near-RT RIC 325.
  • the near-RT RIC 325 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, or both, as well as the O-eNB 311, with the near-RT RIC 325.
  • the non-RT RIC 315 may receive parameters or external enrichment information from external servers. Such information may be utilized by the near-RT RIC 325 and may be received at the SMO Framework 305 or the non-RT RIC 315 from non-network data sources or from network functions.
  • the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance.
  • the non-RT RIC 315 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 305 (such as reconfiguration via 01) or via creation of RAN management policies (such as Al policies).
  • Hybrid automatic repeat request (HARQ) processing improves communications reliability by acknowledging and negatively acknowledging packets transmitted across a wireless communications medium. If a receiver successfully decodes a packet, the receiver transmits an acknowledgement (ACK) to the sender confirming receipt. If the receiver unsuccessfully decodes the packet, the receiver transmits a negative acknowledgement (NACK). Upon receiving a NACK, the sender may retransmit the packet to improve the chances of successful decoding at the receiver.
  • ACK acknowledgement
  • NACK negative acknowledgement
  • the sender may retransmit the packet to improve the chances of successful decoding at the receiver.
  • Multiple HARQ processes may run in parallel for different data packets. For example, sixteen processes may run in parallel.
  • the media access control (MAC) layer of the protocol stack manages HARQ processing.
  • MAC entities start and stop various timers during the HARQ process.
  • a round trip time (RTT) timer e.g., drx-HARQ-RTT-TimerDL
  • PDCCH physical downlink control channel
  • the round trip time (RTT) timer e.g., drx-HARQ-RTT-TimerDL
  • the RTT timer is based on a per downlink HARQ process.
  • FIGURE 4 is a timing diagram illustrating a hybrid automatic repeat request (HARQ) process.
  • HARQ hybrid automatic repeat request
  • the UE receives a control channel (e.g., a PDCCH) indicating a physical downlink shared channel (PDSCH).
  • PDSCH physical downlink shared channel
  • the UE may receive a DCI message that schedules a downlink assignment on the PDSCH.
  • the UE receives the PDSCH.
  • the UE After failing to decode the PDSCH, the UE transmits a NACK (e.g., via physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH)) at time t2.
  • the UE starts the RTT timer after transmitting the NACK. While the RTT timer runs, the UE may enter a sleep mode during this particular HARQ process. After the RTT timer expires, at time t3, the UE awakens from the sleep mode to receive a retransmission (ReTx) and a retransmission timer starts.
  • the retransmission timer is based on a per downlink HARQ process.
  • the retransmission timer may specify a maximum duration until a downlink retransmission is received. That is, the retransmission timer specifies a number of slots the UE remains active to wait for incoming retransmissions after a first available retransmission time. At time t4, the UE receives the retrans
  • Operation in unlicensed and shared spectrum includes alternative solutions for HARQ processing.
  • the UE may receive a PDCCH without any downlink data transmission, but which includes a one shot HARQ-ACK request.
  • the one shot HARQ-ACK request triggers one shot (also referred to as Type-3) HARQ feedback.
  • Type-3 HARQ feedback if a UE is provided with the parameter PDSCH-HARQ-ACK-OneShotFeedback and the UE detects a DCI format in any PDCCH monitoring occasion that includes a one shot HARQ-ACK request field with value 1, the UE may include the HARQ-ACK information in a Type-3 HARQ-ACK codebook for all HARQ processes.
  • the UE sends the HARQ results (e.g., ACK or NACK) for all of the HARQ processes when one shot HARQ feedback is used. It is noted that the UE will set the feedback for a HARQ process without a data transmission to NACK.
  • HARQ results e.g., ACK or NACK
  • the RTT timer (e.g., drx-HARQ- RTT-TimerDL) should be started when the UE receives the one shot HARQ feedback request.
  • the one shot feedback is for all processes and could thus prevent the UE from receiving any signals due to the UE sleeping for all processes.
  • aspects of the present disclosure address options for UE behavior, such as which HARQ processes should start or restart the RTT timer.
  • the UE starts or restarts the RTT timer (e.g., drx-HARQ-RTT-TimerDL) in the first symbol after the end of the corresponding transmission carrying the downlink HARQ feedback.
  • the RTT timer e.g., drx-HARQ-RTT-TimerDL
  • valid HARQ feedback is counted as the corresponding transmission carrying the downlink HARQ feedback. That is, a NACK transmitted in response to a transmission without data does not trigger the RTT timer.
  • the RTT timer starts or restarts for a HARQ process if the RTT timer (e.g., drx-HARQ-RTT-TimerDL) is already running.
  • the RTT timer may be running for a previous HARQ feedback transmission that is not one shot HARQ feedback.
  • the RTT timer is not started for any other HARQ processes.
  • the RTT timer starts or restarts for a HARQ process if a retransmission timer (e.g., drx-RetransmissionTimerDL) is already running. In other aspects, the RTT timer is not started for any other HARQ processes. If the RTT timer starts or restarts due to the running retransmission timer, the UE stops the retransmission timer (e.g., drx-RetransmissionTimerDL) because both timers should not run at the same time.
  • a retransmission timer e.g., drx-RetransmissionTimerDL
  • the UE starts or restarts the RTT timer for a HARQ process if either the RTT timer (e.g., drx-HARQ-RTT-TimerDL) or the retransmission timer (e.g., drx-RetransmissionTimerDL) is currently running. In other aspects, the RTT timer is not started for any other HARQ processes. Again, in this case, the UE stops the retransmission timer (e.g., drx-RetransmissionTimerDL), if the retransmission timer is running.
  • the RTT timer e.g., drx-HARQ-RTT-TimerDL
  • the retransmission timer e.g., drx-RetransmissionTimerDL
  • the UE starts or restarts the RTT timer for a HARQ process a pre-configured duration (e.g., gap) after the retransmission timer (e.g., drx-RetransmissionTimerDL) expires.
  • the base station may configure the gap length during RRC signaling. In some aspects, the gap is 10 ms.
  • the UE may determine whether the retransmission timer expires within this time duration in order to start or restart the RTT timer.
  • the UE may restart the RTT timer after the gap, e.g., 10 ms after the retransmission timer expires.
  • the UE starts or restarts the RTT timer for a HARQ process when an activity timer is not running.
  • the activity timer starts for a HARQ process when data is received for that process.
  • FIGURE 5 is a timing diagram illustrating a one shot HARQ process with an activity timer, in accordance with aspects of the present disclosure.
  • the UE receives a PDCCH Type-3 request.
  • the UE receives a DCI message that includes a one shot HARQ- ACK request.
  • the UE receives a PDSCH and starts the activity timer.
  • the activity timer defines a period of time for when a HARQ process is active.
  • the timer is started, for example for 50 ms.
  • the activity timer may start when the UE transmits the HARQ feedback (e.g., at time t2) instead of upon receiving the incoming PDSCH (e.g., at time tl).
  • the UE receives the retransmission.
  • FIGURE 6 is a timing diagram illustrating a one shot HARQ process with a round trip time (RTT) timer starting when an activity timer is not running, in accordance with aspects of the present disclosure.
  • the UE receives a PDCCH Type-3 request. For example, the UE receives a DCI message that includes a one shot HARQ-ACK request.
  • the UE receives a PDSCH. In this example, the UE does not start the activity timer.
  • the UE transmits HARQ feedback and determines an activity timer is not running. Thus, at time t2, the UE starts the RTT timer.
  • the UE receives the retransmission.
  • the UE starts or restarts the RTT timer for a HARQ process if a HARQ buffer for this process is not empty.
  • This option may vary based on UE implementation. For example, different UEs may have different reasons for flushing the buffer or different UEs may have different buffer sizes.
  • a UE flushes the HARQ buffer once the packet is successfully received and delivered to upper layers. It is also possible that the base station may not schedule any new retransmissions. In that case, a UE implementation may flush the buffer after waiting a certain time, even though the packet is not successfully received. That certain time will be up to the implementation.
  • the RTT timer is not started for any other HARQ processes.
  • the UE starts or restarts the RTT timer for the HARQ process including the DCI for the one shot HARQ feedback request. That is, the one shot HARQ feedback request arrives via DCI and has a corresponding HARQ process.
  • the DCI also includes a field for a HARQ process number.
  • the UE starts the RTT timer for this particular HARQ process.
  • the RTT timer is not started for any other HARQ processes.
  • the UE starts or restarts the RTT timer for a certain HARQ process specified in the DCI. That is, the base station may request one shot feedback for certain HARQ processes. In these aspects, the timer starts (or restarts) for these requested HARQ processes.
  • FIGURES 4-6 are provided as examples. Other examples may differ from what is described with respect to FIGURES 4-6.
  • FIGURE 7 is a flow diagram illustrating an example process 700 performed, for example, by a user equipment (UE), in accordance with various aspects of the present disclosure.
  • the example process 700 is an example of managing hybrid automatic repeat request (HARQ) timers for one shot HARQ feedback.
  • HARQ hybrid automatic repeat request
  • the operations of the process 700 may be implemented by a UE 120.
  • the user equipment (UE) receives, from a network entity station, a request for one shot hybrid automatic repeat request (HARQ) feedback for multiple HARQ processes.
  • the UE e.g. using the antenna 252, DEMOD/MOD 254, MIMO detector 256, receive processor 258, controller/processor 280, and/or memory 282
  • the one shot HARQ feedback may be Type-3 HARQ feedback.
  • the user equipment (UE) transmits, to the network entity, the one shot HARQ feedback in response to receiving the request.
  • the UE e.g.
  • the UE may start or restart an activity timer in response to receiving data or in response to transmitting any HARQ feedback for the one of the plurality of HARQ processes, the activity timer defining a period of time for when the one of the plurality of HARQ processes is active.
  • the user equipment starts or restarts a discontinuous reception (DRX) HARQ round trip time (RTT) timer for one of the HARQ processes based at least on satisfying a condition, after transmitting the one shot HARQ feedback.
  • the UE e.g.
  • the controller/processor 280, and/or memory 282 may start or restart the round trip timer (RTT).
  • RTT round trip timer
  • the starting or restarting occurs in a first symbol after transmission of the one shot HARQ feedback has completed.
  • the condition is satisfied when the one shot HARQ feedback is associated with receiving a transmission with data.
  • the condition is satisfied when the DRX HARQ RTT timer is currently running for the one of the HARQ processes.
  • the condition is satisfied when a DRX retransmission timer is currently running for the one of the processes.
  • the condition is satisfied a pre-configured duration after a DRX retransmission time expires for the one of the processes.
  • condition is satisfied when an activity timer is currently not running for the one of the processes. In some aspects, the condition is satisfied when a buffer for the one of the HARQ processes contains data. In other aspects, the condition is satisfied when the one of the HARQ processes includes downlink control information (DCI) for the request for one shot HARQ feedback.
  • DCI downlink control information
  • FIGURE 8 is a flow diagram illustrating an example process 800 performed, for example, by a network entity, in accordance with various aspects of the present disclosure.
  • the example process 800 is an example of managing hybrid automatic repeat request (HARQ) timers for one shot HARQ feedback.
  • the operations of the process 800 may be implemented by a base station 110 or a distributed unit (DU) 330 of a disaggregated base station 300.
  • HARQ hybrid automatic repeat request
  • DU distributed unit
  • the network entity transmits a request for one shot hybrid automatic repeat request (HARQ) feedback for multiple HARQ processes.
  • the base station e.g. using the antenna 234, MOD/DEMOD 232, TX MEMO processor 230, transmit processor 220, controller/processor 240, and/or memory 242
  • the one shot HARQ feedback may be Type-3 HARQ feedback.
  • the network entity receives the one shot HARQ feedback in response to receiving the request.
  • the base station e.g. using the antenna 234, MOD/DEMOD 232, MIMO detector 236, receive processor 238, controller/processor 240, and/or memory 242 may receive the feedback.
  • the network entity refrains from scheduling data for a period of time for one of the HARQ processes based at least on satisfying a condition, after receiving the one shot HARQ feedback.
  • the base station e.g. using the controller/processor 240, and/or memory 242 may refrain from scheduling data.
  • the condition is satisfied when the one shot HARQ feedback is associated with receiving a transmission with data.
  • the condition is satisfied when the DRX HARQ RTT timer is currently running for the one of the HARQ processes.
  • the condition is satisfied when a DRX retransmission timer is currently running for the one of the processes.
  • condition is satisfied a pre-configured duration after a DRX retransmission time expires for the one of the processes. In still other aspects, the condition is satisfied when an activity timer is currently not running for the one of the processes. In some aspects, the condition is satisfied when a buffer for the one of the HARQ processes contains data. In other aspects, the condition is satisfied when the one of the HARQ processes includes downlink control information (DCI) for the request for one shot HARQ feedback.
  • DCI downlink control information
  • a method of wireless communication by a user equipment comprising: receiving, from a network entity, a request for one shot hybrid automatic repeat request (HARQ) feedback for a plurality of HARQ processes; transmitting, to the network entity, the one shot HARQ feedback in response to receiving the request; and after transmitting the one shot HARQ feedback, starting or restarting a discontinuous reception (DRX) HARQ round trip time (RTT) timer for one of the plurality of HARQ processes based at least on satisfying a condition.
  • DRX discontinuous reception
  • RTT round trip time
  • Aspect 2 The method of Aspect 1, in which the starting or restarting occurs in a first symbol after transmission of the one shot HARQ feedback has completed.
  • Aspect 3 The method of Aspect 1 or 2, in which the condition is satisfied when the one shot HARQ feedback is associated with receiving a downlink data transmission.
  • Aspect 4 The method of any of the preceding Aspects, in which the condition is satisfied when the DRX HARQ RTT timer is currently running for the one of the plurality of HARQ processes.
  • Aspect 5 The method of any of the preceding Aspects, in which the condition is satisfied when a DRX retransmission timer is currently running for the one of the plurality of processes, the method further comprising stopping the DRX retransmission timer for the one of the plurality of processes.
  • Aspect 6 The method of any of the preceding Aspects, in which the condition is satisfied within a pre-configured duration after a DRX retransmission time expires for the one of the plurality of processes.
  • Aspect ? The method of any of the preceding Aspects, in which the condition is satisfied when an activity timer is currently not running for the one of the plurality of processes, the activity timer defining when the one of the plurality of HARQ processes is active.
  • Aspect 8 The method of any of the preceding aspects, further comprising starting or restarting an activity timer in response to receiving data or in response to transmitting any HARQ feedback for the one of the plurality of HARQ processes, the activity timer defining a period of time for when the one of the plurality of HARQ processes is active.
  • Aspect 9 The method of any of the preceding Aspects, in which the condition is satisfied when a buffer for the one of the plurality of HARQ processes contains data.
  • Aspect 10 The method of any of the preceding Aspects, in which the condition is satisfied when the one of the plurality of HARQ processes includes downlink control information (DCI) for the request for one shot HARQ feedback.
  • DCI downlink control information
  • Aspect 11 The method of any of the preceding Aspects, in which the condition is satisfied when downlink control information (DCI) specifies the one of the plurality of HARQ processes for one shot HARQ feedback.
  • DCI downlink control information
  • Aspect 12 The method of any of the preceding Aspects, in which the one shot HARQ feedback includes Type-3 HARQ feedback.
  • a method of wireless communication by a network entity comprising: transmitting, a request for one shot hybrid automatic repeat request (HARQ) feedback for a plurality of HARQ processes; receiving the one shot HARQ feedback in response to receiving the request; and after receiving the one shot HARQ feedback, refraining from scheduling data for a user equipment (UE) for a period of time for one of the plurality of HARQ processes based at least on satisfying a condition.
  • HARQ hybrid automatic repeat request
  • Aspect 14 The method of Aspect-13, in which the condition is satisfied when a discontinuous reception (DRX) HARQ round trip time (RTT) timer is currently running for the one of the plurality of HARQ processes.
  • DRX discontinuous reception
  • RTT round trip time
  • Aspect 15 The method of any of the Aspects 13-14, in which the condition is satisfied when a discontinuous reception (DRX) retransmission timer is currently running for the one of the plurality of processes.
  • DRX discontinuous reception
  • Aspect 16 The method of any of the Aspects 13-15, in which the condition is satisfied within a pre-configured duration after a discontinuous reception (DRX) retransmission time expires for the one of the plurality of processes.
  • DRX discontinuous reception
  • Aspect 17 The method of any of the Aspects 13-16, in which the condition is satisfied when an activity timer is currently not running for the one of the plurality of processes, the activity timer defining when the one of the plurality of HARQ processes is active.
  • Aspect 18 The method of any of the Aspects 13-17, in which the condition is satisfied when a user equipment (UE) buffer for the one of the plurality of HARQ processes contains data.
  • UE user equipment
  • Aspect 19 The method of any of the Aspects 13-18, in which the condition is satisfied when the one of the plurality of HARQ processes includes downlink control information (DCI) for the request for one shot HARQ feedback.
  • DCI downlink control information
  • Aspect 20 The method of any of the Aspects 13-19, in which the one shot HARQ feedback includes Type-3 HARQ feedback.
  • Aspect 21 An apparatus for wireless communication by a user equipment (UE), comprising: a memory; and at least one processor coupled to the memory, the at least one processor configured: to receive, from a network entity, a request for one shot hybrid automatic repeat request (HARQ) feedback for a plurality of HARQ processes; to transmit, to the network entity, the one shot HARQ feedback in response to receiving the request; and after transmitting the one shot HARQ feedback, to start or restart a discontinuous reception (DRX) HARQ round trip time (RTT) timer for one of the plurality of HARQ processes based at least on satisfying a condition.
  • DRX discontinuous reception
  • RTT HARQ round trip time
  • Aspect 22 The apparatus of Aspect 21, in which the at least one processor is configured to start or restart in a first symbol after transmission of the one shot HARQ feedback has completed.
  • Aspect 23 The apparatus of Aspect 21 or 22, in which the condition is satisfied when the one shot HARQ feedback is associated with receiving a downlink data transmission.
  • Aspect 24 The apparatus of any of the Aspects 21-23, in which the condition is satisfied when the DRX HARQ RTT timer is currently running for the one of the plurality of HARQ processes.
  • Aspect 25 The apparatus of any of the Aspects 21-24, in which the condition is satisfied when a DRX retransmission timer is currently running for the one of the plurality of processes, the method further comprising stopping the DRX retransmission timer for the one of the plurality of processes.
  • Aspect 26 The apparatus of any of the Aspects 21-25, in which the condition is satisfied within a pre-configured duration after a DRX retransmission time expires for the one of the plurality of processes.
  • Aspect 27 The apparatus of any of the Aspects 21-26, in which the condition is satisfied when an activity timer is currently not running for the one of the plurality of processes, the activity timer defining when the one of the plurality of HARQ processes is active.
  • Aspect 28 The apparatus of any of the Aspects 21-27, in which the condition is satisfied when a buffer for the one of the plurality of HARQ processes contains data.
  • Aspect 29 The apparatus of any of the Aspects 21-28, in which the condition is satisfied when the one of the plurality of HARQ processes includes downlink control information (DCI) for the request for one shot HARQ feedback.
  • DCI downlink control information
  • Aspect 30 The apparatus of any of the Aspects 21-29, in which the one shot HARQ feedback includes Type-3 HARQ feedback.
  • Aspect 31 An apparatus for wireless communication by a network entity station, comprising: a memory; and at least one processor coupled to the memory, the at least one processor configured: to transmit a request for one shot hybrid automatic repeat request (HARQ) feedback for a plurality of HARQ processes; to receive the one shot HARQ feedback in response to receiving the request; and after receiving the one shot HARQ feedback, refraining from scheduling data for a user equipment (UE) for a period of time for one of the plurality of HARQ processes based at least on satisfying a condition.
  • HARQ hybrid automatic repeat request
  • Aspect 32 The apparatus of Aspect 31, in which the condition is satisfied when a discontinuous reception (DRX) HARQ round trip time (RTT) timer is currently running for the one of the plurality of HARQ processes.
  • DRX discontinuous reception
  • RTT round trip time
  • Aspect 33 The apparatus of Aspect 31 or 32, in which the condition is satisfied when a discontinuous reception (DRX) retransmission timer is currently running for the one of the plurality of processes.
  • DRX discontinuous reception
  • Aspect 34 The apparatus of any of the Aspects 31-33, in which the condition is satisfied within a pre-configured duration after a discontinuous reception (DRX) retransmission time expires for the one of the plurality of processes.
  • DRX discontinuous reception
  • Aspect 35 The apparatus of any of the Aspects 31-34, in which the condition is satisfied when an activity timer is currently not running for the one of the plurality of processes, the activity timer defining when the one of the plurality of HARQ processes is active.
  • Aspect 36 The apparatus of any of the Aspects 31-35, in which the condition is satisfied when a user equipment (UE) buffer for the one of the plurality of HARQ processes contains data.
  • Aspect 37 The apparatus of any of the Aspects 31-36, in which the condition is satisfied when the one of the plurality of HARQ processes includes downlink control information (DCI) for the request for one shot HARQ feedback.
  • DCI downlink control information
  • Aspect 38 The apparatus of any of the Aspects 31-37, in which the one shot HARQ feedback includes Type-3 HARQ feedback.
  • the term “component” is intended to be broadly construed as hardware, firmware, and/or a combination of hardware and software.
  • a processor is implemented in hardware, firmware, and/or a combination of hardware and software.
  • satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, and/or the like.
  • “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, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c- c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).

Abstract

Un procédé de communication sans fil au moyen d'un équipement utilisateur (UE) comprend les étapes consistant à : recevoir d'une entité de réseau une demande de renvoi d'une demande de répétition automatique hybride (HARQ) d'un seul coup pour de multiples processus de HARQ; en réponse à la réception de la demande, transmettre le renvoi de HARQ d'un seul coup à l'entité de réseau; et après la transmission du renvoi de HARQ d'un seul coup, lancer ou relancer un temporisateur de temps d'aller-retour (RTT) de HARQ de réception discontinue (DRX) associé à un des multiples processus de HARQ au moins sur la base de la satisfaction d'une condition.
PCT/US2022/040811 2021-09-16 2022-08-18 Temporisateurs de demande de répétition automatique hybride (harq) à renvoi de harq d'un seul coup WO2023043570A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202280060949.3A CN117917032A (zh) 2021-09-16 2022-08-18 具有单次混合自动重传请求（harq）反馈的harq定时器

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202163245085P 2021-09-16 2021-09-16
US63/245,085 2021-09-16
US17/841,548 2022-06-15
US17/841,548 US20230084318A1 (en) 2021-09-16 2022-06-15 Hybrid automatic repeat request (harq) timers with one shot harq feedback

Publications (1)

Publication Number Publication Date
WO2023043570A1 true WO2023043570A1 (fr) 2023-03-23

Family

ID=83355194

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2022/040811 WO2023043570A1 (fr) 2021-09-16 2022-08-18 Temporisateurs de demande de répétition automatique hybride (harq) à renvoi de harq d'un seul coup

Country Status (1)

Country Link
WO (1) WO2023043570A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210058945A1 (en) * 2019-08-23 2021-02-25 Qualcomm Incorporated Handling missed hybrid automatic repeat request (harq) opportunities, multiple harq opportunities, or both for discontinuous reception (drx)

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210058945A1 (en) * 2019-08-23 2021-02-25 Qualcomm Incorporated Handling missed hybrid automatic repeat request (harq) opportunities, multiple harq opportunities, or both for discontinuous reception (drx)

Similar Documents

Publication Publication Date Title
US11219050B2 (en) Scheduling timelines for multi-transmit receive point operations
CN113892298A (zh) 话务与非连续接收和/或半持久调度的同步
CN114270927A (zh) 用于模式1侧链路的非连续接收
CN111480307A (zh) 时分双工无线通信系统中的可靠低等待时间操作
WO2020252322A2 (fr) Rétroaction de décodage de liaison descendante pour modes de transmission sans demande de répétition automatique hybride
WO2022021215A1 (fr) Ajustement de paramètre de transmission de planification semi-persistante (sps) et d'autorisation configurée (cg)
US20230084318A1 (en) Hybrid automatic repeat request (harq) timers with one shot harq feedback
WO2023043570A1 (fr) Temporisateurs de demande de répétition automatique hybride (harq) à renvoi de harq d'un seul coup
WO2024011394A1 (fr) Temps d'application de faisceau (bat) pour le fonctionnement d'un point d'émission et de réception (mtrp) basé sur un indicateur de configuration de transmission (tci) unifié
CN117917032A (zh) 具有单次混合自动重传请求（harq）反馈的harq定时器
US20240155416A1 (en) Radio access network (ran) enhancements for uplink protocol data unit (pdu) sets
US20240064632A1 (en) User equipment (ue) power saving
US20240057081A1 (en) DEFAULT BEAM RULE FOR UNIFIED TRANSMISSION CONFIGURATION INDICATION (TCI) IN MULTIPLE DOWNLINK CONTROL INFORMATION MESSAGE (mDCI), MULTIPLE TRANSMIT AND RECEIVE POINT (mTRP) SCENARIO
US20240137991A1 (en) Adapting random access channel (rach) process parameters based on a network power mode
WO2023216024A1 (fr) Détermination d'un décalage bêta pour des informations de commande de liaison montante sur un canal partagé de liaison montante avec deux blocs de transport
WO2024021003A1 (fr) Configuration d'un décalage bêta pour deux canaux partagés de liaison montante ou plus pour de multiples points d'émission et de réception basés sur des informations de commande de liaison descendante
US20240064541A1 (en) DYNAMIC ADAPTATION OF PHYSICAL DOWNLINK CONTROL CHANNEL (PDCCH) MONITORING OCCASIONS LINKED BETWEEN MULTIPLE TRANSMIT AND RECEIVE POINTS (mTRPs)
US20230345324A1 (en) User equipment (ue) capability signaling for physical uplink control channel (pucch) cell switching
WO2023245532A1 (fr) Rapport de temps de décodage de signal de dispositif de l'internet des objets (ido) passif
WO2024026767A1 (fr) Commutation de transmission de liaison montante pour porteuses associées à de multiples groupes d'avance de temps (tag)
US20230319581A1 (en) Cell search during dynamic spectrum sharing (dss) operation
US20240031883A1 (en) Connected call recovery
US20230327825A1 (en) Throughput improvement for radio frames containing time division duplex (tdd) special slots or tdd/frequency division duplex (fdd) rate-matched slots
WO2023159412A1 (fr) Calcul d'identifiant temporaire de réseau radio à accès aléatoire (ra-rnti) pour de multiples transmissions de canal d'accès aléatoire physique (prach)
US20240137192A1 (en) Half-duplex and full duplex bandwidth adaptation

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22772644

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022772644

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022772644

Country of ref document: EP

Effective date: 20240416