RETRANSMISSION MONITORING ADAPTATION UNDER DISCONTINUOUS CONFIGURATIONS

Certain aspects of the present disclosure provide techniques for wireless communication by a user-equipment (UE), comprising determining that a cell discontinuous communication cycle does not align with a transmission configuration for a transmission to or from a network entity, and processing the transmission, based on at least one rule that adjusts at least one of the cell discontinuous communication cycle or the transmission configuration, in response to the determination.

BACKGROUND

Field of the Disclosure

Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for wireless transmission configuration alignment during a discontinuous communication cycle.

Description of Related Art

SUMMARY

One aspect provides a method for wireless communication by a user-equipment (UE). The method includes determining that a cell discontinuous communication cycle does not align with a transmission configuration for a transmission to or from a network entity; and processing the transmission, based on at least one rule that adjusts at least one of the cell discontinuous communication cycle or the transmission configuration, in response to the determination.

Another aspect provides a method for wireless communication by a network entity. The method includes determining that a cell discontinuous communication cycle does not align with a transmission configuration for a transmission to or from a UE; and processing the transmission, based on at least one rule that adjusts at least one of the cell discontinuous communication cycle or the transmission configuration, in response to the determination.

DETAILED DESCRIPTION

Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer-readable mediums for aligning wireless transmissions during a discontinuous communication cycle.

To reduce power consumption, a network entity (e.g., base station (BS) or gNB) or a UE may be configured for some type of discontinuous communications. As used herein, discontinuous communications may refer to a mode where transmissions from or reception by a particular device is unavailable. For example, a UE may be configured for a discontinuous reception (DRX) mode, during which the UE is may enter a low power state because it does not need to monitor for downlink transmissions. Similarly, in a discontinuous transmission (DTX) mode, a network may not transmit and may conserve power.

In some cases, certain transmission configurations may be impacted by DTX/DRX inactive modes. As used herein, the term transmission configuration generally refers to a configuration that dictates when certain transmissions or retransmissions may be expected. Thus, having knowledge of a transmission configuration may allow a transmitter to know when a receiver is expecting (and monitoring for) a transmission. For example, as will be described in greater detail below, in some cases, such configurations may dictate that a UE should monitor for certain transmissions, even when the network is in a non-Active state. This may result in a waste of power if the UE continues to monitor for a downlink transmission and may also result in latency, increasing timelines.

Aspects of the present disclosure, however, may help address this issue by providing rules designed to align DTX/DRX cycles with uplink/downlink transmission configurations. The rules may help define UE and network-side behavior, for example, to extend DTX/DRX cycles and/or adjust periods when a UE monitors for transmissions. Aligning DTX/DRX cycles with uplink/downlink transmission configurations in this manner may help reduce unnecessary monitoring by the UE, help conserve power, and reduce latency.

Introduction to Wireless Communications Networks

FIG.1depicts an example of a wireless communications network100, in which aspects described herein may be implemented.

Generally, wireless communications network100includes various network entities (alternatively, network elements or network nodes). A network entity is generally a communications device and/or a communications function performed by a communications device (e.g., a user equipment (UE), a base station (BS), a component of a BS, a server, etc.). For example, various functions of a network as well as various devices associated with and interacting with a network may be considered network entities. Further, wireless communications network100includes terrestrial aspects, such as ground-based network entities (e.g., BSs102), and non-terrestrial aspects, such as satellite140and aircraft145, which may include network entities on-board (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and user equipments.

In the depicted example, wireless communications network100includes BSs102, UEs104, and one or more core networks, such as an Evolved Packet Core (EPC)160and 5G Core (5GC) network190, which interoperate to provide communications services over various communications links, including wired and wireless links.

BSs102wirelessly communicate with (e.g., transmit signals to or receive signals from) UEs104via communications links120. The communications links120between BSs102and UEs104may include uplink (UL) (also referred to as reverse link) transmissions from a UE104to a BS102and/or downlink (DL) (also referred to as forward link) transmissions from a BS102to a UE104. The communications links120may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity in various aspects.

BSs102may generally include: a NodeB, enhanced NodeB (eNB), next generation enhanced NodeB (ng-eNB), next generation NodeB (gNB or gNodeB), access point, base transceiver station, radio base station, radio transceiver, transceiver function, transmission reception point, and/or others. Each of BSs102may provide communications coverage for a respective geographic coverage area110, which may sometimes be referred to as a cell, and which may overlap in some cases (e.g., small cell102′ may have a coverage area110′ that overlaps the coverage area110of a macro cell). A BS may, for example, provide communications coverage for a macro cell (covering relatively large geographic area), a pico cell (covering relatively smaller geographic area, such as a sports stadium), a femto cell (relatively smaller geographic area (e.g., a home)), and/or other types of cells.

Wireless communications network100may subdivide the electromagnetic spectrum into various classes, bands, channels, or other features. In some aspects, the subdivision is provided based on wavelength and frequency, where frequency may also be referred to as a carrier, a subcarrier, a frequency channel, a tone, or a subband. For example, 3GPP currently defines Frequency Range 1 (FR1) as including 410 MHz-7125 MHz, which is often referred to (interchangeably) as “Sub-6 GHz”. Similarly, 3GPP currently defines Frequency Range 2 (FR2) as including 24,250 MHz-52,600 MHz, which is sometimes referred to (interchangeably) as a “millimeter wave” (“mmW” or “mmWave”). A base station configured to communicate using mmWave/near mmWave radio frequency bands (e.g., a mmWave base station such as BS180) may utilize beamforming (e.g.,182) with a UE (e.g.,104) to improve path loss and range.

The communications links120between BSs102and, for example, UEs104, may be through one or more carriers, which may have different bandwidths (e.g., 5, 10, 15, 20, 100, 400, and/or other MHz), and which may be aggregated in various aspects. Carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL).

