Low power wake-up signaling

Abstract

Methods, systems, and devices are described for wireless communication. A wireless device can receive first configuration information defining a first schedule of occasions for receiving a low-power wake-up signal via a first radio of the wireless device associated with low-power operation. The wireless device can receive second configuration information defining a periodic connected mode discontinuous reception (C-DRX) cycle including a second schedule of periodic on durations for monitoring a physical downlink control channel (PDCCH) via a second radio of the wireless device; and receive, in accordance with the first configuration information and at least a threshold amount before a start of a next on duration or a next PDCCH message, the low-power wake-up signal via the first radio of the wireless device.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. Patent Application No. 19 / 092,983, entitled “LOW POWER WAKEUP SIGNALING,” filed March 27, 2025, and U.S. Provisional Patent Application No. 63 / 574,109, entitled “LOW POWER WAKEUP SIGNALING,” filed April 3, 2024, each of which is assigned to the assignee of this application, and each of which is expressly incorporated herein by reference. Background Technology

[0003] The following text relates to wireless communication, including managing wake-up signaling.

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing 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-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may 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 Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0005] The described technology relates to improved methods, systems, devices, and apparatuses that support low-power wake-up signaling.

[0006] A method for wireless communication by a wireless device is described. The method may include: receiving first configuration information defining a first timetable for timing of receiving a low-power wake-up signal via a first radio component of the wireless device associated with low-power operation; receiving second configuration information defining a periodic connected-mode discontinuous reception (C-DRX) period, the C-DRX period including a second timetable for periodic on-duration of monitoring a physical downlink control channel (PDCCH) via a second radio component of the wireless device, different from the first radio component of the wireless device; and receiving the low-power wake-up signal via the first radio component of the wireless device according to the first configuration information and at least a threshold amount before the start of the next on-duration or before the next PDCCH message.

[0007] A wireless device for wireless communication is described. The wireless device may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the wireless device to: receive first configuration information defining a first timetable for timing of receiving a low-power wake-up signal via a first radio component of the wireless device associated with low-power operation; receive second configuration information defining a periodic C-DRX period including a second timetable for periodic on-time monitoring of a PDCCH via a second radio component of the wireless device, different from the first radio component of the wireless device; and receive the low-power wake-up signal via the first radio component of the wireless device according to the first configuration information and at least a threshold amount before the start of the next on-time period or before the next PDCCH message.

[0008] An apparatus for wireless communication at a UE is described. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the UE to: receive first configuration information defining a first timetable for timing of receiving a low-power wake-up signal via a first radio component of the wireless device associated with low-power operation; receive second configuration information defining a periodic C-DRX period including a second timetable for periodic on-time monitoring of a PDCCH via a second radio component of the wireless device, different from the first radio component of the wireless device; and receive the low-power wake-up signal via the first radio component of the wireless device according to the first configuration information and at least a threshold amount before the start of the next on-time period or before the next PDCCH message.

[0009] Another wireless device for wireless communication is described. The wireless device may include: components for receiving first configuration information defining a first timetable for timing of receiving a low-power wake-up signal via a first radio component of the wireless device associated with low-power operation; components for receiving second configuration information defining a periodic C-DRX period including a second timetable for monitoring the periodic on-time of a PDCCH via a second radio component of the wireless device, different from the first radio component of the wireless device; and components for receiving the low-power wake-up signal via the first radio component of the wireless device at least a threshold amount according to the first configuration information and before the start of the next on-time or the next PDCCH message.

[0010] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive first configuration information defining a first timetable for timing the reception of a low-power wake-up signal via a first radio component of the wireless device associated with low-power operation; receive second configuration information defining a periodic C-DRX period including a second timetable for monitoring the periodic on-time of a PDCCH via a second radio component of the wireless device, different from the first radio component of the wireless device; and receive the low-power wake-up signal via the first radio component of the wireless device according to the first configuration information and at least a threshold amount before the start of the next on-time or before the next PDCCH message.

[0011] Some examples of the methods, wireless devices, user equipment (UEs), and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: monitoring the PDCCH via the second radio component of the wireless device during the next power-on period based on receiving the low-power wake-up signal via the first radio component of the wireless device and at least the threshold amount before the start of the next power-on period or the next PDCCH message; and receiving the next PDCCH message via the second radio component of the wireless device during the next power-on period based on the monitoring.

[0012] Some examples of the methods, wireless devices, user equipment (UEs), and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving the low-power wake-up signal via the first radio component of the wireless device within at least the threshold amount at the start of the next power-on period; monitoring the PDCCH via the second radio component of the wireless device after the next power-on period; and receiving the next PDCCH message via the second radio component of the wireless device during subsequent power-on periods that occur after the next power-on period.

[0013] In some examples of the methods, wireless devices, user equipment (UEs), and nontransitory computer-readable media described herein, the low-power wake-up signal includes at least one bit indicating whether the PDCCH is monitored during the next power-on duration.

[0014] Some examples of methods, wireless devices, user equipment (UEs), and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: monitoring the PDCCH via the second radio component of the wireless device during the next power-on duration based on the at least one bit included in the received low-power wake-up signal; and avoiding monitoring the PDCCH via the second radio component of the wireless device during the next power-on duration based on the at least one bit included in the received low-power wake-up signal.

[0015] Some examples of methods, wireless devices, user equipment (UEs), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for monitoring the PDCCH via the second radio component of the wireless device during the next power-on duration, regardless of at least one bit included in the received low-power wake-up signal.

[0016] In some examples of the methods, wireless devices, user equipment (UEs), and nontransitory computer-readable media described herein, receiving the low-power wake-up signal may include operations, features, components, or instructions for receiving the low-power wake-up signal via the first radio component of the wireless device at least before the next activation duration, the method further comprising receiving a tracking reference signal (TRS) via the second radio component of the wireless device according to third configuration information and before the next activation duration.

[0017] In some examples of the methods, wireless devices, user equipment (UEs), and non-transitory computer-readable media described herein, the third configuration information includes TRS configuration and can be indicated by the low-power wake-up signal.

[0018] Some examples of the methods, wireless devices, user equipment (UEs), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting a channel state information (CSI) report via the second radio component of the wireless device during the next activation duration and regardless of the timer used for C-DRX.

[0019] In some examples of the methods, wireless devices, user equipment (UEs), and nontransitory computer-readable media described herein, receiving the low-power wake-up signal may include operations, features, components, or instructions for receiving the low-power wake-up signal via a first radio component of the wireless device prior to the next onset duration, the method further comprising: monitoring the PDCCH via a second radio component of the wireless device for the next PDCCH message based on receiving the low-power wake-up signal via the first radio component of the wireless device and prior to the next PDCCH message.

[0020] Some examples of the methods, wireless devices, user equipment (UEs), and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for terminating monitoring of the PDCCH via the second radio component of the wireless device for the next PDCCH message based on the expiration of one or more of an inactive timer for C-DRX, an enable duration timer, or the expiration of one or more timers associated with the low-power wake-up signal.

[0021] Some examples of the methods, wireless devices, user equipment (UEs), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control signaling from a network entity to terminate monitoring of the PDCCH, wherein the control signaling includes downlink control information (DCI).

[0022] In some examples of the methods, wireless devices, user equipment (UEs), and nontransitory computer-readable media described herein, receiving the low-power wake-up signal may include operations, features, components, or instructions for: receiving the low-power wake-up signal via the first radio component of the wireless device at least a threshold amount before the next PDCCH message during a time period in the first time period of the timing and during the current open time period in the second time period of the periodic open time period; the method further includes: monitoring the PDCCH via the second radio component of the wireless device during the current open time period and at least in part based on receiving the low-power wake-up signal at least a threshold amount before the next PDCCH message associated with the current open time period; and based on the monitoring, receiving the next PDCCH message via the second radio component of the wireless device during the current open time period.

[0023] Some examples of the methods, wireless devices, user equipment (UEs), and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for enabling one or more of an inactive timer or a duration timer for C-DRX based on receiving the low-power wake-up signal via the first radio component of the wireless device.

[0024] Some examples of the methods, wireless devices, user equipment (UEs), and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for terminating monitoring of the PDCCH via the second radio component of the wireless device during the current open duration based on the expiration of one or more of an inactive timer or an open duration timer for C-DRX.

[0025] In some examples of the methods, wireless devices, user equipment (UEs), and nontransitory computer-readable media described herein, receiving the low-power wake-up signal may include operations, features, components, or instructions for: receiving the low-power wake-up signal via the first radio component of the wireless device at least the threshold amount during a time period in the first time schedule of timing and during the current open duration in the second time schedule of periodic open duration, prior to the next PDCCH message; the method further includes: receiving a TRS via the second radio component of the wireless device according to third configuration information and before monitoring the PDCCH for the next PDCCH message during the current open duration.

[0026] In some examples of the methods, wireless devices, user equipment (UEs), and non-transitory computer-readable media described herein, the third configuration information includes TRS configuration and can be indicated by the low-power wake-up signal.

[0027] In some examples of the methods, wireless devices, user equipment (UEs), and non-transitory computer-readable media described herein, the low-power wake-up signal includes an on / off keying (OOK) waveform.

[0028] A method for wireless communication by a network entity is described. The method may include: transmitting first configuration information defining a first timetable for timing of receiving a low-power wake-up signal via a first radio component of a wireless device associated with low-power operation; transmitting second configuration information defining a periodic C-DRX period including a second timetable for periodic on-time of monitoring a PDCCH via a second radio component of the wireless device, different from the first radio component of the wireless device; and transmitting the low-power wake-up signal via the first radio component of the wireless device according to the first configuration information and at least a threshold amount before the start of the next on-time or before the next PDCCH message.

[0029] A network entity for wireless communication is described. The network entity may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the network entity to: transmit first configuration information defining a first timetable for receiving a low-power wake-up signal via a first radio component of a wireless device associated with low-power operation; transmit second configuration information defining a periodic C-DRX period including a second timetable for monitoring the periodic on-time of a PDCCH via a second radio component of the wireless device, different from the first radio component of the wireless device; and transmit the low-power wake-up signal via the first radio component of the wireless device according to the first configuration information and at least a threshold amount before the start of the next on-time or before the next PDCCH message.

[0030] An apparatus for wireless communication at a network entity is described. The apparatus may include one or more memories and is coupled to the one or more memories and configured to cause the network entity to use one or more processors to: transmit first configuration information defining a first timetable for timing of receiving a low-power wake-up signal via a first radio component of a wireless device associated with low-power operation; transmit second configuration information defining a periodic C-DRX period including a second timetable for monitoring the periodic on-time of a PDCCH via a second radio component of the wireless device, different from the first radio component of the wireless device; and transmit the low-power wake-up signal via the first radio component of the wireless device according to the first configuration information and at least a threshold amount before the start of the next on-time or before the next PDCCH message.

[0031] Another network entity for wireless communication is described. This network entity may include: components for transmitting first configuration information defining a first timetable for timing of receiving a low-power wake-up signal via a first radio component of a wireless device associated with low-power operation; components for transmitting second configuration information defining a periodic C-DRX period including a second timetable for monitoring the periodic on-time of a PDCCH via a second radio component of the wireless device, different from the first radio component of the wireless device; and components for transmitting the low-power wake-up signal via the first radio component of the wireless device at least a threshold amount according to the first configuration information and before the start of the next on-time or the next PDCCH message.

[0032] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: transmit first configuration information defining a first timetable for receiving a low-power wake-up signal via a first radio component of a wireless device associated with low-power operation; transmit second configuration information defining a periodic C-DRX period including a second timetable for monitoring the periodic on-time of a PDCCH via a second radio component of the wireless device, different from the first radio component of the wireless device; and transmit the low-power wake-up signal via the first radio component of the wireless device according to the first configuration information and at least by a threshold amount before the start of the next on-time or before the next PDCCH message.

[0033] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending the next PDCCH message during the next open duration.

[0034] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending the next PDCCH message during a subsequent opening period that occurs after the next opening period.

[0035] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the low-power wake-up signal includes at least one bit indicating whether the PDCCH is monitored during the next power-on duration.

[0036] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, sending the low-power wake-up signal may include operations, features, components, or instructions for sending a TRS based on third configuration information and prior to the next activation duration.

[0037] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the third configuration information includes TRS configuration and can be indicated by the low-power wake-up signal.

[0038] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving CSI reports during the next open duration and regardless of the timer used for C-DRX.

[0039] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending control signaling to terminate monitoring of the PDCCH, wherein the control signaling includes DCI.

[0040] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the low-power wake-up signal includes an on / off keying (OOK) waveform. Attached Figure Description

[0041] Figure 1 Examples of wireless communication systems supporting low-power wake-up signaling according to one or more aspects of this disclosure are shown.

[0042] Figure 2 An example of a network architecture supporting low-power wake-up signaling is shown, according to one or more aspects of this disclosure.

[0043] Figure 3 Examples of wireless communication systems supporting low-power wake-up signaling according to one or more aspects of this disclosure are shown.

[0044] Figures 4 to 6 An example of a signaling timeline supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown.

[0045] Figure 7 An example of a process flow supporting low-power wake-up signaling is shown according to one or more aspects of this disclosure.

[0046] Figure 8 and Figure 9 A block diagram of a device supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown.

[0047] Figure 10 A block diagram of a communication manager supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown.

[0048] Figure 11 A diagram of a system including a device supporting low-power wake-up signaling, according to one or more aspects of this disclosure, is shown.

[0049] Figure 12 and Figure 13 A block diagram of a device supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown.

[0050] Figure 14 A block diagram of a communication manager supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown.

[0051] Figure 15 A diagram of a system including a device supporting low-power wake-up signaling, according to one or more aspects of this disclosure, is shown.

[0052] Figure 16 and Figure 17 A flowchart illustrating a method for supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown. Detailed Implementation

