Fault detection for communication power state switching

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive control information from a network entity indicating a first schedule for the UE to transition between a set of power states. The UE may determine to perform a radio link failure (RLF) or beam failure (BF) detection operation for a radio link or beam used to communicate with a network entity. The UE may apply a second schedule to transition between the set of power states based on the determination. The second schedule may include deferring a transition to a power state of the set of power states. The UE may perform an RLF or BF detection operation based on the application of the second schedule. Additionally or alternatively, the UE may modify operation of a hybrid automatic repeat request (HARQ) round trip time timer based on a power state at which the UE is operating.

Description

TECHNICAL FIELD

[0001] The following relates to wireless communications, including failure detection for communication power state switching. BACKGROUND

[0002] Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems can be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple- access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which can be referred to as New Radio (NR) systems. These systems can employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communications system can include one or more base stations, each simultaneously supporting communication for multiple communication devices, which can be otherwise known as user equipment (UE). SUMMARY

[0003] The described techniques relate to improved methods, systems, devices, and apparatuses that support failure detection for communication power state switching. For example, the described techniques enable a user equipment (UE) to receive control information from a network entity in communication with the UE, the control information indicating a first schedule for the UE to transition between a set of power states. The power states can include at least a sole uplink power state and a second power state, such as a downlink and uplink power state. The UE can determine to perform a radio link failure (RLF) or beam failure (BF) detection operation for a radio link or beam used to communicate with the network entity. The UE can apply a second schedule (e.g., different from the first schedule) to transition between the set of power states based on the determination. The second schedule can include a postponement of a transition of the UE between the power states. For example, the second schedule can indicate that the UE is to postpone a transition from the downlink and uplink power state to the sole uplink state. The UE can perform the RLF or BF detection operation based on applying the second schedule (e.g., prior to transitioning to the sole uplink state).

[0004] In some examples, the control information includes or is an example of downlink control information (DCI). In some cases, the UE can receive an indication to trigger the UE to perform the RLF or BF detection operation, such as within the DCI or as an indication associated with a wake-up signal (WUS). For example, the network entity can monitor a quality of a radio link or one or more beams. If the quality worsens, the network entity can trigger the UE to apply a second schedule (e.g., postpone a transition to a Uplink-Only state) and perform the RLF or BF detection operation. Additionally or alternatively, the UE can modify operation of a hybrid automatic repeat request (HARQ) round trip time (RTT) timer based on a power state in which the UE is operating. For example, the UE can suspend, resume, initiate, or refrain from initiating the HARQ RTT timer as a function of the power state.

[0005] A method for wireless communication by a UE is described. The method can include receiving control information indicating a first schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes an uplink-only state during which a main radio of the UE is used for uplink transmissions and a second state during which the main radio of the UE is used for at least downlink transmissions, determining that the UE is to perform an RLF or BF detection operation, and applying a second schedule for the UE to transition between the set of multiple power states based on the determination that the UE is to perform the RLF or BF detection operation.

[0006] A UE for wireless communication is described. The UE can include one or more memories storing processor-executable code and one or more processors coupled with the one or more memories and singly or collectively operable to execute the code to cause the UE to receive control information indicating a first schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes an uplink-only state during which a main radio of the UE is used for uplink transmissions and a second state during which the main radio of the UE is used for at least downlink transmissions, determine that the UE is to perform an RLF or BF detection operation, and apply a second schedule for the UE to transition between the set of multiple power states based on the determination that the UE is to perform the RLF or BF detection operation.

[0007] Another UE for wireless communication is described. The UE can include means for receiving control information indicating a first schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes a only uplink state during which a main radio of the UE is used for uplink transmissions and a second state during which the main radio of the UE is used for at least downlink transmissions, means for determining that the UE is to perform an RLF or BF detection operation, and means for applying a second schedule for the UE to transition between the set of multiple power states based on the determination that the UE is to perform the RLF or BF detection operation.

[0008] A non-transitory computer-readable medium storing code for wireless communications by a UE is described. The code can include instructions executable by one or more processors to receive control information indicating a first schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes a only uplink state during which a main radio of the UE is used for uplink transmissions and a second state during which the main radio of the UE is used for at least downlink transmissions, determine that the UE is to perform an RLF or BF detection operation, and apply a second schedule for the UE to transition between the set of multiple power states based on the determination that the UE is to perform the RLF or BF detection operation.

[0009] In some examples of the method, apparatus, and non-transitory computer-readable medium described herein, determining that the UE can perform the RLF or BF detection operation can include operations, features, means, or instructions for receiving a DCI message activating the RLF or BF detection operation, where applying the second schedule can be based on reception of the DCI message.

[0010] In some examples of the method, apparatus, and non-transitory computer-readable medium described herein, the second schedule includes a postponement of a transition from the second state to the only uplink state until after an expiration of a failure detection timer associated with the RLF or BF detection operation.

[0011] In some examples of the method, apparatus, and non-transitory computer-readable medium described herein, receiving the DCI message can include operations, features, means, or instructions for receiving an indication that the UE can apply the second schedule.

[0012] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, determining that the UE can be to perform the RLF or BF detection operation can include operations, features, means, or instructions for receiving a WUS associated with an indication that the UE can be to perform the RLF or BF detection operation, where applying the second schedule can be based on reception of the WUS, and where the second schedule includes a postponement of a transition from the second state to the only uplink state; and performing the RLF or BF detection operation after applying the second schedule.

[0013] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the WUS includes an indication of the second schedule, and the second schedule includes a transition to the only uplink state after completion of the RLF or BF detection operation.

[0014] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the control information further indicates a set of multiple schedules for the UE to transition between a set of multiple power states, and the method, apparatuses, and non-transitory computer-readable medium can include further operations, features, means, or instructions for receiving a priority indication associated with the RLF or BF detection operation; and selecting the second schedule from the set of multiple schedules based on the priority indication for the RLF or BF detection operation.

[0015] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, selecting the second schedule from the set of multiple schedules can include operations, features, means, or instructions for selecting the second schedule based on an association between a respective timer duration of the second schedule and the priority indication.

[0016] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the association includes a higher priority can be associated with a longer timer duration before a transition from the second state to the only uplink state, and a lower priority can be associated with a shorter timer duration before the transition from the second state to the only uplink state.

[0017] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, determining that the UE can be to perform the RLF or BF detection operation can include operations, features, means, or instructions for receiving a WUS associated with an indication that the UE can be to perform the RLF or BF detection operation, where applying the second schedule can be based on reception of the WUS, and where the second schedule includes a postponement of a transition from the second state to the only uplink state; and performing the RLF or BF detection operation after applying the second schedule.

[0018] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for receiving an indication of a time duration from reception of the WUS and a transition from the only uplink state to the second state.

[0019] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for performing an RLF or BF detection operation and detecting at least one failure instance during the RLF or BF detection operation, where applying the second schedule can be based on detecting the at least one failure instance, and where the second schedule includes a postponement of a transition from the second state to the only uplink state.

[0020] In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the postponement of the transition from the second state to the only uplink state can be until after expiration of a failure detection timer associated with the RLF or BF detection operation.

[0021] In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the control information further indicates a set of multiple schedules for the UE to transition between the set of multiple power states, and the method, apparatuses, and non-transitory computer-readable medium can include further operations, features, means, or instructions for selecting the second schedule from the set of multiple schedules based on detecting the at least one failure instance.

[0022] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for transmitting an uplink message including an indication that the second schedule can be applied and receiving one or more downlink signals for performing the RLF or BF detection operation based on transmitting the uplink message, where the uplink message can be one of an uplink control information message, a medium access control (MAC) control element (CE), or a physical uplink shared channel message to which the indication can be piggybacked.

[0023] A method of wireless communication by a network entity is described. The method can include transmitting, to a UE, control information indicating a first schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes an only uplink state during which a primary radio of the UE is used for uplink transmissions and a second state during which the primary radio of the UE is used at least for downlink transmissions; determining that the UE is to perform an RLF or BF detection operation; and transmitting, to the UE, a message triggering the UE to transition from the first schedule to a second schedule for the UE to transition between the set of multiple power states based on the determination that the UE is to perform the RLF or BF detection operation.

[0024] A network entity for wireless communication is described. The network entity can include one or more memories storing processor-executable code and one or more processors coupled with the one or more memories and operable, singly or collectively, to execute the code to cause the network entity to transmit, to a UE, control information indicating a first schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes a Uplink-Only state during which a main radio of the UE is used for uplink transmissions and a second state during which the main radio of the UE is used for at least downlink transmissions, determine that the UE is to perform an RLF or BF detection operation, and transmit, to the UE, a message triggering the UE to transition from the first schedule to a second schedule for the UE to transition between the set of multiple power states based on the determination that the UE is to perform the RLF or BF detection operation.

[0025] Another network entity for wireless communication is described. The network entity can include means for transmitting, to a UE, control information indicating a first schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes a Uplink-Only state during which a main radio of the UE is used for uplink transmissions and a second state during which the main radio of the UE is used for at least downlink transmissions, means for determining that the UE is to perform an RLF or BF detection operation, and means for transmitting, to the UE, a message triggering the UE to transition from the first schedule to a second schedule for the UE to transition between the set of multiple power states based on the determination that the UE is to perform the RLF or BF detection operation.

[0026] A non-transitory computer-readable medium storing code for wireless communications by a network entity is described. The code can include instructions executable by one or more processors to transmit, to a UE, control information indicating a first schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes a Uplink-Only state during which a main radio of the UE is used for uplink transmissions and a second state during which the main radio of the UE is used for at least downlink transmissions, determine that the UE is to perform an RLF or BF detection operation, and transmit, to the UE, a message triggering the UE to transition from the first schedule to a second schedule for the UE to transition between the set of multiple power states based on the determination that the UE is to perform the RLF or BF detection operation.

[0027] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, transmitting the message that triggers the UE to transition from the first schedule to the second schedule can include operations, features, means, or instructions for transmitting a DCI message that activates the RLF or BF detection operation.

[0028] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the second schedule includes a postponement of a transition from the second state to the uplink only state until after an expiration of a failure detection timer associated with the RLF or BF detection operation.

[0029] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the DCI message includes an indication that the second schedule is to be applied by the UE.

[0030] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, transmitting the message that triggers the UE to transition from the first schedule to the second schedule can include operations, features, means, or instructions for transmitting a WUS associated with an indication that the RLF or BF detection operation is to be performed by the UE, where the second schedule includes a postponement of a transition from the second state to the uplink only state.

[0031] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the WUS includes an indication of the second schedule, and the second schedule includes a transition to the uplink only state after completion of the RLF or BF detection operation.

[0032] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the message that triggers the UE to transition from the first schedule to the second schedule further indicates a set of multiple schedules for the UE to transition between a set of multiple power states, and the method, apparatuses, and non-transitory computer-readable medium can include further operations, features, means, or instructions for transmitting a priority indication associated with the RLF or BF detection operation.

[0033] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, each schedule of the set of multiple schedules includes a respective timer duration for a postponement of a transition from the second state to the uplink only state.

[0034] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, transmitting the message that triggers the UE to transition from the first schedule to the second schedule can include operations, features, means, or instructions for transmitting a WUS associated with an indication that the RLF or BF detection operation is to be performed by the UE, where the second schedule includes a transition from the uplink only state to the second state.

[0035] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for receiving an indication of a time duration for a transition from the WUS reception and a second state to a first state.

[0036] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for receiving an uplink message including an indication that a second schedule can be applied at the UE; and transmitting one or more downlink signals for RLF or BF detection operations at the UE based on receiving the uplink message, where the uplink message can be one of an uplink control information message, a MAC-CE, or a physical uplink shared channel message to which the indication can be piggybacked.

[0037] A method for wireless communication by a UE is described. The method can include receiving control information indicating a schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes an uplink only state during which a main radio of the UE is used for uplink transmissions, a downlink only state during which the main radio of the UE is used for at least downlink transmissions, and a downlink and uplink state during which the main radio of the UE is used for both downlink transmissions and uplink transmissions; transmitting an uplink message; and modifying operation of a HARQ RTT timer based on a first state of the set of multiple power states in which the UE is located, where the HARQ RTT timer defines a minimum time duration between transmission of the uplink message and reception of a retransmission grant related to a retransmission of the uplink message by the UE.

[0038] A UE for wireless communication is described. The UE can include one or more memories storing processor-executable code and one or more processors coupled with the one or more memories and operable, singly or collectively, to execute the code to cause the UE to receive scheduled control information indicating a transition for the UE between a set of multiple power states, where the set of multiple power states includes a Uplink-Only state during which a main radio of the UE is used for uplink transmissions, a Downlink-Only state during which the main radio of the UE is used for at least downlink transmissions, and a Downlink-and-Uplink state during which the main radio of the UE is used for both downlink transmissions and uplink transmissions, transmit an uplink message, and modify operation of a HARQ RTT timer based on a first state of the set of multiple power states in which the UE is located, where the HARQ RTT timer defines a minimum time duration between transmission of the uplink message and reception of a retransmission grant related to retransmission of the uplink message by the UE.

[0039] Another UE for wireless communication is described. The UE can include means for receiving scheduled control information indicating a transition for the UE between a set of multiple power states, where the set of multiple power states includes a Uplink-Only state during which a main radio of the UE is used for uplink transmissions, a Downlink-Only state during which the main radio of the UE is used for at least downlink transmissions, and a Downlink-and-Uplink state during which the main radio of the UE is used for both downlink transmissions and uplink transmissions, means for transmitting an uplink message, and means for modifying operation of a HARQ RTT timer based on a first state of the set of multiple power states in which the UE is located, where the HARQ RTT timer defines a minimum time duration between transmission of the uplink message and reception of a retransmission grant related to retransmission of the uplink message by the UE.

[0040] A non-transitory computer-readable medium storing code for wireless communications by a UE is described. The code can include instructions executable by one or more processors to receive scheduled control information indicating a transition for the UE between a set of multiple power states, where the set of multiple power states includes a sole uplink state during which a main radio of the UE is used for uplink transmissions, a sole downlink state during which the main radio of the UE is used for at least downlink transmissions, and a downlink and uplink state during which the main radio of the UE is used for both downlink transmissions and uplink transmissions, transmit an uplink message, and modify operation of a HARQ RTT timer based on a first state of the set of multiple power states in which the UE is located, where the HARQ RTT timer defines a minimum time duration between transmission of the uplink message and reception of a retransmission grant related to a retransmission of the uplink message by the UE.

[0041] In some examples of the method, apparatus, and non-transitory computer-readable medium described herein, modifying operation of the HARQ RTT timer can include operations, features, means, or instructions for pausing the HARQ RTT timer based on the first state being the sole downlink state.

[0042] In some examples of the method, apparatus, and non-transitory computer-readable medium described herein, modifying operation of the HARQ RTT timer can include operations, features, means, or instructions for refraining from initiating the HARQ RTT timer based on the first state being the sole uplink state.

[0043] In some examples of the method, apparatus, and non-transitory computer-readable medium described herein, modifying operation of the HARQ RTT timer can include operations, features, means, or instructions for initiating the HARQ RTT timer based on the first state being the sole downlink state or the downlink and uplink state.

[0044] In some examples of the method, apparatus, and non-transitory computer-readable medium described herein, modifying operation of the HARQ RTT timer can include operations, features, means, or instructions for pausing the HARQ RTT timer based on the first state being the sole uplink state.

[0045] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for transitioning to a second state of the set of multiple power states, the second state being one of a downlink and uplink state or a downlink only state, and resuming the HARQ RTT timer based on the second state being the downlink only state or the downlink and uplink state. BRIEF DESCRIPTION OF DRAWINGS

[0046] Figure 1 An example of a wireless communications system that supports fault detection for communication power state switching is shown, in accordance with one or more aspects of the present disclosure.

[0047] Figure 2 An example of a wireless communications system that supports fault detection for communication power state switching is shown, in accordance with one or more aspects of the present disclosure.

[0048] Figure 3A And Figure 3B An example of a communication timeline that supports fault detection for communication power state switching is shown, in accordance with one or more aspects of the present disclosure.

[0049] Figure 4 And Figure 5 An example of a process flow that supports fault detection for communication power state switching is shown, in accordance with one or more aspects of the present disclosure.

[0050] Figure 6 And Figure 7 A block diagram of a device that supports fault detection for communication power state switching is shown, in accordance with one or more aspects of the present disclosure.

[0051] Figure 8 A block diagram of a communications manager that supports fault detection for communication power state switching is shown, in accordance with one or more aspects of the present disclosure.

[0052] Figure 9 A diagram of a system including a device that supports fault detection for communication power state switching is shown, in accordance with one or more aspects of the present disclosure.

[0053] Figure 10 And Figure 11 A block diagram of a device that supports fault detection for communication power state switching is shown, in accordance with one or more aspects of the present disclosure.

[0054] Figure 12 A block diagram of a communications manager that supports fault detection for communication power state switching is shown, in accordance with one or more aspects of the present disclosure.

[0055] Figure 13A diagram illustrating a system that includes a device that supports failure detection for communication power state switching in accordance with one or more aspects of the present disclosure is shown.

[0056] Figures 14 to 19 A flow chart illustrating a method that supports failure detection for communication power state switching in accordance with one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0057] In some wireless communications systems, a wireless device (e.g., a user equipment (UE), a network entity) can support one or more power states. The wireless device can operate in a power state based on a tradeoff between communication performance and power saving. For example, some power states can be associated with operations, parameters, or behaviors that reduce power consumption at the wireless device. Other power states can be configured to support relatively high data throughput, for example, at the cost of increased power consumption. The wireless device can switch between power states to accommodate various scenarios, to achieve appropriate performance, or based on a corresponding directional communication profile for each power state. For example, the wireless device can utilize different power states based on compensating for changes in channel conditions, meeting quality of service (QoS) requirements, or saving power.

[0058] In some cases, the wireless device can use or avoid using a main radio of the wireless device or other circuitry to transmit and receive in one or more communication directions based on a power state in which the wireless device is operating. In downlink and uplink power states, the main radio can be used to transmit and receive uplink and downlink messages, respectively. Alternatively, avoiding communication in at least one communication direction can save power at the wireless device, for example, by allowing the wireless device to turn off transmit or receive circuitry. For example, in a

[0059] However, as such, some power states can constrain or prohibit certain operations at the wireless device. For example, when operating in a Uplink-Only power state, the wireless device can not receive or process (e.g., decode) downlink signals, such as a Physical Downlink Control Channel (PDCCH), a Physical Downlink Shared Channel (PDSCH), and the like. As such, the wireless device can not be able to perform operations that rely on reception of downlink signals, such as radio link failure (RLF) detection and recovery, or beam failure (BF) detection and recovery, among other examples. In such examples, if a communication link between the wireless device and a second wireless device (e.g., a UE, a network entity) suffers a performance degradation during operation in the Uplink-Only state, or if a beam of the communication link fails, the wireless device can lose its connection with the second wireless device and can not be able to perform a recovery procedure.

[0060] Accordingly, the present disclosure provides techniques for a wireless device to transition between power states based on failure detection and recovery. The described techniques can enable a wireless device to avoid entering a power state, such as a low power state (e.g., an Uplink-Only state, a Downlink-Only power state, a modem off state) with a relatively low quality beam or communication link. That is, if the wireless device determines that an RLF or BF is relatively likely, the wireless device can defer a transition to a low power state in order to perform an RLF / BF detection operation. In some examples, the wireless device can be configured to apply a schedule that includes a deferral.

[0061] For example, a wireless device can be configured with a first schedule for transitioning between a set of power states, which can include at least an Uplink-Only power state and a second power state (e.g., a Downlink-Only power state, a downlink and uplink power state). The wireless device can determine that the wireless device is to perform an RLF / BF detection operation on a radio link or beam used to communicate with a second wireless device, such as a network entity. Based on the determination, the wireless device can apply a second schedule to transition between the set of power states. The second schedule can include a deferral of a transition of the wireless device between power states. For example, the wireless device can be operating in the second power state, which can be an example of a downlink and uplink power state. The first schedule can indicate that the wireless device is to transition to the Uplink-Only power state, while the second schedule can include a deferral of the transition to the Uplink-Only power state. Based on the determination to perform the RLF / BF detection operation, the wireless device can apply the second schedule and can avoid transitioning to the Uplink-Only power state. That is, the wireless device can perform the RLF / BF detection operation while the wireless device is operating in a power state in which it is able to receive downlink signals.