Communications using higher frequency bands may have higher path loss and a shorter range compared to lower frequency communications. Accordingly, certain base stations (e.g.,180inFIG.1) may utilize beamforming182with a UE104to improve path loss and range. For example, BS180and the UE104may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate the beamforming. In some cases, BS180may transmit a beamformed signal to UE104in one or more transmit directions182′. UE104may receive the beamformed signal from the BS180in one or more receive directions182″. UE104may also transmit a beamformed signal to the BS180in one or more transmit directions182″. BS180may also receive the beamformed signal from UE104in one or more receive directions182′. BS180and UE104may then perform beam training to determine the best receive and transmit directions for each of BS180and UE104. Notably, the transmit and receive directions for BS180may or may not be the same. Similarly, the transmit and receive directions for UE104may or may not be the same.

Wireless communications network100further includes a Wi-Fi AP150in communication with Wi-Fi stations (STAs)152via communications links154in, for example, a 2.4 GHz and/or 5 GHz unlicensed frequency spectrum.

Certain UEs104may communicate with each other using device-to-device (D2D) communications link158. D2D communications link158may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and/or a physical sidelink feedback channel (PSFCH).

EPC160may include various functional components, including: a Mobility Management Entity (MME)162, other MMEs164, a Serving Gateway166, a Multimedia Broadcast Multicast Service (MBMS) Gateway168, a Broadcast Multicast Service Center (BM-SC)170, and/or a Packet Data Network (PDN) Gateway172, such as in the depicted example. MME162may be in communication with a Home Subscriber Server (HSS)174. MME162is the control node that processes the signaling between the UEs104and the EPC160. Generally, MME162provides bearer and connection management.

5GC190may include various functional components, including: an Access and Mobility Management Function (AMF)192, other AMFs193, a Session Management Function (SMF)194, and a User Plane Function (UPF)195. AMF192may be in communication with Unified Data Management (UDM)196.

AMF192is a control node that processes signaling between UEs104and 5GC190. AMF192provides, for example, quality of service (QoS) flow and session management.

Internet protocol (IP) packets are transferred through UPF195, which is connected to the IP Services197, and which provides UE IP address allocation as well as other functions for 5GC190. IP Services197may include, for example, the Internet, an intranet, an IMS, a PS streaming service, and/or other IP services.

In some aspects, the CU210may 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 CU210. The CU210may 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. In some implementations, the CU210can 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 E1 interface when implemented in an O-RAN configuration. The CU210can be implemented to communicate with the DU230, as necessary, for network control and signaling.

Lower-layer functionality can be implemented by one or more RUs240. In some deployments, an RU240, controlled by a DU230, 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. In such an architecture, the RU(s)240can be implemented to handle over the air (OTA) communications with one or more UEs104. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU(s)240can be controlled by the corresponding DU230. In some scenarios, this configuration can enable the DU(s)230and the CU210to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

FIG.3depicts aspects of an example BS102and a UE104.

Generally, BS102includes various processors (e.g.,320,330,338, and340), antennas334a-t(collectively334), transceivers332a-t(collectively332), which include modulators and demodulators, and other aspects, which enable wireless transmission of data (e.g., data source312) and wireless reception of data (e.g., data sink339). For example, BS102may send and receive data between BS102and UE104. BS102includes controller/processor340, which may be configured to implement various functions described herein related to wireless communications.

Generally, UE104includes various processors (e.g.,358,364,366, and380), antennas352a-r(collectively352), transceivers354a-r(collectively354), which include modulators and demodulators, and other aspects, which enable wireless transmission of data (e.g., retrieved from data source362) and wireless reception of data (e.g., provided to data sink360). UE104includes controller/processor380, which may be configured to implement various functions described herein related to wireless communications.

In regards to an example downlink transmission, BS102includes a transmit processor320that may receive data from a data source312and control information from a controller/processor340. The control information may be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical HARQ indicator channel (PHICH), physical downlink control channel (PDCCH), group common PDCCH (GC PDCCH), and/or others. The data may be for the physical downlink shared channel (PDSCH), in some examples.

Transmit processor320may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. Transmit processor320may also generate reference symbols, such as for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS).

Transmit (TX) multiple-input multiple-output (MIMO) processor330may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) in transceivers332a-332t.Each modulator in transceivers332a-332tmay process a respective output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from the modulators in transceivers332a-332tmay be transmitted via the antennas334a-334t, respectively.

In order to receive the downlink transmission, UE104includes antennas352a-352rthat may receive the downlink signals from the BS102and may provide received signals to the demodulators (DEMODs) in transceivers354a-354r,respectively. Each demodulator in transceivers354a-354rmay condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples to obtain received symbols.

MIMO detector356may obtain received symbols from all the demodulators in transceivers354a-354r,perform MIMO detection on the received symbols if applicable, and provide detected symbols. Receive processor358may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE104to a data sink360, and provide decoded control information to a controller/processor380.

In regards to an example uplink transmission, UE104further includes a transmit processor364that may receive and process data (e.g., for the PUSCH) from a data source362and control information (e.g., for the physical uplink control channel (PUCCH)) from the controller/processor380. Transmit processor364may also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS)). The symbols from the transmit processor364may be precoded by a TX MIMO processor366if applicable, further processed by the modulators in transceivers354a-354r(e.g., for SC-FDM), and transmitted to BS102.

At BS102, the uplink signals from UE104may be received by antennas334a-t, processed by the demodulators in transceivers332a-332t,detected by a MIMO detector336if applicable, and further processed by a receive processor338to obtain decoded data and control information sent by UE104. Receive processor338may provide the decoded data to a data sink339and the decoded control information to the controller/processor340.

Memories342and382may store data and program codes for BS102and UE104, respectively.

Scheduler344may schedule UEs for data transmission on the downlink and/or uplink.

In various aspects, BS102may be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” may refer to various mechanisms of outputting data, such as outputting data from data source312, scheduler344, memory342, transmit processor320, controller/processor340, TX MIMO processor330, transceivers332a-t, antenna334a-t, and/or other aspects described herein. Similarly, “receiving” may refer to various mechanisms of obtaining data, such as obtaining data from antennas334a-t, transceivers332a-t, RX MIMO detector336, controller/processor340, receive processor338, scheduler344, memory342, and/or other aspects described herein.