[0053] Wireless devices may be equipped with multiple radio components, such as a primary radio component and a secondary radio component, to support various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). In some examples, the primary and secondary radio components may be able to, be configured to, or be operable to support low-power operation as described herein. In some examples, the primary and secondary radio components may have the capability to support the low-power operation described herein. In other examples, the primary radio component of the wireless device may be referred to as the main radio component, and the secondary radio component may be referred to as the low-power radio component. Therefore, the secondary radio component may only be able to, be configured to, or be operable to support the low-power operation described herein. The secondary radio component may have the capability to support the low-power operation described herein. The low-power radio component may include a transceiver (e.g., one or more receivers and / or transmitters) that is able to, be configured to, or be operable to support a lower power level compared to standard radio components. For example, a low-power radio component may include a transceiver capable of supporting power levels lower than those supported by the primary or master radio component in the user equipment (UE) (e.g., receiving low-power wake-up signals and efficiently switching between on / off states). The low-power radio component may be able to, be configured to, or be operable to support energy efficiency, making it suitable for applications where power savings are achievable. Compared to other complex signals (e.g., signals with more complex waveforms, such as FSK, OFDM), the low-power radio component may be able to, be configured to, or be operable to handle less complex signals (e.g., signals with simpler waveforms, such as OOK), thereby reducing energy consumption.

[0054] Wireless devices can be, are configured to, or are capable of operating to support low-power operation (also known as discontinuous reception (DRX) operation or connected DRX (C-DRX) operation). DRX is a power-saving mechanism that allows the wireless device to periodically switch between an active and sleep state. During the sleep state, the wireless device temporarily disables its receiver to conserve power and periodically wakes up to check for incoming data. This intermittent reception mode helps extend the battery life of the wireless device while maintaining connectivity with the network. C-DRX is another power-saving mechanism that enables the wireless device to synchronize its sleep cycles with network scheduling, resulting in more efficient power management. C-DRX allows the wireless device to enter longer sleep cycles during periods of low data activity, thereby reducing power consumption without sacrificing responsiveness to incoming data. This improved power-saving mechanism is important for extending the battery life of battery-powered wireless devices and ensuring efficient utilization of network resources. Wireless devices can support a variety of operations (e.g., receive, acquire, monitor, output, transmit) during low-power operation. For example, a wireless device may support various operations (e.g., receive, acquire, monitor, output, transmit) during a low-power period (e.g., a C-DRX period). A low-power period (such as a C-DRX period) may be defined by one or more off durations (also known as inactive durations) and at least one on duration (also known as active duration).

[0055] In some cases, the main radio component of a wireless device may be configured to monitor and receive one or more wake-up signals before an on-time period. A wake-up signal is a signal sent by the network to the wireless device to prompt (e.g., trigger) the wireless device to exit a low-power state (e.g., deep sleep mode) and become active. An example of a wake-up signal could be downlink control information (DCI) for power saving (DCP). Additionally, the main radio component of the wireless device may be configured to monitor a control channel (e.g., the Physical Downlink Control Channel (PDCCH)) during the on-time period. That is, the wireless device may be able, configured, or operable to receive a wake-up signal via its main radio component, thereby triggering the wireless device to monitor a control channel (e.g., the PDCCH), such as for downlink signaling (e.g., control information). After the on-time period may be a off-time period, in which the wireless device stops monitoring the control channel (e.g., the PDCCH). In some cases, when outside of the on-time period (e.g., during the off-time period), the wireless device may switch its main radio component to a deep sleep mode to save power. In some cases, the main radio component may still consume power even during deep sleep mode. The reason for this is that wireless devices may need to periodically receive synchronization signals from the network to maintain synchronization with the network (e.g., time and / or frequency synchronization), and the action of switching the main radio component on and off can consume a significant amount of power. Switching the on and off of radio components (such as the main radio component) may involve activating or deactivating transmitter and / or receiver components (e.g., circuitry) within the wireless device. Therefore, in some cases, it may be preferable to keep the main radio component of the wireless device on, even during deep sleep mode.

[0056] To achieve greater power savings at the wireless device, the secondary radio component of the wireless device can operate at a lower power level compared to the primary radio component. For example, the secondary radio component can be configured to receive and process signals of lower complexity (e.g., signals with simpler waveforms) compared to the primary radio component. Additionally, the secondary radio component can be configured to support efficient power switching (e.g., switching off and on), allowing it to switch on and off more effectively. The wireless device can monitor one or more low-power wake-up signals via the secondary radio component during one or more scheduling events (e.g., time periods, time slots, or other time units), and the wireless device can therefore completely power down the primary radio component for time periods outside of one or more scheduled on periods. A low-power wake-up signal may refer to a specific type of signal that triggers the wireless device to power up the primary radio component, and this signal can be configured to consume minimal power, thereby allowing the wireless device to conserve energy. Completely powering down the primary radio component may include disabling or shutting down all radio frequency transmit and receive capabilities of the primary radio component. In some cases, a deep sleep mode may be referred to as a state of complete power-down of the primary radio component and may include disabling or shutting down all radio frequency transmit and receive capabilities of the primary radio component. Therefore, the wireless device may be unable to transmit or receive any signals via the primary radio component, thus consuming minimal or no power. This effectively prevents the primary radio component from communicating with other wireless devices or the network until it is powered back on. If, for example, the wireless device receives a low-power wake-up signal via the secondary radio component (e.g., a low-power radio component) during at least one of one or more scheduling times, instructing the wireless device to monitor the control channel (e.g., PDCCH) via the primary radio component during at least one of one or more scheduling open times, the wireless device may power on the primary radio component. By monitoring and receiving the low-power wake-up signal via the secondary radio component, the wireless device consumes minimal power, and the wireless device can then power on the primary radio component to monitor the control channel (e.g., PDCCH) and receive downlink signaling (e.g., control information) from the network.

[0057] Some wireless communication systems can simultaneously support C-DRX cycles and low-power wake-up signals. For example, a network entity can configure one or more off durations and one or more on durations for a C-DRX cycle for the UE. The UE's primary radio unit can be configured to monitor and receive one or more wake-up signals (such as DCP) via the primary radio unit before the on duration. The UE can receive the DCP via the primary radio unit, thereby triggering the UE to monitor the PDCCH for the DCI. Furthermore, and in some cases, the UE can also be configured to monitor one or more low-power wake-up signals via a secondary radio unit during one or more scheduling periods. The low-power wake-up signal can trigger the UE to power on the primary radio unit. Efficient power switching can include dynamic switching between inactive modes (e.g., off) and active modes (e.g., on) to save energy based on real-time demand and service patterns. In the case of C-DRX with low-power wake-up signals, the network entity simultaneously sends the low-power wake-up signal and the DCP to trigger the UE to monitor the PDCCH. Reducing the signaling amount used to trigger the UE to monitor the PDCCH can improve C-DRX with low-power wake-up signals.

[0058] Techniques that trigger PDCCH monitoring using a low-power wake-up signal with C-DRX configuration can reduce signaling between the UE and network entities. For example, a low-power wake-up signal can be used instead of DCP to trigger UE monitoring of the PDCCH. Additionally or alternatively, sufficient time can be allocated to receive the low-power wake-up signal to allow the primary radio component to be powered on before PDCCH monitoring. In some examples, the UE may receive configuration information that schedules the timing of receiving the low-power wake-up signal via the UE's first radio component (e.g., a low-power wake-up signal radio component). The UE may receive configuration information that defines a periodic C-DRX period including a scheduled periodic on duration for monitoring the PDCCH via the UE's second radio component (e.g., the UE's primary or master radio component). The UE may receive the low-power wake-up signal by at least a threshold amount before the start of the next on duration or before the start of the next PDCCH message.

[0059] The aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to low-power wake-up signaling.

[0060] Figure 1An example of a wireless communication system 100 supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more devices, such as one or more network devices (e.g., network entity 105), one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be an LTE network, an LTE-A network, an LTE-A Pro network, an NR network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein. Network entity 105 may include a network entity communication manager 102 configured to support communications within the wireless communication system 100. Similarly, UE 115 may include a UE communication manager 101 configured to support communications within the wireless communication system 100.

[0061] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via communication link 125 (e.g., a radio frequency (RF) access link). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish communication link 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0062] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Examples of UE 115 are illustrated herein. The UE 115 described herein may be able to support communication with various types of devices in the wireless communication system 100 (e.g., other wireless communication devices, including UE 115 or network entity 105), such as... Figure 1 As shown.

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

[0064] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via backhaul communication link 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0065] One or more of the network entities 105 or network equipment described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity (e.g., network entity 105 or a single RAN node, such as base station 140).

[0066] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across multiple network entities (e.g., network entity 105) such as an integrated access and 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, network entity 105 may include one or more of the following: a central unit (CU) such as CU 160, a distributed unit (DU) such as DU 165, a radio unit (RU) such as RU 170, a RAN intelligent controller (RIC) such as 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) system such as SMO system 180, or any combination thereof. RU170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0067] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host upper-layer 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)). CU 160 (e.g., one or more CUs) may connect to DU 165 (e.g., one or more DUs) or RU 170 (e.g., one or more RUs), or some combination thereof, and DU 165, RU 170, or both may host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and may each be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split may be employed between DU 165 and RU 170, such that DU 165 may support one or more layers of the protocol stack, and RU 170 may support one or more different layers of the protocol stack. DU 165 may (e.g., via one or more different RUs, such as RU 170) support one or more different cells. In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by a different one of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by corresponding network entities (e.g., one or more network entities in network entity 105) that communicate via such communication links.

[0068] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities in network entity 105 (e.g., network entity 105 or IAB node 104) may be partially controlled by each other. IAB node 104 may be referred to as a donor entity or IAB donor. DU 165 or RU 170 may be partially controlled by CU 160 associated with network entity 105 or base station 140 (such as a donor network entity or donor base station). One or more donor entities (e.g., IAB donors) may communicate with one or more additional devices (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include IAB mobile terminals (IAB-MTs) controlled (e.g., scheduled) by one or more DUs (e.g., DU 165) of a coupled IAB donor. IAB-MTs may be separate sets equipped with antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as virtual IAB-MTs (vIAB-MTs)). In some examples, IAB node 104 may include one or more DUs (e.g., DU 165) that support communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., IAB node 104 or component 104 of the IAB node) may be configured to operate according to the techniques described herein.

[0069] For example, the access network (AN) or RAN may include an access node (e.g., an IAB donor), communication between IAB node 104 and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include one or more of CU 160, DU 165, and RU 170, in which case CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, CU 160 may communicate with core network 130 via an interface (which may be part of a backhaul link) and may communicate with other CUs (e.g., including CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be another part of a backhaul link).

[0070] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay for UE transmissions via other IAB nodes 104). Additionally or alternatively, IAB node 104 may also be referred to as a parent or child node of other IAB nodes 104, depending on the AN's relay chain or configuration. Therefore, the IAB-MT entity of IAB node 104 can provide a Uu interface for the child IAB node (e.g., IAB node 104) to receive signaling from the parent IAB node (e.g., IAB node 104), and the DU interface (e.g., DU 165) can provide a Uu interface for the parent IAB node to send signaling notifications to the child IAB node or UE 115.

[0071] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, an IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. An IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to UE 115) via one or more DUs (e.g., DU 165). In other words, data can be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104 (e.g., other IAB nodes). Communication with IAB node 104 can be scheduled by the IAB donor or by DU 165 of IAB node 104.

[0072] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support the tests described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., components such as IAB node, DU 165, CU 160, RU 170, RIC 175, SMO system 180, etc.).

[0073] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances, vehicles, or meters.

[0074] The UE 115 described herein can communicate with various types of devices, such as the UE 115 which sometimes operates as a relay, as well as network entity 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0075] UE 115 and network entity 105 can wirelessly communicate with each other via communication link 125 (e.g., one or more access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined PHY layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (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, such as one or more network entities in network entity 105).

[0076] As described herein, a node, which may be referred to as a node, network node, network entity, or wireless node, can be a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, and / or another suitable processing entity configured to perform any of the techniques described herein. For example, a network node can be a UE. As another example, a network node can be a base station. As yet another example, a first network node can be configured to communicate with a second or third network node. In one aspect of this example, the first network node can be a UE, the second network node can be a base station, and the third network node can be a UE. In another aspect of this example, the first network node can be a UE, the second network node can be a base station, and the third network node can be a base station. In still other aspects of this example, the first network node, the second network node, and the third network node can be different from these examples. Similarly, references to UE, base station, apparatus, device, computing system, etc., can include disclosures of UE, base station, apparatus, device, computing system, etc., as network nodes. For example, the disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a particular example is extended according to this disclosure (e.g., the disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example can be interpreted in reverse, but in a broad, open-ended manner. In the above example where the disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node can refer to a first UE, a first base station, a first device, a first equipment, a first computing system, a first or more components, a first processing entity, etc., configured to receive information; and the second network node can refer to a second UE, a second base station, a second device, a second equipment, a second computing system, a second or more components, a second processing entity, etc.

[0077] As described herein, different terms may be used in various contexts to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with this disclosure, disclosure that a first network node is configured to send information to a second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with this disclosure, disclosure that a first network node is configured to send information to a second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicate, or sent by the first network node.

[0078] In some examples, such as in carrier aggregation configurations, a carrier may have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., of the same or different RATs) are used to anchor the connection.

[0079] The communication link 125 of the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. The carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0080] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a specific RAT (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have a hardware configuration that supports communication using a specific carrier bandwidth, or may be configured to support communication using one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0081] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0082] It can support one or more parameter sets for a carrier, and the parameter sets may include 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 to utilize multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and communication for UE 115 can be constrained to one or more active BWPs.

[0083] 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, in response This can represent the supported subcarrier spacing, while The supported Discrete Fourier Transform (DFT) size can be represented. Time intervals for 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).

[0084] 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 also be 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, such as wireless communication system 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.

[0085] 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)).

[0086] Depending on the technology, carriers can be used to multiplex physical channels for communication. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a common search space set configured to transmit control information to UE 115 (e.g., one or more UEs) or a UE-specific search space set configured to transmit control information to UE 115 (e.g., a particular UE).

[0087] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, etc., or may include buildings, subsets of buildings, or external space between or overlapping coverage areas, etc.

[0088] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast to macro cells, small cells may be associated with network entities 105 operating at lower power (e.g., base station 140 operating at lower power) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also support communication via one or more cells using one or more component carriers.

[0089] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0090] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas (such as coverage area 110). In some examples, coverage areas 110 associated with different technologies (e.g., different coverage areas) may overlap, but coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., network entity 105). In some other examples, overlapping coverage areas (such as coverage area 110) associated with different technologies may be supported by different network entities (e.g., network entity 105). The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different RATs to support communication in coverage areas 110 (e.g., different coverage areas).