[0062] In some cases, a wireless device can receive an indication (e.g., from a network entity) to trigger the wireless device to perform RLF or BF detection operations, such as within control information (e.g., downlink control information (DCI)) or as an indication associated with a wake-up signal (WUS). For example, a network entity can monitor the quality of a radio link or one or more beams. If the quality deteriorates, the network entity can trigger the UE to apply a second schedule (e.g., postpone a transition to a only uplink state). Additionally or alternatively, a wireless device can modify operation of a hybrid automatic repeat request (HARQ) round trip time (RTT) timer based on a power state in which the wireless device is operating. For example, a wireless device can suspend, resume, initiate, or refrain from initiating a HARQ RTT timer as a function of a power state.

[0063] Aspects of the disclosure are first described in the context of a wireless communications system. Aspects of the disclosure are then discussed with reference to communication timelines and process flows. Aspects of the disclosure are further exemplified and described by reference to apparatus diagrams, system diagrams, and flowcharts related to failure detection for communication power state switching.

[0064] Figure 1 An example of a wireless communications system 100 that supports failure detection for communication power state switching is shown in accordance with one or more aspects of the present disclosure. The wireless communications system 100 can include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 can be a Long Term Evolution (LTE) network, a LTE-Advanced (LTE-A) network, a LTE-A Pro network, a New Radio (NR) network, or a network operating according to other wireless communications systems and radio technologies including future iterations of the aforementioned systems and radio technologies, and other systems and radio technologies not explicitly mentioned herein.

[0065] The network entities 105 can be dispersed throughout the geographic area of the wireless communications system 100, and can be associated with or include one or more network equipment identities. In various examples, the network entities 105 can be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment identities, among other nomenclature. In some examples, the network entities 105 and the UEs 115 can wirelessly communicate with one another via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, a network entity 105 can support a coverage area 110 (e.g., a geographic coverage area) within which UEs 115 and the network entity 105 can establish one or more communication links 125. The coverage area 110 can be an example of a geographic area over which a network entity 105 and a UE 115 can support

[0066] The UEs 115 can be dispersed throughout the coverage areas 110 of the wireless communications system 100, and each UE 115 can be stationary, or mobile, or both at different times. The UEs 115 can be devices in different forms or having different capabilities. Figure 1 Some example UEs 115 are illustrated. The UEs 115 described herein can be able to support Figure 1 communications with other UEs 115 or network entities 105 as shown.

[0067] As described herein, a node of the wireless communications system 100 (which can be referred to as a network node or a wireless node) can be a network entity 105 (e.g., any of the network entities described herein), a UE 115 (e.g., any of the UEs described herein), a network controller, a device, an apparatus, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node can be a UE 115. As another example, a node can be a network entity 105. As yet another example, a first node can be configured to communicate with a second node or a third node. In one aspect of this example, the first node can be a UE 115, the second node can be a network entity 105, and the third node can be a UE 115. In another aspect of this example, the first node can be a UE 115, the second node can be a network entity 105, and the third node can be a network entity 105. In other aspects of this example, the first node, the second node, and the third node can be different with respect to these examples. Similarly, references to a UE 115, a network entity 105, a device, an apparatus, a computing system, etc., can include the disclosure of the UE 115, the network entity 105, the device, the apparatus, the computing system, etc., as a node. For example, a disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.

[0068] In some examples, the network entities 105 can communicate with the core network 130 or with each other or both. For example, the network entities 105 can communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to an SI, N2, N3, or other interface protocol). In some examples, the network entities 105 can communicate with each other via backhaul communication links 120 (e.g., according to an X2, Xn, or other interface protocol) either directly (e.g., direct point-to-point between network entities 105) or indirectly (e.g., via core network 130). In some examples, the network entities 105 can communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or front-haul communication links 168 (e.g., according to a front-haul interface protocol), or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or front-haul communication links 168 can be or include one or more wired links (e.g., electrical, fiber optic), one or more wireless links (e.g., radio, wireless optical), etc., or various combinations thereof. The UEs 115 can communicate with the core network 130 via communication links 155.

[0069] One or more of the network entities 105 described herein can include or can be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an evolved NodeB (eNB), a Next Generation NodeB or Guya NodeB (any of which can be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a Home NodeB, a Home eNodeB, or other suitable terminology). In some examples, the network entities 105 (e.g., base stations 140) can be implemented in an aggregated (e.g., monolithic, self-standing) base station architecture that can be configured to utilize protocol stacks that are physically or logically integrated within a single network entity 105 (e.g., a single RAN node such as a base station 140).

[0070] In some examples, the network entity 105 can be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that can be configured to utilize a protocol stack distributed physically or logically among two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 can include one or more of a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near-RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 can also be referred to as a radio head, an intelligent radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entity 105 in the disaggregated RAN architecture can be co-located, or one or more components of the network entity 105 can be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the disaggregated RAN architecture can be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0071] The functional split between the CU 160, the DU 165, and the RU 170 is flexible and can support different functionality depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at the CU 160, the DU 165, or the RU 170. For example, a functional split of the protocol stack can be employed between the CU 160 and the DU 165, such that the CU 160 can support one or more layers of the protocol stack, and the DU 165 can support one or more different layers of the protocol stack. In some examples, the CU 160 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 can connect to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 can host lower protocol layers, such as layer 1 (LI) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and can each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack can be employed between the DU 165 and the RU 170, such that the DU 165 can support one or more layers of the protocol stack, and the RU 170 can support one or more different layers of the protocol stack. The DU 165 can support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between the CU 160 and the DU 165 or between the DU 165 and the RU 170 can be within a protocol layer (e.g., some functions of a protocol layer can be performed by one of the CU 160, the DU 165, or the RU 170, while other functions of that protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170). The CU 160 can be further split in function into CU control plane (CU-CP) and CU user plane (CU-UP) functionality. The CU 160 can connect to one or more DUs 165 via a backhaul communication link 162 (e.g., Fl, Fl-c, Fl-u), and the DU 165 can connect to one or more RUs 170 via a front-haul communication link 168 (e.g., open front-haul (FH) interface). In some examples, the backhaul communication link 162 or the front-haul communication link 168 can be implemented in accordance with an interface (e.g., channel) between layers of a protocol stack supported by the respective network entities 105 that communicate via these communication links.

[0072] In some wireless communications systems (e.g., wireless communications system 100), infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections to provide an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) can be partially controlled by one another. One or more IAB nodes 104 can be referred to as a donor entity or IAB donor. One or more DUs 165 or one or more RUs 170 can be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) can communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). An IAB node 104 can include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled DU 165 of an IAB donor. The IAB-MT can include a separate set of antennas for relaying communications with UEs 115 or can share the same antennas (e.g., of an RU 170) of the IAB node 104 for accessing via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, an IAB node 104 can include a DU 165 that supports a communication link with an additional entity (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of an access network. In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes 104 or components of an IAB node 104) can be configured to operate according to the techniques described herein.

[0073] For example, an access network (AN) or RAN can include communications between an access node (e.g., an IAB donor), an IAB node 104, and one or more UEs 115. The IAB donor can facilitate a connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor can refer to a RAN node that has a wired or wireless connection to the core network 130. The IAB donor can include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 can communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 can communicate via an Fl interface according to a protocol that defines signaling messages (e.g., the Fl-AP protocol). Additionally or alternatively, the CU 160 can communicate with the core network via an interface that can be an example of a backhaul link, and can communicate with other CUs 160 (e.g., associated with alternative IAB donors) via an Xn-C interface that can be an example of a backhaul link.

[0074] The IAB node 104 can refer to a RAN node that provides IAB functionality (e.g., for access for UEs 115, wireless self-backhauling capabilities). The DU 165 can act as a distributed scheduling node toward child nodes associated with the IAB node 104, and the IAB-MT can act as a scheduled node toward parent nodes associated with the IAB node 104. That is, the IAB donor can be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB donor can relay transmissions of a UE through one or more other IAB nodes 104). Additionally or alternatively, the IAB node 104 can also be referred to as a parent node or a child node of other IAB nodes 104, according to a relay chain or configuration of the AN. Thus, the IAB-MT entity of the IAB node 104 can provide a Uu interface for a child IAB node 104 to receive signaling from a parent IAB node 104, and the DU interface (e.g., DU 165) can provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or a UE 115.

[0075] For example, an IAB node 104 can be referred to as a parent node that supports communications for a child IAB node or as a child IAB node associated with an IAB donor or both. An IAB donor can include a CU 160 with a wired or wireless connection (e.g., backhaul communication link 120) to a core network 130 and can act as a parent node for an IAB node 104. For example, a DU 165 of an IAB donor can relay transmissions to a UE 115 through an IAB node 104 or can signal transmissions directly to the UE 115 or both. The CU 160 of the IAB donor can signal communication link establishment to the IAB node 104 via an Fl interface and the IAB node 104 can schedule transmissions (e.g., transmissions relayed from the IAB donor to the UE 115) by the DU 165. That is, data can be relayed to and from the IAB node 104 via signaling via an NR Uu interface to an MT of the IAB node 104. Communications with the IAB node 104 can be scheduled by a DU 165 of the IAB donor and communications with the IAB node 104 can be scheduled by a DU 165 of the IAB node 104.

[0076] In cases where the techniques described herein are applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture can be configured to support fault detection for communication power state switching as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) can additionally or alternatively be performed by one or more components of a disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0077] A UE 115 can include or can be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” can also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 can also include or can be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 can include or can be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which can be implemented in various objects such as appliances or vehicles, among other examples.

[0078] The UEs 115 described herein can be able to communicate with various types of devices, such as other UEs 115 that can sometimes act as relays or can be network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1. The network equipment can include or communicate with an eNB or gNB that can be included or be part of a base station, or network access equipment, among other examples. The equipment can be part of or include an access node or access point. A base station can include or communicate with a central unit (CU) or a distributed unit (DU).Figure 1 are shown.

[0079] The UEs 115 and the network entities 105 can wirelessly communicate with each other using resources associated with one or more carriers via one or more communication links 125 (e.g., access links). The term “carrier” can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication links 125. For example, a carrier used for a communication link 125 can include a portion of an RF spectrum band (e.g., a bandwidth part (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel can carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operations of the carrier, user data, or other signaling. The wireless communications system 100 can support communication with UEs 115 using carrier aggregation or multi-carrier operation. According to carrier aggregation, a UE 115 can be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used for both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communications between a network entity 105 and other devices can refer to communications between these devices and any part of the network entity 105 (e.g., an entity, sub-entity). For example, the terms “transmit,” “receive,” or “communicate” when referring to a network entity 105 can refer to any part of the network entity 105 of a RAN (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0080] In some examples, such as in carrier aggregation configurations, a carrier can also have acquisition signaling or control signaling that coordinates operations of other carriers. A carrier can be associated with a frequency channel (e.g., an evolved universal mobile telecommunications system terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN)) and can be identified according to a channel raster for discovery by UEs 115. A carrier can be operated in a standalone mode where initial acquisition and connection can be performed by a UE 115 via the carrier, or the carrier can be operated in a non-standalone mode where a different carrier (e.g., of a same or different radio access technology) is used for anchoring connection.

[0081] The communication links 125 shown in wireless communication system 100 can include downlink transmissions, from a network entity 105 to a UE 115, uplink transmissions, from a UE 115 to a network entity 105, or both, as well as other transmission configurations. A carrier can carry downlink or uplink communications (e.g., in an FDD mode) or can be configured to carry downlink and uplink communications (e.g., in a TDD mode).

[0082] A carrier can be associated with a particular bandwidth of the RF spectrum, and in some examples the carrier bandwidth can be referred to as a “system bandwidth” of the carrier or wireless communication system 100. For example, the carrier bandwidth can be one of a set of bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of wireless communication system 100 (e.g., network entities 105, UEs 115, or both) can have hardware configurations that support communications using a particular carrier bandwidth or can be configurable to support communications using one of a set of carrier bandwidths. In some examples, wireless communication system 100 can include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 can be configured for operating

[0083] Signal waveforms transmitted over carriers can be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM). In a system employing MCM techniques, a resource element can refer to a resource comprising a symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing can be inversely related. A number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the

[0084] One or more numerologies can be supported for a carrier, and a numerology can include a subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, UE 115 can be configured with multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and the communication of UE 115 can be constrained to one or more active BWPs.

[0085] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which This can represent the supported subcarrier spacing, while The supported Discrete Fourier Transform (DFT) size can be represented. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0086] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0087] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0088] Physical channels can be multiplexed according to various techniques to communicate using a carrier. For example, physical control channels and physical data channels can be multiplexed for signaling via a downlink carrier using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) of a physical control channel can be defined by a collection of symbol periods and can extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) can be configured for a set of UEs 115. For example, one or more of the UEs 115 can monitor or search control regions for control information according to one or more search space sets, and each search space set can include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate can refer to a quantity of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. Search space sets can include common search space sets configured for transmitting control information to multiple UEs 115 and UE-specific search space sets for transmitting control information to a specific UE 115.

[0089] A network entity 105 can provide communication coverage for a geographic area 110 via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term “cell” can refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and can be associated with a identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifiers) used by a network entity 105 to distinguish one cell from another. In some examples, a cell can also refer to a coverage area 110 or a portion (e.g., a sector) of a coverage area 110 within which a logical communication entity operates. The range of such a cell can be from a small area (e.g., a structure, a subset of a structure, or a sub-area of a structure) to a large area depending on various factors such as the ability of a network entity 105. For example, a cell can be or include a building, a subset of a building, or an outdoor space between or overlapping coverage areas 110, among other examples.

[0090] Macrocells generally cover relatively large geographic areas (e.g., a radius of several kilometers) and can allow unrestricted access by UEs 115 with service subscriptions with the network provider supporting the macrocell. Small cells can be associated with a lower- powered network entity 105 (e.g., a low-power base station 140) and can provide restricted or no access by UEs 115 with service subscriptions with the network provider supporting the small cell. For example, small cells can be configured to provide service only to UE 115 within a specific area, to provide service to specific UE 115, or to provide service to UE 115 with specific subscriptions. A network entity 105 can support one or multiple cells, and can also use one or multiple component carriers to support communications via one or more cells.

[0091] In some examples, a carrier can support multiple cells, and different cells can be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that can provide access for different types of devices.

[0092] In some examples, network entities 105 (e.g., base stations 140, RUs 170) can be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies can overlap, but different coverage areas 110 can be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies can be supported by different network entities 105. Wireless communication system 100 can include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0093] Wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) can have similar frame timings, and transmissions from different network entities 105 can be approximately aligned in time. For asynchronous operation, the network entities 105 can have different frame timings, and transmissions from different network entities 105 can not be aligned in time. The techniques described herein can be used for synchronous or asynchronous operation.

[0094] Some UEs 115, such as MTC or IoT devices, can be low cost or low complexity devices, and can provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., base station 140) without the need for human intervention. In some examples, M2M communication or MTC can include communications from devices that integrate sensors or meters to measure or acquire information and relay such information to a central server or application program, which can make use of the information or present the information to humans in interaction with the application program. Some UEs 115 can be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management, remote security sensing, physical access control, and transaction-based business charging.

[0095] Some UEs 115 can be configured to employ operating modes that reduce power consumption, such as a half-duplex communication (e.g., a mode where a device is capable of receiving or transmitting at a time but not both). In some examples, half-duplex communications can be performed at a reduced peak rate. Other energy saving techniques for UEs 115 include entering a power saving deep sleep mode when not engaging in active communications, operating over a limited bandwidth (e.g., according to a narrowband

[0096] The wireless communications system 100 can be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 can be configured to support ultra-reliable low-latency communications (URLLC). UEs 115 can be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communications can include private communication or group communication, and can be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions can include prioritization of services, and such services can be for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency can be used interchangeably herein.

[0097] In some examples, UEs 115 can be configured to communicate directly with other UEs 115 via device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P) or D2D or sidelink protocol). In some examples, one or more UEs 115 in a group that is performing D2D communication can be within the coverage area 110 of a network entity 105 (e.g., base station 140, RU 170) that supports such D2D communication. In some examples, one or more UEs 115 in such a group can be outside the coverage area 110 of a network entity 105 or can not be able to, or enabled to, access the network entity 105 for one reason or another. In some examples, a group of UEs 115 communicating via D2D communications can support one-to-many (1:M) system in which each UE 115 transmits to every other UE 115 in the group. In some examples, a network entity 105 can facilitate scheduling of resources for D2D communications. In some other examples, D2D communication can be carried out between UEs 115 without the involvement of a network entity 105.

[0098] In some systems, D2D communication link 135 can be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115). In some examples, vehicles can communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. A vehicle can signal information about traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to V2X systems. In some examples, a vehicle in a V2X system can communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., network entities 105, base stations 140, RUs 170) using vehicle-to-network (V2N) communications, or both.

[0099] The core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 can be an evolved packet core (EPC) or 5G core (5GC), which can include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity can manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for UEs 115 served by network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets can be transferred through the user plane entity, which can provide IP address allocation as well as other functions. The user plane entity can be connected to the IP services 150 of one or more network operators. The IP services 150 can include access to the Internet, Intranet(s), an IP multimedia subsystem (IMS), or a packet-switched streaming service.

[0100] The wireless communications system 100 can operate using one or more frequency bands, one or more duplexing techniques, one or more network technologies, or a combination thereof. In some examples, the wireless communications system 100 can operate in an ultra-high frequency (UHF) region using technologies including, but not limited to, New Radio (NR) technologies. Thus, the wireless communications system 100 can employ stand-alone NR (SNR) or NR-based access (NBRT) technologies. In some examples, the wireless communications system 100 can use frequency range 1 (FR1) sub-bands from 450 to 6000 MHz. In some examples, the wireless communications system 100 can use frequency range 2 (FR2) sub-bands from 24.25 to 52.6 GHz. In some examples, the wireless communications system 100 can use frequency range 3 (FR3) sub-bands from 52.6 to 71 GHz. In some examples, the wireless communications system 100 can use frequency range 4 (FR4) sub-bands from 71 GHz to 90 GHz. In some examples, the wireless communications system 100 can use frequency range 5 (FR5) sub-bands from 90 GHz to 300 GHz. In some examples, the wireless communications system 100 can use one or more other frequency ranges.

[0101] The wireless communications system 100 can also utilize a super high frequency (SHF) region (also known as the centimeter band) of the frequency spectrum, which can include frequencies between 3 GHz and 30 GHz, or an extremely high frequency (EHF) region (also known as the millimeter band) of the frequency spectrum, which can include frequencies from 30 GHz to 300 GHz. In some examples, the wireless communications system 100 can support millimeter wave (mmW) communications between the UEs 115 and the network entities 105 (e.g., base stations 140, RUs 170), and EHF antennas of the respective devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques can facilitate use of antenna arrays within a device. However, propagation of EHF transmissions can be subject to even greater atmospheric attenuation relative to SHF or UHF transmissions, and EHF transmissions can be blocked or hindered by everyday objects, which can be used to support the techniques disclosed herein. The techniques disclosed herein can be employed across transmissions that use one or more different frequency regions, and designated frequency bands within these frequency regions, and can be applied to transmissions between a base station 140 and a UE 115, between two UEs 115, between two base stations 140, or over other devices or systems in which communications can occur.

[0102] The wireless communications system 100 can utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 can employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed frequency spectrum band, such as the 5 GHz industrial, scientific and medical (ISM) band. When operating in unlicensed frequency spectrum bands, access points and UEs such as the network entities 105 and the UEs 115 can employ carrier sensing for collision detection and avoidance, in some examples, operations in unlicensed frequency spectrum bands can be based on a carrier aggregation configuration in which a primary component carrier (PCC) is operated by a network entity 105 in a licensed frequency spectrum band and one or more additional component carriers (ACCCs) are operated by the network entity 105 in an unlicensed frequency spectrum band. Operations in unlicensed frequency spectrum bands can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0103] The network entities 105 (e.g., base stations 140, RUs 170) or UEs 115 can be equipped with multiple antennas, which can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of a network entity 105 or a UE 115 can be located in one or more antenna arrays or antenna panels, which can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays can be collocated, such as at an antenna assembly of an antenna tower, in some examples, the antennas or antenna arrays associated with a network entity 105 can be located at different geographic locations. A network entity 105 can include an array of antennas with multiple rows and columns of antenna ports that the network entity 105 can use for beamforming to support communication with UEs 115. Likewise, a UE 115 can include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, antenna panels can support RF beamforming of signals transmitted via the antenna ports.

[0104] The network entity 105 or the UE 115 can use MIMO communications to exploit multipath signal propagation and increase the spectral efficiency of a wireless communication system. Such techniques can be referred to as spatial multiplexing. The multiple signals can, for example, be transmitted by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream, and can carry