In various aspects, UE104may likewise be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” may refer to various mechanisms of outputting data, such as outputting data from data source362, memory382, transmit processor364, controller/processor380, TX MIMO processor366, transceivers354a-t, antenna352a-t, and/or other aspects described herein. Similarly, “receiving” may refer to various mechanisms of obtaining data, such as obtaining data from antennas352a-t, transceivers354a-t, RX MIMO detector356, controller/processor380, receive processor358, memory382, and/or other aspects described herein.

FIGS.4A,4B,4C, and4Ddepict aspects of data structures for a wireless communications network, such as wireless communications network100ofFIG.1.

In particular,FIG.4Ais a diagram400illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure,FIG.4Bis a diagram430illustrating an example of DL channels within a 5G subframe,FIG.4Cis a diagram450illustrating an example of a second subframe within a 5G frame structure, andFIG.4Dis a diagram480illustrating an example of UL channels within a 5G subframe.

As depicted inFIGS.4A,4B,4C, and4D, a resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

As illustrated inFIG.4A, some of the REs carry reference (pilot) signals (RS) for a UE (e.g., UE104ofFIGS.1and3). The RS may include demodulation RS (DMRS) and/or channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and/or phase tracking RS (PT-RS).

A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE (e.g.,104ofFIGS.1and3) to determine subframe/symbol timing and a physical layer identity.

Example Resource Allocations

Radio resources can be allocated to a UE by configured scheduling, dynamic scheduling, or a combination of configured and dynamic scheduling.

Configured scheduling is a mechanism in which the network can schedule PUSCH resources for the UE without using DCI to schedule each PUSCH transmission. Configured scheduling is done by configuring the UE with the scheduling parameters semi-statically in RRC signaling. Configured scheduling helps reduce the scheduling overhead.

Configured scheduling for the uplink may be done using a configured grant (CG). Uplink resources are scheduled via CGs that occur periodically (referred to as CG occasions) without the need for control signaling, eliminating expense and delay associated with dynamic signaling. CG parameters are typically configured via RRC signaling and the activation of the grant is through RRC or L1 signaling. Typically, the periodicity and configured parameters (e.g., number of resource blocks (RBs), modulation and coding scheme (MCS), number of repetitions) are the same for all CG occasions in the CG configuration.

Two different types of configured grants include Type 1 CGs and Type 2 CGs. In Type 1 CG, the network send higher layer RRC signaling (e.g., an RRCSetup or RRCReconfiguration message according to 3GPP TS 38.331) configuring all the parameters for PUSCH scheduling including a resource allocation. The UE may transmit PUSCH according to configured scheduling, without receiving any lower layer trigger (e.g., DCI). In Type 2 CG, after the RRC configuration, the network sends a DCI (e.g., masked with a configured scheduling radio network temporary identifier (CS-RNTI)) to activate the configured grant. In both Type 1 CG and Type 2 CG, the network may send medium access control (MAC) control element (CE) signaling to downselect the RRC configured resources and/or DCI overwriting the configured scheduling. Because the configured scheduling is semi-static, the UE may be overallocated with resources for uplink transmission, for example, due to changed channel conditions.

For dynamic grants, the network may send DCI to schedule each uplink transmission for the UE. In some cases, the network schedules uplink resources for the UE based on buffer status reports (BSRs) received from the UE. However, if a BSR accurately reflecting the UEs buffer size is not recently received, the network may still overallocate resources for the UE. In addition, a BSR codepoint can correspond to a large range (e.g., 7-8 MB). In addition, a UE may first send a scheduling request (SR) for resources to send the BSR. SR and BSR transmission, and waiting for an uplink grant, may increase uplink latency at the UE.

Configured scheduling is suitable for periodic and predictable traffic types (e.g., voice over internet protocol (VoIP), ultra-reliable low latency communication (URLLC), Internet-of-things (IoT), etc.). Repetition rates of configured scheduling (e.g., 1, 2, 4, and 8) may be adjusted to increase reliability.

Overview of Discontinuous Communication

As noted above, to reduce power consumption, a network entity (e.g., base station (BS) or gNB) or a UE may be configured for some type of cell discontinuous communications. For example, a UE may be configured for discontinuous reception (DRX) mode, during which the UE is may enter a low power state because it does not need to monitor for downlink transmissions. Similarly, in a discontinuous transmission (DTX) mode, a network may not transmit and may conserve power.

As illustrated in the timing diagram500ofFIG.5A, a UE in a DRX mode (e.g., a connected DRX mode or CDRX) can cycle/alternate between “Active time” durations502and “non-Active” time durations504.

During a CDRX Active time (or On-Duration), the UE monitors for physical downlink shared channel (PDSCH) activity continuously or with a given periodicity, receives downlink data, transmits UL data, and/or makes serving cell measurements or neighbor measurements. During Active time, a UE is generally considered “on” while various timers are running. For example, an Active duration timer (e.g., drx-onDurationTimer), an inactivity timer (drx-InactivityTimer), and a complete DRX cycle duration (e.g., drx-ShortCycle) may run during an Active time. The beginning of a DRX cycle may be defined by a starting offset value.

In the examples, the Active time is 10 ms and the CDRX cycle duration is 30 ms. The UE may be configured with an inactivity timer (starting an inactivity period506) that restarts when activity is detected and expires after 5 ms without detected activity. When the inactivity timer expires, the UE enters an “inactive” or “sleep” mode.

As illustrated in the timing diagram510ofFIG.5B, a network entity (e.g., a gNB) in a DTX mode can cycle/alternate between “Active time” durations512and “non-Active” time durations514.

While the gNB is active at512, the gNB is allowed to send transmissions. When non-Active, the gNB does not need to transmit or receive certain periodic signals/channels, which may allow a network entity to conserve power. For example, when non-Active, the gNB may not need to transmit or receive common channels/signals or user equipment (UE) specific signals/channels, and may have no transmission/reception or only keep limited transmission/reception.