[0091] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timing, and transmissions from different network entities (e.g., different network entities within network entity 105) can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities (e.g., different network entities within network entity 105) may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0092] Some UE 115 devices (such as MTC or IoT devices) can be relatively low-cost or low-complexity devices and can provide 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 each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or instruments to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices may 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 and tracking, remote security sensing, physical access control, and transaction-based service charging.

[0093] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115 may include: entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0094] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0095] In some examples, UE 115 may be configured to support direct communication with other UEs (e.g., one or more UEs in UE 115) via a device-to-device (D2D) communication link (such as D2D communication link 135) (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group performing D2D communication may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, in which each UE 115 transmits to one or more UEs in the group. In some examples, network entity 105 can facilitate the scheduling of resources used for D2D communication. In some other examples, D2D communication can be performed between UEs 115 without involving network entity 105.

[0096] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or a combination of these. Vehicles may signal information related to traffic conditions, signal control, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0097] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be transferred through user plane entities, which provide IP address allocation and other functions. User plane entities can connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0098] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers).

[0099] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) region (also known as the centimeter band) in the range of 3 GHz to 30 GHz or in the extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmission, EHF transmission may experience even greater attenuation and a shorter range. The techniques disclosed herein can be adopted across transmissions using one or more different frequency zones, and the frequency band usage specified across these frequency zones may vary by country or regulatory authority.

[0100] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6GHz" band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is different from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

[0101] The frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G NR studies have identified the operating bands used for these IF bands as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to IF band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating frequency bands have been identified as the frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0102] In light of the foregoing, unless otherwise specifically stated, it should be understood that, as used herein, the term "below 6 GHz" and the like can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that, as used herein, the term "millimeter wave" and the like can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR4-a or FR4-1 and / or FR5, or within the EHF band.

[0103] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0104] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0105] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, 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 information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0106] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device by the transmitting or receiving device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0107] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 along different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

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

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

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

[0111] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0112] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under relatively poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0113] UE 115 supports multiple functions, including wireless communication (e.g., downlink receive, uplink transmit) based on one or more operating modes (including idle mode, inactive mode, and connected mode). In idle mode, UE 115 may not be connected to the network and therefore may not be able to perform wireless communication with the network (e.g., downlink receive, uplink transmit). However, UE 115 can listen to control channels (e.g., the Physical Downlink Control Channel (PDCCH)) to maintain synchronization with the network. In inactive mode, UE 115 may have established a connection with the network but may not perform wireless communication with the network (e.g., downlink receive, uplink transmit). Inactive mode allows UE 115 to re-establish (e.g., reactivate) the connection when wireless communication is needed. In connected mode, UE 115 has an active connection to the network and performs wireless communication with the network (e.g., downlink receive, uplink transmit).

[0114] Figure 2An example of a network architecture 200 (e.g., a decomposed base station architecture, a decomposed RAN architecture) supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown. Network architecture 200 may exemplify examples of one or more aspects for implementing wireless communication system 100. Network architecture 200 may include one or more CUs 160-a that can communicate directly with core network 130-a via backhaul communication link 120-a, or indirectly with core network 130-a via one or more decomposed network entities 105 (e.g., near-RT RIC 175-b via an E2 link or a non-RT RIC 175-a associated with SMO 180-a (e.g., an SMO framework) or both). CUs 160-a may communicate with one or more DUs 165-a via a corresponding midhaul communication link 162-a (e.g., an F1 interface). DUs 165-a may communicate with one or more RUs 170-a via a corresponding fronthaul communication link 168-a. RU 170-a may be associated with a corresponding coverage area 110-a and may communicate with UE 115-a via one or more communication links 125-a. In some implementations, UE 115-a may be served by multiple RU 170-a simultaneously.

[0115] Each network entity in network entity 105 of network architecture 200 (e.g., CU 160-a, DU 165-a, RU170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, Open Cloud (O-Cloud) 205, Open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or transmit signals (e.g., data, information) via wired or wireless transmission media. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to the interfaces of network entity 105 may be configured to communicate with one or more network entities in other network entities 105 via transmission media. For example, these network entities 105 may include wired interfaces configured to receive signals or transmit signals to one or more network entities in other network entities 105 via wired transmission media. Additionally or alternatively, network entity 105 may include a wireless interface that may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals via a wireless transmission medium or to transmit signals to one or more other network entities in network entity 105, or both.

[0116] In some examples, the CU 160-a can host one or more higher-level control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function can be implemented using an interface configured to communicate signaling with other control functions hosted by the CU 160-a. The CU 160-a can be configured to handle user plane functionalities (e.g., CU-UP), control plane functionalities (e.g., CU-CP), or combinations thereof. In some examples, the CU 160-a can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 160-a can be implemented to communicate with the DU 165-a for network control and signaling purposes, as needed.

[0117] DU 165-a may correspond to a logic unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RU 170-a. In some examples, DU 165-a may at least partially host one or more aspects of the RLC layer, MAC layer, and PHY layer (e.g., high PHY layers, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on the functional partitioning, such as those defined by the 3rd Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface configured to communicate with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0118] In some examples, lower-layer functionality may be implemented by one or more RU 170-a units. For example, an RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (e.g., performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both) based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UE 115-a units. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a unit. In some examples, such configurations enable the DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0119] The SMO 180-a can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (e.g., the O1 interface). For virtualized network entities 105, the SMO 180-a can be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., the O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a can communicate with components configured according to the 4G RAN (e.g., via the O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RU 170-a via the O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0120] The non-RT RIC 175-a can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updates, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a can be coupled to or communicate with the near-RT RIC 175-b (e.g., via the A1 interface). The near-RT RIC 175-b can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions on an interface (e.g., via the E2 interface) connecting one or more CU 160-a, one or more DU 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b.

[0121] In some examples, to generate AI / ML models to be deployed in a near-RT RIC 175-b, a non-RT RIC 175-a may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 175-b and can be received from non-network data sources or network functions at the SMO 180-a or non-RT RIC 175-a. In some examples, a non-RT RIC 175-a or near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, a non-RT RIC 175-a may monitor long-term trends and patterns in performance and employ AI or ML models to perform corrective actions via the SMO 180-a (e.g., via O1 reconfiguration) or via the generation of RAN management policies such as the A1 policy.

[0122] Figure 3 An example of a wireless communication system 300 supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown. The wireless communication system 300 may implement as referenced... Figure 1 The wireless communication system 100 is described in various aspects. The wireless communication system 300 can achieve the functions described herein. Figure 2 The network architecture 200 described herein may be implemented by or comprise various aspects of the network architecture 200. For example, the wireless communication system 300 may include network entities 105-a and UE 115-b, which may be as referred to herein respectively. Figure 1 and Figure 2 Examples of network entity 105 and UE 115 described. Wireless communication system 300 may support one or more radio access technologies, including 4G, 5G, or higher. Therefore, one or more of network entity 105-a or UE 115-b may support one or more radio access technologies, including 4G, 5G, or higher.

[0123] exist Figure 3In the example, UE 115-b may be equipped with multiple radio components, such as radio component 302 and radio component 304, to support various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Radio component 302 of UE 115-b may be referred to as a low-power radio component, while radio component 304 of UE 115-b may be referred to as a primary radio component. UE 115-b may be equipped with at least one processor 305 configured to perform one or more of the operations described herein. At least one processor 305 may include multiple processors configured to perform one or more of the operations described herein. UE 115-b may have the capability to, be able to, be configured to, or be operable to support low-power operation (also known as DRX operation, C-DRX operation). UE 115-b may support various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) during low-power operation. For example, UE 115-b can support various operations (e.g., receive, acquire, monitor, output, transmit) during low-power cycles (e.g., C-DRX cycles). A low-power cycle (such as a C-DRX cycle) can be defined by one or more shutdown durations (also known as inactive durations) and at least one on duration (also known as an active duration). In some cases, a C-DRX cycle may include an offset (e.g., a timing offset) between the start of the C-DRX cycle and the start of at least one on duration. That is, the offset may define the start of at least one on duration relative to the start of the C-DRX cycle.

[0124] In some cases, the radio component 304 of UE 115-b may be configured to monitor and receive one or more wake-up signals before the start-up duration. Additionally, the radio component 304 of UE 115-b may be configured to monitor a control channel (e.g., PDCCH) during the start-up duration. That is, UE 115-b may be able, configured, or operable to receive a wake-up signal via its radio component 304 during a C-DRX cycle, thereby triggering UE 115-b to monitor a control channel (e.g., PDCCH), such as for downlink signaling from network entity 105-a. The start-up duration may be followed by a stop-down duration, in which UE 115-b stops monitoring the control channel (e.g., PDCCH).

[0125] In some cases, UE 115-b may switch its radio component 304 to deep sleep mode to save power when outside of the on period. In some instances, even during deep sleep mode, the radio component 304 of UE 115-b may still consume power. This is because UE 115-b may need to periodically receive synchronization signals from network entity 105-a to maintain synchronization with network entity 105-a (e.g., time and / or frequency synchronization), and switching the radio component 304 of UE 115-b on and off can consume significant power. Therefore, in some cases, keeping the radio component 304 of UE 115-b on even during deep sleep mode may be preferred. In some cases, deep sleep mode is a power-saving state in which the radio component 304 is inactive or off.

[0126] In some cases, if UE 115-b receives downlink signaling, UE 115-b may start an inactivity timer, and when the inactivity timer expires, UE 115-b's radio component 304 may switch to a lower power mode (e.g., deep sleep mode). In some cases, UE 115-b may receive one or more synchronization signals (e.g., one or more synchronization signal blocks (SSBs)) via UE 115-b's radio component 304. UE 115-b may need to receive one or more synchronization signals to maintain synchronization with network entity 105-a. Additionally or alternatively, UE 115-b may support CSI reporting via UE 115-b's radio component 304 during the on-time period.

[0127] To achieve greater power savings at UE 115-b, radio component 302 of UE 115-b can operate at a lower power level compared to radio component 304 of UE 115-b. For example, radio component 302 of UE 115-b can be configured to receive and process signals of lower complexity (e.g., signals with simpler waveforms, such as OOK waveforms) compared to radio component 304 of UE 115-b. Additionally, radio component 302 of UE 115-b can be designed to support efficient power switching, thereby enabling the radio component to switch on and off more effectively. In some cases, efficient power switching may include dynamic switching between inactive modes (e.g., off) and active modes (e.g., on) to save energy based on real-time demand and service patterns. UE 115-b can monitor one or more low-power wake-up signals during one or more scheduling periods, and UE 115-b can therefore completely power down radio component 304 for periods outside of one or more scheduling on periods. For example, if UE 115-b receives a low-power wake-up signal during at least one of one or more scheduling times, indicating that UE 115-b should monitor the control channel (e.g., PDCCH) via radio component 304 during at least one of one or more scheduling open times, then UE 115-b may power on radio component 304.

[0128] UE 115-b may receive first configuration information 306, which defines a first timetable for the timing of receiving a low-power wake-up signal 308 via the radio component 302 of UE 115-b associated with low-power operation. The low-power wake-up signal 308 may have or be an on / off keying (OOK) waveform. UE 115-b may receive second configuration information 310, which defines a periodic C-DRX period, which includes a second timetable for the periodic on-time duration of PDCCH monitoring via the radio component 304 of UE 115-b. The periodic on-time duration may occur in fixed intervals (e.g., every...). x (milliseconds, seconds, time slots, or other time units). UE 115-b may receive a low-power wake-up signal 308 via its radio component 302, based on first configuration information 306 and at least a threshold amount before the start of the next activation duration or the next PDCCH message, as referenced. Figures 4 to 6 More detailed description.

[0129] UE 115-b may monitor the PDCCH via its radio component 304 during the next power-on period based on receiving a low-power wake-up signal 308 via its radio component 302 and at least a threshold amount before the start of the next power-on period or before the next PDCCH message. UE 115-b may receive the next PDCCH message via its radio component 304 during the next power-on period based on this monitoring. In some examples, based on receiving the low-power wake-up signal 308 via its radio component 302 within at least a threshold amount at the start of the next power-on period, UE 115-b may monitor the PDCCH via its radio component 304 after the next power-on period. UE 115-b may receive the next PDCCH message via its radio component 304 during a subsequent power-on period occurring after the next power-on period, as referenced. Figures 4 to 6 More detailed description.

[0130] In some examples, UE 115-b may monitor the PDCCH via its radio component 304 during the next power-on duration based on at least one bit included in the received low-power wake-up signal 308, as referenced. Figure 4 More detailed description. UE 115-b may avoid (e.g., suppress, prevent, stop, obstruct, bypass, skip) monitoring of the PDCCH via its radio component 304 during the next power-on duration based on at least one bit included in the received low-power wake-up signal 308. In some examples, UE 115-b may monitor the PDCCH via its radio component 304 during the next power-on duration regardless of (e.g., ignoring, independent of) at least one bit included in the received low-power wake-up signal 308. Additionally or alternatively, UE 115-b may receive the low-power wake-up signal 308 via its radio component 302 at least a threshold amount before the next power-on duration, and receive the TRS via its radio component 304 according to third configuration information 312 before the next power-on duration. The third configuration information 312 includes a TRS configuration, and the third configuration information 312 may be indicated by the low-power wake-up signal 308.

[0131] UE 115-b may receive a low-power wake-up signal 308 via its radio component 302 before the next on-duration, and based on the receipt of the low-power wake-up signal 308 via its radio component 302 and before the next PDCCH message, monitor the PDCCH via its radio component 304 for the next PDCCH message. UE 115-b may terminate (e.g., stop, end) its monitoring of the PDCCH via its radio component 304 for the next PDCCH message based at least in part on the expiration of one or more of the inactive timer 314, the on-duration timer 316 for connected-mode discontinuous reception, or the expiration of one or more timers 318 associated with the low-power wake-up signal 308, as referenced. Figures 4 to 6 More detailed description.