[0105] Beamforming, which can also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer a beam of energy in a specific direction, for example, along with the spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining the signals communicated by antennas of an antenna array such that some signals propagating at particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated by antennas of an antenna array can include instructing the antennas to phase shift signals in a particular manner. The adjustment of signals can be elicits signals with particular characteristics (e.g., amplitude, phase, polarity, and / or other characteristics).

[0106] The network entity 105 or UE 115 can use beam sweeping techniques as part of a beamforming operation. For example, a network entity 105 (e.g., a base station 140, a RU 170) can use multiple antennas or antenna arrays (e.g., antenna panels) to conduct a beamforming operation for directional communications with a UE 115. Some signals (e.g., synchronization signals, reference signals, beam- selection signals, or other control signals) can be transmitted by the network entity 105 multiple times in different directions. For example, the network entity 105 can transmit the signals according to different beamforming weight sets associated with different directions. Transmissions in different beam directions can be used, for example, to identify (e.g., by a transmitting device, such as a network entity 105, or by a receiving device, such as a UE 115) a beam direction for subsequent transmission or reception by the network entity 105.

[0107] Some signals, such as data signals associated with a particular receiving device, can be transmitted by a transmitting device (e.g., a transmitting network entity 105, a transmitting UE 115) in a single beam direction (e.g., a direction associated with the receiving device, such as a receiving network entity 105 or a receiving UE 115). In some examples, the beam direction associated with transmissions in a single beam direction can be determined based on a signal that was transmitted in one or more beam directions. For example, a UE 115 can receive one or more of the signals transmitted by the network entity 105 in different directions, and can report to the network entity 105 an indication of the signal that the UE 115 received with a highest signal quality, or other acceptable signal quality.

[0108] In some examples, transmissions by a device (e.g., by a network entity 105 or a UE 115) can be performed using multiple beam directions, and the device can use a combination of digital precoding or beamforming to generate a combined beam for transmissions (e.g., from a network entity 105 to a UE 115). The UE 115 can report feedback that indicates precoding weights for one or more beam directions, and the feedback can correspond to a set of beams that are configured across a system bandwidth or one or more sub-bands. The network entity 105 can transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)) that can or can not be precoded. The UE 115 can provide feedback for beam selection, which can be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals transmitted by a network entity 105 (e.g., a base station 140, a RU 170) in one or more directions, a UE 115 can use similar techniques for transmitting signals multiple times in different directions (e.g., for identifying a beam direction for subsequent transmission or reception by a UE 115), or for transmitting a signal in a single direction (e.g., for transmitting data to a receiving device).

[0109] A receiving device (e.g., a UE 115) can perform reception operations according to multiple receive configurations (e.g., directional listening) when receiving various signals from a transmitting device (e.g., a network entity 105), such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device can perform reception according to multiple receive directions by using different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which can be referred to as“listening” according to different receive configurations or receive directions. In some examples, a receiving device can use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receive configuration can be aligned in a beam direction determined based on listening in different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening in multiple beam directions).

[0110] Wireless communications system 100 can be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer can be IP -based. A RLC layer can perform packet segmentation and reassembly to communicate over logical channels. A MAC layer can perform priority handling and multiplexing of logical channels into transport channels. The MAC layer can also implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency. In the control plane, the RRC layer can provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or core network 130 supporting radio bearers for user plane data. The PHY layer can map transmission channels to physical channels.

[0111] UEs 115 and network entities 105 can support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique used to increase the likelihood that data is received correctly over a communication link, such as communication link 125, D2D communication link 135. HARQ can include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve throughput at the MAC layer in poor radio conditions, such as low signal-to-noise conditions. In some examples, a device can support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific slot for data received in a previous symbol in the slot. In some other examples, the device can provide HARQ feedback in a subsequent slot, or according to some other time interval.

[0112] In some examples, the wireless communications system 100 can support multiple power states (e.g., network power states, network energy states, UE power states) for wireless devices, such as UEs 115 and network entities 105. Each power state can be associated with a configuration of the wireless device that is tailored for a respective traffic profile. That is, a power state can include or be an example of a set of parameters or behaviors that optimize operation of the wireless device in a corresponding communication state. For example, some power states can be configured for high data rate or high throughput communications, while other power states can be configured for low data rate communications or low power consumption. A low power state can refer to a power state in which the wireless device turns off circuitry for one or more (e.g., all) communication directions. For example, in an uplink-only power state, the wireless device can turn off receive circuitry, while in a downlink-only power state, the wireless device can turn off transmit circuitry. In a modem-off state, the wireless device can turn off all modem (e.g., transmit and receive circuitry) and can not transmit or receive. In some cases, a power state can be configured to achieve maximum power saving while meeting quality of service (QoS) requirements of a corresponding traffic profile.

[0113] A wireless device can transition between power states based on one or more timers, one or more schedules, a change in a traffic profile, feedback information, or reception of an indication to adapt to different communication scenarios or traffic profiles. For example, a UE 115 can transition from a first power state to a second power state based on reception of control signaling (e.g., DCI, MAC-CE) from a network entity 105, where the control signaling indicates the second power state to the UE 115. The UE 115 can transition from the second power state back to the first power state based on expiration of a timer at the UE 115. In other examples, the UE 115 can transition between power states based on satisfaction of a condition. For example, the condition can be satisfied based on the UE 115 initiating a retransmission timer, transmitting a negative acknowledgement message for one or more downlink messages, operating in an active period of the second power state, receiving a burst of downlink messages, receiving a second control message indicating the second power state, expiration of a timer, or any combination thereof. In yet another example, the UE 115 can be configured to periodically transition between a first power state associated with relatively low power consumption and a second power state associated with relatively high data throughput, e.g., according to a duty cycle, a schedule, one or more timers, etc.

[0114] To maintain communication with the network entity 105, the UE 115 can be configured to perform RLF detection and recovery, BF detection and recovery, or some combination thereof for a communication link 125 (e.g., a radio link) between the UE 115 and the network entity 105. The communication link 125, as well as one or more beams (e.g., beam pairs) used for communication via the communication link 125, can be susceptible to blockage, interruption, and degradation, which can disrupt the ability of the UE 115 to communicate with the network entity 105. A BF can be understood as a connection failure of a beam, and the UE 115 can reestablish a connection with the network entity 105 by switching beams used to communicate with the network entity 105 during a beam recovery procedure. An RLF can occur when the UE 115 fails to connect to the network entity 105, for example, if the UE 115 is unable to find any suitable beams or if the UE 115 is unable to perform a successful random access procedure with the network entity 105.

[0115] To detect RLF or BF, the UE 115 and the network entity 105 can monitor the quality of the communication link 125 and one or more beams. The network entity 105 can configure (e.g., RRC configuration) the UE 115 with a set of resources and one or more parameters to be used for RLF / BF detection and recovery. The network entity 105 can transmit one or more downlink signals (e.g., one or more downlink reference signals, such as synchronization signal blocks (SSBs), channel state information (CSI) reference signals (CSI-RSs), etc.) to the UE 115 using one or more beams, and the UE 115 can perform one or more measurements based on receiving the one or more downlink signals. The UE 115 can detect a beam failure instance (BFI) of a beam when a measured value of a downlink signal transmitted using the beam (e.g., a reference signal received power (RSRP), a reference signal received quality (RSRQ), a signal to interference plus noise ratio (SINR)) is below a signal quality threshold (e.g., as configured by the network entity 105). A BF can occur when the UE 115 detects a threshold number of BFIs of a beam.

[0116] Upon detecting a BF, the UE 115 can initiate a recovery procedure (e.g., a beam recovery procedure), in which the UE 115 searches for new candidate beams. The UE 115 can select a best candidate beam during the recovery procedure by receiving and measuring downlink reference signals received using respective beams (e.g., according to a configured set of resources), where the “best” candidate beam refers to the beam having the best signal quality relative to other beams. The UE 115 can use the selected beam to initiate a random access procedure with the network entity 105. For example, the UE 115 can use the selected beam to transmit a random access preamble to the network entity 105. In some cases, if the UE 115 is unable to recover the connection during the beam recovery procedure after detecting a BF, the UE 115 can assume an RLF.

[0117] Because RLF / BF detection and recovery procedures utilize downlink reference signals, the UE 115 can be unable to reestablish a connection with the network entity 105 when operating in some power states, such as a sole uplink power state. That is, in a sole uplink power state, the UE 115 can not receive or decode downlink signals, including those used in RLF / BF detection and recovery procedures. Thus, if an RLF or BF occurs during operation in a sole uplink state, the UE 115 can suffer from degraded performance, increased latency, reduced communication reliability, and the like.

[0118] According to the techniques described herein, a UE 115 operating in a first power state (e.g., a sole downlink power state, a downlink and uplink power state, and the like) can defer a transition to a second power state (e.g., a sole uplink state, a modem off state) if the UE 115 determines that an RLF / BF detection operation is necessary. In some aspects, the UE 115 can be triggered to initiate an RLF / BF detection operation by the network entity 105. For example, the network entity 105 can transmit a signal (e.g., a DCI, a WUS) that activates the RLF / BF detection operation, and the UE 115 can receive the signal. In other examples, the UE 115 can autonomously determine to perform an RLF / BF detection operation, e.g., based on detecting one or more BFI.

[0119] The network entity 105 can configure the UE 115 with a first schedule for transitioning between a set of power states, which can include at least a first power state and a second power state. Based on determining that the UE 115 is to perform an RLF / BF detection operation, the UE 115 can apply a second schedule (e.g., different from the first schedule) to transition between the set of power states. The second schedule can include a deferral of the UE 115 transitioning between power states such that the UE 115 avoids transitioning to the second power state based on applying the second schedule. The UE 115 can perform the RLF / BF detection operation while the UE 115 is operating in the first power state (e.g., in which the UE 115 is capable of receiving downlink signals). Additionally, or alternatively, the UE 115 can modify operation of a HARQ RTT timer based on a power state in which the UE 115 is operating. For example, the UE 115 can suspend, resume, initiate, or avoid initiating the HARQ RTT timer as a function of the power state.

[0120] Figure 2 An example of a wireless communications system 200 that supports failure detection for communication power state switching is shown, in accordance with one or more aspects of the present disclosure. For example, the wireless communications system 200 can include one or more network entities 105 (e.g., network entity 105-a) and one or more UEs 115 (e.g., UE 115-a), which can be examples of the corresponding devices as described with reference to FIG. 1. The wireless communications system 200 can support using one or more schedules for transitioning between power states based on RLF / BF detection. Figure 1

[0121] In the wireless communications system 200, the UE 115-a and the network entity 105-a can communicate via one or more communication links 125 in the coverage area 110-a. For example, the network entity 105-a can transmit downlink signals, such as control messages 205, DCI 207, or WUS 210, via a communication link 125-a, which can include or be an example of a downlink communication link (e.g., PDCCH, PDSCH). The UE 115-a can monitor the communication link 125-a to detect, receive, and decode the downlink signals. Additionally, or alternatively, the UE 115-a can transmit uplink signals, such as uplink messages 212, to the network entity 105-a via a communication link 125-b, which can include or be an example of an uplink communication link (e.g., physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH)). The network entity 105-a can monitor the communication link 125-b to detect, receive, and decode the uplink signals.

[0122] ​The UE 115-a and the network entity 105-a can implement RLF / BF detection and recovery operations to maintain the communication link 125. The network entity 105-a can transmit control signaling (e.g., RRC signaling), such as a control message 205, to the UE 115-a indicating a configuration (e.g., RRC configuration) for RLF / BF detection and recovery. The control message 205 can include, for example, an RLF detection and recovery configuration (e.g., RadioLinkMonitoringConfig), a BF detection and recovery configuration (e.g., BeamFailureRecoveryConfig), or a combination thereof, and can indicate one or more parameters for performing RLF / BF detection and recovery operations at the UE 115-a. The one or more parameters can include a threshold number of BFIs (e.g., BeamFailureInstanceMaxCount), one or more time durations for one or more timers (e.g., BeamFailureDetectionTimer, BeamFailureRecoveryTimer), or resources for beam selection during a recovery procedure (e.g., failureDetectionResourcesToAddModList, failureDetectionResourcesToReleaseList), among other examples or combinations thereof.

[0123] To perform RLF / BF detection operations, the network entity 105-a can transmit downlink reference signals to the UE 115-a via the communication link 125-a using one or more beams. The UE 115-a can measure the downlink reference signals to obtain one or more measurement values (e.g., RSRP, RSRQ, SINR) associated with signal strength, signal quality, and the like for the communication link 125-a or the one or more beams. The UE 115-a can determine whether an RLF or a BF has occurred (e.g., can detect an RLF or a BF) based on the measurement values for the associated communication link 125-a, one or more beams, or a combination thereof. For example, a BFI can refer to an instance in which the UE 115-a measures a reference signal to have a signal quality that fails to satisfy a threshold (e.g., a signal quality threshold, such as an RSRP value threshold, or an error rate threshold, such as an estimated block error rate (BLER) for a hypothetical PDCCH). The UE 115-a can detect a BF based on detecting a threshold number of BFIs (e.g., beamFailureInstanceMaxCount), and can initiate a beam recovery procedure based on detecting the BF. If the UE 115-a fails to perform beam recovery and is no longer able to establish a connection with the network entity 105-a, the UE 115-a can detect an RLF and can initiate a radio link recovery procedure.

[0124] The RLF / BF detection operation can be a combined Layer One (LI) (e.g., physical (PHY) layer) and Layer Two (L2) (e.g., MAC layer) procedure. The LI of the UE 115-a can detect a BFI by detecting that a reference signal of a serving beam fails to satisfy a threshold. The LI can indicate the BFI to the MAC layer. The MAC layer can initiate a beam failure detection timer (e.g., BeamFailureDetectionTimer) and a counter (e.g., BFI_COUNTER) based on receiving the indication of the BFI from the LI. For each BFI that occurs within a duration of the beam failure detection timer, the MAC layer can increment the counter by one (1). In some examples, the MAC layer can additionally reset the beam failure detection timer each time the MAC layer receives an indication of a BFI. When the value of the counter exceeds a threshold number of BFIs (e.g., beamFailurelnstanceMaxCount), the MAC layer can determine that a BF has occurred and can trigger (e.g., initiate) a beam recovery procedure. Alternatively, if the signal quality has improved and the LI no longer detects a BFI, the MAC layer can determine not to perform a beam recovery. For example, if the MAC layer does not receive any BFI indications from the LI and the beam failure detection timer expires (e.g., if the LI does not detect any BFIs within a duration of the beam failure detection timer), the MAC layer can reset the counter and can not perform a beam recovery procedure. The UE 115-a can instead continue to use the same serving beam.

[0125] In some aspects, the UE 115-a can be triggered to initiate the RLF / BF detection operation by the network entity 105-a. For example, the network entity 105-a can monitor the quality of the communication link 125 and one or more beams to detect an RLF or a BF. If the network entity 105-a determines that the quality of the communication link 125 or the one or more beams is relatively poor, or if the network entity 105-a detects a threshold number of BFIs, the network entity 105-a can transmit a signal (e.g., DCI 207, WUS 210) that activates the RLF / BF detection operation, and the UE 115-a can receive the signal. In another example, the UE 115-a can detect one or more BFIs and can report the one or more BFIs to the network entity 105-a, e.g., in an uplink message 212 (e.g., can transmit an indication of the one or more BFIs). Based on receiving the uplink message 212, the network entity 105-a can activate the RLF / BF detection operation by transmitting control signaling, such as DCI 207, to the UE 115-a. Alternatively, the UE 115-a can determine to perform the RLF / BF detection operation autonomously, e.g., based on detecting the one or more BFIs.

[0126] If the UE 115-a, the network entity 105-a, or both detect an RLF or a BF for the communication link 125 or one or more beams, the UE 115-a can perform an RLF / BF recovery operation. Upon detecting a BF, or based on receiving control signaling to activate a recovery procedure, the UE 115-a can initiate a recovery procedure (e.g., a beam recovery procedure) in which the UE 115-a uses the resources indicated in the control message 205 to search for new candidate beams. The UE 115-a can select a best beam from the candidate beams and can use the selected beam to initiate a random access procedure with the network entity 105-a. For example, the UE 115-a can use the selected beam to transmit a random access preamble to the network entity 105-a. In some cases, if the UE 115-a is unable to recover the connection during the beam recovery procedure after detecting the BF, the UE 115-a can assume an RLF. For example, in some examples, a MAC layer can initiate a beam failure recovery timer (e.g., BeamFailureRecoveryTimer) upon triggering the beam recovery procedure. If the UE 115-a is unable to select a candidate beam before the beam failure recovery timer expires, the UE 115-a can determine that the BF recovery operation has failed. To recover from the RLF, the UE 115-a can search for a new candidate cell to utilize to attempt a connection establishment procedure (e.g., a random access procedure).

[0127] The wireless communications system 200 can support transitions of the UE 115-a (and in some cases, the network entity 105-a) between a plurality of power states (e.g., N power states), where each power state of the plurality of power states corresponds to a respective directional communication profile of the UE 115-a. The plurality of power states can include, but are not limited to, an uplink-only power state (e.g., an uplink-only configured grant power state, an uplink-only dynamic grant power state), a downlink-only power state, a downlink semi-persistent scheduling (SPS) power state, an uplink and downlink power state (e.g., a normal power state), a modem-off power state, a high-rate power state (e.g., a downlink high-rate power state, an uplink high-rate power state), a low-rate power state (e.g., a downlink low-rate power state, an uplink low-rate power state), or any combination thereof. For example, the plurality of power states can include at least one power state associated with uplink communications (e.g., uplink-only communications), at least one power state associated with downlink communications (e.g., downlink-only communications), and at least one power state associated with both uplink and downlink communications. In some examples, the plurality of power states can be associated with a plurality of CCs (e.g., according to one or more power state patterns).

[0128] For illustrative purposes, Figure 2 The plurality of power states in the context of FIG. 2 can include a first power state 215, a second power state 220, and a third power state 225, each of which can be any power state or any combination of power states described herein. Although wireless communications system 200 illustrates a configuration of three power states (e.g., first power state 215, second power state 220, and third power state 225), it should be understood that any wireless device or combination of wireless devices can be configured to cycle between any number or combination of power states.

[0129] Each directional communication profile can correspond to one or more communication parameters that configure UE 115-a to communicate in a respective communication direction and according to a respective traffic profile. For example, each directional communication profile can indicate or otherwise be associated with a BWP for a primary cell, a dormant BWP for the primary cell, one or more BWPs for one or more secondary cells, a dormant BWP for the one or more secondary cells, or a combination thereof. Additionally or alternatively, each directional communication profile can be associated with a restricted reception of data channels, control channels, or both in a BWP for a primary cell, one or more BWPs for one or more secondary cells, or some combination thereof.

[0130] Additionally, each power state and each directional communication profile can be associated with a configuration of UE 115-a that enables the UE 115-a to operate according to one or more behaviors. As Figure 2 For illustrative examples in the context of FIG. 2, first power state 215 can be associated with a first directional communication profile and a first configuration of UE 115-a, second power state 220 can be associated with a second directional communication profile and a second configuration of UE 115-a, and third power state 225 can be associated with a third directional communication profile and a third configuration of UE 115-a. Moreover, each power state (e.g., each directional communication profile) can be associated with a power consumption (e.g., an expected power level consumption). For example, first power state 215 can be associated with a first power consumption level, second power state 220 can be associated with a second power consumption level, and third power state 225 can be associated with a third power consumption level, where the first power consumption level is less than the second power consumption level, and the second power consumption level is less than the third power consumption level.

[0131] In some examples, the first directional communication profile, the second directional communication profile, the third directional communication profile, or any combination thereof, can indicate a constrained reception or transmission of a single type of data traffic or multiple types of data traffic to flexibly allocate modem power states for the UE 115-a and reduce power consumption of the UE 115-a. Thus, each directional communication profile can be tailored to an expected traffic environment (e.g., traffic volume, one or more traffic directions, data rates, throughput) or lack thereof at the UE 115-a, such that the UE 115-a is configured to perform one or more behaviors.

[0132] For example, an uplink only configuration grant power state can be associated with a configuration of the UE 115-a in which the UE 115-a avoids monitoring for downlink transmissions (e.g., via PDCCH and PDSCH), reduces a frequency of retransmissions (e.g., as compared to uplink and downlink power states), can put to sleep one or more BWPs associated with additional cells (e.g., additional network entities 105) of the UE 115-a, and can perform uplink positioning. In another example, an uplink only dynamic grant power state can be associated with a configuration of the UE 115-a in which the UE 115-a avoids monitoring for downlink transmissions associated with scheduling downlink transmissions (e.g., downlink DCI messages), and can monitor a downlink control channel for downlink transmissions associated with scheduling uplink transmissions (e.g., uplink grants).