DTX may be configured to achieve energy savings at the network. DTX cycles can be configured semi-statically or dynamically, with a particular configuration typically determined with data communication as a goal.

Aspects Related Transmission Configuration Alignment during DRX/DTX

In some cases, certain transmission configurations may be impacted by discontinuous communication (DTX/DRX) inactive modes. For example, as will be described in greater detail below, in some cases, such configurations may dictate that a UE should monitor for certain transmissions, even when the network is in a non-Active state. This may result in a waste of power if the UE continues to monitor for a downlink transmission and may also result in latency, increasing timelines.

One example of where a DTX/DRX timeline may impact a transmission configuration is an uplink data transmission scenario, where a physical uplink shared channel (PUSCH) is transmitted via a configured grant (CG). In such cases, an explicit hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback mechanism is not used to trigger retransmissions. Instead, a UE may wait for a retransmission indication from the network, for a defined period of time.

For example, as illustrated in the timeline600ofFIG.6, a UE may monitor for a physical downlink control channel (PDCCH) with a retransmission request, for a period of time after transmitting a PUSCH602. As illustrated, a configured round-trip time (RTT) timer (drx-HARQ-RTT-TimerUL) starts after the PUSCH transmission. drx-HARQ-RTT-TimerUL generally represents the minimum duration before a UL HARQ retransmission grant is expected. When the drx-HARQ-RTT-TimerUL RTT timer expires, as shown at604, a configured retransmission timer (drx-RetransmissionTimerUL) starts.

As shown at606, while the drx-RetransmissionTimerUL is running, the UE may stay in an Active state to monitor for a PDCCH transmission triggering an uplink retransmission. If this period does not fully overlap with a DTX (on/Active) cycle, the UE may be monitoring unnecessarily, wasting power.

Another example scenario where a DTX/DRX timeline may impact a transmission configuration is a downlink (DL) scenario where the UE may trigger retransmission of a physical downlink shared channel (PDSCH) via a HARQ negative ACK (HARQ-NACK). After transmitting the HARQ-NACK, the UE may monitor for the PDSCH retransmission for a period of time.

For example, as illustrated in the timeline700ofFIG.7, a UE may monitor for a PDSCH retransmission for a period of time after transmitting a HARQ-NACK702. In the illustrated example, the UE starts a configured RTT timer (drx-HARQ-RTT-TimerDL) after transmitting the HARQ-NACK. drx-HARQ-RTT-TimerDL generally represents the minimum duration before a DL assignment for HARQ retransmission is expected. After drx-HARQ-RTT-TimerDL expires, at704, a configured retransmission timer (drx-RetransmissionTimerDL) starts.

As shown, while the drx-RetransmissionTimerDL is running, the UE may stay in an Active state to monitor for a PDSCH retransmission. If this period does not fully overlap with a DTX (on/Active) cycle, the UE may be monitoring unnecessarily, wasting power.

Aspects of the present disclosure, however, may help address this issue by providing rules designed to align DTX/DRX cycles with uplink/downlink transmission configurations. The rules may help define UE and network-side behavior, for example, to extend DTX/DRX cycles and/or adjust periods when a UE monitors for transmissions.

Mechanisms for aligning DTX/DRX cycles with uplink/downlink transmissions proposed herein may be understood with reference to the call flow diagram800ofFIG.8. In some aspects, the network entity shown inFIG.8may be an example of the BS102depicted and described with respect toFIGS.1and3or a disaggregated base station depicted and described with respect toFIG.2. Similarly, the UE shown inFIG.8may be an example of UE104depicted and described with respect toFIGS.1and3. However, in other aspects, UE104may be another type of wireless communications device and BS102may be another type of network entity or network node, such as those described herein.

As illustrated at802, the network entity may indicate, to the UE, a rule to align DRX/DTX cycles with transmission configurations. As illustrated, the indication may be signaled via layer 1 (L1 or physical/PHY), layer 2 (L2 or MAC), and/or layer 3 (L3, such as RRC) signaling.

Then, as shown at804, both the network entity and the UE determine that a DRX/DTX cycle does not align with a transmission/retransmission. The network then sends the transmission/retransmission to the UE. As shown at806and808, the UE and network entity may both process the transmission/retransmission according to the rule.

Processing the transmission/retransmission may involve adjusting some type of timing so that the transmission may be sent/received during an active time of a discontinuous communication cycle. For example, based on the rule, the UE and network entity may both adjust a DRX/DTX cycle and/or a transmission configuration to allow a corresponding transmission/retransmission to be sent and received.

Aspects of the present disclosure provide various options for how DRX/DTX cycles and transmission configurations may be adjusted, based on one or more rules.

According to one option, the drx-HARQ-RTT-TimerUL timer and the drx-RetransmissionTimerUL timer may be adjusted to effectively extend the cell DRX duration. Referring back toFIG.6, this may allow the UE Active state to align with a PDCCH transmission triggering an uplink retransmission, which may help the UE avoid monitoring unnecessarily and wasting power.

According to another option, the drx-HARQ-RTT-TimerDL RTT timer and drx-RetransmissionTimerDL retransmission timer may effectively extend the cell DTX duration. Referring back toFIG.7, this may allow the UE Active state to align with a PDSCH retransmission.

The network entity may indicate to the UE whether an active cell DRX/DTX times is extendable. This indication may be provided, for example, via a scheduling downlink control information (DCI) (e.g., that schedules the corresponding PUSCH/PDSCH) or in a (e.g., newly defined/dedicated) non-scheduling DCI. In general, the indication of whether DRX/DTX is extendable can be provided via L1, L2, or L3 signaling from the network entity to the UE.