[0132] Therefore, to experience power efficiency at UE 115-b, radio component 302 can be configured to operate at a reduced power level compared to radio component 304 of UE 115-b. Specifically, radio component 302 can handle signals with simpler characteristics, such as signals with lower-complexity waveforms (e.g., OOK waveforms). OOK waveforms can be a form of amplitude modulation where the carrier signal represents a binary mode (e.g., binary data) by switching on and off. Furthermore, compared to radio component 304 of UE 115-b, radio component 302 of UE 115-b can be configured to facilitate seamless power switching, thereby allowing for more efficient activation and deactivation processes. In some cases, seamless power switching may involve dynamically switching between inactive modes (e.g., off) and active modes (e.g., on) in an efficient and timely manner. Therefore, UE 115-b can actively monitor one or more wake-up signals during scheduling periods while completely deactivating radio component 304 of UE 115-b during periods outside of the scheduled on duration.

[0133] Figure 4 An example of a signaling timeline 400 supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown. The signaling timeline 400 may be implemented as described in the reference. Figure 1 The wireless communication system 100 described herein includes various aspects. The signaling timeline 400 can be implemented as referenced herein. Figure 2 The network architecture 200 described herein, or can be implemented by these aspects, is as follows. The signaling timeline 400 can be implemented as referenced in this document. Figure 3 The described aspects of the wireless communication system 300, or aspects thereof, can be implemented. The signaling timeline 400 can implement 5G or higher radio access technologies, or can be implemented using 5G or higher radio access technologies.

[0134] For example, UE 115-c can execute a set of instructions to control the functional elements (e.g., circuits) of UE 115-c to perform the described functions. UE 115-c may be as shown in the reference. Figures 1 to 3 Example of a UE as described. Additionally or alternatively, UE115-c may use radio component 302-a or radio component 304-a to perform aspects of the described functions, the radio component being as described in the reference. Figure 3 Examples of the described radio components 302 and 304.

[0135] In the following description of signaling timeline 400, the operations performed by UE 115-c may be in a different order than the example order shown, or the operations performed by UE 115-c may be performed in a different order or at different times. Some operations may also be omitted from signaling timeline 400, and other operations may be added to signaling timeline 400.

[0136] UE 115-c may be equipped with multiple radio components, such as radio component 302-a and radio component 304-a, to support various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Figure 4 In the example, radio component 302-a of UE 115-c may be referred to as the low-power radio component, while radio component 304-a of UE 115-c may be referred to as the primary radio component. Radio component 302-a of UE 115-c may be configured to monitor and receive one or more low-power wake-up signals during one or more scheduling events 402 (also known as low-power wake-up signal monitoring events). Radio component 304-a of UE 115-c may be configured to monitor and receive one or more control channels (e.g., one or more PDCCHs) during one or more scheduling on durations 404 (also known as active durations) of a C-DRX cycle. A C-DRX cycle consists of two components: an on duration 404 and an off duration (i.e., the time period outside of the on duration 404).

[0137] UE 115-c may switch its radio component 304-a to deep sleep mode to conserve power outside of one or more scheduled on durations 404. Therefore, UE 115-c can avoid (e.g., suppress, prevent, stop, obstruct, bypass, skip) monitoring one or more control channels (e.g., one or more PDCCHs) outside of one or more scheduled on durations 404. In some instances, even during deep sleep mode, the radio component 304-a of UE 115-c may still consume power. This is because UE 115-c may need to periodically receive synchronization signals from the network to maintain synchronization with the network (e.g., time and / or frequency synchronization), and switching the radio component 304-a off and on can consume significant power. Therefore, it is preferable to keep the radio component 304-a of UE 115-c on even during deep sleep mode.

[0138] To achieve greater power savings at UE 115-c, radio component 302-a of UE 115-c can operate at a lower power level compared to radio component 304-a of UE 115-c. For example, radio component 302-a of UE 115-c can be configured to receive and process signals of lower complexity (e.g., signals with simpler waveforms, such as OOK waveforms) compared to radio component 304-a of UE 115-c. Additionally, radio component 302-a of UE 115-c can be designed to support efficient power switching (e.g., switching radio component 302-a of UE 115-c to on or off), thereby enabling the radio component to switch on and off more efficiently. Therefore, UE 115-c can monitor one or more wake-up signals during one or more scheduling periods 402, and UE 115-c can power off radio component 304-a during a period 401 outside of one or more scheduling on durations 404. For example, if UE 115-c receives a low-power wake-up signal during at least one of one or more scheduling opportunities 402, instructing UE 115-c to monitor the control channel (e.g., PDCCH) via its radio component 304-a during at least one of one or more scheduling open durations 404, then UE 115-c may power on radio component 304-a. Additionally or alternatively, if UE 115-c does not expect to receive a low-power wake-up signal or other low-power signals (e.g., low-power reference signals, low-power synchronization signals), then UE 115-c may power off radio component 302-a (e.g., shut down circuitry such as the receiver and transmitter of the radio component).

[0139] exist Figure 4In the example, one or more scheduling opportunities 402 can be configured to occur at least a threshold amount 406 before the start of one or more scheduling start durations 404. That is, scheduling opportunity 402-a can be configured to occur at least a threshold time before the start of the next start duration 404-a following scheduling opportunity 402-a. The threshold time may represent the minimum duration required for UE 115-c to power on radio component 304-a. If UE 115-c receives a low-power wake-up signal 308-a via radio component 302-a during scheduling opportunity 402-a, where scheduling opportunity 402-a occurs at least a threshold amount 406 before the start of the next start duration 404-a or the next PDCCH message 408, then UE 115-c may monitor the control channel (e.g., PDCCH) via radio component 304-a during the next start duration 404-a. In other words, if UE 115-c receives a low-power wake-up signal 308-a during scheduling timing 402-a, UE 115-c may initiate (e.g., start, initiate, trigger, enable) a timer, such as onDurationTimer, associated with the next on-time duration 404-a. For example, UE 115-c may power on radio component 304-a to monitor the control channel (e.g., PDCCH) during the next on-time duration 404-a and receive the next PDCCH message 408 based on that monitoring. However, if scheduling timing 402-a does not occur at least a threshold amount 406 before the start of the next on-time duration 404-a, UE 115-c may be configured to monitor the control channel (e.g., PDCCH) during a subsequent on-time duration 404-b (e.g., after the next on-time duration 404-a).

[0140] In some examples, the low-power wake-up signal 308-a may include at least one bit 424 indicating whether the control channel (e.g., PDCCH) is monitored during the next on-time duration 404-a. This means that the low-power wake-up signal 308-a can explicitly command UE 115-c whether to monitor the control channel (e.g., PDCCH) during the next on-time duration 404-a. In some cases, if UE 115-c monitors the low-power wake-up signal 308-a via its radio component 302-a during scheduling timing 402-a and does not receive the low-power wake-up signal, then UE 115-c may by default monitor the control channel (e.g., PDCCH) via its radio component 304-a during the next on-time duration 404-a. This means that regardless of the presence of at least one bit 424 included in the low-power wake-up signal 308-a, UE 115-c can use radio component 304-a to monitor the control channel (e.g., PDCCH) during the next power-on duration 404-a.

[0141] In some other examples, the low-power wake-up signal 308-a may exclude (e.g., not include) at least bit 424 indicating whether to monitor the control channel (e.g., PDCCH) during the next on-time duration 404-a. In this example, if UE 115-c monitors the low-power wake-up signal 308-a via its radio component 302-a during scheduling timing 402-a and receives the low-power wake-up signal 308-a during scheduling timing 402-a, then UE 115-c may monitor the control channel (e.g., PDCCH) during the next on-time duration 404-a. Otherwise, if UE 115-c monitors the low-power wake-up signal 308-a via its radio component 302-a during scheduling timing 402-a but does not receive the low-power wake-up signal 308-a during scheduling timing 402-a, then UE 115-c may, for example, default to avoiding (e.g., suppressing, preventing, stopping, hindering, bypassing, skipping) monitoring the control channel (e.g., PDCCH) during the next on-time duration 404-a.

[0142] exist Figure 4 In the example, after receiving a low-power wake-up signal 308-a via radio component 302-a of UE 115-c during scheduling timing 402-a, and before monitoring the control channel (e.g., PDCCH) during the next on-time duration 404-a, UE 115-c may receive TRS 410 via radio component 304-a. Alternatively, UE 115-c may receive TRS 410 via radio component 304-a during the next on-time duration 404-a. As referenced herein Figures 1 to 3 The TRS 410 described, received from network entity 105 or base station 140, may be received before the next activation duration 404-a. In some examples, TRS 410 may indicate a TRS configuration, such as indicated by a low-power wake-up signal 308-a. This TRS configuration enables UE115-c to synchronize with network entity 105 or base station 140, as referenced herein. Figures 1 to 3 As described herein. In some examples, because synchronization, such as frequency synchronization and time synchronization, can be performed via radio component 304-a of UE 115-c, UE 115-c can receive TRS 410 before monitoring the control channel (e.g., PDCCH) during the next on-time duration 404-a. Additionally, as referenced herein... Figures 1 to 3 As described, synchronization with network entity 105 or base station 140 may be necessary before UE 115-c is able to monitor control channels (e.g., PDCCH).

[0143] UE 115-c may support CSI measurement and reporting during at least one of one or more on-duration periods 404. For example, UE 115-c may receive and measure one or more CSI-RS via radio component 304-a of UE 115-c. Subsequently, UE 115-b may transmit a CSI report based on the measured one or more CSI-RS via radio component 304-a of UE 115-c. For example, during an on-duration period 404 (such as on-duration period 404-b), UE 115-c may transmit a CSI report 412 based on the received CSI-RS. CSI report 412 may provide CSI to network entity 105 or base station 140, as referenced herein. Figures 1 to 3 As described. CSI can indicate channel quality, channel gain, and other CSI parameters. Figure 4 In the example, UE 115-c can be configured to send CSI report 412 regardless of the timer used for C-DRX. That is, even if such... onDurationTimer If the timer is not triggered by a low-power wake-up signal (such as low-power wake-up signal 308-a), UE115-c can also be configured to send a CSI report 412. Alternatively, when such as onDurationTimer When the timer is not triggered by a low-power wake-up signal (such as low-power wake-up signal 308-a), UE 115-c can be configured to avoid sending (e.g., skip sending) CSI report 412. CSI report 412 may include (e.g., contain, indicate, identify) one or more Layer 1 (L1) Reference Signal Received Power (RSRP) (L1-RSRP) or L1 Signal-to-Interference-plus-Noise Ratio (L1-SINR) measurements. L1 measurements such as L1-RSRP and / or L1-SINR may refer to measurements performed at the PHY layer of UE 115-c.

[0144] Therefore, to experience power efficiency at UE 115-c, radio component 302-a can be configured to operate at a reduced power level compared to radio component 304-a. Specifically, radio component 302-a can be configured to prioritize signals with simpler characteristics, such as signals with lower waveform complexity. Furthermore, radio component 302-a can be configured to facilitate seamless power switching, allowing for more efficient activation and deactivation processes. Thus, UE 115-c can actively monitor one or more wake-up signals during scheduling timing 402, while deactivating radio component 304-a during periods outside of scheduling start duration 404. As described herein, if a low-power wake-up signal is received during scheduling timing 402, indicating the need to monitor the control channel (e.g., PDCCH) during the subsequent scheduling start duration 404, UE 115-c can therefore activate radio component 304-a.

[0145] Figure 5 An example of a signaling timeline 500 supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown. The signaling timeline 500 may implement as referenced... Figure 1 The wireless communication system 100 described herein. The signaling timeline 500 can be implemented as referenced herein. Figure 2 The network architecture 200 described herein, or can be implemented by these aspects, is similar to the signaling timeline 500, which can be implemented as referenced in this document. Figure 3 The described aspects of the wireless communication system 300, or aspects thereof, can be implemented. The signaling timeline 500 can implement 5G or higher radio access technologies, or can be implemented using 5G or higher radio access technologies.

[0146] For example, UE 115-d can execute a set of instructions to control its functional elements (e.g., circuitry) to perform the described functions. UE 115-d may be as shown in the reference. Figures 1 to 3 Example of a UE as described. Additionally or alternatively, UE115-d may use radio component 302-b or radio component 304-b to perform aspects of the described functions, the radio component being as described in the reference. Figure 3 Examples of the described radio components 302 and 304.

[0147] In the following description of signaling timeline 500, the operations performed by UE 115-d may be in a different order than the example order shown, or the operations performed by UE 115-d may be performed in a different order or at different times. Some operations may also be omitted from signaling timeline 500, and other operations may be added to signaling timeline 500.

[0148] UE 115-d may be equipped with multiple radio components, such as radio component 302-b and radio component 304-b, to support various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Figure 5 In the example, radio component 302-b of UE 115-d may be referred to as the low-power radio component, while radio component 304-b of UE 115-d may be referred to as the primary radio component. Radio component 302-b of UE 115-d may be configured to monitor and receive one or more low-power wake-up signals during one or more scheduling events 502 (also known as low-power wake-up signal monitoring events). Radio component 304-b of UE 115-d may be configured to monitor and receive one or more control channels (e.g., one or more PDCCHs) during one or more scheduling on durations 504 (also known as activity durations) of a C-DRX cycle.

[0149] To achieve greater power savings at UE 115-d, the radio component 302-b of UE 115-d can operate at a lower power level compared to the radio component 304-b of UE 115-d. For example, compared to the radio component 304-b of UE 115-d, the radio component 302-b of UE 115-d can be configured to receive and process signals of lower complexity (e.g., signals with simpler waveforms). Additionally, compared to the radio component 304-b of UE 115-d, the radio component 302-b of UE 115-d can be designed to support efficient power switching, thereby enabling the radio component to switch on and off more effectively.