[0133] Additionally or alternatively, a downlink only power state can be associated with a configuration of the UE 115-a in which the UE 115-a monitors for downlink transmissions and avoids transmitting uplink control messages (e.g., DCI messages). In some examples, when operating in the downlink only power state, the UE 115-a can transmit a scheduling request (e.g., a conditional scheduling request). Additionally or alternatively, a downlink SPS power state can be associated with a configuration of the UE 115-a in which the UE 115-a monitors for transmissions associated with SPS configurations.

[0134] An uplink and downlink power state can be associated with a configuration of the UE 115-a in which the UE 115-a monitors for both uplink transmissions and downlink transmissions. Additionally, the uplink and downlink power state can be associated with relatively dense configurations of communications, such as reference signals, wake-up signal (WUS) occasions, or other examples. A modem off power state can be associated with a configuration of the UE 115-a in which the UE 115-a sleeps or idles, and in which an SSSG is configured to be empty, a WUS is deactivated, and the UE 115-a does not transmit or receive signals.

[0135] InFigure 2 In the examples, the first power state 215 could be an example of a modem power-off state, the second power state 220 could be an example of an uplink-only power state, and the third power state 225 could be an example of both uplink and downlink power states. When the power state corresponds to a directional communication profile with a constrained receive or transmit channel, UE 115-a can reduce power consumption by shutting down one or more modems (e.g., transmit or receive circuits) that are not used by UE 115-a for communication via the directional channel. For example, when operating in the first power state 215, UE 115-a can shut down multiple (e.g., all) modems. In some cases, the first power state 215 can correspond to an idle or sleep state. Therefore, UE 115-a can consume less power during operation in the first power state 215 compared to operation in the second power state 220 or the third power state 225.

[0136] like Figure 2 As illustrated, the second directed communication profile may correspond to reduced or restricted downlink data traffic at UE 115-a. Therefore, the second directed communication profile may indicate restricted reception of the downlink shared channel, downlink control channel, or both. UE 115-a may shut down one or more modems associated with downlink traffic reception when operating in the second power state 220 (e.g., uplink power state only). Alternatively, in other examples, the second directed profile may correspond to reduced or restricted uplink data traffic at UE 115-a and may indicate restricted transmission of the uplink shared channel, uplink control channel, or both. In such examples, UE 115-a may shut down one or more modems associated with uplink traffic transmission when operating in the second power state 220 (e.g., downlink power state only). In any example, based on the constrained reception or transmission of one or more channels, the second power state 220 may specify that while reducing power consumption at UE 115-a, UE 115-a supports one or more applications associated with relatively stringent QoS requirements, such as latency requirements (e.g., periodic low-latency power-constrained service (LLPCT), or services for other applications associated with relatively frequent transmission or low latency).

[0137] The third directional communication profile can not correspond to a constrained data traffic at the UE 115-a. Thus, the UE 115-a can communicate via one or more downlink channels and one or more uplink channels while operating in the third power state 225. During operation in the third power state 225, the UE 115-a can refrain from shutting down any modem. The third power state 225 and the third directional communication profile can thus be used for relatively high throughput at the UE 115-a, or for scenarios in which the UE 115-a is able to support relatively high power consumption.

[0138] The network entity 105-a can configure the UE 115-a with multiple power states (e.g., the first power state 215, the second power state 220, and the third power state 225). For example, the network entity 105-a can indicate the multiple power states to the UE 115-a via the communication link 125-a as part of control signaling (e.g., RRC signaling). The control signaling can indicate the multiple power states, one or more parameters (e.g., of an associated configuration of the UE 115-a) corresponding to each of the multiple power states, or some combination thereof. In some cases, the control message 205 can indicate the multiple power states as well as the RLF / BF detection and recovery configuration. Although the wireless communication system 200 illustrates configuration of three power states (e.g., the first power state 215, the second power state 220, and the third power state 225), it should be understood that the techniques described herein can be applied to any number or configuration of power states.

[0139] The UE 115-a can transition between power states to increase power saving, to meet a QoS threshold of a given directional communication profile, or both. More specifically, the UE 115-a can transition between power states based on receiving a downlink control message (e.g., DCI, MAC-CE) from the network entity 105-a, based on satisfying one or more conditions, according to one or more schedules (e.g., power state transition schedules), or some combination thereof. In some examples, the one or more conditions can be satisfied based on the UE 115-a initiating a retransmission timer, transmitting a negative acknowledgement message for one or more downlink messages, operating in an active period of a power state, receiving a burst of downlink messages, receiving a second control message indicating a power state, expiration of a timer, or any combination thereof.

[0140] For example, UE 115-a can transition between power states based on receiving control signaling (such as a downlink control message (e.g., a DCI message)) from network entity 105-a indicating a power state. For example, UE 115-a can operate in a first power state 215. During operation in the first power state 215, UE 115-a can receive a DCI message from network entity 105-a indicating a second power state 220. UE 115-a can transition from the first power state 215 to the second power state 220 based on receiving the DCI message.

[0141] Additionally or alternatively, each power state can correspond to a timer. Network entity 105-a can configure a respective timer for each of the plurality of power states. In some cases, network entity 105-a can indicate, via control signaling, a set of timers corresponding to the plurality of power states to UE 115-a (e.g., UE 115-a can be RRC configured with timers for the plurality of power states). In some examples, network entity 105-a can dynamically adapt one or more timers of the set of timers according to a directional traffic periodicity (e.g., uplink traffic periodicity, downlink traffic periodicity), or dynamically adapt one or more timers of the set of timers to align with a start of an on duration (e.g., a connected mode discontinuous reception (CDRX) on duration). In other examples, the set of timers can be associated with SSSG skipping, but UE 115-a can be configured to use the set of timers for the plurality of power states in addition to or instead of SSSG skipping. In any case, UE 115-a can operate in a power state for a time duration of a timer corresponding to the power state. After the timer expires, UE 115-a can transition to a different power state.

[0142] Alternatively, UE 115-a can transition between power states at periodic times (e.g., according to a set of power state patterns, periodic cycles, or activation periods). For example, each power state can be associated with one or more timers and one or more activation periods. UE 115-a can transition from the first power state 215 to the second power state 220 based on UE 115-a transitioning to an activation period associated with the second power state 220. UE 115-a can initiate a first timer Tl associated with the activation period based on transitioning to the second power state 220 during the activation period. Additionally, UE 115-a can transition from the second power state 220 to (e.g., back to) the first power state 215 based on the first timer Tl expiring. In some other examples, UE 115-a can transition between power states according to periodicity of uplink traffic, downlink traffic, or both, based on activation periods or timers associated with each power state.

[0143] In yet another example, UE 115-a can be configured with multiple schedules for transitioning between power states (e.g., power state transition schedules). As referenced above, a UE 115-a can be configured with a power state transition schedule that indicates a timing pattern for transitioning between power states. In some cases, the timing pattern can be based on a timer. For example, the UE 115-a can be configured with a power state transition schedule that indicates a first power state and a second power state, and a timer associated with the first power state. When the UE 115-a starts operating in the first power state, the UE 115-a can initiate the timer. When the timer expires, the UE 115-a can transition to the second power state. In some cases, the UE 115-a can be configured with multiple power state transition schedules. For example, the UE 115-a can be configured with a first power state transition schedule that indicates a first power state and a second power state, and a timer associated with the first power state. The UE 115-a can be configured with a second power state transition schedule that indicates the first power state and a third power state, and a timer associated with the first power state. When the UE 115-a starts operating in the first power state, the UE 115-a can initiate the timer. When the timer expires, the UE 115-a can transition to the second power state or the third power state, depending on which power state transition schedule the UE 115-a is configured to apply. In some cases, the UE 115-a can be configured with multiple power state transition schedules that indicate different power states and different timers. In some cases, the UE 115-a can be configured with multiple power state transition schedules that indicate the same power states and different timers. In some cases, the UE 115-a can be configured with multiple power state transition schedules that indicate the same power states and the same timer. Figure 3A and Figure 3B As described in more detail, a schedule for transitioning between power states can be understood as a timing pattern for a set of power states. That is, a schedule can include one or more time durations corresponding to one or more power states. The UE 115-a can apply the schedule to operate in each of the one or more power states for a respective time duration of the one or more time durations. Accordingly, the UE 115-a can transition between power states according to the schedule. In some cases, each time duration of the schedule (and thus each power state) can be associated with or based on a timer, where the UE 115-a initiates the timer when the UE 115-a starts operating in the power state; when the timer expires, the UE 115-a can transition to a second power state.

[0144] In a first set of power states of the multiple power states (e.g., only downlink power states, downlink and uplink power states), such as the third power state 225, the UE 115-a can be able to receive downlink reference signals and thus can perform RLF / BF detection operations. In a second set of power states of the multiple power states that are different from the first set of power states (e.g., only uplink power states, modem-off power states), such as the first power state 215 or the second power state 220, the UE 115-a can not be able to receive downlink reference signals and thus can not perform RLF / BF detection operations when operating in such power states. Accordingly, if an RLF or BF occurs during operation in the first power state 215 or the second power state 220, the UE 115-a can not be able to recover or reestablish a connection with the network entity 105-a. Accordingly, the network entity 105-a and the UE 115-a can implement transitions between power states using a timing (e.g., a timing pattern, a schedule) that supports RLF / BF detection and recovery operations. For example, the network entity 105-a can configure (e.g., RRC configure) the UE 115-a with a set of schedules indicated via control signaling, such as the control message 205. The UE 115-a can select and apply a schedule from the set of schedules based on whether the UE 115-a is to perform RLF / BF detection operations. Additionally or alternatively, the UE 115-a can apply a schedule of the set of schedules based on receiving an indication of the schedule from the network entity 105-a (e.g., via DCI, such as the DCI 207, or a MAC-CE).

[0145] For example, some scheduling for transitioning between power states can be configured to include a relatively long duration for operating in a power state in a first set of power states, such as the third power state 225, and the UE 115-a can apply such scheduling before initiating RLF / BF detection operations. Thus, the UE 115-a can have sufficient time to perform RLF / BF detection operations before switching to a power state in a second set of power states, such as the second power state 220. Thus, the UE 115-a can avoid entering the second power state 220 with a relatively weak serving beam or radio link, which can improve communication reliability. Additionally, by ensuring that the UE 115-a is able to perform RLF / BF detection operations before transitioning to the second power state 220, the UE 115-a can significantly reduce the likelihood of an RLF or BF occurring during operation in the second power state 220.

[0146] Additionally or alternatively, the UE 115-a can switch or otherwise apply scheduling based on whether operation in a power state supports RLF / BF detection operations and based on whether the UE 115-a is to perform RLF / BF detection operations. For example, the UE 115-a can operate according to a first scheduling that includes a first time duration for operation in the third power state 225 and a second time duration for operation in the second power state 220. The UE 115-a can determine that the UE 115-a is to perform RLF / BF detection operations, but can be configured to transition to the second power state 220 according to the first scheduling. To perform the RLF / BF detection operations, the UE 115-a can switch to a second scheduling. The second scheduling can include a postponement of the transition to the second power state 220, such that the UE 115-a can perform the RLF / BF detection operations before transitioning to the second power state 220. In some examples, the second scheduling can include a relatively long first time duration for operation in the third power state 225. Additionally or alternatively, the second scheduling can not include any power states that would prevent the UE 115-a from performing RLF / BF detection operations. In some cases, the second scheduling can indicate that the UE 115-a is to postpone transitioning to the second power state 220 until after an expiration of a failure detection timer for the RLF / BF detection operations (e.g., a beam failure detection timer).

[0147] In some examples, the UE 115-a can be triggered by the network entity 105-a to apply the second schedule (e.g., triggered to postpone transitioning to the second power state 220). For example, the UE 115-a can apply the second schedule based on receiving an RLF / BF detection operation activation DCI (e.g., DCI 207) from the network entity 105-a. That is, if the UE 115-a is commanded to start an RLF / BF detection operation by the network entity 105-a, the UE 115-a can autonomously apply the second schedule to prevent transitioning to the second power state 220. In such examples, the UE 115-a can maintain the second schedule (e.g., can refrain from transitioning to the second power state 220) until the quality of the radio link or serving beam improves (e.g., above a signal quality threshold) or until a failure detection timer expires.

[0148] Additionally or alternatively, the RLF / BF detection operation activation DCI (e.g., DCI 207) can include an indication that the UE 115-a is to apply the second schedule. More specifically, the network entity 105-a can multiplex the indication that the UE 115-a is to apply the second schedule with the DCI 207. For example, if the network entity 105-a determines that the quality of the communication link 125-a or a serving beam associated with the communication link 125-a is poor or otherwise degraded, the network entity 105-a can send the DCI 207 to the UE 115-a to postpone the UE 115-a’s transition to the second power state 220 and initiate the RLF / BF detection operation at the UE 115-a.

[0149] As another example, the network entity 105-a can send the WUS 210 to the UE 115-a to indicate that the UE 115-a is to apply the second schedule. In some cases, the WUS 210 can be associated with an indication that the UE 115-a is to perform an RLF / BF detection operation. The UE 115-a can apply the second schedule (e.g., can postpone transitioning to the second power state 220) based on receiving the WUS 210 and can initiate the RLF / BF detection operation. In some cases, the WUS 210 can include an indication of the second schedule.

[0150] In some aspects, the second schedule can include a transition from a power state in which the UE 115-a is unable to perform RLF / BF detection operations, such as the first power state 215 or the second power state 220, to a power state in which the UE 115-a can perform RLF / BF detection operations, such as the third power state 225. During operation in the second power state 220, for example, the main radio of the UE 115-a can operate in an uplink only state, while the wake-up receiver of the UE 115-a can remain active and be able to receive the WUS. The network entity 105-a can monitor the communication link 125-a and the serving beam. If the network entity 105-a determines that the quality of the communication link 125-a or the serving beam degrades and falls below the signal quality threshold, the network entity 105-a can transmit the WUS 210 to the UE 115-a to initiate the RLF / BF detection operation at the UE 115-a. The wake-up receiver of the UE 115-a can trigger the main radio to transition to the third power state 225 for the UE 115-a to perform the RLF / BF detection operation.

[0151] Alternatively, the UE 115-a can autonomously determine whether to apply a schedule, for example, based on whether the UE 115-a determines to perform the RLF / BF detection operation. In some cases, the UE 115-a can select a schedule from the set of schedules based on a configuration priority associated with the RLF / BF detection operation. Here, the control message 205 can additionally indicate a priority (e.g., high, medium, low) of a beam failure detection timer (e.g., BeamFailureDetectionTimer) as part of the RLF or BF monitoring configuration. Each schedule in the set of schedules can be associated with a respective timer duration for deferring the transition to the second power state 220. The UE 115-a can select a schedule from the set of schedules based on an association (e.g., mapping) between the respective timer durations and the indicated priority of the beam failure detection timer. A higher priority can be associated with a relatively longer timer duration, such that the UE 115-a is provided with sufficient time to perform the RLF / BF detection operation before transitioning to the second power state 220. Thus, if the beam failure detection timer is configured with a “high” priority, the UE 115-a can select a schedule that includes a relatively long timer duration. Alternatively, a lower priority can correspond to a relatively short timer duration. If the beam failure detection timer is associated with a “low” priority, the UE 115-a can select a schedule that enables the UE 115-a to transition to the second power state 220 more quickly (e.g., a schedule with a short timer duration).

[0152] In some examples, UE 115-a can select or apply the scheduling based on detecting a BFI (e.g., during an RLF / BF detection operation). For example, UE 115-a can perform an RLF / BF detection operation while operating in the third power state 225 and according to a first schedule that includes a transition to the second power state 220. If UE 115-a detects at least one BFI during the RLF / BF detection operation, UE 115-a can postpone the transition to the second power state 220 by applying a second schedule. In some cases, UE 115-a can postpone the transition until after a failure detection timer associated with the RLF / BF detection operation expires. If the failure detection timer expires, or if UE 115-a no longer detects any BFI, UE 115-a can transition to the second power state 220.

[0153] UE 115-a can transmit an uplink message 212 to network entity 105-a to indicate that UE 115-a has applied the second schedule (e.g., to indicate that UE 115-a has postponed the transition to the second power state 220). The indication can include or be an example of a set of bits of an uplink message 212. In some cases, uplink message 212 can include or be an example of an uplink control message (UCI) or MAC-CE. In other cases, uplink message 212 can include or be an example of a data message (such as a PUSCH), and UE 115-a can piggyback an indication (e.g., a set of bits) that the second schedule is applied to the data message. Based on receiving uplink message 212, network entity 105-a can transmit one or more downlink reference signals to UE 115-a for UE 115-a to use to perform an RLF / BF detection operation.

[0154] In some cases, UE 115-a and network entity 105-a can additionally modify or otherwise adjust the HARQ RTT timer (e.g., drx-HARQ-RTT-TimerUL) based on a power state in which UE 115-a is operating. UE 115-a can initiate the HARQ RTT timer when transmitting an uplink message, such as uplink message 212, to network entity 105-a. The HARQ RTT timer can define a minimum time duration between the transmission of uplink message 212 and the reception of a retransmission grant for uplink message 212 (e.g., a retransmission grant pertaining to a retransmission of uplink message 212 by UE 115-a). If the HARQ RTT timer expires before UE 115-a receives feedback information (e.g., HARQ feedback information, such as a positive acknowledgement (ACK) or a negative acknowledgement (NACK)) from network entity 105-a related to uplink message 212, UE 115-a can assume that network entity 105-a failed to receive uplink message 212. Accordingly, UE 115-a can begin monitoring for a retransmission grant for uplink message 212.

[0155] In a first example, when UE 115-a is operating in a downlink only power state, UE 115-a can be unable to transmit a retransmission of uplink message 212. Accordingly, UE 115-a and network entity 105-a can suspend the HARQ RTT timer based on UE 115-a operating in the downlink only power state. In a second example, when UE 115-a is operating in an uplink only power state (e.g., second power state 220), UE 115-a can enable HARQ mode B in which retransmissions (e.g., of uplink message 212) are disabled. Accordingly, UE 115-a can refrain from initiating the HARQ RTT timer based on HARQ mode B. If UE 115-a transitions from the uplink only power state to the downlink only power state or a downlink and uplink power state, UE 115-a can initiate the HARQ RTT timer. In a third example, UE 115-a can suspend the HARQ RTT timer during the uplink only power state because UE 115-a can not receive downlink transmissions and, thus, can be unable to monitor for a retransmission grant for uplink message 212. During operation in the downlink only power state, UE 115-a can resume the HARQ RTT timer and can monitor for the retransmission grant.

[0156] Figure 3A and Figure 3BExamples of communication timelines 300 and 301 that support fault detection for communication power state switching are shown in accordance with one or more aspects of the present disclosure. The communication timelines 300 and 301 can implement aspects of the present disclosure as described with reference to Figure 1 and Figure 2 For example, the communication timelines 300 and 301 can illustrate timing patterns for communications by a UE and a network entity, which can be examples of the corresponding devices as described herein. The UE and the network entity can communicate via a communication link (e.g., a radio link) using one or more beams. The UE can be configured with multiple power states including at least a downlink and uplink power state 305 and an uplink only power state 310, which can be examples of downlink and uplink power states and uplink only power states as described with reference to Figure 2 The UE can transition between the downlink and uplink power state 305 and the uplink only power state 310 according to one or more schedules and based on whether the UE is to perform RLF / BF detection operations.

[0157] The communication timelines 300 and 301 illustrate uplink and downlink traffic between the UE and the network entity over time as the UE transitions between the downlink and uplink power state 305 and the uplink only power state 310 according to the first schedule and the second schedule. Although the communication timelines 300 and 301 are described with reference to transitions between the downlink and uplink power state 305 and the uplink only power state 310, it should be understood that the communication timelines 300 and 301 illustrated in Figure 3A and Figure 3B The communication timelines 300 and 301 can correspond to any combination of power states, for example. The timing illustrated by the communication timelines 300 and 301 can apply to any number and combination of power states and schedules as discussed herein.

[0158] In Figure 3AIn the communication timeline 300 illustrated in the middle, the UE can initially operate in the downlink and uplink power state 305. In the downlink and uplink power state 305, the UE can be able to receive downlink traffic (e.g., downlink control signals 315, downlink signals 325, downlink reference signals 330) and transmit uplink traffic (e.g., uplink messages 320). For example, the UE can receive a downlink control signal 315, such as an RRC message including control information. The control information can indicate a first schedule for the UE to transition between the downlink and uplink power state 305 and the uplink only power state 310. The first schedule can include a first set of time durations during which the UE is to operate in the downlink and uplink power state 305, such as time duration 335-a and time duration 335-c. The first schedule can also include a second set of time durations during which the UE is to operate in the uplink only power state 310, such as time duration 340-a. In some cases, the UE can maintain a respective timer for each time duration (e.g., each time duration 335, each time duration 340) and can transition between power states when the respective timer expires.