In some cases, the network may allow for cell DRX/DTX extension for specific UL logical channel groups (LCGs), logical channel prioritizations (LCPs), L1/L2 priorities, and/or quality of services (QoSs). For example, based on the priority, LCG, and/or LCP of a given packet, the UE may know or ascertain whether the network entity will extend the active cell DRX/DTX and, possibly, to what degree such an extension may be implemented. This specified extension may apply for both connected mode DRX (C-DRX) and connected mode DTX (C-DTX). In some cases, this extension may be configured based on L1/L2/L3 signaling per LCG. In some cases, this extension may be autonomously derived according to a predefined rule, such that the network entity may extend C-DTX/DRX and the UE may expect the network entity to extend according to the rule.

There are various options for determining/indicating a particular time of extension of the C-DTX/DRX. For example, the extension time may be a particular time configured via L1/L2/L3 signaling (e.g., including scheduling DCI that scheduled the PUSCH/PDSCH) or may be pre-configured (e.g., which may be similar to application times specified in a standard specification).

In some cases, the extension time of the C-DTX/DRX may be derived from some other configured time. For example, the extension time may be a same time as the defined for drx-HARQ-RTT-TimerDL, drx-RetransmissionTimerDL, or a combination thereof. For example, the extension time may be the drx-HARQ-RTT-TimerDL the drx-RetransmissionTimerDL, plus some offset value(s) configured by the network.

In some cases, a UE may provide a status report to the network. How long to extend DTX/DRX may be based, at least in part, on the status report.

For example, in certain wireless systems or scenarios, such as extended reality (XR) deployments, a network entity may receive a delay status report (DSR) from the UE. In some cases, the network entity and the UE may agree on expected C-DRX/C-DTX sizes. This agreement may dictate, for example, what values to use based on reported DSR and associated L1/L2 priorities of packets, and/or based on other agreements between the UE and the network entity on extension behavior and procedure.

In another example, a network entity may receive an energy status report (ESR) from the UE. The ESR may contain at least one of a charging rate profile, a discharging rate profile, an energy level profile, an energy value or a communication state profile. Each profile may contain a current value and predicted values over a certain pre-configured time period. In some cases, based on an energy level profile (an amount of energy at a storage unit or battery) of an ESR, a UE may report an energy value X to be greater than a value Y, where Y is a configured threshold. When X is greater than Y, the UE and the network entity may agree on an extension behavior and procedure based on the energy level profile of the ESR. When X is less than Y, the UE and the network entity may agree not to implement an extension behavior, or may agree to reduce or disable applicable timers. Similarly, a UE may report a value X for an energy state, communication state, or multiple states within an ESR, where each state is associated with a certain UE or behavior configuration. In some cases, the UE may be an Internet-of-Things (IOT) device, a zero power device, or an energy harvesting device.

In some cases, a rule for alignment may allow for a dynamic RTT timer and/or a dynamic retransmission timer for DL and/or UL. Dynamic RTT and/or dynamic retransmission timers may be set for the purpose of energy saving, where each network energy state (NES) has different RTT/retransmission timers. In some cases, a network entity may shorten RTT/retransmission timers to fit into (align with) the current C-DTX/DRX, or make RTT/retransmission longer based at least on network capability and/or UE capability. An indication to change or adapt RTT/retransmission timers (which may include scheduling DCI the transmission) may be provided via L1, L2, or L3 signaling from the network entity to the UE.

There are various options (rules) how one or both of these timers may be adjusted, for example, depending on whether a retransmission request monitoring window starts before, during, or after a DTX Active time. According to a first option, a UE may simply monitor for retransmission requests regardless of the DTX cycle.

According to a second option, as illustrated inFIG.9A, if a retransmission request monitoring window904starts before a DTX Active time, all UL CG occasions whose time windows start before the DTX Active time (e.g., CG occasion902) are not used by the UE.

According to a third option, as illustrated inFIG.9B, if the initial drx-RetransmissionTimerUL timer would result in a retransmission request monitoring window914starting before the DTX Active time, the timer may be adjusted, as shown at912, resulting in a shifted retransmission request window916that starts at the beginning or within the DTX Active time, without modifying the length of the monitoring window. In some cases, the drx-RetransmissionTimerUL timer may be adjusted to start at the beginning of or X time units past the beginning of the DTX Active time. The value of X may be configurable by the network entity, may be UE-specific, or may be common across multiple UEs.

As illustrated inFIG.9C, in some cases, in addition to shifting the start of the drx-RetransmissionTimerUL timer, as shown at922, the drx-RetransmissionTimerUL timer may be shortened. This may result in a shorter retransmission request window926that fully overlaps with the DTX cycle. In some cases, the drx-RetransmissionTimerUL timer may only be shortened if the shifted retransmission request window would otherwise not be fully contained within the DTX cycle.

There are various options (rules) to apply if the drx-RetransmissionTimerUL timer starts within the DTX Active time. This situation may be problematic and warrant adjustment, particularly if the retransmission request monitoring window would otherwise extend beyond the end of the DTX Active time.

According to a first option, as illustrated inFIGS.10A, a UE may simply monitor for retransmission requests for the entirety of the request monitoring window1002, regardless of the DTX cycle. In other words, the retransmission request monitoring window may still be active until the end of the configured window (or until receiving a response), even if it extends beyond the DTX cycle.

According to a second option, as illustrated inFIG.10B, a retransmission request monitoring window1012may be shortened/truncated to align with the end of the DTX Active time.

According to a third option, when the drx-RetransmissionTimerUL timer starts within the DTX Active time, the DTX cycle may be extended by a certain amount (e.g., X units of time). In this case, the retransmission request monitoring window may be active for its initial duration or until the end of the extended active duration. This option effectively extends the DTX Active time, in contrast to options that only extend the retransmission request monitoring window. In some cases, extending the DTX Active time in this manner, may allow the network to perform other operations (e.g., communicating with other UEs, while active).

In one case, the particular option and/or rule to be used to align DRX/DTX and a transmission configuration may be indicated to the UE via L1, L2, or L3 signaling as described above (and as shown in the call flow diagram800ofFIG.8). In one case, the option and/or rule may be updated/indicated via a dynamic DTX control indication. A signaling control message indicating the DTX state triggering/activation may include an indication or an update of the retransmission request monitoring window behavior to be used until the next DTX state triggering/activation is provided to the UE. In one case, the option and/or rule may be determined automatically as a function of the data transmitted (e.g., different types of data may warrant different options/rules). The option and/or rule may also be indicated via a combination of these options.