[0150] UE 115-d may monitor one or more wake-up signals during scheduling opportunity 502, and UE 115-d may power down radio component 304-b outside of scheduling start duration 504. In some examples, UE 115-d may monitor at least one scheduling opportunity 502 of one or more scheduling opportunities 502 before scheduling start duration 504 in one or more scheduling start durations 504. That is, UE 115-d may monitor one scheduling opportunity 502 for each scheduling start duration 504. In some other examples, UE 115-d may monitor multiple scheduling opportunities (e.g., at least two scheduling opportunities 502) before scheduling start duration 504. If UE 115-d receives a low-power wake-up signal during any of the scheduling opportunities 502, indicating that UE 115-d should monitor control channel 506 (e.g., PDCCH) after receiving low-power wake-up signal 308-b and before the next scheduling start duration 504-a, then UE 115-d may power on radio component 304-b. In some examples, in addition to scheduling start duration 504-a, monitoring of the control channel 506 (e.g., PDCCH) may also be triggered by a low-power wake-up signal 308-b. Even if UE 115-d does not receive a low-power wake-up signal, for example during scheduling timing 502-a (e.g., the previous scheduling timing), UE 115-d may power on radio component 304-b to monitor the control channel (e.g., PDCCH) during scheduling start duration 504-a. That is, UE 115-d can monitor each scheduling start duration 504 regardless of whether UE 115-d receives a low-power wake-up signal. In some other examples, monitoring of the control channel (e.g., PDCCH) may be triggered by the low-power wake-up signal 308-b instead of scheduling start duration 504-a. If UE 115-d receives a low-power wake-up signal 308-b during scheduling timing 502-a, prior to scheduling start duration 504-a, then UE 115-d can avoid monitoring the control channel (e.g., PDCCH) during scheduling start duration 504-a. In other words, if UE 115-d receives the low-power wake-up signal 308-b and triggers monitoring of the control channel 506 prior to scheduling start duration 504-a, then UE 115-d can skip (e.g., cancel) monitoring of the control channel (e.g., PDCCH) during the upcoming scheduling start duration 504-a.

[0151] exist Figure 5In one example, UE 115-d may receive a low-power wake-up signal 308-b via its radio component 302-b during scheduling time 502-a in one or more scheduling times 502. In some examples, if UE 115-d receives the low-power wake-up signal 308-b during scheduling time 502-a in one or more scheduling times 502 and before the next activation duration (such as activation duration 504-a) or PDCCH monitoring triggered by the low-power wake-up signal 308-b, then UE 115-d may begin monitoring the control channel 506 (e.g., PDCCH) after receiving the low-power wake-up signal 308-b for a threshold amount 508 (e.g., a threshold amount of time). That is, when the low-power wake-up signal 308-b is received, UE 115-d begins monitoring the control channel 506 (e.g., PDCCH) for a period of time after receiving the low-power wake-up signal.

[0152] UE 115-d can be configured to support low-power operation based on one or more timers. For example, UE 115-d can be configured to support low-power operation based on an enable duration timer (e.g., onDurationTimer ), inactive timers (e.g., inactivityTimer The UE 115-b may support low-power operation by using one or more timers associated with the low-power wake-up signal 308-b. The UE 115-b may be configured to terminate (e.g., stop, end, pause) monitoring of the control channel 506 (e.g., PDCCH) triggered by the low-power wake-up signal 308-b, for example, in response to the expiration (e.g., at least in part based on the expiration of the example timers described above). The one or more timers associated with the low-power wake-up signal 308-b may be separate timers associated with C-DRX, and the control channel monitoring triggered by the low-power wake-up signal 308-b may terminate upon the expiration of one or more of these timers. Additionally or alternatively, the UE 115-d may receive control signaling from network entity 105 or base station 140 via radio component 304-a of the UE 115-d, as referenced herein. Figures 1 to 3 As described, monitoring of the control channel 506 (e.g., PDCCH) triggered by a low-power wake-up signal 308-b is terminated (e.g., stopped, ended, paused). Control signaling may include a MAC control element (MAC-CE).

[0153] Therefore, to experience power efficiency at UE 115-d, radio component 302-b can be configured to operate at a reduced power level compared to radio component 304-b. Additionally, the functionality described above for UE 115-d can reduce latency when the C-DRX cycle length is relatively long. In other words, UE 115-d can reduce latency by configuring C-DRX to achieve maximum power savings and avoiding sacrificing latency for power savings when multiple low-power wake-up signals are configured between activation durations.

[0154] Figure 6 An example of a signaling timeline 600 supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown. The signaling timeline 600 may implement as referenced... Figure 1 The wireless communication system 100 described herein includes various aspects. The signaling timeline 600 can be implemented as referenced herein. Figure 2 The network architecture 200 described herein, or the aspects thereof, can be implemented by these aspects. The signaling timeline 600 can be implemented as referenced in this document. Figure 3 The described aspects of the wireless communication system 300, or aspects thereof, can be implemented. The signaling timeline 600 can implement 5G or higher radio access technologies, or can be implemented using 5G or higher radio access technologies.

[0155] For example, UE 115-e can execute a set of instructions to control the functional elements (e.g., circuits) of UE 115-e to perform the described functions. UE 115-e may be as shown in the reference. Figures 1 to 3 An example of the described UE. Additionally or alternatively, UE115-e may use radio component 302-c or radio component 304-c to perform aspects of the described functions, the radio component being as described in the reference. Figure 3 Examples of the described radio components 302 and 304.

[0156] In the following description of signaling timeline 600, the operations performed by UE 115-e may be in a different order than the example order shown, or the operations performed by UE 115-e may be performed in a different order or at different times. Some operations may also be omitted from signaling timeline 600, and other operations may be added to signaling timeline 600.

[0157] UE 115-e may be equipped with multiple radio components, such as radio component 302-c and radio component 304-c, to support various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Figure 6In the example, radio component 302-c of UE 115-e may be referred to as the low-power radio component, while radio component 304-c of UE 115-e may be referred to as the primary radio component. Radio component 302-c of UE 115-e may be configured to monitor and receive one or more low-power wake-up signals during one or more scheduling events 602 (also known as low-power wake-up signal monitoring events). Radio component 304-c of UE 115-e may be configured to monitor and receive one or more control channels (e.g., one or more PDCCHs) during one or more scheduling on durations 604 (also known as activity durations) of a C-DRX cycle. To achieve greater power savings at UE 115-e, radio component 302-c of UE 115-e may operate at a lower power level compared to radio component 304-c of UE 115-e, as described herein.

[0158] exist Figure 6 In the example, UE 115-e may receive a low-power wake-up signal 308-c via radio component 302-c of UE 115-d at least a threshold amount during scheduling timing 602-a and before the next PDCCH message during the current on duration 604-a. UE 115-e may perform control channel monitoring 609 (e.g., PDCCH monitoring) via radio component 304-c of UE 115-e during the current on duration 604-a. UE 115-e may begin control channel monitoring 609 (e.g., PDCCH monitoring) during the current on duration 604-a after receiving the low-power wake-up signal 308-c, at a threshold amount 606 (e.g., a threshold time). That is, when the low-power wake-up signal 308-c is received, UE 115-e may begin control channel monitoring 609 (e.g., PDCCH monitoring) for a period of time after receiving the low-power wake-up signal 308-c.

[0159] UE 115-e can be configured to support low-power operation based on one or more timers. UE 115-e can enable one or more of the following based on receiving a low-power wake-up signal 308-c via UE 115-e's radio component 302-c or based on receiving a PDCCH message 608: an inactive timer or a duration timer. For example, UE 115-e can start or restart the inactive timer after receiving the low-power wake-up signal 308-c via UE 115-e's radio component 302-c, or UE 115-e can start or restart the inactive timer after receiving a PDCCH message 608 via UE 115-e's radio component 302-c. In some examples, UE 115-b may be configured to terminate control channel monitoring 609 (e.g., PDCCH monitoring) triggered by low-power wake-up signal 308-c in response to the expiration (e.g., at least in part based on the expiration) of the example timer (e.g., one or more of the inactive timer or the start-up timer) associated with the current start-up duration 604-a.

[0160] In some examples, UE 115-e may receive TRS via its radio component 304-c for a period of time after receiving the low-power wake-up signal 308-c and before the control channel monitoring 609 (e.g., PDCCH monitoring) triggered by the low-power wake-up signal 308-c during the current on-time duration 604-a, as referenced. Figure 4 As described herein. (See references in this article.) Figures 1 to 4 The TRS received from network entity 105 or base station 140 as described herein may be received during the current on-time duration 604-a. In some examples, a low-power wake-up signal 308-c may indicate TRS configuration. This TRS configuration enables UE 115-e to synchronize with network entity 105 or base station 140, as referenced herein. Figures 1 to 4 As described herein. Because synchronization, such as frequency synchronization and time synchronization, may need to be performed via radio component 304-c of UE 115-e, UE 115-e may receive TRS during the current on-time duration 604-a prior to control channel monitoring 609 (e.g., PDCCH monitoring). Additionally, as referenced herein... Figures 1 to 4 As described, synchronization with network entity 105 or base station 140 may be necessary before UE 115-e can perform control channel monitoring 609 (e.g., PDCCH monitoring).

[0161] Therefore, to achieve power efficiency at UE 115-e, radio component 302-c can be configured to operate at a reduced power level compared to radio component 304-c. Additionally, the functions described above for UE 115-e can reduce power consumption and processing load when there is no data transmission for UE 115-e at the beginning of the power-on period. In other words, if there is no pending data transmission in the network at the beginning of the power-on period, UE 115-e can save power at that beginning of the power-on period.

[0162] Figure 7 An example of a process flow 700 supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown. Process flow 700 can be implemented as referenced. Figure 1 The wireless communication system 100 described herein. The process flow 700 can be implemented as referenced herein. Figure 2 The network architecture 200 described herein, or which can be implemented by these aspects, is described. Process flow 700 can be implemented as referenced. Figure 3 The described aspects of the wireless communication system 300. The process flow 700 can implement, or can be implemented by, 5G or higher radio access technologies.

[0163] Process flow 700 may include network entity 105-b and UE 115-f, which may be examples of network entity and UE as described herein. In the following description of process flow 700, operations between network entity 105-b and UE 115-f may be sent in a different order than the example order shown, or operations performed by network entity 105-b and UE 115-f may be performed in a different order or at different times. Some operations may also be omitted from process flow 700, and other operations may be added to process flow 700.

[0164] exist Figure 7 In the example, UE 115-f can execute a set of instructions to control the functional elements (e.g., circuitry) of UE 115-f to perform the operations described in process flow 700. UE 115-f can be as shown in the reference... Figures 1 to 6 An example of the described UE. Additionally or alternatively, UE 115-f may use radio component 302-d or radio component 304-d to perform aspects of the described operations, the radio component being as described in the reference. Figures 3 to 6 Examples of the described radio components 302 and 304.

[0165] For example, UE 115-f may be equipped with multiple radio components, such as radio component 302-d and radio component 304-d, to support various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Radio component 302-d of UE 115-f may be referred to as the low-power radio component, while radio component 304-d of UE 115-f may be referred to as the primary radio component. Radio component 302-d of UE 115-f may be configured to monitor and receive one or more low-power wake-up signals during one or more scheduling events, as referenced herein. Figures 3 to 6 As described herein, the radio component 304-d of UE 115-f can be configured to monitor and receive one or more control channels (e.g., one or more PDCCHs) during one or more scheduling open durations, as referenced herein. Figures 3 to 6 As described.

[0166] To achieve greater power savings at UE 115-f, radio component 302-d of UE 115-f can operate at a lower power level compared to radio component 304-d of UE 115-f. For example, compared to radio component 304-d of UE 115-f, radio component 302-d of UE 115-f can be configured to receive and process signals of lower complexity (e.g., signals with simpler waveforms). Additionally, compared to radio component 304-d of UE 115-f, radio component 302-d of UE 115-f can be designed to support efficient power switching, thereby enabling the radio component to switch on and off more effectively.

[0167] refer to Figure 7At 705, network entity 105-b can transmit, and UE 115-f can receive, first configuration information via radio component 304-d of UE 115-f, which defines a first timetable for the timing of receiving a low-power wake-up signal via radio component 302-d of UE 115-f associated with low-power operation. At 710, network entity 105-b can transmit, and UE 115-f can receive, second configuration information via radio component 304-d of UE 115-f, which defines a periodic C-DRX period including a second timetable for monitoring the periodic on-time of the PDCCH via radio component 304-d of UE 115-f, which is different from radio component 302-d of UE 115-f. At 715, network entity 105-b may transmit, and UE 115-f may receive, via radio component 302-d of UE 115-f, a low-power wake-up signal according to first configuration information and at least a threshold amount before the start of the next power-on period or the next PDCCH message. At 720, UE 115-f may optionally, for example, monitor the PDCCH via radio component 304-d of UE 115-f based on receiving the low-power wake-up signal and at least a threshold amount before the start of the next power-on period or the next PDCCH message, as referenced herein. Figures 3 to 6 As described. At 725, network entity 105-b can send and UE 115-f can receive downlink messages (e.g., PDCCH messages) via radio component 304-d of UE 115-f.

[0168] Figure 8 A block diagram 800 of a device 805 supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown. Device 805 may be an example of various aspects of UE 115 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805, or one or more components of device 805 (e.g., receiver 810, transmitter 815, communication manager 820), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0169] Receiver 810 may provide components 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 associated with low-power wake-up signaling). The information may be passed to other components of device 805. Receiver 810 may utilize a single antenna or a collection of antennas.

[0170] Transmitter 815 may provide components for transmitting signals generated by other components of device 805. For example, transmitter 815 may 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 associated with low-power wake-up signaling). In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0171] The communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be examples of components used to perform various aspects of low-power wake-up signaling as described herein. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0172] In some examples, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0173] Additionally or alternatively, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in code (e.g., referred to as processor executable code) executed by at least one processor (e.g., implemented as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0174] In some examples, the communication manager 820 may be configured to use a receiver 810, a transmitter 815, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or a combination of both to acquire information, output information, or perform various other operations as described herein.

[0175] Communication manager 820 may support wireless communication according to examples disclosed herein. For example, communication manager 820 may be, configured to, or operable to support components for: receiving first configuration information that defines a first schedule for the timing of receiving a low-power wake-up signal via a first radio component of device 805 associated with low-power operation. For example, communication manager 820 may be, configured to, or operable to support components for: receiving second configuration information that defines a periodic C-DRX period that includes a second schedule for monitoring the periodic on-time of the PDCCH via a second radio component of device 805, different from the first radio component of device 805. For example, communication manager 820 may be, configured to, or operable to support components for: receiving the low-power wake-up signal via the first radio component of device 805 according to the first configuration information and at least a threshold amount before the start of the next on-time period or the next PDCCH message.

[0176] By including or configuring a communication manager 820 according to an example as described herein, device 805 (e.g., controlling receiver 810, transmitter 815, communication manager 820 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing power consumption.

[0177] Figure 9 A block diagram 900 of a device 905 supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown. Device 905 may be an example of aspects of device 805 or UE 115 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905 or one or more components of device 905 (e.g., receiver 910, transmitter 915, communication manager 920) 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).