[0159] While operating according to the first schedule, the UE can transition from the downlink and uplink power state 305 to the uplink only power state 310 at the end of time duration 340-a and can operate in the uplink only power state 310 for time duration 335-a. In the uplink only power state 310, the UE can refrain from monitoring for downlink traffic, but can be able to transmit uplink traffic. Thus, in the uplink only power state 310, the UE can not be able to receive downlink reference signals used in RLF / BF detection operations, such as downlink reference signals 330. If the quality of the communication link or a beam (e.g., a serving beam) of the one or more beams degrades or fails, the UE can not be able to perform RLF / BF detection and recovery while operating in the uplink only power state 310. As such, if the UE determines that the UE is to perform an RLF / BF detection operation, the UE can postpone the transition to the uplink only power state 310 by applying a second schedule.

[0160] Applying the second schedule can enable the UE to perform an RLF / BF detection operation before transitioning to the only uplink power state. In some cases, the UE can apply the second schedule autonomously, e.g., without instruction from the network entity. For example, the UE can apply the second schedule based on a determination that the UE is to perform an RLF / BF detection operation or based on detecting at least one BFI during an RLF / BF detection operation. In other cases, the UE can apply the second schedule based on receiving an indication from the network entity. As an example, the UE can receive a downlink signal 325 that includes an indication that the UE is to apply the second schedule. Additionally or alternatively, the downlink signal 325 can be an example of an activation DCI for an RLF / BF detection operation, and the UE can apply the second schedule based on receiving the activation DCI. In another example, the downlink signal 325 can be an example of a WUS associated with an indication that the UE is to perform an RLF / BF detection operation, and the UE can apply the second schedule based on receiving the WUS. In some cases, the downlink signal 325 can include an indication of the second schedule.

[0161] The second schedule can be different from the first schedule in that the second schedule can have different time durations for operation in each of the downlink and uplink power state 305 and the only uplink power state 310. For example, the second schedule can include a time duration 335-b that defers the transition to the only uplink power state 310. The UE can remain in the downlink and uplink power state 305 for the time duration 335-b, in which the UE can perform an RLF / BF detection operation. During the RLF / BF detection operation and based on operating in the downlink and uplink power state 305, the UE can receive one or more downlink reference signals, such as the downlink reference signals 330, for use in the RLF / BF detection operation.

[0162] The UE can transition to the only uplink power state 310 after the time duration 335-b according to the second schedule, and can operate in the only uplink power state for a time duration 340-b as indicated by the second schedule. In some examples, the time duration 335-b can be a time duration of a failure detection timer associated with the RLF / BF detection operation. Here, the UE can initiate the failure detection timer during the RLF / BF detection operation (e.g., after detecting a BFI), and can refrain from transitioning to the only uplink power state 310 until the failure detection timer expires. If the UE detects a BFI during the failure detection timer (e.g., within the time duration 335-b), the UE can restart the failure detection timer, and can transition to the only uplink power state until the failure detection timer has expired without detecting any BFI.

[0163] Additionally or alternatively, the time duration 335-b can correspond to a time duration for the UE to perform the RLF / BF detection operation. That is, the end time of the time duration 335-b can correspond to a time at which the UE completes the RLF / BF detection operation, such that the UE transitions to the uplink only power state 310 after performing the RLF / BF detection operation.

[0164] In some examples, the time duration 335-b (e.g., a time duration for which the transition to the uplink only power state 310 is postponed) can be different based on a priority of the failure detection timer. For example, the UE can be configured with a plurality of schedules including at least a first schedule and a second schedule, where each of the plurality of schedules can correspond to a respective timer duration for a postponement of the transition to the uplink only power state 310. Each timer duration, and thus each schedule, can be associated with a respective priority of the RLF / BF detection operation. The UE can receive a priority indication associated with the RLF / BF detection operation (e.g., associated with the failure detection timer), and can select a schedule from the set of schedules based on the priority indication. A higher priority can be associated with a longer timer duration before transitioning to the uplink only power state 310, while a lower priority can be associated with a shorter timer duration before transitioning to the uplink only power state 310. Thus, the time duration 335-b can correspond to the timer duration of the schedule selected by the UE based on the priority indication.

[0165] Figure 3B A communication timeline 301 is illustrated in which the UE can transition from the uplink only power state 345 to the downlink and uplink power state 350 according to a first schedule and a second schedule. The first schedule can include a time duration 375-a and a time duration 375-c in which the UE operates in the uplink only power state 345. During operation in the uplink only power state 345, the main radio of the UE can transmit uplink messages 355 (e.g., can not receive downlink transmissions), while the wake-up radio of the UE can monitor for the WUS 360 from the network entity. Additionally, the first schedule can include a time duration 380-b in which the UE operates in the downlink and uplink power state 350. In the downlink and uplink power state 350, the main radio can be available for uplink transmissions and downlink transmissions.

[0166] In Figure 3BIn the example of FIG. 3, the UE can be triggered to apply a second schedule and perform an RLF / BF detection operation based on receiving the WUS 360. When the UE is in the uplink only power state 345 (e.g., during the time duration 375-a) and is unable to receive downlink reference signals via a communication link with the network entity using the main radio, the network entity can monitor the quality of the communication link and one or more beams. If the network entity determines that the UE is to perform an RLF / BF detection operation, the network entity can transmit the WUS 360 to the UE to transition the UE to the downlink and uplink power state 350. The wake-up radio of the UE can receive the WUS 360 and can trigger the main radio of the UE to wake up, e.g., transition to the downlink and uplink power state 350, in order to perform the RLF / BF detection operation.

[0167] In some examples, the UE can be configured with a time interval between reception of the WUS 360 and the transition to the downlink and uplink power state 350. For example, the UE can receive control signaling, such as RRC signaling, a MAC-CE, or the like, indicating the time interval. When the wake-up radio of the UE receives the WUS 360, the wake-up radio can trigger the main radio of the UE to transition to the downlink and uplink power state 350 after the time interval.

[0168] Based on receiving the WUS 360, the UE can apply the second schedule, switch to the downlink and uplink power state 350, and perform the RLF / BF detection operation. In some cases, the WUS 360 can include an indication of the second schedule. In the second schedule, the transition from the uplink only power state 345 to the downlink and uplink power state 350 can occur before the transition from the uplink only power state 345 to the downlink and uplink power state 350 of the first schedule. That is, by applying the second schedule, the UE can transition to the downlink and uplink power state 350 earlier than if the UE were to operate according to the first schedule by a time duration 375-b. After transitioning to the downlink and uplink power state 350, the UE can receive the downlink reference signals 370 from the network entity and can perform the RLF / BF detection operation using the downlink reference signals 370.

[0169] Figure 4An example of a process flow 400 that supports failure detection for communication power state switching is shown in accordance with one or more aspects of the present disclosure. In some examples, process flow 400 can implement or be implemented by aspects of wireless communication system 100 or wireless communication system 200. For example, process flow 400 can include one or more network entities 105 (e.g., network entity 105-b) and one or more UEs 115 (e.g., UE 115-b), which can be examples of the corresponding devices as described with reference to Figure 1

[0170] Process flow 400 can support UE 115-b and network entity 105-b transitioning between power states from a set of power states based on performing an RLF / BF detection procedure. The power states can include at least a first uplink only power state in which UE 115-b can transmit uplink transmissions (e.g., and can not receive downlink transmissions) and a second state in which UE 115-b can receive downlink transmissions. For example, the second state can include a downlink only power state or a downlink and uplink power state, among other examples or examples thereof.

[0171] At 405, network entity 105-b can transmit, and UE 115-b can receive, control information indicating a first schedule for UE 115-b to transition between a set of power states. The first schedule can include at least a first time duration for UE 115-b to operate in a first uplink only power state and a second time duration for UE 115-b to operate in a second power state. In some cases, the control information can additionally indicate a set of schedules for UE 115-b to transition between the set of power states, where the set of schedules includes at least the first schedule and a second schedule. The second schedule can include a deferment of a transition from the second power state to the first uplink only power state.

[0172] At 410, UE 115-b can determine that UE 115-b is to perform an RLF / BF detection operation. In some cases, at 410, UE 115-b can determine to perform the RLF / BF detection operation based on receiving a DCI. In such cases, network entity 105-b can transmit, and UE 115-b can receive, the DCI, which can activate the RLF / BF detection operation (e.g., the DCI can be an activation DCI for the RLF / BF detection operation). For example, the DCI can include an indication that the RLF / BF detection operation is activated, and UE 115-b can begin the RLF / BF detection operation based on receiving the DCI. In some examples, the DCI can further indicate that UE 115-b is to apply the second schedule to transition between power states.​

[0173] Additionally or alternatively, at 410, UE 115-b can determine to perform an RLF / BF detection operation based on receiving the WUS. For example, the WUS can be associated with an indication that UE 115-b is to perform an RLF / BF detection operation, such that receiving the WUS triggers UE 115-b to perform the RLF / BF detection operation. In some cases, the WUS can include an indication of the second schedule.

[0174] At 415, UE 115-b can apply the second schedule for UE 115-b to transition between power states, for example, based on determining at 410 that the UE is to perform an RLF detection operation or a BF detection operation. In some examples, UE 115-b can apply the second schedule based on receiving the DCI at 410. For example, receiving the DCI at UE 115-b can trigger UE 115-b to apply the second schedule, or the DCI can include an indication that UE 115-b is to apply the second schedule. In other examples, UE 115-b can apply the second schedule based on receiving the WUS at 410. In such cases, UE 115-b can additionally receive an indication from network entity 105-b of a time duration from reception of the WUS to transition from the only uplink state to the second state.

[0175] In some examples, at 415, UE 115-b can apply the second schedule based on selecting the second schedule from a set of schedules. Each schedule of the set of schedules can include a respective timer duration for deferring a transition from the second state to the only uplink state. UE 115-b can receive an indication of a priority associated with the RLF / BF detection operation, and can select the second schedule based on the priority (e.g., based on an association between the respective timer duration of the second schedule and the indication of the priority). For example, if the priority is indicated as high, UE 115-b can select the second schedule based on the second schedule having a relatively long timer duration. Alternatively, if the priority is indicated as low, UE 115-b can select the second schedule based on the second schedule having a relatively short timer duration.

[0176] At 420, UE 115-b can optionally transmit an uplink message, and network entity 105-b can receive the uplink message including an indication that the second schedule was applied. The uplink message can include or be an example of a UCI message, a MAC-CE, or a PUSCH message that indicates the second schedule was applied.

[0177] At 425, the network entity 105-b can transmit one or more downlink signals and the UE 115-b can receive the one or more downlink signals for use by the UE 115-b in an RLF / BF detection operation, e.g., based on receiving the uplink message at 420.

[0178] At 430, the UE 115-b can perform the RLF / BF detection operation. In some examples, the UE 115-b can perform the RLF / BF detection operation after applying the second schedule. If the second schedule includes a postponement of a transition from the second state to the uplink-only state, applying the second schedule at 415 can include the UE 115-b remaining in the second state to perform the RLF / BF detection operation. In some cases, the postponement of the transition from the second state to the uplink-only state included in the second schedule can be configured to occur after expiration of a failure detection timer associated with the RLF / BF detection operation. The UE 115-b can initiate the failure detection timer during the RLF / BF detection operation and can transition to the uplink-only state if no BFI is detected prior to expiration of the failure detection timer. In some cases, the second schedule can include a transition to the uplink-only state after completion of the RLF / BF detection operation.

[0179] In other examples, the UE 115-b can perform the RLF / BF detection operation prior to applying the second schedule. For example, the UE 115-b can detect at least one BFI during the RLF / BF detection operation and can apply the second schedule based on detecting the BFI. In some cases, the UE 115-b can select the second schedule from the set of schedules based on detecting the BFI.

[0180] Figure 5 A process flow 500 that supports failure detection for communication power state switching is shown in accordance with one or more aspects of the present disclosure. In some examples, process flow 500 can implement or be implemented by aspects of wireless communication system 100 or wireless communication system 200. For example, process flow 500 can include one or more network entities 105 (e.g., network entity 105-c) and one or more UEs 115 (e.g., UE 115-c), which can be examples of the corresponding devices as described with reference to Figure 1

[0181] ​The process flow 500 can support the UE 115-c and the network entity 105-c transitioning between a set of power states according to one or more schedules based on performing RLF / BF detection operations. The set of power states can include at least: an uplink only power state in which the UE 115-c can transmit uplink transmissions (e.g., and can not receive downlink transmissions); a downlink only power state in which the UE 115-c can receive downlink transmissions (e.g., and can not transmit uplink transmissions); and a downlink and uplink power state in which the UE 115-c can both transmit uplink transmissions and receive downlink transmissions.

[0182] At 505, the network entity 105-c can transmit, and the UE 115-c can receive, control information indicating a schedule for the UE 115-c to transition between the set of power states.

[0183] At 510, the UE 115-c can operate in a first power state of the set of power states. The UE 115-c can transmit an uplink message, and the network entity 105-c can receive the uplink message, such as an uplink data message (e.g., PUSCH), an uplink control message (e.g., PUCCH), and / or the like.

[0184] Based on transmitting the uplink message, the UE 115-c can initiate a HARQ RTT timer that defines a minimum time duration between the transmission of the uplink message and the reception of a retransmission grant for a retransmission (e.g., by the UE 115-c) of the uplink message. At 515, the UE 115-c can modify the HARQ RTT timer based on operating in the first power state. The modification of the HARQ RTT timer can include pausing the HARQ RTT timer (e.g., pausing a decrement of the HARQ RTT timer), initiating the HARQ RTT timer, or refraining from initiating the HARQ RTT timer. Additionally, the modification can be based on the first power state, e.g., based on whether the first power state is an uplink only power state, a downlink only power state, or a downlink and uplink power state.

[0185] In a first example, at 515, UE 115-c can suspend the HARQ RTT timer when the first power state is a downlink only power state, e.g., because UE 115-c can not be able to transmit a retransmission of an uplink message during operation in the downlink only power state. In a second example, the first power state can be an uplink only power state, and UE 115-c can enable HARQ mode B, in which retransmissions by UE 115-c are disabled. Thus, at 515, UE 115-b can refrain from initiating the HARQ RTT timer, e.g., based on retransmissions being disabled. In a third example, if the first power state is a downlink only power state or a downlink and uplink power state, UE 115-c can initiate the HARQ RTT timer at 515.

[0186] In a fourth example, the first power state can be an uplink only power state. At 515, UE 115-c can suspend the HARQ RTT timer based on the first power state being an uplink only power state.

[0187] In this example, at 520, UE 115-c can transition to a second power state of the set of power states. The second power state can be a downlink only power state or a downlink and uplink power state. UE 115-c can resume the HARQ RTT timer after transitioning to the second power state, e.g., based on the second power state being a downlink only state or a downlink and uplink power state.

[0188] Figure 6 FIG. 6 shows a block diagram 600 of a device 605 that supports fault detection for communication power state switching in accordance with one or more aspects of the present disclosure. The device 605 can be an example of aspects of a UE 115 as described herein. The device 605 can include a receiver 610, a transmitter 615, and a communication manager 620. The device 605, or one or more components of the device 605 (e.g., the receiver 610, the transmitter 615, and the communication manager 620), can include at least one processor that can be coupled to at least one memory to individually or collectively support or implement at least one of the described technologies. Each of the components of the device 605 can be in communication with one another (e.g., via one or more buses).

[0189] The receiver 610 can provide means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to fault detection for communication power state switching). Information can be passed on to other components of the device 605. The receiver 610 can utilize a single antenna or a set of multiple antennas.

[0190] The transmitter 615 can provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 can transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to failure detection for communication power state switching). In some examples, the transmitter 615 can be collocated with the receiver 610 in a transceiver module. The transmitter 615 can utilize a single antenna or a set of multiple antennas.

[0191] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or various components thereof can be examples of means for performing various aspects of failure detection for communication power state switching as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof can be capable of performing one or more of the functions described herein.

[0192] In some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof can be implemented in hardware (e.g., in communication management circuitry). The hardware can include at least one of the following: a processor, a digital signal processor (DSP), a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a microcode, discrete gate or transistor logic, discrete hardware components, or any combination thereof, that is configured as or otherwise supports a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor can be configured to perform one or more of the functions described herein (e.g., the at least one processor executing instructions stored in the at least one memory).

[0193] Additionally or alternatively, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof can be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functions of the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof can be executed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).

[0194] In some examples, the communication manager 620 can be configured as or otherwise control a receiver 610, a transmitter 615, or both, to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting). For example, the communication manager 620 can receive information from the receiver 610, send information to the transmitter 615, or integrate with the receiver 610, the transmitter 615, or both, to obtain information, output information, or perform various other operations as described herein.

[0195] According to examples as disclosed herein, the communication manager 620 can support wireless communication by a UE. For example, the communication manager 620 can receive, be configured to receive, or be capable of operating to support means for receiving control information indicating a first schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes a

[0196] Additionally, or alternatively, the communication manager 620 can support wireless communication by a UE in accordance with examples as disclosed herein. For example, the communication manager 620 can include means for receiving control information indicating a schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes an uplink only state during which a main radio of the UE is used for uplink transmissions, a downlink only state during which the main radio of the UE is used for at least downlink transmissions, and a downlink and uplink state during which the main radio of the UE is used for both downlink transmissions and uplink transmissions, means for transmitting an uplink message, means for modifying operation of a HARQ RTT timer based on a first state of the set of multiple power states in which the UE is located, where the HARQ RTT timer defines a minimum time duration between transmission of the uplink message and reception of a retransmission grant related to retransmission of the uplink message by the UE.

[0197] By including or configuring the communication manager 620 in accordance with examples as described herein, the device 605 (e.g., at least one processor of the device 605 controlling or otherwise coupled with the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof) can support techniques for reducing processing and reducing power consumption. For example, by configuring the device 605 with one or more schedules for transitioning between multiple power states, the device 605 can be able to operate adaptively according to a tradeoff between power consumption and performance, which can reduce processing, reduce latency, and conserve battery, while improving reliability.

[0198] Figure 7 A block diagram 700 of a device 705 that supports fault detection for communication power state switching in accordance with one or more aspects of the present disclosure is shown. The device 705 can be an example of aspects of a device 605 or a UE 115 as described herein. The device 705 can include a receiver 710, a transmitter 715, and a communication manager 720. The device 705, or one or more components of the device 705 (e.g., the receiver 710, the transmitter 715, and the communication manager 720), can include at least one processor that can be coupled to at least one memory to support the described techniques. Each of these components can be in communication with one another (e.g., via one or more buses).

[0199] The receiver 710 can provide means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to failure detection for communication power state switching). Information can be passed on to other components of the device 705. The receiver 710 can utilize a single antenna or a set of multiple antennas.

[0200] The transmitter 715 can provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 can transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to failure detection for communication power state switching). In some examples, the transmitter 715 can be collocated with the receiver 710 in a transceiver module. The transmitter 715 can utilize a single antenna or a set of multiple antennas.

[0201] The device 705 or its various components can be an example of means for performing various aspects of failure detection for communication power state switching as described herein. The communication manager 720 can include a control information component 725, a failure detection component 730, a scheduling component 735, an uplink message component 740, a HARQ RTT timer component 745, or any combination thereof. The communication manager 720 can be an example of aspects of the communication manager 620 as described herein. In some examples, the communication manager 720 or its various components can be configured to use or otherwise employ the receiver 710, the transmitter 715, or both, to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting). For example, the communication manager 720 can receive information from the receiver 710, send information to the transmitter 715, or be integrated in combination with the receiver 710, the transmitter 715, or both, to obtain information, output information, or perform various other operations as described herein.

[0202] According to examples as disclosed herein, the communications manager 720 can support wireless communication by a UE. The control information component 725 can receive, be configured for receiving, or be operable to support a means for receiving control information indicating a first schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes a only uplink state during which a main radio of the UE is used for uplink transmissions and a second state during which the main radio of the UE is used for at least downlink transmissions. The failure detection component 730 can determine, be configured for determining, or be operable to support a means for determining that the UE is to perform an RLF or BF detection operation. The scheduling component 735 can apply, be configured for applying, or be operable to support a means for applying a second schedule for the UE to transition between the set of multiple power states based on the determination that the UE is to perform the RLF or BF detection operation.