Example Operations

FIG.11shows an example of a method1100of wireless communication by a UE, such as a UE104ofFIGS.1and3.

Method1100begins at step1105with determining that a cell discontinuous communication cycle does not align with a transmission configuration for a transmission to or from a network entity. In some cases, the operations of this step refer to, or may be performed by, circuitry for determining and/or code for determining as described with reference toFIG.13.

Method1100then proceeds to step1110with processing the transmission, based on at least one rule that adjusts at least one of the cell discontinuous communication cycle or the transmission configuration, in response to the determination. In some cases, the operations of this step refer to, or may be performed by, circuitry for processing and/or code for processing as described with reference toFIG.13.

In some aspects, the at least one rule dictates that the cell discontinuous communication cycle be extended to allow for processing the transmission.

In some aspects, the cell discontinuous communication cycle comprises a DRX cycle; the transmission comprises a retransmission of a PUSCH from the UE; and the at least one rule dictates that the DRX cycle be extended to allow for the retransmission of the PUSCH.

In some aspects, the cell discontinuous communication cycle comprises a DTX cycle; the transmission comprises a retransmission of a PDSCH from the network entity; and the at least one rule dictates that the DTX cycle be extended to allow for the retransmission of the PDSCH.

In some aspects, the method1100further includes receiving an indication of whether or not the cell discontinuous communication cycle is extendable. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and/or code for receiving as described with reference toFIG.13.

In some aspects, the indication is received via DCI scheduling an uplink transmission, a DCI scheduling a downlink transmission, or a non-scheduling DCI.

In some aspects, the indication is received via physical layer signaling, MAC-CE signaling, or RRC signaling.

In some aspects, the indication also indicates that the cell discontinuous communication cycle is extendable for processing certain LCGs, LCPs, or QoSs.

In some aspects, the method1100further includes receiving an indication of how long to extend the cell discontinuous communication cycle. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and/or code for receiving as described with reference toFIG.13.

In some aspects, the indication is received via physical layer signaling, MAC-CE signaling, or RRC signaling.

In some aspects, the indication is received as at least one of a configured RTT timer value, a configured retransmission timer value, or one or more offset values.

In some aspects, the method1100further includes transmitting a status report to the network entity. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and/or code for transmitting as described with reference toFIG.13.

In some aspects, the method1100further includes determining how long to extend the cell discontinuous communication cycle based, at least in part, on the status report. In some cases, the operations of this step refer to, or may be performed by, circuitry for determining and/or code for determining as described with reference toFIG.13.

In some aspects, the cell discontinuous communication cycle comprises a DTX cycle; the transmission comprises a retransmission of a PDSCH from the network entity; and the at least one rule dictates how to monitor for the retransmission of the PDSCH when a retransmission timer starts within an active DTX time.

In some aspects, the at least one rule dictates that at least one of a RTT timer value or retransmission timer value be dynamically updated to allow for processing the transmission.

In some aspects, the method1100further includes receiving an indication of how to dynamically update the RTT timer value or the retransmission timer value. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and/or code for receiving as described with reference toFIG.13.

In some aspects, the indication is received via physical layer signaling, MAC-CE signaling, or RRC signaling.

In some aspects, the method1100further includes determining at least one of:

the at least one rule to apply; or how to apply the at least one rule. In some cases, the operations of this step refer to, or may be performed by, circuitry for determining and/or code for determining as described with reference toFIG.13.

In some aspects, the determination is based on at least one of: signaling from the network entity; or a function of data involved in the transmission.

In one aspect, method1100, or any aspect related to it, may be performed by an apparatus, such as communications device1300ofFIG.13, which includes various components operable, configured, or adapted to perform the method1100. Communications device1300is described below in further detail.

Note thatFIG.11is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.

FIG.12shows an example of a method1200of wireless communication by a network entity, such as a BS102ofFIGS.1and3, or a disaggregated base station as discussed with respect toFIG.2.

Method1200begins at step1205with determining that a cell discontinuous communication cycle does not align with a transmission configuration for a transmission to or from a UE. In some cases, the operations of this step refer to, or may be performed by, circuitry for determining and/or code for determining as described with reference toFIG.13.

Method1200then proceeds to step1210with processing the transmission, based on at least one rule that adjusts at least one of the cell discontinuous communication cycle or the transmission configuration, in response to the determination. In some cases, the operations of this step refer to, or may be performed by, circuitry for processing and/or code for processing as described with reference toFIG.13.

In some aspects, the at least one rule dictates that the cell discontinuous communication cycle be extended to allow for processing the transmission.

In some aspects, the cell discontinuous communication cycle comprises a DRX cycle; the transmission comprises a retransmission of a PUSCH from the UE; and the at least one rule dictates that the DRX cycle be extended to allow for the retransmission of the PUSCH.

In some aspects, the cell discontinuous communication cycle comprises a DTX cycle; the transmission comprises a retransmission of a PDSCH from the network entity; and the at least one rule dictates that the DTX cycle be extended to allow for the retransmission of the PDSCH.

In some aspects, the method1200further includes transmitting, to the UE, an indication of whether or not the cell discontinuous communication cycle is extendable. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and/or code for transmitting as described with reference toFIG.13.

In some aspects, the indication is transmitted via DCI scheduling an uplink transmission, a DCI scheduling a downlink transmission, or a non-scheduling DCI.

In some aspects, the indication is transmitted via physical layer signaling, MAC-CE signaling, or RRC signaling.

In some aspects, the indication also indicates that the cell discontinuous communication cycle is extendable for processing certain LCGs, LCPs, or QoSs.

In some aspects, the method1200further includes transmitting, to the UE, an indication of how long to extend the cell discontinuous communication cycle. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and/or code for transmitting as described with reference toFIG.13.