[0178] Receiver 910 may provide components 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 associated with low-power wake-up signaling). The information may be passed to other components of device 905. Receiver 910 may utilize a single antenna or a collection of antennas.

[0179] Transmitter 915 may provide components for transmitting signals generated by other components of device 905. For example, transmitter 915 may 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 associated with low-power wake-up signaling). In some examples, transmitter 915 may be co-located with receiver 910 in a transceiver module. Transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0180] Device 905 or its various components may be examples of parts used to perform various aspects of low-power wake-up signaling as described herein. For example, communication manager 920 may include configuration component 925, low-power signaling component 930, or any combination thereof. Communication manager 920 may be examples of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use receiver 910, transmitter 915, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or be integrated with receiver 910, transmitter 915, or a combination thereof to acquire information, output information, or perform various other operations as described herein.

[0181] Communication manager 920 may support wireless communication according to examples disclosed herein. Configuration component 925 is capable of, configured to, or operable to support components for: receiving first configuration information that defines a first schedule for the timing of receiving a low-power wake-up signal via a first radio component of device 905 associated with low-power operation. Configuration component 925 is capable of, configured to, or operable to support components for: receiving second configuration information that defines a periodic C-DRX period that includes a second schedule for monitoring the periodic on-time of the PDCCH via a second radio component of device 905, different from the first radio component of device 905. Low-power signal component 930 is capable of, configured to, or operable to support components for: receiving the low-power wake-up signal via the first radio component of device 905 according to the first configuration information and at least a threshold amount before the start of the next on-time period or the next PDCCH message.

[0182] Figure 10 A block diagram 1000 of a communication manager 1020 supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown. The communication manager 1020 may be an example of a communication manager 820, a communication manager 920, or aspects thereof as described herein. The communication manager 1020 or its various components may be examples of components for performing various aspects of low-power wake-up signaling as described herein. For example, the communication manager 1020 may include a configuration component 1025, a low-power signaling component 1030, a downlink component 1035, a reference signaling component 1040, a timer component 1045, a control component 1050, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0183] Communication manager 1020 may support wireless communication according to examples disclosed herein. Configuration component 1025 is capable of, configured to, or operable to support components for: receiving first configuration information that defines a first schedule for the timing of receiving a low-power wake-up signal via a first radio component of the wireless device associated with low-power operation. In some examples, configuration component 1025 is capable of, configured to, or operable to support components for: receiving second configuration information that defines a periodic C-DRX period that includes a second schedule for monitoring the periodic on-time of the PDCCH via a second radio component of the wireless device, different from the first radio component of the wireless device. Low-power signal component 1030 is capable of, configured to, or operable to support components for: receiving the low-power wake-up signal via the first radio component of the wireless device according to the first configuration information and at least a threshold amount before the start of the next on-time period or the next PDCCH message.

[0184] In some examples, downlink component 1035 is capable of, configured to, or able to operate to support components for: monitoring the PDCCH via the second radio component of the wireless device during the next activation period based on the receipt of the low-power wake-up signal via the first radio component of the wireless device and at least the threshold amount before the start of the next activation period or the next PDCCH message. In some examples, downlink component 1035 is capable of, configured to, or able to operate to support components for: receiving the next PDCCH message via the second radio component of the wireless device during the next activation period based on the monitoring.

[0185] In some examples, downlink component 1035 is capable of, configured to, or able to operate to support components for: monitoring the PDCCH via the second radio component of the wireless device after the next activation period, based on receiving the low-power wake-up signal via the first radio component of the wireless device within at least the threshold amount at the start of the next activation period. In some examples, downlink component 1035 is capable of, configured to, or able to operate to support components for: receiving the next PDCCH message via the second radio component of the wireless device during a subsequent activation period that occurs after the next activation period.

[0186] In some examples, the low-power wake-up signal includes at least one bit that indicates whether the PDCCH is monitored during the next power-on duration.

[0187] In some examples, downlink component 1035 is capable of, configured to, or operable to support components for: avoiding monitoring of the PDCCH via the second radio component of the wireless device during the next power-on duration based on at least one bit included in the received low-power wake-up signal. In some examples, downlink component 1035 is capable of, configured to, or operable to support components for: avoiding (e.g., suppressing, preventing, stopping, hindering, bypassing, skipping) monitoring of the PDCCH via the second radio component of the wireless device during the next power-on duration based on at least one bit included in the received low-power wake-up signal.

[0188] In some examples, downlink component 1035 is capable of, configured to, or able to operate to support components for monitoring the PDCCH via the second radio component of the wireless device during the next power-on duration, regardless of (e.g., regardless of, independent of) the at least one bit included in the received low-power wake-up signal.

[0189] In some examples, to support receiving a low-power wake-up signal, the low-power signal component 1030 is capable of, configured to, or operable to support components for receiving the low-power wake-up signal via the first radio component of the wireless device at least the threshold amount prior to the next onset duration. In some examples, to support receiving a low-power wake-up signal, the reference signal component 1040 is capable of, configured to, or operable to support components for receiving a TRS via the second radio component of the wireless device according to third configuration information and prior to the next onset duration.

[0190] In some examples, this third configuration information includes TRS configuration. In some examples, this third configuration information is indicated by the low-power wake-up signal.

[0191] In some examples, the reference signal component 1040 is capable of, configured to, or able to operate to support components for transmitting CSI reports via the second radio component of the wireless device during the next on-time period and regardless of (e.g., regardless of, independent of) the timer for C-DRX.

[0192] In some examples, to support receiving a low-power wake-up signal, the low-power signal component 1030 is capable of, configured to, or operable to support components for receiving the low-power wake-up signal via the first radio component of the wireless device prior to the next onset duration. In some examples, to support receiving a low-power wake-up signal, the downlink component 1035 is capable of, configured to, or operable to support components for monitoring the PDCCH via the second radio component of the wireless device for the next PDCCH message based on receiving the low-power wake-up signal via the first radio component of the wireless device and prior to the next PDCCH message.

[0193] In some examples, downlink component 1035 is capable of, configured to, or able to operate to support components for: terminating (e.g., stopping, aborting, ending, disconnecting, completing) monitoring the PDCCH for the next PDCCH message via the second radio component of the wireless device based on the expiration of one or more of the inactive timer for C-DRX, the start-up timer, or the expiration of one or more timers associated with the low-power wake-up signal.

[0194] In some examples, control component 1050 is capable of, configured to, or able to operate to support components for receiving control signaling from a network entity to terminate monitoring of the PDCCH, wherein the control signaling includes DCI.

[0195] In some examples, to support receiving a low-power wake-up signal, the low-power signal component 1030 is capable of, configured to, or able to operate to support components for receiving the low-power wake-up signal via the first radio component of the wireless device at least the threshold amount before the next PDCCH message during a time period in the first timetable of timing and during the current on-time period in the second timetable of periodic on-time. In some examples, to support receiving a low-power wake-up signal, the downlink component 1035 is capable of, configured to, or able to operate to support components for monitoring the PDCCH via the second radio component of the wireless device during the current on-time period and based on receiving the low-power wake-up signal at least the threshold amount before the next PDCCH message associated with the current on-time. In some examples, to support receiving a low-power wake-up signal, the downlink component 1035 is capable of, configured to, or able to operate to support components for receiving the next PDCCH message via the second radio component of the wireless device based on the monitoring during the current on-time period.

[0196] In some examples, the timer component 1045 is capable of, configured to, or able to operate to support components for enabling one or more of an inactive timer or an end-of-life timer for C-DRX based on the low-power wake-up signal received via the first radio component of the wireless device.

[0197] In some examples, the downlink component 1035 is capable of, configured to, or able to operate to support the monitoring of the PDCCH via the second radio component of the wireless device based on the expiration of one or more of the inactive timer or the start duration timer for C-DRX, during the current start duration (e.g., stop, abort, end, disconnect, complete).

[0198] In some examples, to support receiving a low-power wake-up signal, the low-power signal component 1030 is capable of, configured to, or operable to support components for receiving the low-power wake-up signal via the first radio component of the wireless device at least the threshold amount during a time period in the first timetable of timing and before the next PDCCH message during the current on-time period in the second timetable of periodic on-time. In some examples, to support receiving a low-power wake-up signal, the reference signal component 1040 is capable of, configured to, or operable to support components for receiving a TRS via the second radio component of the wireless device according to third configuration information and before monitoring the PDCCH for the next PDCCH message during the current on-time period.

[0199] In some examples, this third configuration information includes TRS configuration. In some examples, this third configuration information is indicated by the low-power wake-up signal.

[0200] In some examples, the low-power wake-up signal includes an OOK waveform.

[0201] Figure 11A diagram of a system 1100 including a device 1105 supporting low-power wake-up signaling, according to one or more aspects of this disclosure, is shown. Device 1105 may be an example of device 805, device 905, or UE 115 as described herein, or may include components thereof. Device 1105 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entity 105, UE 115, or a combination thereof). Device 1105 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1120, an input / output (I / O) controller (such as I / O controller 1110), transceivers 1115 (e.g., transceiver 1115-a, transceiver 1115-b), one or more antennas 1125 (one or more antennas 1125-a, one or more antennas 1125-b), at least one memory 1130, code 1135, and at least one processor 1140. These components may be electronically communicated or otherwise coupled via one or more buses (e.g., bus 1145).

[0202] I / O controller 1110 manages the input and output signals of device 1105. I / O controller 1110 can also manage peripheral devices not integrated into device 1105. In some cases, I / O controller 1110 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1110 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Or another known operating system. Additionally or alternatively, the I / O controller 1110 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1110 may be implemented as part of one or more processors, such as at least one processor 1140. In some cases, a user may interact with the device 1105 via the I / O controller 1110 or via hardware components controlled by the I / O controller 1110.

[0203] In some cases, device 1105 may include a single antenna. However, in other cases, device 1105 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1115 may communicate bidirectionally via one or more antennas 1125 using wired or wireless links as described herein. For example, transceiver 1115 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1115 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1125 for transmission; and demodulating packets received from one or more antennas 1125. Transceiver 1115, or transceiver 1115 and one or more antennas 1125, may be an example of transmitter 815, transmitter 915, receiver 810, receiver 910, or any combination thereof or components thereof as described herein. As described herein, device 1105 may be configured with low-power radio components (such as transceiver 1115-a and antenna 1125-a) and main radio components (such as transceiver 1115-b and antenna 1125-b) to support the various operations described herein.

[0204] At least one memory 1130 may include random access memory (RAM) and read-only memory (ROM). At least one memory 1130 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1135. Code 1135 may include instructions that, when executed by at least one processor 1140, cause device 1105 to perform the various functions described herein. Code 1135 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1135 may not be directly executable by at least one processor 1140, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1130 may include a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0205] At least one processor 1140 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 1140 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into at least one processor 1140. At least one processor 1140 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 1130) to cause device 1105 to perform various functions (e.g., functions or tasks that support low-power wake-up signaling). For example, device 1105 or components of device 1105 may include at least one processor 1140 and at least one memory 1130 coupled to or coupled to at least one processor 1140, wherein at least one processor 1140 and at least one memory 1130 are configured to perform the various functions described herein.

[0206] In some examples, at least one processor 1140 may include multiple processors, and at least one memory 1130 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1140 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1140) and memory circuitry (which may include at least one memory 1130)) or components that receive or receive input and process the input to produce, generate, or obtain output. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1140 or a processing system including at least one processor 1140 may be configured, configured to, or operable to cause device 1105 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code 1135 (e.g., processor-executable code) stored in at least one memory 1130 or otherwise.

[0207] Communication manager 1120 may support wireless communication according to examples disclosed herein. For example, communication manager 1120 may be, configured to, or operable to support components for: receiving first configuration information that defines a first schedule for the timing of receiving a low-power wake-up signal via a first radio component of device 1105 associated with low-power operation. For example, communication manager 1120 may be, configured to, or operable to support components for: receiving second configuration information that defines a periodic C-DRX period that includes a second schedule for monitoring the periodic on-time of the PDCCH via a second radio component of device 1105, different from the first radio component of device 1105. For example, communication manager 1120 may be, configured to, or operable to support components for: receiving the low-power wake-up signal via the first radio component of device 1105 according to the first configuration information and at least a threshold amount before the start of the next on-time period or the next PDCCH message.

[0208] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 can support technologies for longer battery life.

[0209] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 1115, one or more antennas 1125, or any combination thereof, or otherwise cooperating with them. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported by or executed by at least one processor 1140, at least one memory 1130, code 1135, or any combination thereof. For example, code 1135 may include instructions that can be executed by at least one processor 1140 to cause the device 1105 to perform various aspects of low-power wake-up signaling as described herein, or at least one processor 1140 and at least one memory 1130 may be otherwise configured to perform or support such operations individually or jointly.

[0210] Figure 12A block diagram 1200 of a device 1205 supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown. Device 1205 may be an example of aspects of network entity 105 as described herein. Device 1205 may include receiver 1210, transmitter 1215, and communication manager 1220. Device 1205 or one or more components of device 1205 (e.g., receiver 1210, transmitter 1215, communication manager 1220) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0211] Receiver 1210 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1205. In some examples, receiver 1210 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1210 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0212] Transmitter 1215 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1205. For example, transmitter 1215 may 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, transmitter 1215 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1215 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1215 and receiver 1210 may be co-located in a transceiver, which may include or be coupled to a modem.

[0213] The communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be examples of components used to perform various aspects of the low-power wake-up signaling as described herein. For example, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0214] In some examples, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0215] Additionally or alternatively, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be implemented in code (e.g., referred to as processor executable code) executed by at least one processor (e.g., implemented as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0216] In some examples, the communication manager 1220 may be configured to use the receiver 1210, the transmitter 1215, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1220 may receive information from the receiver 1210, transmit information to the transmitter 1215, or be integrated with the receiver 1210, the transmitter 1215, or a combination of both to acquire information, output information, or perform various other operations as described herein.

[0217] Communication manager 1220 may support wireless communication according to examples disclosed herein. For example, communication manager 1220 may be, configured to, or operable to support components for: transmitting first configuration information defining a first schedule for the timing of receiving a low-power wake-up signal via a first radio component of the wireless device associated with low-power operation; communication manager 1220 may be, configured to, or operable to support components for: transmitting second configuration information defining a periodic C-DRX period including a second schedule for monitoring the periodic on-time of the PDCCH via a second radio component of the wireless device, different from the first radio component of the wireless device; and communication manager 1220 may be, configured to, or operable to support components for: transmitting the low-power wake-up signal via the first radio component of the wireless device according to the first configuration information and at least a threshold amount before the start of the next on-time period or the next PDCCH message.