[0203] Additionally or alternatively, according to examples as disclosed herein, the communications manager 720 can support wireless communication by a UE. The control information component 725 can receive, be configured for receiving, or be operable to support a means for receiving control information indicating a schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes a only uplink state during which a main radio of the UE is used for uplink transmissions, a only downlink state during which the main radio of the UE is used for at least downlink transmissions, and a downlink and uplink state during which the main radio of the UE is used for both downlink transmissions and uplink transmissions. The uplink message component 740 can transmit, be configured for transmitting, or be operable to support a means for transmitting an uplink message. The HARQ RTT timer component 745 can modify, be configured for modifying, or be operable to support a means for modifying operation of a HARQ RTT timer based on a first state of the set of multiple power states in which the UE is located, where the HARQ RTT timer defines a minimum time duration between transmission of the uplink message and reception of a retransmission grant related to retransmission of the uplink message by the UE.

[0204] Figure 8A block diagram 800 showing a communications manager 820 that supports failure detection for communication power state switching in accordance with one or more aspects of the present disclosure is shown. The communications manager 820 can be an example of aspects of a communications manager 620, a communications manager 720, or both, as described herein. The communications manager 820, or various components thereof, can be an example of means for performing various aspects of failure detection for communication power state switching as described herein. For example, the communications manager 820 can include a control information component 825, a failure detection component 830, a scheduling component 835, an uplink message component 840, a HARQ RTT timer component 845, a WUS component 850, a priority indication component 855, a power state transition component 860, or any combination thereof. Each of these components, or components or sub-components thereof, can be in communication with one another (for example, via one or more buses).

[0205] The communications manager 820 can support wireless communication by a UE in accordance with examples as disclosed herein. The control information component 825 can receive, be configured to receive, or be operable to support a means for receiving control information indicating a first schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes a only uplink state during which a main radio of the UE is used for uplink transmissions and a second state during which the main radio of the UE is used for at least downlink transmissions. The failure detection component 830 can determine, be configured to determine, or be operable to support a means for determining that the UE is to perform an RLF or BF detection operation. The scheduling component 835 can apply, be configured to apply, or be operable to support a means for applying a second schedule for the UE to transition between the set of multiple power states based on the determination that the UE is to perform the RLF or BF detection operation.

[0206] In some examples, to support determining that the UE is to perform the RLF or BF detection operation, the control information component 825 can receive, be configured to receive, or be operable to support a means for receiving a DCI message activating the RLF or BF detection operation, where applying the second schedule is based on the reception of the DCI message.

[0207] In some examples, the second schedule includes a postponement of a transition from the second state to the only uplink state until after expiration of a failure detection timer associated with the RLF or BF detection operation.

[0208] In some examples, to support receiving the DCI message, the control information component 825 can include, be configured as, or operate to support means for receiving an indication that the second scheduling is to be applied by the UE.

[0209] In some examples, to support determining that the UE is to perform the RLF or BF detection operation, the WUS component 850 can include, be configured as, or operate to support means for receiving a WUS associated with an indication that the UE is to perform the RLF or BF detection operation, where applying the second scheduling is based on reception of the WUS, and where the second scheduling includes a postponement of a transition from the second state to the uplink-only state. In some examples, to support determining that the UE is to perform the RLF or BF detection operation, the failure detection component 830 can include, be configured as, or operate to support means for performing the RLF or BF detection operation after applying the second scheduling. In some examples, the WUS includes an indication of the second scheduling. In some examples, the second scheduling includes a transition to the uplink-only state after completion of the RLF or BF detection operation.

[0210] In some examples, the control information further indicates a set of multiple schedules for the UE to transition between the set of multiple power states, and the priority indication component 855 can include, be configured as, or operate to support means for receiving a priority indication associated with the RLF or BF detection operation. In some examples, the control information further indicates a set of multiple schedules for the UE to transition between the set of multiple power states, and the scheduling component 835 can include, be configured as, or operate to support means for selecting the second scheduling from the set of multiple schedules based on the priority indication of the RLF or BF detection operation.

[0211] In some examples, to support selecting the second scheduling from the set of multiple schedules, the scheduling component 835 can include, be configured as, or operate to support means for selecting the second scheduling based on an association between a respective timer duration of the second scheduling and the priority indication. In some examples, the association includes a higher priority being associated with a longer timer duration before a transition from the second state to the uplink-only state, and a lower priority being associated with a shorter timer duration before the transition from the second state to the uplink-only state.

[0212] In some examples, to support determining that the UE is to perform the RLF or BF detection operation, the WUS component 850 can receive, be configured for receiving, or be operable to support a means for receiving a WUS associated with an indication that the UE is to perform the RLF or BF detection operation, where application of the second schedule is based on reception of the WUS, and where the second schedule includes a transition from the only uplink state to the second state. In some examples, the scheduling component 835 can receive, be configured for receiving, or be operable to support a means for receiving an indication of a time duration from reception of the WUS and the transition from the only uplink state to the second state.

[0213] In some examples, the failure detection component 830 can perform, be configured for performing, or be operable to support a means for performing the RLF or BF detection operation. In some examples, the failure detection component 830 can perform, be configured for performing, or be operable to support a means for detecting at least one failure instance during the RLF or BF detection operation, where application of the second schedule is based on detecting the at least one failure instance, and where the second schedule includes a postponement of a transition from the second state to the only uplink state.

[0214] In some examples, the postponement of the transition from the second state to the only uplink state is until after expiration of a failure detection timer associated with the RLF or BF detection operation.

[0215] In some examples, the control information further indicates a set of multiple schedules for the UE to transition between the set of multiple power states, and the scheduling component 835 can perform, be configured for performing, or be operable to support a means for selecting the second schedule from the set of multiple schedules based on detecting the at least one failure instance.

[0216] In some examples, the scheduling component 835 can transmit, be configured for transmitting, or be operable to support a means for transmitting an uplink message including an indication that the second schedule is applied. In some examples, the failure detection component 830 can receive, be configured for receiving, or be operable to support a means for receiving one or more downlink signals for performing the RLF or BF detection operation based on transmitting the uplink message, where the uplink message is one of an uplink control information message, a medium access control (MAC) control element (CE), or a PUSCH message to which the indication is piggybacked.

[0217] Additionally or alternatively, the communications manager 820 can support wireless communication by a UE in accordance with examples as disclosed herein. In some examples, the control information component 825 can include, be configured as, or be operable support a means for receiving control information indicating a schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes a

[0218] In some examples, and to support modifying the operation of the HARQ RTT timer, the HARQ RTT timer component 845 can include, be configured as, or be operable support a means for suspending the HARQ RTT timer based on the first state being the downlink only state.

[0219] In some examples, and to support modifying the operation of the HARQ RTT timer, the HARQ RTT timer component 845 can include, be configured as, or be operable support a means for refraining from initiating the HARQ RTT timer based on the first state being the uplink only state.

[0220] In some examples, and to support modifying the operation of the HARQ RTT timer, the HARQ RTT timer component 845 can include, be configured as, or be operable support a means for initiating the HARQ RTT timer based on the first state being the downlink only state or the downlink and uplink state.

[0221] In some examples, and to support modifying operation of the HARQ RTT timer, the HARQ RTT timer component 845 can perform the following, be configured to perform the following, or be operable to support means for: pausing the HARQ RTT timer based on the first state being the uplink only state.

[0222] In some examples, and to support modifying operation of the HARQ RTT timer, the HARQ RTT timer component 845 can perform the following, be configured to perform the following, or be operable to support means for: pausing the HARQ RTT timer based on the first state being the uplink only state.

[0223] Figure 9 A diagram illustrating a system 900 including a device 905 that supports fault detection for communication power state switching in accordance with one or more aspects of the present disclosure is shown. The device 905 can be an example of or include the components of device 605, device 705, or a UE 115 as described herein. The device 905 can communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). The device 905 can include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, at least one memory 930, code 935, and one or more processors 940. These components can be in electronic communication or operatively coupled via one or more buses (e.g., bus 945).

[0224] The I / O controller 910 can manage input and output signals for the device 905. The I / O controller 910 can also manage peripherals not integrated into the device 905. In some cases, the I / O controller 910 can represent a physical connection or port to the ® , ANDROID ® , MS-DOS ® , MS-WINDOWS ® , OS / 2 ® , UNIX ® , LINUX ®or another known operating system. Additionally or alternatively, I / O controller 910 can represent a modem, a keyboard, a mouse, a touchscreen, or a similar device, or interact with such devices. In some cases, I / O controller 910 can be implemented as part of one or more processors, such as at least one processor 940. In some cases, a user can interact with device 905 via I / O controller 910 or via hardware components controlled by I / O controller 910.

[0225] In some cases, device 905 can include a single antenna 925. However, in some other cases, device 905 can have more than one antenna 925, which can be capable of concurrently sending or receiving multiple wireless transmissions. Transceiver 915 can communicate bi-directionally, via one or more antennas 925, wired, or wireless links as described herein. For example, transceiver 915 can represent a wireless transceiver and can communicate bi-directionally with another wireless transceiver. Transceiver 915 can also include a modem to modulate the packets and to demodulate packets received from one or more antennas 925. Transceiver 915, or transceiver 915 and one or more antennas 925, can be an example of transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination thereof, or components thereof, as described herein.

[0226] The at least one memory 930 can include random access memory (RAM) and read-only memory (ROM). The at least one memory 930 can store computer-readable, computer- executable code 935 including instructions that, when executed by the at least one processor 940, cause device 905 to perform various functions described herein. The code 935 can be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 935 can not be directly executable by the at least one processor 940 but can cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 930 can include, among other things, a basic I / O system (BIOS), which can control basic hardware or software operation such as the interaction with peripheral components or devices.

[0227] The at least one processor 940 can include an intelligent hardware device, (e.g., a general- purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the at least one processor 940 can be configured to operate a memory array. In some other cases, a memory controller can be integrated into the at least one processor 940. The at least one processor 940 can be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks supporting fault detection for communication power state transitions). For example, the device 905 or a component of the device 905 can include the at least one processor 940 and the at least one memory 930 coupled with or to the at least one processor 940, the at least one processor 940 and the at least one memory 930 configured to perform various functions described herein. In some examples, the at least one processor 940 can include a plurality of processors, and the at least one memory 930 can include a plurality of memories. One or more processors in the plurality of processors can be coupled with one or more memories in the plurality of memories, which can be individually or collectively configured to perform various functions herein.

[0228] According to examples as disclosed herein, the communications manager 920 can support wireless communications by a UE. For example, the communications manager 920 can include means for receiving control information indicating a first schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes a first uplink only state during which a primary radio of the UE is used for uplink transmissions and a second state during which the primary radio of the UE is used for at least downlink transmissions, means for determining that the UE is to perform an RLF or BF detection operation, and means for applying a second schedule for the UE to transition between the set of multiple power states based on the determination that the UE is to perform the RLF or BF detection operation.

[0229] Additionally or alternatively, the communication manager 920 can support wireless communication by a UE, in accordance with examples as disclosed herein. For example, the communication manager 920 can include means for receiving control information indicating a schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes an uplink only state during which a main radio of the UE is used for uplink transmissions, a downlink only state during which the main radio of the UE is used for at least downlink transmissions, and a downlink and uplink state during which the main radio of the UE is used for both downlink transmissions and uplink transmissions, means for transmitting an uplink message, means for modifying operation of a HARQ RTT timer based on a first state of the set of multiple power states in which the UE is located, where the HARQ RTT timer defines a minimum time duration between transmission of the uplink message and reception of a retransmission grant related to retransmission of the uplink message by the UE.

[0230] By including or configuring the communication manager 920 in accordance with examples as described herein, the device 905 can support techniques for reducing latency, reducing power consumption, improving utilization of processing capabilities, and prolonging battery life. For example, the device 905 can reduce power consumption and improve battery life by scheduling transitions between power states in accordance with examples as described herein. Further, by configuring the device 905 with multiple schedules, the device 905 can adaptively defer transitions to power states in order to perform RLF or BF detection operations, which can improve performance and reliability.

[0231] In some examples, the communication manager 920 can be configured to use or otherwise coordinate with the transceiver 915, the one or more antennas 925, or any combination thereof, to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 can be supported by or performed by the at least one processor 940, the at least one memory 930, the code 935, or any combination thereof. For example, the code 935 can include instructions executable by the at least one processor 940 to cause the device 905 to perform various aspects of failure detection for communication power state switching as described herein, or the at least one processor 940 and the at least one memory 930 can be otherwise configured to, individually or collectively, perform or support performance of such operations.

[0232] Figure 10 A block diagram 1000 of a device 1005 that supports fault detection for communication power state switching in accordance with one or more aspects of the present disclosure is shown. The device 1005 can be an example of aspects of a network entity 105 as described herein. The device 1005 can include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005, or one or more components of the device 1005 (e.g., the receiver 1010, the transmitter 1015, and the communication manager 1020), can include at least one processor that can be coupled to at least one memory to individually or collectively support or implement at least the described technology. Each of the components of the device 1005 can be in communication with one another (e.g., via one or more buses).

[0233] The receiver 1010 can provide a means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information can pass to other components of the device 1005. In some examples, the receiver 1010 can support obtaining information by receiving signals through one or more antennas. Additionally or alternatively, the receiver 1010 can support obtaining information by receiving signals through one or more wired (e.g., electrical, optical), wireless interfaces, or any combination thereof.

[0234] The transmitter 1015 can provide a means for outputting (e.g., sending, providing, transmitting, communicating) information generated by other components of the device 1005. For example, the transmitter 1015 can output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1015 can support outputting information by sending signals through one or more antennas. Additionally or alternatively, the transmitter 1015 can support outputting information by sending signals through one or more wired (e.g., electrical, optical), wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 can be co-located in a transceiver, which can include or be coupled to a modem.

[0235] The communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or various components thereof can be examples of means for performing various aspects of failure detection for communication power state switching as described herein. For example, the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof can be capable of performing one or more of the functions described herein.

[0236] In some examples, the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof can be implemented in hardware (e.g., in communications management circuitry). The hardware can include at least one of the processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcode, state machine logic, discrete hardware components, or any combination thereof, which are configured as or otherwise support a means for performing the functions described herein. In some examples, at least one processor and at least one memory coupled with the at least one processor can be configured to perform one or more of the functions described herein (e.g., executing instructions stored in the at least one memory by the one or more processors, individually or collectively).

[0237] Additionally or alternatively, the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof can be implemented in code (e.g., as communications management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functions of the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof can be executed by a general-purpose processor, a DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices, configured to perform the functions described herein (e.g., as a means for performing the functions described in the present disclosure).

[0238] In some examples, the communications manager 1020 can be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both. For example, the communications manager 1020 can receive information from the receiver 1010, transmit information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0239] According to the examples disclosed herein, the communication manager 1020 can support wireless communication performed by network entities. For example, the communication manager 1020 can, is configured to, or is operable to support components for: sending control information to the UE instructing a first scheduling for the UE to transition between a set of multiple power states, wherein the set of multiple power states includes an uplink-only state and a second state, during which the UE's primary radio component is used for uplink transmission, and during which the UE's primary radio component is used for at least downlink transmission. The communication manager 1020 can, is configured to, or is operable to support components for: determining that the UE wants to perform an RLF or BF detection operation. The communication manager 1020 can, is configured to, or is operable to support components for: sending a message to the UE triggering a transition from a first scheduling to a second scheduling for the UE to transition between the multiple power states based on the determination that the UE wants to perform an RLF or BF detection operation.

[0240] By including or configuring a communication manager 1020 according to examples as described herein, device 1005 (e.g., at least one processor that controls or is otherwise coupled to receiver 1010, transmitter 1015, communication manager 1020, or a combination thereof) can support techniques for reducing processing and utilizing communication resources more efficiently. For example, by utilizing one or more scheduling mechanisms as described herein, device 1005 can enable a UE communicating with device 1005 to perform an RLF or BF detection operation before transitioning to an uplink-only power state. By performing an RLF or BF detection operation, the UE and device 1005 can avoid RLF or BF, thereby reducing processing and preventing additional resource utilization associated with connection re-establishment procedures.

[0241] Figure 11 A block diagram 1100 of a device 1105 supporting fault detection for communication power state switching according to one or more aspects of this disclosure is shown. Device 1105 may be an example of aspects of device 1005 or network entity 105 as described herein. Device 1105 may include receiver 1110, transmitter 1115, and communication manager 1120. Device 1105, or one or more components of device 1105 (e.g., receiver 1110, transmitter 1115, and communication manager 1120), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0242] Receiver 1110 can provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information can pass to other components of the device 1105. In some examples, the receiver 1110 can support obtaining information by receiving signals through one or more antennas. Additionally or alternatively, the receiver 1110 can support obtaining information by receiving signals through one or more wired (e.g., electrical, optical), wireless interfaces, or any combination thereof.

[0243] Transmitter 1115 can provide means for outputting (e.g., sending, providing, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 can output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1115 can support outputting information by transmitting signals through one or more antennas. Additionally or alternatively, the transmitter 1115 can support outputting information by transmitting signals through one or more wired (e.g., electrical, optical), wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 can be collocated in a transceiver, which can include or be coupled with a modem.

[0244] Device 1105 or its various components can be an example of means for performing various aspects of failure detection for communication power state transitions as described herein. For example, the communication manager 1120 can include a control information component 1125, a failure detection component 1130, a transition trigger component 1135, or any combination thereof. The communication manager 1120 can be an example of aspects of the communication manager 1020 as described herein. In some examples, the communication manager 1120 or its various components can be configured to use or otherwise employ the receiver 1110, the transmitter 1115, or both, to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting). For example, the communication manager 1120 can receive information from the receiver 1110, transmit information to the transmitter 1115, or be integrated in combination with the receiver 1110, the transmitter 1115, or both, to obtain information, output information, or perform various other operations as described herein.

[0245] The communication manager 1120 can support wireless communication by a network entity in accordance with examples as disclosed herein. The control information component 1125 can include, be configured as, or be operable to support means for transmitting, to a UE, control information indicating a first schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes a only uplink state during which a primary radio of the UE is used for uplink transmissions and a second state during which the primary radio of the UE is used for at least downlink transmissions. The failure detection component 1130 can include, be configured as, or be operable to support means for determining that the UE is to perform an RLF or BF detection operation. The transition trigger component 1135 can include, be configured as, or be operable to support means for transmitting, to the UE, a message triggering the UE to transition from the first schedule to a second schedule for the UE to transition between the set of multiple power states based on the determination that the UE is to perform the RLF or BF detection operation.

[0246] Figure 12 A block diagram 1200 of a communication manager 1220 that supports failure detection for communication power state switching is shown in accordance with one or more aspects of the present disclosure. The communication manager 1220 can be an example of aspects of a communication manager 1020, a communication manager 1120, or both, as described herein. The communication manager 1220, or various components thereof, can be an example of means for performing various aspects of failure detection for communication power state switching as described herein. For example, the communication manager 1220 can include a control information component 1225, a failure detection component 1230, a transition trigger component 1235, a priority indication component 1240, or any combination thereof. Each of these components, or the components or subcomponents thereof, can be in direct or indirect communication with one another (e.g., via one or more buses), which can include communication among

[0247] The communication manager 1220 can support wireless communication by a network entity in accordance with examples as disclosed herein. The control information component 1225 can support, be configured for, or be operable to support means for transmitting, to a UE, control information indicating a first schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes a only uplink state during which a primary radio of the UE is used for uplink transmissions and a second state during which the primary radio of the UE is used for at least downlink transmissions. The failure detection component 1230 can support, be configured for, or be operable to support means for determining that the UE is to perform an RLF or BF detection operation. The transition trigger component 1235 can support, be configured for, or be operable to support means for transmitting, to the UE, a message triggering the UE to transition from the first schedule to a second schedule for the UE to transition between the set of multiple power states based on the determination that the UE is to perform the RLF or BF detection operation.

[0248] In some examples, and to support transmitting the message triggering the UE to transition from the first schedule to the second schedule, the control information component 1225 can support, be configured for, or be operable to support means for transmitting a DCI message activating the RLF or BF detection operation.

[0249] In some examples, the second schedule includes a postponement of a transition from the second state to the only uplink state until after an expiration of a failure detection timer associated with the RLF or BF detection operation.

[0250] In some examples, the DCI message includes an indication that the UE is to apply the second schedule.

[0251] In some examples, and to support transmitting the message triggering the UE to transition from the first schedule to the second schedule, the transition trigger component 1235 can support, be configured for, or be operable to support means for transmitting a WUS associated with an indication that the UE is to perform the RLF or BF detection operation, where the second schedule includes a postponement of a transition from the second state to the only uplink state.