In some aspects, the indication is transmitted via physical layer signaling, MAC-CE signaling, or RRC signaling.

In some aspects, the indication is transmitted as at least one of a configured RTT timer value, a configured retransmission timer value, or one or more offset values.

In some aspects, the method1200further includes receiving a status report from the UE. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and/or code for receiving as described with reference toFIG.13.

In some aspects, the method1200further includes determining how long to extend the cell discontinuous communication cycle based on the status report and associated packet priorities. In some cases, the operations of this step refer to, or may be performed by, circuitry for determining and/or code for determining as described with reference toFIG.13.

In some aspects, the cell discontinuous communication cycle comprises a DTX cycle; the transmission comprises a retransmission of a PDSCH from the network entity; and the at least one rule dictates how to determine a window for the retransmission of the PDSCH when a retransmission timer starts within an active DTX time.

In some aspects, the at least one rule dictates that at least one of a RTT timer value or retransmission timer value be dynamically updated to allow for processing the transmission.

In some aspects, the method1200further includes transmitting, to the UE, an indication of how to dynamically update the RTT timer value or the retransmission timer value. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and/or code for transmitting as described with reference toFIG.13.

In some aspects, the indication is transmitted via physical layer signaling, MAC-CE signaling, or RRC signaling.

In some aspects, the method1200further includes determining at least one of: the at least one rule to apply; or how to apply the at least one rule. In some cases, the operations of this step refer to, or may be performed by, circuitry for determining and/or code for determining as described with reference toFIG.13.

In some aspects, the determination is based on at least one of: signaling from the network entity; or a function of data involved in the transmission.

In one aspect, method1200, or any aspect related to it, may be performed by an apparatus, such as communications device1300ofFIG.13, which includes various components operable, configured, or adapted to perform the method1200. Communications device1300is described below in further detail.

Note thatFIG.12is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.

Example Communications Device

FIG.13depicts aspects of an example communications device1300. In some aspects, communications device1300is a user equipment, such as UE104described above with respect toFIGS.1and3. In some aspects, communications device1300is a network entity, such as BS102ofFIGS.1and3, or a disaggregated base station as discussed with respect toFIG.2.

The communications device1300includes a processing system1305coupled to the transceiver1365(e.g., a transmitter and/or a receiver). In some aspects (e.g., when communications device1300is a network entity), processing system1305may be coupled to a network interface1375that is configured to obtain and send signals for the communications device1300via communication link(s), such as a backhaul link, midhaul link, and/or fronthaul link as described herein, such as with respect toFIG.2. The transceiver1365is configured to transmit and receive signals for the communications device1300via the antenna1370, such as the various signals as described herein. The processing system1305may be configured to perform processing functions for the communications device1300, including processing signals received and/or to be transmitted by the communications device1300.

The processing system1305includes one or more processors1310. In various aspects, the one or more processors1310may be representative of one or more of receive processor358, transmit processor364, TX MIMO processor366, and/or controller/processor380, as described with respect toFIG.3. In various aspects, one or more processors1310may be representative of one or more of receive processor338, transmit processor320, TX MIMO processor330, and/or controller/processor340, as described with respect toFIG.3. The one or more processors1310are coupled to a computer-readable medium/memory1335via a bus1360. In certain aspects, the computer-readable medium/memory1335is configured to store instructions (e.g., computer-executable code) that when executed by the one or more processors1310, cause the one or more processors1310to perform the method1100described with respect toFIG.11, or any aspect related to it; and the method1200described with respect to FIG.12, or any aspect related to it. Note that reference to a processor performing a function of communications device1300may include one or more processors1310performing that function of communications device1300.

In the depicted example, computer-readable medium/memory1335stores code (e.g., executable instructions), such as code for determining1340, code for processing1345, code for receiving1350, and code for transmitting1355. Processing of the code for determining1340, code for processing1345, code for receiving1350, and code for transmitting1355may cause the communications device1300to perform the method1100described with respect toFIG.11, or any aspect related to it; and the method1200described with respect toFIG.12, or any aspect related to it.

The one or more processors1310include circuitry configured to implement (e.g., execute) the code stored in the computer-readable medium/memory1335, including circuitry for determining1315, circuitry for processing1320, circuitry for receiving1325, and circuitry for transmitting1330. Processing with circuitry for determining1315, circuitry for processing1320, circuitry for receiving1325, and circuitry for transmitting1330may cause the communications device1300to perform the method1100described with respect toFIG.11, or any aspect related to it; and the method1200described with respect toFIG.12, or any aspect related to it.

Various components of the communications device1300may provide means for performing the method1100described with respect toFIG.11, or any aspect related to it; and the method1200described with respect toFIG.12, or any aspect related to it. For example, means for transmitting, sending or outputting for transmission may include transceivers354and/or antenna(s)352of the UE104illustrated inFIG.3, transceivers332and/or antenna(s)334of the BS102illustrated inFIG.3, and/or the transceiver1365and the antenna1370of the communications device1300inFIG.13. Means for receiving or obtaining may include transceivers354and/or antenna(s)352of the UE104illustrated inFIG.3, transceivers332and/or antenna(s)334of the BS102illustrated inFIG.3, and/or the transceiver1365and the antenna1370of the communications device1300inFIG.13.

Example Clauses

Clause 1: A method for wireless communication by a UE, comprising: determining that a cell discontinuous communication cycle does not align with a transmission configuration for a transmission to or from a network entity; and processing the transmission, based on at least one rule that adjusts at least one of the cell discontinuous communication cycle or the transmission configuration, in response to the determination.

Clause 2: The method of Clause 1, wherein the at least one rule dictates that the cell discontinuous communication cycle be extended to allow for processing the transmission.

Clause 3: The method of Clause 2, wherein: the cell discontinuous communication cycle comprises a DRX cycle; the transmission comprises a retransmission of a PUSCH from the UE; and the at least one rule dictates that the DRX cycle be extended to allow for the retransmission of the PUSCH.