[0218] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 (e.g., controlling receiver 1210, transmitter 1215, communication manager 1220, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for more efficient use of communication resources.

[0219] Figure 13 A block diagram 1300 of a device 1305 supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown. Device 1305 may be an example of aspects of device 1205 or network entity 105 as described herein. Device 1305 may include receiver 1310, transmitter 1315, and communication manager 1320. Device 1305 or one or more components of device 1305 (e.g., receiver 1310, transmitter 1315, communication manager 1320) 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).

[0220] Receiver 1310 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1305. In some examples, receiver 1310 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1310 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0221] Transmitter 1315 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1305. For example, transmitter 1315 may 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, transmitter 1315 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1315 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1315 and receiver 1310 may be co-located in a transceiver, which may include or be coupled to a modem.

[0222] Device 1305 or its various components may be examples of parts for performing various aspects of low-power wake-up signaling as described herein. For example, communication manager 1320 may include configuration component 1325, low-power signaling component 1330, or any combination thereof. Communication manager 1320 may be examples of aspects of communication manager 1220 as described herein. In some examples, communication manager 1320 or its various components may be configured to use receiver 1310, transmitter 1315, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1320 may receive information from receiver 1310, transmit information to transmitter 1315, or be integrated with receiver 1310, transmitter 1315, or a combination thereof to acquire information, output information, or perform various other operations as described herein.

[0223] Communication manager 1320 may support wireless communication according to examples disclosed herein. Configuration component 1325 is capable of, configured to, or operable to support components for: transmitting first configuration information defining a first schedule for the timing of receiving a low-power wake-up signal via a first radio component of the wireless device associated with low-power operation. Configuration component 1325 is capable of, configured to, or operable to support components for: transmitting second configuration information defining a periodic C-DRX period that includes a second schedule for monitoring the periodic on-time of the PDCCH via a second radio component of the wireless device, different from the first radio component of the wireless device. Low-power signal component 1330 is capable of, configured to, or operable to support components for: transmitting the low-power wake-up signal via the first radio component of the wireless device according to the first configuration information and at least a threshold amount before the start of the next on-time period or the next PDCCH message.

[0224] Figure 14 A block diagram 1400 of a communication manager 1420 supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown. The communication manager 1420 may be an example of aspects of the communication manager 1220, communication manager 1320, or both as described herein. The communication manager 1420 or its various components may be examples of components for performing various aspects of the low-power wake-up signaling as described herein. For example, the communication manager 1420 may include a configuration component 1425, a low-power signaling component 1430, a downlink component 1435, a reference signaling component 1440, a control component 1445, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses). This communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of the protocol stack, within a device, component, or virtualization component associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0225] Communication manager 1420 may support wireless communication according to examples disclosed herein. Configuration component 1425 is capable of, configured to, or operable to support components for: transmitting first configuration information defining a first schedule for the timing of receiving a low-power wake-up signal via a first radio component of the wireless device associated with low-power operation. In some examples, configuration component 1425 is capable of, configured to, or operable to support components for: transmitting second configuration information defining a periodic C-DRX period that includes a second schedule for monitoring the periodic on-time of the PDCCH via a second radio component of the wireless device, different from the first radio component of the wireless device. Low-power signal component 1430 is capable of, configured to, or operable to support components for: transmitting the low-power wake-up signal via the first radio component of the wireless device according to the first configuration information and at least a threshold amount before the start of the next on-time or the next PDCCH message.

[0226] In some examples, downlink component 1435 is capable of, configured to, or able to operate to support components for sending the next PDCCH message during the next open duration.

[0227] In some examples, downlink component 1435 is capable of, configured to, or able to operate to support components for sending the next PDCCH message during a subsequent open period that occurs after the next open period.

[0228] In some examples, the low-power wake-up signal includes at least one bit that indicates whether the PDCCH is monitored during the next power-on duration.

[0229] In some examples, in order to support the transmission of a low-power wake-up signal, the reference signal component 1440 can be configured or operated to support components for transmitting a TRS according to third configuration information and before the next activation duration.

[0230] In some examples, this third configuration information includes TRS configuration. In some examples, this third configuration information is indicated by the low-power wake-up signal.

[0231] In some examples, the reference signal component 1440 is capable of, configured to, or able to operate to support components for receiving CSI reports during the next on-time period, regardless of (e.g., regardless of, independent of) the timer used for C-DRX.

[0232] In some examples, control component 1445 is capable of, configured to, or able to operate to support components for sending control signaling to terminate monitoring of the PDCCH, wherein the control signaling includes DCI.

[0233] In some examples, the low-power wake-up signal includes an OOK waveform.

[0234] Figure 15 A diagram of a system 1500 including a device 1505 supporting low-power wake-up signaling, according to one or more aspects of this disclosure, is shown. Device 1505 may be an example of device 1205, device 1305, or network entity 105 as described herein, or may include components thereof. Device 1505 may communicate with other network devices or network equipment, such as network entity 105, UE 115, or any combination thereof. Communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1505 may include components supporting output and acquisition of communication, such as a communication manager 1520, a transceiver 1510, one or more antennas 1515, at least one memory 1525, code 1530, and at least one processor 1535. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1540).

[0235] Transceiver 1510 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1510 may include a wired transceiver and be able to communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1510 may include a wireless transceiver and be able to communicate bidirectionally with another wireless transceiver. In some examples, device 1505 may include one or more antennas 1515 that may be able to transmit or receive wireless transmissions (e.g., concurrently). Transceiver 1510 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1515, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1515, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1510 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1515 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1515 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1510 may include one or more processors or one or more memory components or configured to be coupled to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1510, or transceiver 1510 and one or more antennas 1515, or transceiver 1510 and one or more antennas 1515 and one or more processors or one or more memory components (e.g., at least one processor 1535, at least one memory 1525, or both) may be included in a chip or chip assembly mounted in device 1505. In some examples, transceiver 1510 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0236] At least one memory 1525 may include RAM, ROM, or any combination thereof. At least one memory 1525 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1530. Code 1530 may include instructions that, when executed by one or more of the at least one processor 1535, cause device 1505 to perform the various functions described herein. Code 1530 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1530 may not be directly executable by one of the at least one processor 1535, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1525 may include a BIOS, etc., which controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1535 may include multiple processors, and at least one memory 1525 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0237] At least one processor 1535 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 1535 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1535. At least one processor 1535 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1525) to cause device 1505 to perform various functions (e.g., functions or tasks that support low-power wake-up signaling). For example, device 1505 or components thereof may include at least one processor 1535 and at least one memory 1525 coupled to one or more processors in the at least one processor 1535, the at least one processor 1535 and the at least one memory 1525 being configured to perform the various functions described herein. The at least one processor 1535 may 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 functions (e.g., by executing code 1530) to perform the functions of device 1505. The at least one processor 1535 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1505 (such as within one or more memories of the at least one memory 1525).

[0238] In some examples, at least one processor 1535 may include multiple processors, and at least one memory 1525 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1535 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1535) and memory circuitry (which may include at least one memory 1525)) or components that receive or receive input and process the input to produce, generate, or obtain output. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1535 or a processing system including at least one processor 1535 may be configured, configured to, or operable to cause device 1505 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1525 or otherwise.

[0239] In some examples, bus 1540 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1540 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1505, or communication performed between different components of device 1505 that are co-addressable or may be located in different locations (e.g., where device 1505 may refer to a system in which one or more of communication manager 1520, transceiver 1510, at least one memory 1525, code 1530 and at least one processor 1535 may be located in one component of different components or partitioned between different components).

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

[0241] Communication manager 1520 may support wireless communication according to examples disclosed herein. For example, communication manager 1520 may be, configured to, or operable to support components for: transmitting first configuration information defining a first schedule for the timing of receiving a low-power wake-up signal via a first radio component of the wireless device associated with low-power operation; communication manager 1520 may be, configured to, or operable to support components for: transmitting second configuration information defining a periodic C-DRX period including a second schedule for monitoring the periodic on-time of the PDCCH via a second radio component of the wireless device, different from the first radio component of the wireless device; and communication manager 1520 may be, configured to, or operable to support components for: transmitting the low-power wake-up signal via the first radio component of the wireless device according to the first configuration information and at least a threshold amount before the start of the next on-time period or the next PDCCH message.

[0242] By including or configuring a communication manager 1520 according to an example as described herein, device 1505 can support technologies for improving and reducing processing-related user experiences, utilizing communication resources more efficiently, and improving coordination benefits between devices.

[0243] In some examples, the communication manager 1520 may be configured to use or cooperate with transceiver 1510, one or more antennas 1515 (e.g., where applicable), or any combination thereof, to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1520 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1520 may be supported or performed by transceiver 1510, one or more processors in at least one processor 1535, one or more memories in at least one memory 1525, code 1530, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1535, at least one memory 1525, code 1530, or any combination thereof). For example, code 1530 may include instructions that can be executed by one or more processors in at least one processor 1535 to cause device 1505 to perform various aspects of low-power wake-up signaling as described herein, or at least one processor 1535 and at least one memory 1525 may be otherwise configured to perform or support such operations individually or jointly.

[0244] Figure 16A flowchart illustrating a method 1600 supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown. Operation of method 1600 may be implemented by a UE or its components as described herein. For example, operation of method 1600 may be performed by, as referenced... Figures 1 to 11 The UE 115 described herein performs the following: In some examples, the 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 may use dedicated hardware to perform aspects of the described functions.

[0245] At 1605, the method may include: receiving first configuration information that defines a first timetable for the timing of receiving a low-power wake-up signal via a first radio component of the wireless device associated with low-power operation. Operation of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1605 may be provided by reference to... Figure 10 The described configuration component 1025 is executed.

[0246] At 1610, the method may include: receiving second configuration information defining a periodic C-DRX period, the periodic C-DRX period including a second timetable for monitoring the periodic on-time of the PDCCH via a second radio component different from the first radio component of the wireless device. Operation of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1610 may be provided by reference to... Figure 10 The described configuration component 1025 is executed.

[0247] At 1615, the method may include: receiving the low-power wake-up signal via the first radio component of the wireless device, based on the first configuration information and at least a threshold amount before the start of the next activation duration or the next PDCCH message. Operation of 1615 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1615 may be as described in references... Figure 10 The low-power signal component 1030 described herein is used to perform this action.

[0248] Figure 17 A flowchart illustrating a method 1700 supporting low-power wake-up signaling according to one or more aspects of this disclosure is shown. Operation of method 1700 may be implemented by a network entity or its components as described herein. For example, operation of method 1700 may be implemented by, as referenced... Figures 1 to 7 as well as Figures 12 to 15 The described network entity performs the functions. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0249] At 1705, the method may include: sending first configuration information that defines a first schedule for the timing of receiving a low-power wake-up signal via a first radio component of the wireless device associated with low-power operation. Operation of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1705 may be provided by reference to... Figure 14 The described configuration component 1425 is executed.

[0250] At 1710, the method may include: sending second configuration information defining a periodic C-DRX period, the periodic C-DRX period including a second timetable for monitoring the periodic on-time of the PDCCH via a second radio component different from the first radio component of the wireless device. Operation of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1710 may be provided by reference to... Figure 14 The described configuration component 1425 is executed.

[0251] At 1715, the method may include: transmitting the low-power wake-up signal via the first radio component of the wireless device according to the first configuration information and at least a threshold amount before the start of the next activation duration or the next PDCCH message. Operation of 1715 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1715 may be as described in references... Figure 14 The low-power signal component 1430 described herein is used to perform this action.

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

[0253] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication at a wireless device, the method comprising: receiving first configuration information, the first configuration information defining a first timetable for timing of receiving a low-power wake-up signal via a first radio component of the wireless device associated with low-power operation; receiving second configuration information, the second configuration information defining a periodic C-DRX period, the periodic C-DRX period including a second timetable for monitoring a periodic on-time of a PDCCH via a second radio component of the wireless device, different from the first radio component of the wireless device; and receiving the low-power wake-up signal via the first radio component of the wireless device according to the first configuration information and at least a threshold amount before the start of the next on-time or before the next PDCCH message.

[0254] Aspect 2: According to the method of aspect 1, the method further includes: monitoring the PDCCH via the second radio component of the wireless device during the next power-on duration based at least in part on receiving the low-power wake-up signal via the first radio component of the wireless device and at least the threshold amount before the start of the next power-on duration or the next PDCCH message; and receiving the next PDCCH message via the second radio component of the wireless device during the next power-on duration based at least in part on the monitoring.

[0255] Aspect 3: The method according to any one of Aspects 1 to 2, the method further comprising: receiving the low-power wake-up signal via the first radio component of the wireless device at least in part based on at least the threshold amount at the start of the next power-on duration; monitoring the PDCCH via the second radio component of the wireless device after the next power-on duration; and receiving the next PDCCH message via the second radio component of the wireless device during a subsequent power-on duration that occurs after the next power-on duration.

[0256] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the low-power wake-up signal includes at least one bit indicating whether the PDCCH is monitored during the next power-on duration.

[0257] Aspect 5: The method according to aspect 4, the method further comprising: monitoring the PDCCH via the second radio component of the wireless device during the next power-on duration based at least in part on the at least one bit included in the received low-power wake-up signal; or avoiding monitoring the PDCCH via the second radio component of the wireless device during the next power-on duration based at least in part on the at least one bit included in the received low-power wake-up signal.

[0258] Aspect 6: The method according to aspect 5, the method further comprising: monitoring the PDCCH via the second radio component of the wireless device during the next power-on duration, at least in part based on the at least one bit included in the received low-power wake-up signal.

[0259] Aspect 7: The method according to aspect 6, the method further comprising: at least in part based on the at least one bit included in the received low-power wake-up signal, avoiding monitoring of the PDCCH via the second radio component of the wireless device during the next power-on duration.

[0260] Aspect 8: The method according to any one of Aspects 4 to 5, the method further comprising: monitoring the PDCCH via the second radio component of the wireless device during the next power-on duration, regardless of at least one bit included in the received low-power wake-up signal.