[0252] In some examples, the WUS includes an indication of the second schedule. In some examples, the second schedule includes a transition to the only uplink state after completion of the RLF or BF detection operation.

[0253] In some examples, the message that triggers the UE to transition from the first schedule to the second schedule further indicates a set of multiple schedules for the UE to transition between a set of multiple power states, and the priority indication component 1240 can, is configured to, or is capable of operating with means to support transmitting a priority indication associated with the RLF or BF detection operation.

[0254] In some examples, each schedule of the set of multiple schedules includes a respective timer duration for a defer of a transition from the second state to the only uplink state.

[0255] In some examples, and to support transmitting the message that triggers the UE to transition from the first schedule to the second schedule, the transition trigger component 1235 can, is configured to, or is capable of operating with means to support transmitting a WUS associated with an indication that the UE is to perform the RLF or BF detection operation, where the second schedule includes a transition from the only uplink state to the second state.

[0256] In some examples, the transition trigger component 1235 can, is configured to, or is capable of operating with means to support transmitting an indication of a time duration for the transition from the reception of the WUS and the only uplink state to the second state.

[0257] In some examples, the transition trigger component 1235 can, is configured to, or is capable of operating with means to support receiving an uplink message that includes an indication to apply the second schedule at the UE. In some examples, the failure detection component 1230 can, is configured to, or is capable of operating with means to support transmitting one or more downlink signals for the RLF or BF detection operation at the UE based on receiving the uplink message, where the uplink message is one of an uplink control information message, a medium access control (MAC) control element (CE), or a PUSCH message that the indication is piggybacked onto.

[0258] Figure 13An illustration of a system 1300 including a device 1305 that supports fault detection for communication power state switching is shown, in accordance with one or more aspects of the present disclosure. The device 1305 can be an example of or include the components of a device 1005, a device 1105, or a network entity 105, as described herein. The device 1305 can communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, that can include communicating using one or more wired interfaces, one or more wireless interfaces, or any combination thereof. The device 1305 can include components for supporting output and obtaining communications, such as a communication manager 1320, a transceiver 1310, an antenna 1315, at least one memory 1325, code 1330, and at least one processor 1335. These components can be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1340).

[0259] The transceiver 1310 can support bi-directional communication over a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 1310 can include a wired transceiver and can communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 can include a wireless transceiver and can communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 can include one or more antennas 1315, which can be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1310 can also include a modem to modulate signals, provide the modulated signals to be transmitted (e.g., by the one or more antennas 1315, by a wired transmitter), receive the modulated signals (e.g., from the one or more antennas 1315, from a wired receiver), and demodulate the signals. In some implementations, the transceiver 1310 can include one or more interfaces, such as one or more interfaces coupled with one or more antennas 1315 configured to support various receive or obtain operations, or one or more interfaces coupled with one or more antennas 1315 configured to support various transmit or output operations, or a combination thereof. In some implementations, the transceiver 1310 can include or be coupled with one or more processors or one or more memory components capable of operating to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1310, or the transceiver 1310 and the one or more antennas 1315, or the transceiver 1310 and the one or more antennas 1315 and the one or more processors or one or more memory components (e.g., the at least one processor 1335, the at least one memory 1325, or both) can be included in a chip or chip assembly mounted in the device 1305. In some examples, the transceiver 1310 can be capable of operating to support communication via one or more communication links (e.g., the communication links 125, the backhaul communication links 120, the in-transit communication links 162, the fronthaul communication links 168).

[0260] The at least one memory 1325 can include RAM, ROM, or any combination thereof. The at least one memory 1325 can store computer-readable, computer-executable code 1330 including instructions that, when executed by the one or more of the at least one processor 1335, cause the device 1305 to perform various functions described herein. The code 1330 can be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1330 can not be directly executable by the at least one processor 1335 but can cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1325 can include, among other things, a BIOS which can control basic hardware or software operation such as the interaction with peripheral components or devices. In some examples, the at least one processor 1335 can include a plurality of processors, and the at least one memory 1325 can include a plurality of memories. One or more of the plurality of processors can be coupled with one or more of the plurality of memories, which can be configured individually or collectively to perform various functions in this document (e.g., as part of a processing system).

[0261] The at least one processor 1335 can include an intelligent hardware device, e.g., a general- purpose processor, a DSP, an ASIC, a CPU, a FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof. In some cases, the at least one processor 1335 can be configured to operate a memory array using a memory controller. In some other cases, a memory controller can be integrated into one or more of the at least one processor 1335. The at least one processor 1335 can be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 1325 or another memory) to cause the device 1305 to perform various functions (e.g., functions or tasks supporting fault detection for communication power state transitions). For example, the device 1305 or a component of the device 1305 can include the at least one processor 1335 and the at least one memory 1325 coupled with the one or more of the at least one processor 1335, the at least one processor 1335 and the at least one memory 1325 configured to perform various functions described herein. The at least one processor 1335 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host (e.g., by executing code 1330) functions for performing functions of the device 1305. The at least one processor 1335 can be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1305, such as within one or more of the at least one memory 1325. In some implementations, the at least one processor 1335 can be a component of a processing system. A processing system generally can refer to a system or series of machines or components that receive inputs and process those inputs to produce a set of outputs (which can be passed to other systems or components of the device 1305, for example) that can be delivered to, for example, a user of the device 1305. For example, a processing system of the device 1305 can refer to a system that includes various other components or subcomponents of the device 1305, such as the at least one processor 1335 or the transceiver 1310 or the communications manager 1320, or a combination of other components or components of the device 1305. The processing system of the device 1305 can interface with other components of the device 1305 and can process information received from other components (such as inputs or signals) or output information to other components. For example, a chip or modem of the device 1305 can include a processing system and one or more interfaces for outputting information or for obtaining information or both. The one or more interfaces can be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information or the same interface configured to output information and to obtain information, among other implementations.In some implementations, the one or more interfaces can refer to an interface between the processing system and a transmitter of the chip or modem that enables the device 1305 to transmit information output from the chip or modem. Additionally or alternatively, in some implementations, the one or more interfaces can refer to an interface between the processing system and a receiver of the chip or modem that enables the device 1305 to obtain information or signal input and that information can be passed to the processing system. One of ordinary skill in the art will readily recognize that the first interface can also obtain information or signal input and the second interface can also output information or signal output.

[0262] In some examples, the bus 1340 can support communication of protocol layers (e.g., within which protocol layers) of a protocol stack. In some examples, the bus 1340 can support communications associated with logical channels of a protocol stack (e.g., between protocol layers of the protocol stack), which can include communications performed within a component of the device 1305, or between different components of the device 1305 that can be co-located or located at different locations (e.g., where the device 1305 can refer to a system in which one or more of the communication manager 1320, the transceiver 1310, the at least one memory 1325, the code 1330, and the at least one processor 1335 can be located in one component or partitioned between different components).

[0263] In some examples, the communication manager 1320 can manage aspects of the communication with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 1320 can manage the transfer of data communications for client devices, such as one or more UEs 115. In some examples, the communication manager 1320 can manage communications with other network entities 105, and can include a controller or scheduler for coordinating communications with UEs 115 in cooperation with other network entities 105. In some examples, the communication manager 1320 can support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0264] According to examples as disclosed herein, the communications manager 1320 can support wireless communications by a network entity. For example, the communications manager 1320 can perform, be configured for, or operate to support means for transmitting, to a UE, control information indicating a first schedule for the UE to transition between a set of multiple power states, where the set of multiple power states includes a only uplink state during which a primary radio of the UE is used for uplink transmissions and a second state during which the primary radio of the UE is used for at least downlink transmissions. The communications manager 1320 can perform, be configured for, or operate to support means for determining that the UE is to perform an RLF or BF detection operation. The communications manager 1320 can perform, be configured for, or operate to support means for transmitting, to the UE, a message triggering the UE to transition from the first schedule to a second schedule for the UE to transition between the set of multiple power states based on the determination that the UE is to perform the RLF or BF detection operation.

[0265] By including or configuring the communications manager 1320 in accordance with examples as described herein, the device 1305 can support techniques for reducing processing and more efficiently utilizing communication resources. For example, by utilizing one or more schedules for transitioning between power states, the device 1305 can improve coordination between devices and reduce latency. By enabling a UE in communication with the device 1305 to perform an RLF or BF detection operation procedure prior to transitioning to a only uplink power state, the device 1305 can improve communication reliability. Further, the device 1305 can prevent RLF or BF with the UE, thereby reducing latency.

[0266] In some examples, the communication manager 1320 may be configured to use or otherwise coordinate with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the transceiver 1310, one or more processors in at least one processor 1335, one or more memories in at least one memory 1325, code 1330, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1335, at least one memory 1325, code 1330, or any combination thereof). For example, code 1330 may include instructions that can be executed by one or more processors in at least one processor 1335 to cause the device 1305 to perform various aspects of fault detection for communication power state switching as described herein, or at least one processor 1335 and at least one memory 1325 may be otherwise configured to perform or support such operations individually or jointly.

[0267] Figure 14 A flowchart illustrating a method 1400 for fault detection of communication power state switching according to various aspects of this disclosure is shown. Operation of method 1400 can be implemented by a UE or its components as described herein. For example, operation of method 1400 can be implemented by, as referenced... Figures 1 to 9 The UE 115 described herein is used to perform this function. In some examples, the UE may execute multiple instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0268] At 1405, the method may include: receiving control information indicating a first scheduling for the UE to transition between multiple multi-power states, wherein the multiple multi-power states include an uplink-only state and a second state, during which the UE's primary radio component is used for uplink transmission, and during which the UE's primary radio component is used for at least downlink transmission. The operation of block 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1405 may be provided by reference to [reference needed]. Figure 8 The described control information component 825 is executed.

[0269] At 1410, the method may include: determining whether the UE wants to perform an RLF or BF detection operation. The operation of block 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be derived from references... Figure 8 The fault detection component 830 described herein is used to perform this operation.

[0270] At 1415, the method can include applying a second schedule for the UE to transition between the plurality of multi-power states based at least in part on the determination that the UE is to perform the RLF or BF detection operation. The operations of block 1415 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1415 can be performed by a scheduling component 835 as described with reference to Figure 8

[0271] Figure 15 A flow diagram illustrating a method 1500 that supports fault detection for communication power state switching in accordance with aspects of the present disclosure is shown. The operations of method 1500 can be implemented by a UE or its components as described herein. For example, the operations of method 1500 can be performed by a UE 115 as described with reference to Figures 1 to 9 FIGS. 13 through 15. In some examples, a UE can execute a set of instructions to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE can perform aspects of the functions described herein using special-purpose hardware.

[0272] At 1505, the method can include receiving control information indicating a first schedule for the UE to transition between a plurality of multi-power states, wherein the plurality of multi-power states includes a first state during which a primary radio of the UE is used for uplink transmissions and a second state during which the primary radio of the UE is used at least for downlink transmissions. The operations of block 1505 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1505 can be performed by a control information component 825 as described with reference to Figure 8 FIGS. 13 through 15. In some examples, a UE can execute a set of instructions to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE can perform aspects of the functions described herein using special-purpose hardware.

[0273] At 1510, the method can include receiving a WUS associated with an indication that the UE is to perform the RLF or BF detection operation. The operations of block 1510 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1510 can be performed by a WUS component 850 as described with reference to Figure 8 FIGS. 13 through 15. In some examples, a UE can execute a set of instructions to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE can perform aspects of the functions described herein using special-purpose hardware.

[0274] At 1520, the method can include receiving an indication of a time duration for a transition from the reception of the WUS and the first state to the second state. The operations of block 1520 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1520 can be performed by a scheduling component 835 as described with reference to Figure 8 FIGS. 13 through 15. In some examples, a UE can execute a set of instructions to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE can perform aspects of the functions described herein using special-purpose hardware.

[0275] ​At 1525, the method can include applying a second schedule for the UE to transition between the plurality of multi-power states based at least in part on the WUS, where the second schedule includes a transition from the only uplink state to the second state. The operations of block 1525 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1525 can be performed by a scheduling component 835 as described with reference to Figure 8

[0276] Figure 16 A flow diagram illustrating a method 1600 that supports fault detection for communication power state switching in accordance with aspects of the present disclosure is shown. The operations of method 1600 can be implemented by a network entity or its components as described herein. For example, the operations of method 1600 can be performed by a network entity as described with reference to Figures 1 to 5 Figures 10 to 13 In some examples, a network entity can execute a plurality of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity can perform aspects of the described functions using special-purpose hardware.

[0277] At 1605, the method can include transmitting, to a UE, control information indicating a first schedule for the UE to transition between a plurality of multi-power states, where the plurality of multi-power states includes an only uplink state during which a main radio of the UE is used for uplink transmissions and a second state during which the main radio of the UE is used at least for downlink transmissions. The operations of block 1605 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1605 can be performed by a control information component 1225 as described with reference to Figure 12

[0278] At 1610, the method can include determining that the UE is to perform an RLF or BF detection operation. The operations of block 1610 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1610 can be performed by a failure detection component 1230 as described with reference to Figure 12

[0279] At 1615, the method can include transmitting, to the UE, a message triggering the UE to transition from the first schedule to a second schedule for the UE to transition between the plurality of multi-power states based at least in part on the determination that the UE is to perform the RLF or BF detection operation. The operations of block 1615 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1615 can be performed by a transition triggering component 1235 as described with reference to Figure 12

[0280] Figure 17 ​​​​​A flowchart illustrating a method 1700 that supports fault detection for communication power state switching in accordance with aspects of the present disclosure is shown. The operations of method 1700 can be implemented by a network entity or its components as described herein. For example, the operations of method 1700 can be performed by a network entity as described with reference to Figures 1 to 5 Also Figures 10 to 13 Additionally or alternatively, the network entity can execute a plurality of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity can use special-purpose hardware to perform aspects of the described functions.

[0281] At 1705, the method can include transmitting, to a UE, control information indicating a first schedule for the UE to transition between a plurality of multi-power states, where the plurality of multi-power states includes a first state during which a primary radio of the UE is used for uplink transmissions and a second state during which the primary radio of the UE is used for at least downlink transmissions. The operations of block 1705 can be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1705 can be performed by a control information component 1225 as described with reference to Figure 12 FIG. 12.

[0282] At 1710, the method can include determining that the UE is to perform RLF or BF detection operations. The operations of block 1710 can be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1710 can be performed by a failure detection component 1230 as described with reference to Figure 12 FIG. 12.

[0283] At 1715, the method can include transmitting a DCI message that activates the RLF or BF detection operations. The operations of block 1715 can be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1715 can be performed by a control information component 1225 as described with reference to Figure 12 FIG. 12.

[0284] At 1720, the method can include transmitting, to the UE, a message that triggers the UE to transition from the first schedule to a second schedule for the UE to transition between the plurality of multi-power states based at least in part on the determination that the UE is to perform the RLF or BF detection operations. The operations of block 1720 can be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1720 can be performed by a transition trigger component 1235 as described with reference to Figure 12 FIG. 12.

[0285] At 1725, the method can include receiving an uplink message including an indication to apply the second schedule at the UE. The operations of block 1725 can be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1725 can be performed by a transition trigger component 1235 as described with reference to Figure 12

[0286] At 1730, the method can include transmitting one or more downlink signals for RLF or BF detection operations at the UE based at least in part on receiving the uplink message, where the uplink message is one of an uplink control information message, a MAC-CE, or a PUSCH message to which the indication is piggybacked. The operations of block 1730 can be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1730 can be performed by a failure detection component 1230 as described with reference to Figure 12

[0287] Figure 18 A flow diagram illustrating a method 1800 that supports failure detection for communication power state transitions in accordance with aspects of the present disclosure is shown. The operations of method 1800 can be implemented by a UE or its components as described herein. For example, the operations of method 1800 can be performed by a UE 115 as described with reference to Figures 1 to 9 FIGS. 8 through 9. In some examples, a UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE can perform aspects of the described functions using special-purpose hardware.

[0288] At 1805, the method can include receiving control information indicating a schedule for the UE to transition between a plurality of multi-power states, where the plurality of multi-power states includes an uplink only state during which a main radio of the UE is used for uplink transmissions, a downlink only state during which the main radio of the UE is used for at least downlink transmissions, and a downlink and uplink state during which the main radio of the UE is used for both downlink transmissions and uplink transmissions. The operations of block 1805 can be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1805 can be performed by a control information component 825 as described with reference to Figure 8

[0289] At 1810, the method can include transmitting an uplink message. The operations of block 1810 can be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1810 can be performed by an uplink message component 840 as described with reference to Figure 8

[0290] ​​​​At 1815, the method can include modifying operation of a HARQ RTT timer based at least in part on a first state of the UE from among the plurality of multi-power states, where the HARQ RTT timer defines a minimum time duration between transmission of an uplink message and reception of a retransmission grant related to retransmission of the uplink message by the UE. The operations of block 1815 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1815 can be performed by a HARQ RTT timer component 845 as described with reference to Figure 8

[0291] Figure 19 A flow diagram illustrating an example method 1900 that supports fault detection for communication power state switching in accordance with aspects of the present disclosure is shown. The operations of method 1900 can be implemented by a UE or its components as described herein. For example, the operations of method 1900 can be performed by a UE 115 as described with reference to Figures 1 to 9 FIGS. 13 through 19. In some examples, a UE can execute a set of instructions to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE can perform aspects of the functions described herein using special-purpose hardware.

[0292] At 1905, the method can include receiving control information indicating a schedule for the UE to transition between a plurality of multi-power states, where the plurality of multi-power states includes an uplink only state during which a primary radio of the UE is used for uplink transmissions, a downlink only state during which the primary radio of the UE is used for at least downlink transmissions, and a downlink and uplink state during which the primary radio of the UE is used for both downlink transmissions and uplink transmissions. The operations of block 1905 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1905 can be performed by a control information component 825 as described with reference to Figure 8

[0293] At 1910, the method can include transmitting an uplink message. The operations of block 1910 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1910 can be performed by an uplink message component 840 as described with reference to Figure 8

[0294] ​​​At 1915, the method can include modifying operation of a HARQ RTT timer based at least in part on a first state of the plurality of multi-power states in which the UE is located, where the HARQ RTT timer defines a minimum time duration between transmission of an uplink message and reception of a retransmission grant related to retransmission of the uplink message by the UE. The operations of block 1915 can be performed according to and in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1915 can be performed by a HARQ RTT timer component 845 as described with reference to Figure 8 FIG. 8.

[0295] At 1920, the method can include suspending the HARQ RTT timer based at least in part on the first state being a sole uplink state. The operations of block 1920 can be performed according to and in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1920 can be performed by a HARQ RTT timer component 845 as described with reference to Figure 8 FIG. 8.

[0296] At 1925, the method can include transitioning to a second state of the plurality of multi-power states, the second state being one of a downlink and uplink state or a sole downlink state. The operations of block 1925 can be performed according to and in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1925 can be performed by a power state transition component 860 as described with reference to Figure 8 FIG. 8.

[0297] At 1930, the method can include resuming the HARQ RTT timer based at least in part on the second state being a sole downlink state or a downlink and uplink state. The operations of block 1930 can be performed according to and in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1930 can be performed by a HARQ RTT timer component 845 as described with reference to Figure 8 Figure 8 FIG. 8.

[0298] Aspect 1 : A method for wireless communications by a UE, comprising: receiving control information indicating a first schedule for the UE to transition between a plurality of power states, wherein the plurality of power states includes a sole uplink state during which a primary radio of the UE is used for uplink transmissions and a second state during which the primary radio of the UE is used at least for downlink transmissions; determining that the UE is to perform an RLF / BF detection operation; and applying a second schedule for the UE to transition between the plurality of power states based at least in part on the determination that the UE is to perform the RLF / BF detection operation.

[0299] Aspect 2: The method of aspect 1, wherein determining that the UE is to perform the RLF / BF detection operation comprises: receiving a DCI message activating the RLF / BF detection operation, wherein applying the second schedule is based at least in part on reception of the DCI message.

[0300] Aspect 3: The method of aspect 2, wherein the second schedule comprises: a postponement of a transition from the second state to the uplink only state until after expiration of a failure detection timer associated with the RLF / BF detection operation.

[0301] Aspect 4: The method of any one of aspects 2 through 3, wherein receiving the DCI message comprises: receiving an indication that the UE is to apply the second schedule.