Clause 4: The method of Clause 2, wherein: the cell discontinuous communication cycle comprises a DTX cycle; the transmission comprises a retransmission of a PDSCH from the network entity; and the at least one rule dictates that the DTX cycle be extended to allow for the retransmission of the PDSCH.

Clause 5: The method of Clause 2, further comprising receiving an indication of whether or not the cell discontinuous communication cycle is extendable.

Clause 6: The method of Clause 5, wherein the indication is received via DCI scheduling an uplink transmission, a DCI scheduling a downlink transmission, or a non-scheduling DCI.

Clause 7: The method of Clause 5, wherein the indication is received via physical layer signaling, MAC-CE signaling, or RRC signaling.

Clause 8: The method of Clause 5, wherein the indication also indicates that the cell discontinuous communication cycle is extendable for processing certain LCGs, LCPs, or QoSs.

Clause 9: The method of Clause 2, further comprising receiving an indication of how long to extend the cell discontinuous communication cycle.

Clause 10: The method of Clause 9, wherein the indication is received via physical layer signaling, MAC-CE signaling, or RRC signaling.

Clause 11: The method of Clause 9, wherein the indication is received as at least one of a configured RTT timer value, a configured retransmission timer value, or one or more offset values.

Clause 12: The method of Clause 2, further comprising: transmitting a status report to the network entity; and determining how long to extend the cell discontinuous communication cycle based, at least in part, on the status report.

Clause 13: The method of Clause 2, wherein: the cell discontinuous communication cycle comprises a DTX cycle; the transmission comprises a retransmission of a PDSCH from the network entity; and the at least one rule dictates how to monitor for the retransmission of the PDSCH when a retransmission timer starts within an active DTX time.

Clause 14: The method of any one of Clauses 1-12, wherein the at least one rule dictates that at least one of a RTT timer value or retransmission timer value be dynamically updated to allow for processing the transmission.

Clause 15: The method of Clause 13, further comprising receiving an indication of how to dynamically update the RTT timer value or the retransmission timer value.

Clause 16: The method of Clause 14, wherein the indication is received via physical layer signaling, MAC-CE signaling, or RRC signaling.

Clause 17: The method of any one of Clauses 1-16, further comprising determining at least one of: the at least one rule to apply; or how to apply the at least one rule.

Clause 18: The method of Clause 17, wherein the determination is based on at least one of: signaling from the network entity; or a function of data involved in the transmission.

Clause 19: A method for wireless communication by a network entity, comprising: determining that a cell discontinuous communication cycle does not align with a transmission configuration for a transmission to or from a UE; and processing the transmission, based on at least one rule that adjusts at least one of the cell discontinuous communication cycle or the transmission configuration, in response to the determination.

Clause 20: The method of Clause 19, wherein the at least one rule dictates that the cell discontinuous communication cycle be extended to allow for processing the transmission.

Clause 21: The method of Clause 20, wherein: the cell discontinuous communication cycle comprises a DRX cycle; the transmission comprises a retransmission of a PUSCH from the UE; and the at least one rule dictates that the DRX cycle be extended to allow for the retransmission of the PUSCH.

Clause 22: The method of Clause 20, wherein: the cell discontinuous communication cycle comprises a DTX cycle; the transmission comprises a retransmission of a PDSCH from the network entity; and the at least one rule dictates that the DTX cycle be extended to allow for the retransmission of the PDSCH.

Clause 23: The method of Clause 20, further comprising transmitting, to the UE, an indication of whether or not the cell discontinuous communication cycle is extendable.

Clause 24: The method of Clause 23, wherein the indication is transmitted via DCI scheduling an uplink transmission, a DCI scheduling a downlink transmission, or a non-scheduling DCI.

Clause 25: The method of Clause 23, wherein the indication is transmitted via physical layer signaling, MAC-CE signaling, or RRC signaling.

Clause 26: The method of Clause 23, wherein the indication also indicates that the cell discontinuous communication cycle is extendable for processing certain LCGs, LCPs, or QoSs.

Clause 27: The method of Clause 20, further comprising transmitting, to the UE, an indication of how long to extend the cell discontinuous communication cycle.

Clause 28: The method of Clause 27, wherein the indication is transmitted via physical layer signaling, MAC-CE signaling, or RRC signaling.

Clause 29: The method of Clause 27, wherein the indication is transmitted as at least one of a configured RTT timer value, a configured retransmission timer value, or one or more offset values.

Clause 30: The method of Clause 20, further comprising: receiving a status report from the UE; and determining how long to extend the cell discontinuous communication cycle based, at least in part, on the status report.

Clause 31: The method of Clause 20, wherein: the cell discontinuous communication cycle comprises a DTX cycle; the transmission comprises a retransmission of a PDSCH from the network entity; and the at least one rule dictates how to determine a window for the retransmission of the PDSCH when a retransmission timer starts within an active DTX time.

Clause 32: The method of any one of Clauses 19-30, wherein the at least one rule dictates that at least one of a RTT timer value or retransmission timer value be dynamically updated to allow for processing the transmission.

Clause 33: The method of Clause 31, further comprising transmitting, to the UE, an indication of how to dynamically update the RTT timer value or the retransmission timer value.

Clause 34: The method of Clause 32, wherein the indication is transmitted via physical layer signaling, MAC-CE signaling, or RRC signaling.

Clause 35: The method of any one of Clauses 19-34, further comprising determining at least one of: the at least one rule to apply; or how to apply the at least one rule.

Clause 36: The method of Clause 35, wherein the determination is based on at least one of: signaling from the network entity; or a function of data involved in the transmission.

Clause 38: An apparatus, comprising means for performing a method in accordance with any one of Clauses 1-36.

Clause 39: A non-transitory computer-readable medium comprising executable instructions that, when executed by a processor of an apparatus, cause the apparatus to perform a method in accordance with any one of Clauses 1-36.

Clause 40: A computer program product embodied on a computer-readable storage medium comprising code for performing a method in accordance with any one of Clauses 1-36.

Additional Considerations