[0261] Aspect 9: The method according to any one of Aspects 1 to 8, wherein receiving the low-power wake-up signal comprises: receiving the low-power wake-up signal via the first radio component of the wireless device at least the threshold amount before the next power-on duration, the method further comprising: receiving a TRS via the second radio component of the wireless device according to third configuration information and before the next power-on duration.

[0262] Aspect 10: According to the method of aspect 9, wherein the third configuration information includes TRS configuration and the third configuration information is indicated by the low-power wake-up signal.

[0263] Aspect 11: The method according to any one of Aspects 1 to 10, the method further comprising: during the next activation duration and regardless of the timer used for C-DRX, transmitting a CSI report via the second radio component of the wireless device.

[0264] Aspect 12: The method according to any one of Aspects 1 to 11, wherein receiving the low-power wake-up signal comprises: receiving the low-power wake-up signal via the first radio component of the wireless device before the next on-time, the method further comprising: monitoring the PDCCH via the second radio component of the wireless device for the next PDCCH message based at least in part on receiving the low-power wake-up signal via the first radio component of the wireless device and before the next PDCCH message.

[0265] Aspect 13: The method according to aspect 12, the method further comprising: terminating monitoring of the PDCCH via the second radio component of the wireless device for the next PDCCH message based at least in part on the expiration of one or more of an inactive timer for C-DRX, an enable duration timer, or the expiration of one or more timers associated with the low-power wake-up signal.

[0266] Aspect 14: The method according to aspect 13 further includes: receiving control signaling from a network entity for terminating monitoring of the PDCCH, wherein the control signaling includes DCI.

[0267] Aspect 15: The method according to any one of Aspects 1 to 14, wherein receiving the low-power wake-up signal comprises: receiving the low-power wake-up signal via a first radio component of the wireless device at least the threshold amount during a time period in a first time period of timing and during the current power-on duration in a second time period of periodic power-on duration, prior to the next PDCCH message, the method further comprising: monitoring the PDCCH via a second radio component of the wireless device during the current power-on duration and at least in part based on receiving the low-power wake-up signal at least the threshold amount prior to the next PDCCH message associated with the current power-on duration; and receiving the next PDCCH message via a second radio component of the wireless device during the current power-on duration, at least in part based on the monitoring.

[0268] Aspect 16: The method according to any one of Aspects 1 to 14, wherein receiving the low-power wake-up signal comprises: receiving the low-power wake-up signal via the first radio component of the wireless device at least the threshold amount during a time period in the first time schedule of timing and during the current time period in the second time schedule of periodic on-time, prior to the next PDCCH message.

[0269] Aspect 17: The method according to aspect 16, the method further comprising: monitoring the PDCCH via the second radio component of the wireless device during the current power-on duration and based at least in part on receiving the low-power wake-up signal based on at least the threshold amount prior to the next PDCCH message associated with the current power-on duration.

[0270] Aspect 18: The method according to aspect 17, the method further comprising: receiving the next PDCCH message via the second radio component of the wireless device during the current on duration, at least in part based on the monitoring.

[0271] Aspect 19: The method according to aspect 15, the method further comprising: enabling one or more of an inactive timer for C-DRX or an open duration timer based at least in part on receiving the low-power wake-up signal via the first radio component of the wireless device.

[0272] Aspect 20: The method according to aspect 19, the method further comprising: terminating monitoring of the PDCCH via the second radio component of the wireless device during the current enable duration, at least in part based on the expiration of one or more of an inactive timer or an enable duration timer for C-DRX.

[0273] Aspect 21: The method according to any one of Aspects 1 to 20, wherein receiving the low-power wake-up signal comprises: receiving the low-power wake-up signal via the first radio component of the wireless device at least the threshold amount during a time period in the first time schedule of timing and during the current time period in the second time schedule of periodic on-duration, before the next PDCCH message, the method further comprising: receiving a TRS via the second radio component of the wireless device according to third configuration information and before monitoring the PDCCH for the next PDCCH message during the current time period.

[0274] Aspect 22: According to the method of aspect 21, wherein the third configuration information includes a TRS configuration and the third configuration information is indicated by the low-power wake-up signal.

[0275] Aspect 23: The method according to any one of Aspects 1 to 22, wherein the low-power wake-up signal comprises an on / off keying (OOK) waveform.

[0276] Aspect 24: A method for wireless communication at a network entity, the method comprising: transmitting first configuration information defining a first timetable for timing of receiving a low-power wake-up signal via a first radio component of a wireless device associated with low-power operation; transmitting second configuration information defining a periodic C-DRX period, the periodic C-DRX period including a second timetable for monitoring a periodic on-time of a PDCCH via a second radio component of the wireless device, different from the first radio component of the wireless device; and transmitting the low-power wake-up signal via the first radio component of the wireless device according to the first configuration information and at least a threshold amount before the start of the next on-time or before the next PDCCH message.

[0277] Aspect 25: According to the method of aspect 24, the method further includes: sending the next PDCCH message during the next start duration.

[0278] Aspect 26: The method according to any one of Aspects 24 to 25, the method further comprising: sending the next PDCCH message during a subsequent activation period that occurs after the next activation period.

[0279] Aspect 27: The method according to any one of Aspects 24 to 26, wherein the low-power wake-up signal includes at least one bit indicating whether the PDCCH is monitored during the next power-on duration.

[0280] Aspect 28: The method according to any one of Aspects 24 to 27, wherein sending the low-power wake-up signal comprises: sending a TRS according to third configuration information and before the next activation duration.

[0281] Aspect 29: According to the method of aspect 28, wherein the third configuration information includes a TRS configuration and the third configuration information is indicated by the low-power wake-up signal.

[0282] Aspect 30: The method according to any one of Aspects 24 to 29, the method further comprising: receiving a CSI report during the next start duration and regardless of the timer used for C-DRX.

[0283] Aspect 31: The method according to any one of Aspects 24 to 30, the method further comprising: sending control signaling for terminating monitoring of the PDCCH, wherein the control signaling includes DCI.

[0284] Aspect 32: The method according to any one of Aspects 24 to 31, wherein the low-power wake-up signal comprises an on / off keying (OOK) waveform.

[0285] Aspect 33: A wireless device for wireless communication, the wireless device comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the wireless device to perform a method according to any one of aspects 1 to 23.

[0286] Aspect 34: A wireless device for wireless communication, the wireless device comprising at least one component for performing the method according to any one of aspects 1 to 23.

[0287] Aspect 35: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 23.

[0288] Aspect 36: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of Aspects 24 to 32.

[0289] Aspect 37: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 24 to 32.

[0290] Aspect 38: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform a method according to any one of aspects 24 to 32.

[0291] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0292] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0293] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, graphics processing unit (GPU), neural processing unit (NPU), FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described function or operation individually or jointly.

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

[0295] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0296] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, 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). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0297] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components,” and subsequent reference to “the component” in a claim may be understood to be equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” may refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0298] The term "determine" encompasses a wide range of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), ascertainment, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.

[0299] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numerals and a second reference numeral to differentiate between similar components. If only the first reference numeral is used in the description, the description applies to any of the similar components having the same first reference numeral, regardless of (e.g., regardless of, independent of) the second reference numeral or other subsequent reference numerals.

[0300] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some of the drawings, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0301] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories and configured to cause the UE to: Receive first configuration information, the first configuration information defining a first timetable for the timing of receiving a low-power wake-up signal via a first radio component associated with low-power operation of the wireless device; Receive second configuration information, the second configuration information defining a periodic connection mode discontinuous reception period, the periodic connection mode discontinuous reception period including a second timetable for monitoring the periodic on-time of the physical downlink control channel via a second radio component different from the first radio component of the wireless device. as well as The low-power wake-up signal is received via the first radio component of the wireless device based on the first configuration information and at least a threshold amount before the start of the next activation duration or the next physical downlink control channel message.

2. The apparatus of claim 1, wherein the one or more processors are configured to cause the UE to: Based at least in part on receiving the low-power wake-up signal via the first radio component of the wireless device and at least the threshold amount before the start of the next activation duration or the next physical downlink control channel message, the physical downlink control channel is monitored via the second radio component of the wireless device during the next activation duration; and Based at least in part on the monitoring, the next physical downlink control channel message is received via the second radio component of the wireless device during the next activation duration.

3. The apparatus of claim 1, wherein the one or more processors are configured to cause the UE to: Based at least in part on receiving the low-power wake-up signal via the first radio component of the wireless device within at least the threshold amount at the start of the next activation duration, and monitoring the physical downlink control channel via the second radio component of the wireless device after the next activation duration; and The next physical downlink control channel message is received via the second radio component of the wireless device during a subsequent activation period that occurs after the next activation period.

4. The apparatus of claim 1, wherein the low-power wake-up signal includes at least one bit indicating whether the physical downlink control channel is monitored during the next power-on duration.

5. The apparatus of claim 4, wherein the one or more processors are configured to cause the UE to: The physical downlink control channel is monitored via the second radio component of the wireless device during the next power-on duration, based at least in part on at least one bit included in the received low-power wake-up signal; or Based at least in part on the at least one bit included in the received low-power wake-up signal, the monitoring of the physical downlink control channel via the second radio component of the wireless device is avoided during the next power-on duration.

6. The apparatus of claim 4, wherein the one or more processors are configured to cause the UE to: Regardless of at least one bit included in the received low-power wake-up signal, the physical downlink control channel is monitored via the second radio component of the wireless device during the next power-on duration.

7. The apparatus of claim 1, wherein the one or more processors are configured to cause the UE to: During the next activation duration and regardless of the timer used for discontinuous reception in connection mode, a channel state information report is transmitted via the second radio component of the wireless device.

8. The apparatus according to claim 1, wherein, In order to receive the low-power wake-up signal, the one or more processors are configured to cause the UE to: Prior to the next activation duration, the low-power wake-up signal is received via the first radio component of the wireless device, wherein one or more processors are configured to cause the wireless device to: The physical downlink control channel is monitored via the second radio component of the wireless device for the next physical downlink control channel message, at least in part based on receiving the low-power wake-up signal via the first radio component of the wireless device and prior to the next physical downlink control channel message.

9. The apparatus of claim 8, wherein the one or more processors are configured to cause the UE to: The monitoring of the physical downlink control channel via the second radio component of the wireless device is terminated at least in part based on the expiration of one or more of the inactive timer for connected-mode discontinuous reception, the start-up duration timer, or the expiration of one or more timers associated with the low-power wake-up signal.

10. The apparatus according to claim 1, wherein, In order to receive the low-power wake-up signal, the one or more processors are configured to cause the UE to: During a timing period in the first timetable and during the current on-time period in the second timetable with periodic on-time duration, at least the threshold amount is received via the first radio component of the wireless device before the next physical downlink control channel message, wherein the one or more processors are configured to cause the wireless device to: The physical downlink control channel is monitored via the second radio component of the wireless device during the current activation duration and at least in part based on receiving the low-power wake-up signal at least the threshold amount before the next physical downlink control channel message associated with the current activation duration; as well as Based at least in part on the monitoring, the next physical downlink control channel message is received via the second radio component of the wireless device during the current activation duration.

11. The apparatus of claim 10, wherein the one or more processors are configured to cause the UE to: At least in part, based on the receipt of the low-power wake-up signal via the first radio component of the wireless device, one or more of an inactive timer or an open duration timer for connected-mode discontinuous reception are enabled.

12. The apparatus of claim 11, wherein the one or more processors are configured to cause the UE to: Monitoring of the physical downlink control channel via the second radio component of the wireless device is terminated during the current open duration, based at least in part on the expiration of one or more of the inactive timer or the open duration timer used for discontinuous reception in connection mode.

13. An apparatus for wireless communication at a network entity, the apparatus comprising: One or more memory units; and One or more processors, said one or more processors being coupled to said one or more memories and configured to cause the network entity to: Send first configuration information, the first configuration information defining a first timetable for the timing of receiving a low-power wake-up signal; Send second configuration information, the second configuration information defining the discontinuous reception period of the periodic connection mode, the discontinuous reception period of the periodic connection mode including a second timetable for monitoring the periodic on duration of the physical downlink control channel; as well as The low-power wake-up signal is sent according to the first configuration information and at least a threshold amount before the start of one of the periodic activation periods or before the next physical downlink control channel message.

14. The apparatus of claim 13, wherein the one or more processors are configured to cause the network entity to: The next physical downlink control channel message is sent during the next activation duration.

15. The apparatus of claim 13, wherein the one or more processors are configured to cause the network entity to: The next physical downlink control channel message is transmitted during a subsequent activation period following one of the periodic activation periods that occurs within the periodic activation period.

16. The apparatus of claim 13, wherein the low-power wake-up signal includes at least one bit indicating whether the physical downlink control channel is monitored during one of the periodic on-times.

17. The apparatus of claim 13, wherein the one or more processors are configured to cause the network entity to: During one of the periodic on-time periods, regardless of the timer used for discontinuous reception in connection mode, a channel state information report is received.

18. A method for conducting wireless communication at a wireless device, the method comprising: Receive first configuration information, the first configuration information defining a first timetable for the timing of receiving a low-power wake-up signal via a first radio component associated with low-power operation of the wireless device; Receive second configuration information, the second configuration information defining a periodic connection mode discontinuous reception period, the periodic connection mode discontinuous reception period including a second timetable for monitoring the periodic on-time of the physical downlink control channel via a second radio component different from the first radio component of the wireless device. as well as The low-power wake-up signal is received via the first radio component of the wireless device based on the first configuration information and at least a threshold amount before the start of the next activation duration or the next physical downlink control channel message.

19. The method according to claim 18, further comprising: The physical downlink control channel is monitored via the second radio component of the wireless device during the next activation period, based at least in part on the receipt of the low-power wake-up signal via the first radio component of the wireless device and at least the threshold amount before the start of the next activation period or the next physical downlink control channel message; as well as Based at least in part on the monitoring, the next physical downlink control channel message is received via the second radio component of the wireless device during the next activation duration.

20. The method according to claim 18, further comprising: The physical downlink control channel is monitored via the second radio component of the wireless device after the next activation period, based at least in part on receiving the low-power wake-up signal via the first radio component of the wireless device within at least the threshold amount at the start of the next activation period. as well as The next physical downlink control channel message is received via the second radio component of the wireless device during a subsequent activation period that occurs after the next activation period.

Images