[0302] Aspect 5: The method of aspect 1, wherein determining that the UE is to perform the RLF / BF detection operation comprises: receiving a WUS associated with an indication that the UE is to perform the RLF / BF detection operation, wherein applying the second schedule is based at least in part on reception of the WUS, and wherein the second schedule comprises a postponement of a transition from the second state to the uplink only state; and performing the RLF / BF detection operation after applying the second schedule.

[0303] Aspect 6: The method of aspect 5, wherein the WUS comprises an indication of the second schedule, and the second schedule comprises a transition to the uplink only state after completion of the RLF / BF detection operation.

[0304] Aspect 7: The method of any one of aspects 1 through 6, wherein the control information further indicates a plurality of schedules for the UE to transition between the plurality of power states, wherein the plurality of schedules comprises at least the first schedule and the second schedule, the method further comprising: receiving a priority indication associated with the RLF / BF detection operation; and selecting the second schedule from the plurality of schedules based at least in part on the priority indication for the RLF / BF detection operation.

[0305] Aspect 8: The method of aspect 7, wherein each schedule of the plurality of schedules comprises a respective timer duration for a postponement of a transition from the second state to the uplink only state, wherein selecting the second schedule from the plurality of schedules comprises: selecting the second schedule based at least in part on an association between the respective timer duration of the second schedule and the priority indication.

[0306] Aspect 9: The method of aspect 8, wherein the association comprises: a higher priority is associated with a longer timer duration before a transition from the second state to the uplink only state, and a lower priority is associated with a shorter timer duration before the transition from the second state to the uplink only state.

[0307] Aspect 10: The method of aspect 1, wherein determining that the UE is to perform the RLF / BF detection operation comprises: receiving a WUS associated with an indication that the UE is to perform the RLF / BF detection operation, wherein applying the second schedule is based at least in part on reception of the WUS, and wherein the second schedule comprises a transition from the uplink only state to the second state.

[0308] Aspect 11: The method of aspect 10, further comprising: receiving an indication of a time duration from reception of the WUS and the transition from the uplink only state to the second state.

[0309] Aspect 12: The method of any of aspects 1 through 11, further comprising: performing the RLF / BF detection operation; and detecting at least one failure instance during the RLF / BF detection operation, wherein applying the second schedule is based at least in part on detecting the at least one failure instance, and wherein the second schedule comprises a postponement of a transition from the second state to the uplink only state.

[0310] Aspect 13: The method of aspect 12, wherein the postponement of the transition from the second state to the uplink only state is until after expiration of a failure detection timer associated with the RLF / BF detection operation.

[0311] Aspect 14: The method of any of aspects 12 through 13, wherein the control information further indicates a plurality of schedules for the UE to transition between the plurality of power states, the plurality of schedules comprising at least the first schedule and the second schedule, the method further comprising: selecting the second schedule from the plurality of schedules based at least in part on detecting the at least one failure instance.

[0312] Aspect 15: The method of any of aspects 12 through 14, further comprising: transmitting an uplink message comprising an indication that the second schedule is applied; and receiving one or more downlink signals for performing the RLF / BF detection operation based at least in part on transmitting the uplink message, wherein the uplink message is one of an uplink control information message, a MAC-CE, or a PUSCH message to which the indication is piggybacked.

[0313] Aspect 16: A method for wireless communications by a network entity, comprising: transmitting, to a UE, control information indicating a first schedule for the UE to transition between a plurality of power states, wherein the plurality of power states includes a Uplink-Only state during which a main radio of the UE is used for uplink transmissions and a second state during which the main radio of the UE is used for at least downlink transmissions; determining that the UE is to perform an RLF / BF detection operation; and transmitting, to the UE, a message triggering the UE to transition from the first schedule to a second schedule for the UE to transition between the plurality of power states based at least in part on the determination that the UE is to perform the RLF / BF detection operation.

[0314] Aspect 17: The method of aspect 16, wherein transmitting the message triggering the UE to transition from the first schedule to the second schedule comprises transmitting a DCI message activating the RLF / BF detection operation.

[0315] Aspect 18: The method of aspect 17, wherein the second schedule comprises a postponement of a transition from the second state to the Uplink-Only state until after an expiration of a failure detection timer associated with the RLF / BF detection operation.

[0316] Aspect 19: The method of any one of aspects 17-18, wherein the DCI message comprises an indication that the UE is to apply the second schedule.

[0317] Aspect 20: The method of aspect 16, wherein transmitting the message triggering the UE to transition from the first schedule to the second schedule comprises transmitting a WUS associated with an indication that the UE is to perform the RLF / BF detection operation, wherein the second schedule comprises a postponement of a transition from the second state to the Uplink-Only state.

[0318] Aspect 21: The method of aspect 20, wherein the WUS comprises an indication of the second schedule, and the second schedule comprises a transition to the Uplink-Only state after completion of the RLF / BF detection operation.

[0319] Aspect 22: The method of any one of aspects 16-21, wherein the message triggering the UE to transition from the first schedule to the second schedule further indicates a plurality of schedules for the UE to transition between the plurality of power states, and wherein the plurality of schedules includes at least the first schedule and the second schedule, the method further comprising: transmitting a priority indication associated with the RLF / BF detection operation.

[0320] Aspect 23: The method of aspect 22, wherein each of the plurality of schedules comprises a respective timer duration for a defer of a transition from the second state to the uplink only state.

[0321] Aspect 24: The method of aspect 16, wherein transmitting the message that triggers the UE to transition from the first schedule to the second schedule comprises transmitting a WUS associated with an indication that the UE is to perform the RLF / BF detection operation, wherein the second schedule comprises a transition from the uplink only state to the second state.

[0322] Aspect 25: The method of aspect 24, further comprising transmitting an indication of a time duration from reception of the WUS and the transition from the uplink only state to the second state.

[0323] Aspect 26: The method of any one of aspects 16 through 25, further comprising receiving an uplink message comprising an indication to apply the second schedule at the UE; and transmitting one or more downlink signals for the RLF / BF detection operation at the UE based at least in part on receiving the uplink message, wherein the uplink message is one of an uplink control information message, a MAC-CE, or a PUSCH message to which the indication is piggybacked.

[0324] Aspect 27: A method for wireless communications by a UE, comprising: receiving control information indicating a schedule for the UE to transition between a plurality of power states, wherein the plurality of power states comprise an uplink only state during which a main radio of the UE is used for uplink transmissions, a downlink only state during which the main radio of the UE is used at least for downlink transmissions, and a downlink and uplink state during which the main radio of the UE is used for both downlink transmissions and uplink transmissions; transmitting an uplink message; and modifying operation of a HARQ RTT timer based at least in part on a first state of the plurality of power states in which the UE is, wherein the HARQ RTT timer defines a minimum time duration between transmission of the uplink message and reception of a retransmission grant related to a retransmission of the uplink message by the UE.

[0325] Aspect 28: The method of aspect 27, wherein modifying operation of the HARQ RTT timer comprises suspending the HARQ RTT timer based at least in part on the first state being the downlink only state.

[0326] Aspect 29: The method of any of Aspect 27, wherein modifying operation of the HARQ RTT timer comprises refraining from initiating the HARQ RTT timer based at least in part on the first state being the uplink only state.

[0327] Aspect 30: The method of Aspect 27, wherein modifying operation of the HARQ RTT timer comprises initiating the HARQ RTT timer based at least in part on the first state being the downlink only state or the downlink and uplink state.

[0328] Aspect 31: The method of Aspect 27, wherein modifying operation of the HARQ RTT timer comprises suspending the HARQ RTT timer based at least in part on the first state being the uplink only state.

[0329] Aspect 32: The method of Aspect 31, further comprising transitioning to a second state of the plurality of power states, the second state being one of the downlink and uplink state or the downlink only state; and resuming the HARQ RTT timer based at least in part on the second state being the downlink only state or the downlink and uplink state.

[0330] Aspect 33: A UE for wireless communication, comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and operable, singly or collectively, to execute the code to cause the UE to perform the method of any of aspects 1 through 15.

[0331] Aspect 34: A UE for wireless communication, comprising at least one means for performing the method of any of aspects 1 through 15.

[0332] Aspect 35: A non-transitory computer-readable medium storing code for wireless communication by a UE, the code comprising instructions executable by one or more processors to perform the method of any of aspects 1 through 15.

[0333] Aspect 36: A network entity for wireless communication, comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and operable, singly or collectively, to execute the code to cause the network entity to perform the method of any of aspects 16 through 26.

[0334] Aspect 37: A network entity for wireless communication, comprising at least one means for performing a method of any of aspects 16 through 26.

[0335] Aspect 38: A non-transitory computer-readable medium storing code for wireless communications by a network entity, the code comprising instructions executable by one or more processors to perform a method of any of aspects 16 through 26.

[0336] Aspect 39: A UE for wireless communication, comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and operable, singly or collectively, to execute the code to cause the UE to perform a method of any of aspects 27 through 32.

[0337] Aspect 40: A UE for wireless communication, comprising at least one means for performing a method of any of aspects 27 through 32.

[0338] Aspect 41: A non-transitory computer-readable medium storing code for wireless communications by a UE, the code comprising instructions executable by one or more processors to perform a method of any of aspects 27 through 32.

[0339] It should be noted that the methods described herein describe possible implementations, and that the operations and the steps can be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods can be combined.

[0340] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system can be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology can be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques can be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and others.

[0341] Information and signals described herein can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that can be referenced throughout the description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0342] The various illustrative blocks and components described in connection with the disclosure herein can be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, a FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor can be a microprocessor, but in the alternative, the processor can be any processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). The various functions and operations described herein as being able to be performed by the processor can alternatively be performed by the processor in combination with other processors.

[0343] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions can also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0344] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium can be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0345] As used herein, including in the claims “or” as used in a list of items (for example, a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” can be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”

[0346] As used herein, including in the claims, the article “a” preceding a noun is an open, indefinite article, and is to be construed to mean “at least one” or “one or more” of the noun. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of each” are interchangeable. For example, where a claim recites “a component” that performs one or more functions, each function can be performed by the single component or by any combination of more components. Therefore, the term “component” having a particular characteristic or performing a particular function can refer to “at least one of each component” having that characteristic or performing that function. A subsequent reference to “the component” in the claim, where the claim has been introduced by the article “a” or “the,” can refer to any or all of the components. For example, a component introduced by the article “a” can be understood to mean “one or more components,” and a subsequent reference to “the component” in the claim can be understood as a reference to “at least one of the one or more components.” Similarly, a subsequent reference to “the component,” where the claim has been introduced by the article “a” or “the,” can refer to any or all of the components. For example, a subsequent reference to “the one or more components” in the claim can be understood as a reference to “at least one of the one or more components.”

[0347] The term “determining” encompasses a wide variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via a table, a database, or another data structure), ascertaining and the like. Also, “determining” can include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like. Also, “determining” can include resolving, selecting, choosing, establishing, and other such similar actions.

[0348] In the drawings, like components or features can have the same reference label. Also, various components of the same type can be distinguished by adding a dash and a second label that distinguishes among the components. If only the first reference label is used in the specification, the description is applicable to any one of the components having the same first reference label irrespective of the second reference label, or other subsequent reference label.

[0349] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that can be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” over other examples. The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0350] The description herein is presented to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not to be limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively capable of operating to execute the code to cause the UE to: receive first scheduled control information indicating for the UE to transition between a plurality of power states, wherein the plurality of power states includes an uplink only state during which a main radio of the UE is used for uplink transmissions and a second state during which the main radio of the UE is used at least for downlink transmissions; determine that the UE is to perform a radio link failure or beam failure detection operation; and apply a second schedule for the UE to transition between the plurality of power states based at least in part on the determination that the UE is to perform the radio link failure or beam failure detection operation.

2. The UE of claim 1, wherein to determine that the UE is to perform the radio link failure or beam failure detection operation, the one or more processors individually or collectively are capable of operating to execute the code to cause the UE to: receive a downlink control information message activating the radio link failure or beam failure detection operation, wherein applying the second schedule is based at least in part on receipt of the downlink control information message. a postponement of a transition from the second state to the uplink only state until after expiration of a failure detection timer associated with the radio link failure or beam failure detection operation.

3. The UE of claim 2, wherein the second schedule comprises:

4. The UE of claim 2, wherein to receive the downlink control information message, the one or more processors individually or collectively are capable of operating to execute the code to cause the UE to: receive an indication that the UE is to apply the second schedule.

5. The UE of claim 1, wherein to determine that the UE is to perform the radio link failure or beam failure detection operation, the one or more processors individually or collectively are capable of operating to execute the code to cause the UE to: receive a wake-up signal associated with an indication that the UE is to perform the radio link failure or beam failure detection operation, wherein applying the second schedule is based at least in part on receipt of the wake-up signal, and wherein the second schedule includes a postponement of a transition from the second state to the uplink only state; and perform the radio link failure or beam failure detection operation after applying the second schedule.

6. The UE of claim 5, wherein: the wake-up signal includes an indication of the second schedule, and the second schedule includes a transition to the uplink only state after completion of the radio link failure or beam failure detection operation. ​ 7. The UE of claim 1, wherein the control information further indicates a plurality of schedules for the UE to transition between the plurality of power states, and the one or more processors, individually or collectively, are further capable of executing the code to cause the UE to: receive a priority indication associated with the radio link or beam failure detection operation; and select the second schedule from the plurality of schedules based at least in part on the priority indication for the radio link or beam failure detection operation.

8. The UE of claim 7, wherein each schedule of the plurality of schedules includes a respective timer duration for a deferral of a transition from the second state to the uplink only state, and wherein to select the second schedule from the plurality of schedules, the one or more processors, individually or collectively, are capable of executing the code to cause the UE to: select the second schedule based at least in part on an association between the respective timer duration of the second schedule and the priority indication. A higher priority is associated with a longer timer duration before a transition from the second state to the uplink only state, and a lower priority is associated with a shorter timer duration before the transition from the second state to the uplink only state.

10. The UE of claim 1, wherein to determine that the UE is to perform the radio link or beam failure detection operation, the one or more processors, individually or collectively, are capable of executing the code to cause the UE to: receive a wake-up signal associated with an indication that the UE is to perform the radio link or beam failure detection operation, wherein applying the second schedule is based at least in part on reception of the wake-up signal, and wherein the second schedule includes a transition from the uplink only state to the second state.

11. The UE of claim 10, wherein the one or more processors, individually or collectively, are further capable of executing the code to cause the UE to: receive an indication of a time duration from the reception of the wake-up signal and the transition from the uplink only state to the second state.

9. The UE of claim 8, wherein the association comprises:

12. The UE of claim 1, wherein the one or more processors, individually or collectively, are further capable of executing the code to cause the UE to: perform the radio link or beam failure detection operation; and detect at least one instance of failure during the radio link or beam failure detection operation, wherein applying the second schedule is based at least in part on detecting the at least one instance of failure, and wherein the second schedule includes a deferral of a transition from the second state to the uplink only state.

13. The UE of claim 12, wherein the deferral of the transition from the second state to the uplink only state is until after expiration of a failure detection timer associated with the radio link or beam failure detection operation. ​ ​ ​ ​ ​ ​ ​ 14. The UE of claim 12, wherein the control information further indicates a plurality of schedules for the UE to transition between the plurality of power states, and the one or more processors, individually or collectively, are further capable of executing the code to cause the UE to: select the second schedule from the plurality of schedules based at least in part on detecting the at least one failure instance.

15. The UE of claim 12, wherein the one or more processors, individually or collectively, are further capable of executing the code to cause the UE to: transmit an uplink message including an indication that the second schedule is applied; and receive one or more downlink signals to perform the radio link or beam failure detection operation based at least in part on transmitting the uplink message, wherein the uplink message is one of an uplink control information message, a medium access control (MAC) control element (CE), or a physical uplink shared channel message to which the indication is piggybacked.

16. A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and capable, individually or collectively, of executing the code to cause the network entity to: transmit, to a user equipment (UE), control information indicating a first schedule for the UE to transition between a plurality of power states, wherein the plurality of power states includes a first state during which a primary radio of the UE is used for uplink transmissions and a second state during which the primary radio of the UE is used at least for downlink transmissions; determine that the UE is to perform a radio link or beam failure detection operation; and transmit, to the UE, a message triggering the UE to transition from the first schedule to a second schedule for the UE to transition between the plurality of power states based at least in part on the determination that the UE is to perform the radio link or beam failure detection operation.

17. The network entity of claim 16, wherein to transmit the message triggering the UE to transition from the first schedule to the second schedule, the one or more processors, individually or collectively, are capable of executing the code to cause the network entity to: transmit a downlink control information message activating the radio link or beam failure detection operation.

18. The network entity of claim 17, wherein the second schedule comprises: defer a transition from the second state to the first state until after expiration of a failure detection timer associated with the radio link or beam failure detection operation.

19. The network entity of claim 17, wherein the downlink control information message includes an indication that the second schedule is to be applied by the UE.

20. The network entity of claim 16, wherein to transmit the message that triggers the UE to transition from the first schedule to the second schedule, the one or more processors, singly or collectively, are able to operate, individually or collectively, to execute the code to cause the network entity to: transmit a wake-up signal associated with an indication that the UE is to perform the radio link failure or beam failure detection operation, wherein the second schedule comprises a postponement of a transition from the second state to the only uplink state.

21. The network entity of claim 16, wherein the message that triggers the UE to transition from the first schedule to the second schedule further indicates a plurality of schedules for the UE to transition between the plurality of power states, and the one or more processors, singly or collectively, are further able to operate, individually or collectively, to execute the code to cause the network entity to: transmit a priority indication associated with the radio link failure or beam failure detection operation.

22. The network entity of claim 21, wherein each schedule of the plurality of schedules comprises a respective timer duration for a postponement of a transition from the second state to the only uplink state.

23. The network entity of claim 16, wherein to transmit the message that triggers the UE to transition from the first schedule to the second schedule, the one or more processors, singly or collectively, are able to operate, individually or collectively, to execute the code to cause the network entity to: transmit a wake-up signal associated with an indication that the UE is to perform the radio link failure or beam failure detection operation, wherein the second schedule comprises a transition from the only uplink state to the second state.

24. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and able to operate, individually or collectively, to execute the code to cause the UE to: receive control information indicating a schedule for the UE to transition between a plurality of power states, wherein the plurality of power states comprises an only uplink state during which a primary radio of the UE is used for uplink transmissions, an only downlink state during which the primary radio of the UE is used for at least downlink transmissions, and a downlink and uplink state during which the primary radio of the UE is used for both downlink transmissions and uplink transmissions; transmit an uplink message; and modify operation of a hybrid automatic repeat request (HARQ) round trip time timer based at least in part on a first state of the plurality of power states in which the UE is, wherein the HARQ round trip time timer defines a minimum time duration between transmission of the uplink message and reception of a retransmission grant related to retransmission of the uplink message by the UE. ​ 25. The UE of claim 24, wherein to modify operation of the HARQ round trip time timer, the one or more processors, singly or collectively, are capable of operating, individually or collectively, to execute the code to cause the UE to: suspend the HARQ round trip time timer based at least in part on the first state being the downlink only state.

26. The UE of claim 24, wherein to modify operation of the HARQ round trip time timer, the one or more processors, singly or collectively, are capable of operating, individually or collectively, to execute the code to cause the UE to: avoid initiating the HARQ round trip time timer based at least in part on the first state being the uplink only state.

27. The UE of claim 24, wherein to modify operation of the HARQ round trip time timer, the one or more processors, singly or collectively, are capable of operating, individually or collectively, to execute the code to cause the UE to: initiate the HARQ round trip time timer based at least in part on the first state being the downlink only state or the downlink and uplink state.

28. The UE of claim 24, wherein to modify operation of the HARQ round trip time timer, the one or more processors, singly or collectively, are capable of operating, individually or collectively, to execute the code to cause the UE to: suspend the HARQ round trip time timer based at least in part on the first state being the uplink only state.

29. The UE of claim 28, wherein the one or more processors, singly or collectively, are capable of operating, individually or collectively, to execute the code to cause the UE to: transition to a second state of the plurality of power states, the second state being one of the downlink and uplink state or the downlink only state; and resume the HARQ round trip time timer based at least in part on the second state being the downlink only state or the downlink and uplink state.

30. A method for wireless communication by a user equipment (UE), the method comprising: receiving control information indicating a first schedule for the UE to transition between a plurality of power states, wherein the plurality of power states includes an uplink only state during which a main radio of the UE is used for uplink transmissions and a second state during which the main radio of the UE is used at least for downlink transmissions; determining that the UE is to perform a radio link failure or beam failure detection operation; and applying a second schedule for the UE to transition between the plurality of power states based at least in part on the determination that the UE is to perform the radio link failure or beam failure detection operation.

Images