Discontinuous reception configuration for wake-up signal monitoring

Abstract

Methods, systems, and apparatus for wireless communication are described. A user equipment (UE) may, for example, receive control signaling from a network entity indicating multiple discontinuous reception (DRX) configurations for the UE, wherein the multiple DRX configurations include a first DRX configuration associated with a first set of wake-up signal monitoring opportunities and a second DRX configuration associated with a second set of wake-up signal monitoring opportunities. Both the first and second DRX configurations may be active during a time period. During this time period, the UE may monitor the first set of wake-up signal monitoring opportunities according to the first DRX configuration and the second set of wake-up signal monitoring opportunities according to the second DRX configuration.

Description

[0001] Cross-referencing

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 394,631, filed December 22, 2023, entitled “DISCONTINUOUSRECEPTION CONFIGURATIONS FOR WAKE-UP SIGNAL MONITORING”, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following discussion relates to wireless communication, including discontinuous reception configurations for wake-up signal monitoring. Background Technology

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

[0005] The UE can monitor messages, such as those from network entities, at varying intervals or periods. In some examples, the period may include wake-up periods and idle periods. Such periods can be configured by the network. Summary of the Invention

[0006] The described technology relates to improved methods, systems, devices, and apparatuses for supporting discontinuous reception (DRX) configurations for wake-up signal (WUS) monitoring. For example, the described technology provides a user equipment (UE) that receives control signaling from a network entity indicating multiple DRX configurations for the UE. The multiple DRX configurations may include a first DRX configuration associated with a first set of WUS monitoring opportunities and a second DRX configuration associated with a second set of WUS monitoring opportunities, wherein both the first and second DRX configurations are active during a time period. The UE may monitor the first set of WUS monitoring opportunities according to the first DRX configuration and the second set of WUS monitoring opportunities according to the second DRX configuration during this time period. In some examples, the first set of WUS monitoring opportunities associated with the first DRX configuration has a first periodicity, and the second set of WUS monitoring opportunities associated with the second DRX configuration has a second periodicity, wherein the second periodicity differs from the first periodicity.

[0007] A method for wireless communication by a UE is described. The method may include: receiving control signaling indicating a plurality of DRX configurations for the UE, wherein the plurality of DRX configurations include a first DRX configuration associated with a first set of WUS monitoring opportunities and a second DRX configuration associated with a second set of WUS monitoring opportunities, and wherein both the first DRX configuration and the second DRX configuration are active during a time period; during the time period, monitoring the first set of WUS monitoring opportunities according to the first DRX configuration; and during the time period, monitoring the second set of WUS monitoring opportunities according to the first DRX configuration.

[0008] A UE for wireless communication is described. The UE 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 individually or jointly operable to execute the code to cause the UE to: receive control signaling instructing a plurality of DRX configurations for the UE, wherein the plurality of DRX configurations include a first DRX configuration associated with a first set of WUS monitoring times and a second DRX configuration associated with a second set of WUS monitoring times, and wherein the first DRX configuration and the second DRX configuration are both active during a time period; during the time period, monitor the first set of WUS monitoring times according to the first DRX configuration; and during the time period, monitor the second set of WUS monitoring times according to the first DRX configuration.

[0009] Another UE for wireless communication is described. The UE may include: components for receiving control signaling indicating a plurality of DRX configurations for the UE, wherein the plurality of DRX configurations include a first DRX configuration associated with a first set of WUS monitoring opportunities and a second DRX configuration associated with a second set of WUS monitoring opportunities, and wherein both the first DRX configuration and the second DRX configuration are active during a time period; components for monitoring the first set of WUS monitoring opportunities according to the first DRX configuration during the time period; and components for monitoring the second set of WUS monitoring opportunities according to the first DRX configuration during the time period.

[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 control signaling indicating a plurality of DRX configurations for the UE, wherein the plurality of DRX configurations include a first DRX configuration associated with a first set of WUS monitoring opportunities and a second DRX configuration associated with a second set of WUS monitoring opportunities, and wherein both the first DRX configuration and the second DRX configuration are active during a time period; during the time period, monitoring the first set of WUS monitoring opportunities according to the first DRX configuration; and during the time period, monitoring the second set of WUS monitoring opportunities according to the first DRX configuration.

[0011] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first set of WUS monitoring opportunities associated with the first DRX configuration may have a first periodicity, and the second set of WUS monitoring opportunities associated with the second DRX configuration may have a second periodicity, which is different from the first periodicity.

[0012] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the timeline for the first set of WUS monitoring opportunities associated with the first DRX configuration may be based on a first timing offset relative to a reference time, and the timeline for the second set of WUS monitoring opportunities associated with the second DRX configuration may be based on a second timing offset relative to the reference time, the second timing offset being different from the first timing offset.

[0013] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first set of WUS monitoring opportunities associated with the first DRX configuration may be associated with a first timer duration, and the second set of WUS monitoring opportunities associated with the second DRX configuration may be associated with a second timer duration, which is different from the first timer duration.

[0014] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first timer duration and the second timer duration may be used for the same type of timer, including inactive timers, monitoring duration timers, active duration timers, offset timers, uplink hybrid autorepeat request timers, downlink hybrid autorepeat request timers, uplink retransmission timers, or downlink retransmission timers.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the WUS monitoring timings of the first set associated with the first DRX configuration may each have a first duration, and the WUS monitoring timings of the second set associated with the second DRX configuration may each have a second duration, which is different from the first duration.

[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first set of WUS monitoring opportunities associated with the first DRX configuration may be associated with a first WUS index, and the second set of WUS monitoring opportunities associated with the second DRX configuration may be associated with a second WUS index, which is different from the first WUS index. The first set of monitoring WUS monitoring opportunities includes monitoring one or more first WUS corresponding to the first WUS index, and the second set of monitoring WUS monitoring opportunities includes monitoring one or more second WUS corresponding to the second WUS index.

[0017] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first set of WUS monitoring opportunities associated with the first DRX configuration may be associated with a first transmission configuration indication state, and the second set of WUS monitoring opportunities associated with the second DRX configuration may be associated with a second transmission configuration indication state, which is different from the first transmission configuration indication state.

[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first set of WUS monitoring opportunities associated with the first DRX configuration may be associated with a first WUS bandwidth, and the second set of WUS monitoring opportunities associated with the second DRX configuration may be associated with a second WUS bandwidth that is different from the first WUS bandwidth.

[0019] The methods described herein, UEs, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for: identifying a first WUS monitoring opportunity included in the first set of WUS monitoring opportunities associated with the first DRX configuration that overlaps temporally with a second WUS monitoring opportunity included in the second set of WUS monitoring opportunities associated with the second DRX configuration; and monitoring the first WUS monitoring opportunity based on the priority of the first WUS monitoring opportunity being higher than that of the second WUS monitoring opportunity, while suppressing the monitoring of the second WUS monitoring opportunity.

[0020] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the plurality of DRX configurations also include a third DRX configuration associated with a third set of WUS monitoring times, and the third DRX configuration may also be active during that time period.

[0021] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first set of timings and the second set of timings may be associated with the same frequency range.

[0022] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the UE includes a first radio component and a second radio component associated with a lower active power consumption than the first radio component, and at least one of the first set of timings and the second set of timings can be performed via the second radio component.

[0023] The methods described herein, UEs, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for receiving WUS via the second radio component and waking up the first radio component in response to receiving the WUS via the second radio component.

[0024] The methods described herein, UEs, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for receiving second control signaling that activates the first DRX configuration and the second DRX configuration during the time period.

[0025] The methods described herein, UEs, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for receiving a third control signaling that disables the first DRX configuration, the second DRX configuration, or both during a second time period after the second time period.

[0026] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first DRX configuration can be used for a first service associated with a first service mode, and one or more parameters of the first set for timing can be based on the first service mode, and the second DRX configuration can be used for a second service associated with a second service mode, and one or more parameters of the second set for timing can be based on the second service mode, which is different from the first service mode.

[0027] A method for wireless communication by a network entity is described. The method may include: outputting control signaling indicating a plurality of DRX configurations for a UE, wherein the plurality of DRX configurations include a first DRX configuration associated with a first set of WUS monitoring times for WUS monitoring and a second DRX configuration associated with a second set of WUS monitoring times, and wherein both the first DRX configuration and the second DRX configuration are active during a time period; during the time period, outputting a first WUS during a first WUS monitoring time included in the first set of WUS monitoring times; and during the time period, outputting a second WUS during a second WUS monitoring time included in the second set of WUS monitoring times.

[0028] 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 individually or jointly operable to execute the code to cause the network entity to: output control signaling instructing a plurality of DRX configurations for a UE, wherein the plurality of DRX configurations include a first DRX configuration associated with a first set of WUS monitoring times for WUS monitoring and a second DRX configuration associated with a second set of WUS monitoring times, and wherein both the first DRX configuration and the second DRX configuration are active during a time period; during the time period, outputting a first WUS during a first WUS monitoring time included in the first set of WUS monitoring times; and during the time period, outputting a second WUS during a second WUS monitoring time included in the second set of WUS monitoring times.

[0029] Another network entity for wireless communication is described. This network entity may include: components for outputting control signaling indicating multiple DRX configurations for a UE, wherein the multiple DRX configurations include a first DRX configuration associated with a first set of WUS monitoring times for WUS monitoring and a second DRX configuration associated with a second set of WUS monitoring times, and wherein both the first DRX configuration and the second DRX configuration are active during a time period; components for outputting a first WUS during the first WUS monitoring time period included in the first set of WUS monitoring times; and components for outputting a second WUS during the second WUS monitoring time period included in the second set of WUS monitoring times.

[0030] 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: output control signaling indicating a plurality of DRX configurations for a UE, wherein the plurality of DRX configurations include a first DRX configuration associated with a first set of WUS monitoring times for WUS monitoring and a second DRX configuration associated with a second set of WUS monitoring times, and wherein both the first DRX configuration and the second DRX configuration are active during a time period; during the time period, outputting a first WUS during a first WUS monitoring time included in the first set of WUS monitoring times; and during the time period, outputting a second WUS during a second WUS monitoring time included in the second set of WUS monitoring times.

[0031] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first set of WUS monitoring opportunities associated with the first DRX configuration may have a first periodicity, and the second set of WUS monitoring opportunities associated with the second DRX configuration may have a second periodicity, which differs from the first periodicity.

[0032] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the timeline for the first set of WUS monitoring timings associated with the first DRX configuration may be based on a first timing offset relative to a reference time, and the timeline for the second set of WUS monitoring timings associated with the second DRX configuration may be based on a second timing offset relative to the reference time, which is different from the first timing offset.

[0033] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first set of WUS monitoring opportunities associated with the first DRX configuration may be associated with a first timer duration, and the second set of WUS monitoring opportunities associated with the second DRX configuration may be associated with a second timer duration, which is different from the first timer duration.

[0034] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first timer duration and the second timer duration may be used for the same type of timer, including inactive timers, monitoring duration timers, active duration timers, offset timers, or retransmission timers.

[0035] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the WUS monitoring timings of the first set associated with the first DRX configuration may each have a first duration, and the WUS monitoring timings of the second set associated with the second DRX configuration may each have a second duration, which is different from the first duration.

[0036] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first set of WUS monitoring opportunities associated with the first DRX configuration may be associated with a first WUS index, and the second set of WUS monitoring opportunities associated with the second DRX configuration may be associated with a second WUS index, which is different from the first WUS index.

[0037] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first set of WUS monitoring opportunities associated with the first DRX configuration may be associated with a first transmission configuration indication state, and the second set of WUS monitoring opportunities associated with the second DRX configuration may be associated with a second transmission configuration indication state, which is different from the first transmission configuration indication state.

[0038] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first set of WUS monitoring opportunities associated with the first DRX configuration may be associated with a first WUS bandwidth, and the second set of WUS monitoring opportunities associated with the second DRX configuration may be associated with a second WUS bandwidth, which is different from the first WUS bandwidth.

[0039] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first set of WUS monitoring opportunities associated with the first DRX configuration may be associated with a first priority, and the second set of WUS monitoring opportunities associated with the second DRX configuration may be associated with a second priority, which is different from the first priority.

[0040] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the plurality of DRX configurations also include a third DRX configuration associated with a third set of WUS monitoring times, and this third DRX configuration may also be active during that time period.

[0041] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first set of timings and the second set of timings may be associated with the same frequency range.

[0042] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for outputting second control signaling that activates the first DRX configuration and the second DRX configuration during the time period.

[0043] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for outputting a third control signaling to disable the first DRX configuration, the second DRX configuration, or both during a second time period after the second time period.

[0044] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first DRX configuration may be used for a first service associated with a first service mode, and one or more parameters of the first set for timing may be based on the first service mode; and the second DRX configuration may be used for a second service associated with a second service mode, and one or more parameters of the second set for timing may be based on the second service mode, which is different from the first service mode. Attached Figure Description

[0045] Figure 1 An example of a wireless communication system supporting a discontinuous reception (DRX) configuration for wake-up signal (WUS) monitoring is shown, according to one or more aspects of this disclosure.

[0046] Figure 2 An example of a wireless communication system supporting DRX configuration for WUS monitoring, according to one or more aspects of this disclosure, is shown.

[0047] Figure 3An example of a DRX graph supporting a DRX configuration for WUS monitoring, according to one or more aspects of this disclosure, is shown.

[0048] Figure 4 An example of a DRX graph supporting a DRX configuration for WUS monitoring, according to one or more aspects of this disclosure, is shown.

[0049] Figure 5 An example of a DRX graph supporting a DRX configuration for WUS monitoring, according to one or more aspects of this disclosure, is shown.

[0050] Figure 6 An example of a DRX graph supporting a DRX configuration for WUS monitoring, according to one or more aspects of this disclosure, is shown.

[0051] Figure 7 An example flowchart of a process for configuring DRX for WUS monitoring, according to one or more aspects of this disclosure, is shown.

[0052] Figure 8 and Figure 9 A block diagram of a device supporting DRX configuration for WUS monitoring, according to one or more aspects of this disclosure, is shown.

[0053] Figure 10 A block diagram of a communication manager supporting DRX configuration for WUS monitoring, according to one or more aspects of this disclosure, is shown.

[0054] Figure 11 A diagram of a system including a device supporting DRX configuration for WUS monitoring is shown, according to one or more aspects of this disclosure.

[0055] Figure 12 and Figure 13 A block diagram of a device supporting DRX configuration for WUS monitoring, according to one or more aspects of this disclosure, is shown.

[0056] Figure 14 A block diagram of a communication manager supporting DRX configuration for WUS monitoring, according to one or more aspects of this disclosure, is shown.

[0057] Figure 15 A diagram of a system including a device supporting DRX configuration for WUS monitoring is shown, according to one or more aspects of this disclosure.

[0058] Figure 16 and Figure 17 A flowchart illustrating a method for supporting DRX configuration for WUS monitoring according to one or more aspects of this disclosure is shown. Detailed Implementation

[0059] In some wireless communication systems, the User Equipment (UE) can monitor wake-up signals (WUS) from network entities. In some examples, the UE may have a low-power receiver (LR) for receiving low-power WUS (LP-WUS). The LR can use less power than the main radio component (MR), and receiving LP-WUS consumes less power than receiving WUS. In some examples, the UE can monitor signals according to discontinuous reception modes (DRX), which may include idle discontinuous reception (iDRX) mode and connected mode discontinuous reception mode (CDRX). When operating in iDRX mode, the UE can periodically wake up to monitor paging messages. In some examples, the UE can monitor signals according to CDRX mode, where the UE can periodically wake up to monitor WUS, such as LP-WUS. In some examples, when monitoring according to DRX mode, the UE saves power but may experience increased latency relative to the received signal.

[0060] The techniques described herein provide a WUS monitoring scheme in which the UE monitors multiple DRX configurations simultaneously (e.g., multiple iDRX or multiple CDRX configurations, or any combination thereof), thereby creating “floating” LP-WUS reception. Monitoring multiple DRX configurations reduces data reception latency, and periodically monitoring LP-WUS reduces power consumption (e.g., the UE is configured with multiple DRX configurations, where two or more of the configured DRX configurations can be active concurrently). For example, using LR to monitor LP-WUS allows MR to remain in sleep mode for a significant portion of the UE's operation, resulting in power savings for the UE. One or more parameters can vary between the active DRX configurations used for the UE, providing flexibility regarding the timing and frequency of the UE's active monitoring of one or more WUS. For example, different activity DRX configurations for a UE can correspond to different corresponding service flows (e.g., information flows) for the UE, where the corresponding service flows are associated with different service modes (e.g., message timing and duration), and the DRX configuration is configured to align the associated monitoring timing with the corresponding service flow (e.g., so that the UE can wake up with low latency for each service flow, but without needing to wake up unnecessarily).

[0061] The UE can receive control signaling indicating multiple DRX configurations for monitoring LP-WUS and parameters associated with each DRX configuration. Parameters may include configuration parameters such as periodicity, start offset, monitoring timing duration, and timers, as well as signaling parameters such as index, transmit configuration index (TCI) status, and bandwidth. For example, a first DRX configuration may have a different periodicity than a second DRX configuration, or it may have the same periodicity with a start offset. In some examples, the monitoring timings of different active DRX configurations may overlap, leading to potential conflicts. The UE can skip conflicting monitoring timings based on priority, which may be indicated by a network entity. In some examples, a network entity may activate or deactivate a DRX configuration, or configure the UE to, for example, autonomously activate or deactivate a DRX configuration upon receiving LP-WUS. Upon receiving a signal, the UE can wake up the MR. In some examples, the DRX configurations described herein may be applicable to one or both of iDRX mode or CDRX mode.

[0062] The various aspects of this disclosure are first described in the context of a wireless communication system. Further aspects of this disclosure are illustrated and described with reference to DRX diagrams and process flowcharts. Further aspects of this disclosure are illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts related to the DRX configuration for WUS monitoring.

[0063] Figure 1 An example of a wireless communication system 100 supporting DRX configuration for WUS monitoring, according to one or more aspects of this disclosure, is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0064] 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 one or more communication links 125 (e.g., radio frequency (RF) access links). 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 one or more communication links 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).

[0065] 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 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0066] 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.

[0067] 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 one or more backhaul communication links 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 links 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.

[0068] One or more network entities in network entity 105 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, evolved 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 evolved 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 105 (e.g., a single RAN node, such as base station 140).

[0069] 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 two or more network entities 105, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 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 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0070] 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, and 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 higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can 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 each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). 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 different 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 one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more 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 the corresponding network entities 105 communicating via such communication links.

[0071] In a wireless communication system (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 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of 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 a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports 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., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0072] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), 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 a CU 160 and at least one DU 165 (e.g., and RU 170), wherein the 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, the CU 160 may communicate with the core network via an interface (which may be part of a backhaul link) and may communicate with other CU 160s (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be part of a backhaul link).

[0073] 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 DRX configurations for WUS monitoring as 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., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0074] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some 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 or vehicles, meters, etc.

[0075] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0076] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., 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 physical 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 physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, 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, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0077] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate 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., the same or different radio access technologies) are used to anchor the connection.

[0078] The communication link 125 shown in 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. A 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).

[0079] 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 particular radio access technology (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 hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one of the carrier bandwidths in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include 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.

[0080] 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 may 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.

[0081] 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 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.

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

[0083] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, 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 can be defined by a set of symbol periods and can 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 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can 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 can 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 multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0084] 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), or other identifier). 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, or may include buildings, subsets of buildings, or external space between or overlapping coverage areas.

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

[0086] 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 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 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 radio access technologies to provide coverage for various coverage areas 110.

[0087] 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 timings, and transmissions from different network entities 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 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0088] Some UE 115 devices (such as MTC or IoT devices) can be 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 billing.

[0089] Some UE 115s can be configured to operate in reduced-power modes, 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 reduced peak rates. Other power-saving techniques for UE 115s 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.

[0090] 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 or 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 prioritization of 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.

[0091] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group 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 UE 115s 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 UE 115s communicating via D2D communication may support a one-to-many (1:M) system in which each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0092] 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 some combination of these. Vehicles may signal information related to traffic conditions, signaling, 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.

[0093] 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 delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may 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.

[0094] 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 100 km).

[0095] The wireless communication system 100 can also operate using the ultra-high frequency (SHF) region (also known as the centimeter band) in the range of 3 GHz to 30 GHz or 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 transmissions, EHF transmissions may experience even greater attenuation and shorter range. The techniques disclosed herein can be adopted across transmissions using one or more different frequency regions, and the frequency band usage specified across these frequency regions may vary by country or regulatory authority.

[0096] 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) radio access technology, 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.

[0097] 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.

[0098] Network entity 105 or UE 115 may use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique may be referred to as spatial multiplexing. The multiple signals may be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), for which multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.

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

[0100] 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 in different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Beam directions may be identified (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) by transmission along different beam directions for later transmission or reception by network entity 105.

[0101] Some signals (such as data signals associated with a specific receiving device) may be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., the direction associated with a receiving device (such as receiving network entity 105 or receiving 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.

[0102] 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 beam set configured 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) along one or more directions, UE 115 may use similar techniques to transmit signals multiple times along different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals along a single direction (e.g., to transmit data to a receiving device).

[0103] 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 signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of the antenna array; or processing the received signal 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).

[0104] 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 implement error detection, error correction, or both to support retransmission and improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 supporting user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0105] 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 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 may 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.

[0106] The techniques described herein provide multiple DRX configurations (e.g., multiple iDRX configurations, multiple CDRX configurations, or any combination thereof) for WUS monitoring. DRX configurations can be sent by network entity 105 and received by UE 115. UE 115 can monitor WUS, such as LP-WUS, according to the DRX configuration indicated by network entity 105-a. The network entity can send further control signaling indicating parameters associated with each DRX configuration. Parameters may include configuration parameters (such as periodicity, start offset, monitoring timing duration, and timers) and signal parameters (such as index, TCI status, and bandwidth). For example, a first DRX configuration may have a different periodicity than a second DRX configuration, or it may have the same periodicity with a start offset.

[0107] In some examples, the monitoring timing of different DRX configurations may overlap, leading to potential conflicts. In the event of a conflict, network entity 105 may indicate the priority of each DRX configuration, indicating the default configuration. For example, UE 115 may receive an indication that the first DRX configuration is the default or has the highest priority, and skip any other monitoring timings occurring simultaneously. In some examples, network entity 105 may activate or deactivate DRX configurations, or configure UE 115 to activate or deactivate DRX configurations, such as upon receiving an LP-WUS signal. Upon receiving a WUS signal, the UE may wake up the MR. (References: This document refers to...) Figures 2 to 7 The techniques and methods are further described.

[0108] Figure 2 An example of a wireless communication system 200 supporting DRX configurations for WUS monitoring, according to one or more aspects of this disclosure, is shown. Specifically, the wireless communication system 200 exemplifies one or more DRX configurations 215 transmitted from network entity 105-a to UE 115-a. Network entity 105-a may be as described in reference... Figure 1 The example of network entity 105 described herein, and UE 115-a may be as referenced Figure 1 An example of UE 115 as described. Figure 2 The aspects of the accompanying drawings described herein can be implemented or are implemented by these aspects. In some examples, the multiple DRX configurations can be multiple CDRX configurations, multiple iDRX configurations, or any combination thereof.

[0109] Network entity 105-a and UE 115-a can communicate via communication link 205 (e.g., downlink channel, physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH), etc.) and communication link 210 (e.g., uplink channel, physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), etc.). Network entity 105-a can send DRX configuration 215 via communication link 205. In some examples, network entity 105-a can send one or more WUS 220s (e.g., WUS 220-a and WUS 220-b) and one or more WUS 225s (e.g., WUS 225-a and WUS 225-b). Network entity 105-a can send message 230-a after sending one or more WUS 220s, one or more WUS 225s, or both. In some examples, UE 115-a can send response message 230-b.

[0110] In some examples, UE 115-a may use a low-power receiver (LR) 235 (e.g., a low-power wake-up radio component (LP-WUR)) to monitor and receive low-power WUS (LP-WUS). In some examples, WUS 220 and WUS 225 may be LP-WUS. UE 115-a may replace MR 240 to monitor signals such as WUS or LP-WUS. In some examples, UE 115-a may receive LP-WUS via LR 235 and wake up MR 240. For example, UE 115-a may receive WUS220-a via LR 235. In some examples, UE 115-a may receive WUS 220-b, WUS 225-a, WUS 225-b, or another WUS via LR 235. In some examples, UE 115-a may send a wake-up indication 245 to instruct the MR 240 radio component to wake up, or send another indication for received LP-WUS. For example, LR 235 may send wake-up indication 245 to MR 240; or LR 235 may signal to a communication manager as described herein, and the communication manager may, in response to receiving a signal from LR 235, send wake-up indication 245 to MR 240. This approach reduces power consumption because LR 235 operates at lower power than MR 240. After waking MR 240, MR 240 may monitor DCI, and LR 235 may return to idle mode.

[0111] In some examples, UE 115-a can operate according to DRX and can periodically enter sleep states (e.g., idle mode, reduced power mode, etc.). Network entity 105-a can send a DRX configuration indicating the periodicity of monitoring timing, whereby UE 115-a can monitor LP-WUS signals at intervals and enter sleep states between intervals. UE 115-a can monitor at each interval for a certain period of time or monitoring duration. This approach, combined with LP-WUS, enables power savings for both idle and connected modes, especially in applications with high power consumption, such as frequency range 2 (FR2)

[0112] UE 115-a can monitor LP-WUS via LR 235 for the same frequency band (e.g., FR2) using multiple DRX configurations 215 with different parameters, maximizing power utilization for monitoring. Monitoring multiple DRX configurations 215 creates the possibility of “floating” wake-up, including continuous monitoring (e.g., a fully floating monitoring window) and duty cycle monitoring (e.g., discretized floating based on the monitoring periodicity of LR 235 capabilities). Multiple DRX configurations 215 can be configured for each set of component carriers or frequency bands. Interleaving monitoring timings reduces latency while lowering power consumption, as multiple DRX modes and timings can be monitored without powering on MR 240.

[0113] Multiple DRX configurations 215 may include multiple configurations with different parameters, such as DRX parameters and LP-WUS parameters. LP-WUS parameters may include an LP-WUS index, an LP-WUS TCI state for the transmit or receive beam, and an LP-WUS bandwidth. DRX parameters may include periodicity, offset, a timer for the multiple DRX configurations, and the timing of LP-WUS monitoring for each of these multiple DRX configurations. For example, a first DRX configuration may have a periodicity of monitoring every 80 milliseconds (ms), and a second DRX configuration may have a periodicity of 60 ms, where monitoring starts simultaneously. UE 115-a may monitor two DRX configurations simultaneously, monitor the second DRX configuration at 60 ms, monitor the first DRX configuration at 80 ms, monitor the second DRX configuration at 120 ms, monitor the first DRX configuration at 160 ms, and so on.

[0114] DRX timers may include inactive timers (e.g., drx-inactivity-timer), monitoring duration timers, active duration timers (e.g., drx-on-duration-timer), offset timers, uplink hybrid automatic repeat request (HARQ) timers (e.g., drx-HARQ-RTT-timer-UL), downlink HARQ timers (e.g., HARQ-RTT-timer-DL), uplink retransmission timers (e.g., drx-retransmission-timer-UL), downlink retransmission timers (e.g., drx-retransmission timer-DL), or combinations thereof. In some examples, a DRX configuration may have multiple timers of the same type, and for a given type of timer, the timer duration for that type of timer may differ between at least some of the multiple DRX configurations.

[0115] In some examples, network entity 105-a may send multiple WUS according to multiple DRX configurations 215. For example, network entity 105-a may send WUS 220-a according to a first DRX configuration and WUS 225-a according to a second DRX configuration. In some examples, network entity 150-a may send multiple WUS for each configuration, such as sending a second WUS 220-b corresponding to the first configuration and a WUS 225-b corresponding to the second configuration.

[0116] Figure 3 An example of a DRX diagram 300 supporting DRX configurations for WUS monitoring, according to one or more aspects of this disclosure, is shown. Specifically, the DRX diagram 300 may describe multiple DRX configurations (e.g., as referenced in [reference]). Figure 2 The described DRX configuration 215 and the monitoring timing for each configuration. Monitoring timing can be determined by the UE (such as a reference). Figure 1 The UE 115 described is being monitored. Figure 2 The aspects of the accompanying drawings described herein can be implemented or are implemented by these aspects. In some examples, the multiple DRX configurations can be multiple CDRX configurations, multiple iDRX configurations, or any combination thereof.

[0117] The UE can receive multiple DRX configurations, such as a first DRX configuration, a second DRX configuration, a third DRX configuration, and a fourth DRX configuration. Each DRX configuration can have a set of parameters. In some examples, a DRX configuration can configure the UE to always use the LR to monitor LP-WUS when the MR is in idle or sleep mode. In some examples, each DRX configuration can have different periodicity, start offset, timer, beam, etc. The offset can reference another DRX configuration, period time, or another point in time, such as a time slot.

[0118] The network entity can configure each parameter as the service arrival mode of the UE at the network entity, which can further reduce latency.

[0119] For example, the first DRX configuration may have an 80ms periodicity (e.g., an 80ms DRX cycle, or 80ms between monitoring moments), a monitoring duration of one time slot (e.g., 1ms), and an offset of -10ms (e.g., or 70ms). That is, the first DRX configuration may be configured with a -10ms offset from the third DRX configuration, or start 10ms before the third DRX configuration.

[0120] The second DRX configuration can have a period of 30ms and a monitoring duration of 1ms. The third DRX configuration can have a period of 80ms and a monitoring duration of 1ms. The fourth DRX configuration can have a period of 80ms, an offset of 15ms and a monitoring duration of 2ms, and an offset of 45ms and a monitoring duration of 5ms. That is, there can be a monitoring opportunity of 2ms duration 15ms after monitoring opportunity 305, and then a monitoring opportunity of 2ms duration every 80ms. In addition, there can be a monitoring opportunity of 5ms duration 45ms after monitoring opportunity 305, and then a monitoring opportunity of 5ms duration after 80ms thereafter.

[0121] In some examples, DRX configuration monitoring timings can overlap. For example, monitoring timing 305 or the first monitoring timing of the third DRX configuration can overlap with skipped monitoring timing 310 or the first monitoring timing of the second DRX configuration. In such examples, the UE can determine the parameters (e.g., sequence index, bandwidth, beam, etc.) for LP-WUS monitoring during the overlapping monitoring timings based on one of the DRX configurations involved in the overlap. Which DRX configuration to use for monitoring during the overlapping monitoring timings and which DRX configuration to skip monitoring can be determined by the UE based on priority, pre-configured, or otherwise determined. In some examples, such as for longer monitoring durations, periodicity can be counted from the end of the monitoring duration rather than the beginning.

[0122] Figure 4 An example of a DRX diagram 400 supporting a DRX configuration for WUS monitoring according to one or more aspects of this disclosure is shown. For example, DRX diagram 400 illustrates a first DRX configuration and a second DRX configuration with different parameters for monitoring monitoring timing 405. Parameters may include DRX parameters and LP-WUS parameters. LP-WUS parameters may include the LP-WUS index, the LP-WUS Transmission Configuration Indicator (TCI) status, and the LP-WUS bandwidth. Figure 4 The aspects of the accompanying drawings described herein can be implemented or are implemented by these aspects. In some examples, the multiple DRX configurations can be multiple CDRX configurations, multiple iDRX configurations, or any combination thereof.

[0123] The first DRX configuration can have a periodicity of 80ms, and the second DRX configuration can have a periodicity of 30ms. Monitoring timing 405-a can occur simultaneously with the skipped monitoring timing 410.

[0124] For each DRX configuration, the UE can monitor LP-WUS parameters. For example, the LP-WUS indexes may be the same or different for different DRX configurations. For instance, the first DRX configuration might have index 1, and the DRX configuration might have index 2. In some examples, the index may be associated with the UE group ID. Furthermore, for the same DRX configuration, the index may change over time. For example, the UE group ID and therefore the monitored LP-WUS index may change across different LP-WUS monitoring times for different DRX configurations.

[0125] Each WUS may have a TCI state for transmitting or receiving beams. The TCI states used for LP-WUS monitoring may be the same or different for different DRX configurations. In some examples, the TCI states may be the same or different for different monitoring times in a DRX configuration. For example, monitoring times 405-a and 405-d may have TCI state 1, while monitoring time 405-b may have TCI state 2, monitoring time 405-c may have TCI state 3, and monitoring time 405-e may have TCI state 4.

[0126] Different TCI states allow beam scanning and increase the probability of wake-up. Sharper beams can be used for high-priority data, while wider beams (e.g., with the antenna off) can be used for low-priority data. Sharper or narrower beams can provide more signal energy, but may increase the energy cost of more active antenna elements and lead to higher power consumption. For example, TCI state 1 can be a narrower beam used on monitoring times 405-a and 405-d spaced 80ms apart, while TCI states 2, 3, and 4 can be wider beams used on monitoring times 405-b, 405-c, and 405-e spaced 30ms apart. The network entity can receive an ACK / NACK for the UE after UE wake-up based on LP-WUS, which indicates to the network entity which beam was detected by the UE. If the UE is not within LP-WUS coverage, the network entity can transmit WUS on different beams or switch to a different LP-WUS index.

[0127] DRX configurations can have different bandwidths associated with LP-WUS. Higher bandwidth can be allocated more periodically to ensure more reliable wake-up, but this results in higher power consumption. UEs can be configured more frequently for monitoring with lower bandwidth, which saves UE power. UEs monitoring LP-WUS with different bandwidths across different DRX configurations also allows the network to scan across different levels of cell coverage and improves communication reliability. For example, narrower beams (such as those used in monitoring times 405-a and 405-d) provide more coverage. Wider beams (such as those used in monitoring times 405-b, 405-c, and 405-e) may have less coverage. UEs closer to the cell center can detect LP-WUS with lower bandwidth (and lower coverage), while UEs at the cell edge can detect only LP-WUS with higher bandwidth (and higher coverage). Therefore, by maintaining the periodicity of the second DRX configuration associated with LP-WUS monitoring of a smaller bandwidth more frequently than that of the first DRX configuration associated with LP-WUS monitoring of a larger bandwidth, UE power can be saved for UEs located near the cell center. For example, the first DRX configuration monitoring timing 405 may have a bandwidth of 80 MHz, and the second DRX configuration monitoring timing 405 may have a bandwidth of 20 MHz.

[0128] Figure 5 An example of a DRX diagram 500 supporting DRX configurations for WUS monitoring, according to one or more aspects of this disclosure, is shown. Specifically, DRX diagram 500 depicts a first DRX configuration and a second DRX configuration, which may have varying activity durations and periodicity. Figure 5 The aspects of the accompanying drawings described herein can be implemented or are implemented by these aspects. In some examples, the multiple DRX configurations can be multiple CDRX configurations, multiple iDRX configurations, or any combination thereof.

[0129] Network entities can be configured with multiple DRX configurations with varying periods and offsets to match service patterns or arrival times. For example, a first DRX configuration might have a period of 30ms and correspond to a service arriving at approximately 30fps or 100 frames per three-second interval. A second DRX configuration might correspond to an arrival time of approximately 80ms and have a period of 80ms.

[0130] DRX configuration can include timers, such as an on-duration timer, a retransmission timer, and an inactive timer. For example, a service arriving at 30fps may have a small data volume and can be received by monitoring a small number of time slots during the on-duration period, but a service arriving every 80ms may have a larger data volume and can be received by monitoring multiple time slots during a longer on-duration period.

[0131] Network entities can activate and deactivate DRX configurations. In some examples, there may be a set of configured DRX configurations, and a subset may be active. The UE can monitor active DRX configurations. Network entities can activate or deactivate DRX configurations by adding bits to LP-WUS when transmitting to the LR, or by transmitting DCI or MAC-CE when the MR is activated.

[0132] Additionally, each DRX configuration can have its own corresponding activity duration 505. The activity duration 505 can be the start time (T... on ) and inactivity time (I nactivity A combination of these activities is possible. For example, a first DRX configuration may be configured with an activity duration of 505-a, which may repeat periodically. For example, activity duration 505-a may repeat at activity duration 505-e. Activity durations 505-a and 505-e may be of the same length. Activity durations 505-b, 505-c, and 505-d may be configured for a second DRX configuration. The activity duration 505 associated with the second DRX configuration may be shorter than the activity duration 505 associated with the first DRX configuration. In some examples, activity durations 505 may overlap, such as activity durations 505-d and 505-e. Depending on which LP-WUS monitoring timing is sent by the network and the associated DRX configuration (e.g., the LP-WUS corresponding to the first DRX configuration or the LP-WUS corresponding to the second DRX configuration) to wake up the UE, any activity duration 505 may be used for the MR to wake up the UE. In some examples, if the UE is woken up by LP-WUS to monitor activity duration 505-e according to the first DRX configuration, the network may not transmit another LP-WUS to wake up the UE to monitor overlapping activity duration 505-d according to the second DRX configuration, because the UE is already in an active state.

[0133] A common timing reference can be configured for DRX configuration. For example, an aligned start time can be defined for DRX configurations with different periodicities. The aligned start time can be the time when the UE switches from another mode (such as connected mode) to DRX mode, or it can be set as a periodic reference time. For example, all DRX configurations can be restarted every 10 seconds.

[0134] Network entities can configure the start and stop of DRX configuration monitoring, such as by configuring automatic or autonomous monitoring start and stop performed by the UE. For example, if no wake-up command is received, the network entity can configure the UE to gradually stop monitoring one or more DRX configurations. For instance, the UE can stop monitoring one DRX configuration at a time if no wake-up signal is received on that DRX configuration within a specific time period. Similarly, when LP-WUS is received, the UE can gradually (e.g., one by one) start monitoring DRX configurations.

[0135] Multiple DRX configurations configured to start and stop can be similar to short DRX cycles, increasing flexibility and reducing latency. Additionally, using LP-WUS to start and stop DRX configurations enables reduced power consumption.

[0136] The UE can skip monitoring LP-WUS that overlap with the MR's activity time. For example, in addition to sending permission to the MR via DCI, the network entity may not transmit LP-WUS. In some examples, the network entity can wake up the UE by indicating several bits of information by selecting which LP-WUS in the LP-WUS set within a time period. For example, within a configured LP-WUS set, the signal can transmit log2(M) bits, where M is the number of configured LP-WUS in which the UE receives (e.g., also expects to find) the LP-WUS. Configured LP-WUS may belong to the same DRX configuration (e.g., with the same periodicity, offset, etc.) or belong to different DRX configurations (e.g., with different periodicity, offset, etc.).

[0137] In some examples, the monitoring timing can be single-time monitoring or window-based monitoring. Single-time LP-WUS monitoring can be associated with a periodicity. In some examples, a single timing can instead be a window, or timing associated with additional timings. The window can be continuous monitoring 515 or duty cycle monitoring 510. The UE can be monitored within the window and not outside the window. For example, a first DRX configuration can be configured with duty cycle monitoring 510, where each monitoring timing has a non-continuous monitoring timing. A second DRX configuration can be configured with continuous monitoring 515, where each timing is monitored continuously.

[0138] Figure 6 An example of a DRX diagram 600 supporting a DRX configuration for WUS monitoring according to one or more aspects of this disclosure is shown. DRX diagram 600 further describes multiple DRX configurations with overlapping timings 605 (e.g., overlapping monitoring timings), which can be addressed according to a specified order or priority. Figure 5The aspects of the accompanying drawings described herein can be implemented or are implemented by these aspects. In some examples, the multiple DRX configurations can be multiple CDRX configurations, multiple iDRX configurations, or any combination thereof.

[0139] The first DRX configuration may have an 80-second period, the second DRX configuration may have an 80-ms period with a 10-ms offset (e.g., a start time 10ms after the first DRX configuration), the third DRX configuration may have a 30-ms period, and the fourth DRX configuration may have a 20-ms period. Various rules, conditions, or configurations can determine which monitoring events to monitor during the overlap period.

[0140] For example, the first DRX configuration can be set as the default configuration. The default configuration can have the highest priority and can be set as the default or fallback monitoring timing. For example, at overlap timing 605-a, the monitoring timings for the first, third, and fourth DRX configurations overlap. The first DRX configuration, as the default and highest priority, can be monitored, while the third and fourth DRX configurations can be skipped. At overlap timing 605-a, only the LP-WUS of the first DRX configuration can be received.

[0141] In some examples, network entities can assign priorities to each DRX configuration. For instance, a second DRX configuration might have the second highest priority, a third DRX configuration the third highest priority, and a fourth DRX configuration the fourth highest priority. For example, at overlap timing 605-b, monitoring timings for the third and fourth DRX configurations can overlap. In this example, the third DRX configuration has a higher priority than the fourth DRX configuration, and therefore the monitoring timing for the third DRX configuration can be monitored, while the monitoring timing for the fourth DRX configuration can be skipped.

[0142] In another example, at overlap timing 605-c, the default or highest priority timing is the timing of the first DRX configuration. The monitoring timing of the fourth DRX configuration can be skipped. At overlap timing 605-d, the second DRX configuration can have a higher priority than the third DRX configuration, and therefore the UE can monitor the second DRX configuration and skip the third DRX configuration.

[0143] In some examples, DRX configurations can be configured tightly in time. Tightly configured monitoring timings (which can be combined with beam or bandwidth scanning) can improve reliability and reduce latency. For example, multiple timings for different DRX configurations can be close in time, such as... Figure 6 The first five timings have a 10ms interval.

[0144] In some examples, different LP-WUS corresponding to the DRX configuration can have different bandwidths or be transmitted on different beams, which can increase the possible WUS coverage. For example, the first DRX configuration can have a beamwidth of 20 MHz, the second DRX configuration can have a beamwidth of 40 MHz, the third DRX configuration can have a beamwidth of 80 MHz, and the fourth DRX configuration can have a beamwidth of 160 MHz. Therefore, in the first 40 ms of the first four monitoring times, the UE can monitor a bandwidth from 20 MHz to 160 MHz. Increasing the bandwidth can improve the reliability of LP-WUS detection or allow more information to be transmitted.

[0145] In some examples, a minimum interleaving gap, such as gap 610, can be configured between the initial positioning of the DRX configuration. The initial gap 610 between each first monitoring opportunity of each DRX configuration can be configured to allow the UE to transmit a response to the network entity upon receiving LP-WUS. For example, gap 610 can be two time slots, or sufficient time for the UE to transmit an ACK after receiving LP-WUS. The network entity can receive this response and can suppress the transmission of another LP-WUS.

[0146] Figure 7 An example of a process flowchart 700 supporting DRX configuration for WUS monitoring according to one or more aspects of this disclosure is shown. Specifically, process flowchart 700 illustrates DRX configuration communication and WUS monitoring between network entity 105-b and UE 115-b. Network entity 105-b may be as described in reference... Figure 1 The example of network entity 105 described herein, and UE115-b may be as referenced Figure 1 An example of UE 115 is described. Process flowchart 700 may implement or be implemented by aspects of the accompanying drawings described herein. In the following description of process flowchart 700, operations between UE 115-b and network entity 105-b may be performed in different orders or at different times. Some operations may also be excluded from process flowchart 700, or other operations may be added. Although UE 115-b and network entity 105-b are shown as performing the operations of process flowchart 700, some aspects of some operations may also be performed by one or more other radio devices. In some examples, multiple DRX configurations may be multiple CDRX configurations, multiple iDRX configurations, or any combination thereof.

[0147] At 705, UE 115-b may receive control signaling indicating multiple DRX configurations for UE 115-b, wherein the multiple DRX configurations include a first DRX configuration associated with a first set of WUS monitoring times and a second DRX configuration associated with a second set of WUS monitoring times, and wherein both the first and second DRX configurations are active during the time period. In some examples, WUS may be LP-WUS.

[0148] A first set of WUS monitoring times associated with a first DRX configuration may have a first periodicity, and a second set of WUS monitoring times associated with a second DRX configuration may have a second periodicity, wherein the second periodicity is different from the first periodicity.

[0149] In some examples, multiple DRX configurations may also include a third DRX configuration associated with a third set of WUS monitoring times, wherein the third DRX configuration is also active during that time period.

[0150] The timeline for the first set of WUS monitoring events associated with the first DRX configuration may be based on a first timing offset relative to a reference time, and the timeline for the second set of WUS monitoring events associated with the second DRX configuration may be based on a second timing offset relative to a reference time, wherein the second timing offset is different from the first timing offset.

[0151] A first set of WUS monitoring events associated with a first DRX configuration may be associated with a first timer duration, and a second set of WUS monitoring events associated with a second DRX configuration may be associated with a second timer duration, wherein the second timer duration differs from the first timer duration. The first and second timer durations may be used for timers of the same type, including inactive timers, monitoring duration timers, active duration timers, offset timers, uplink hybrid automatic repeat request timers, downlink hybrid automatic repeat request timers, uplink retransmission timers, or downlink retransmission timers.

[0152] In some examples, the WUS monitoring times of the first set may each have a first duration, and the WUS monitoring times of the second set may each have a second duration, wherein the second duration is different from the first duration.

[0153] In some examples, a first set of WUS monitoring opportunities may be associated with a first WUS index, a first TCI state, a first WUS bandwidth, or a combination thereof. A second set of WUS monitoring opportunities may be associated with a second WUS index, a second TCI state, a second WUS bandwidth, or a combination thereof. In some examples, the second WUS index may differ from the first WUS index, the second TCI state may differ from the first TCI state, and the second WUS bandwidth may differ from the first WUS bandwidth.

[0154] The first set and the second set of WUS monitoring opportunities can be associated with the same frequency range.

[0155] A first DRX configuration can be used for a first service associated with a first service mode, and one or more parameters for a first set of timings can be based on the first service mode. A second DRX configuration can be used for a second service associated with a second service mode, and one or more parameters for a second set of timings can be at least partially based on the second service mode, wherein the second service mode differs from the first service mode.

[0156] At 710, UE 115-b can receive control signaling. For example, UE 115-b can receive a second control signaling that activates the first DRX configuration and the second DRX configuration during the specified time period. UE 115-b can also receive a third control signaling that deactivates the first DRX configuration, the second DRX configuration, or both during a second time period that follows the specified time period.

[0157] At 715, UE 115-b can monitor a first set of WUS monitoring opportunities according to a first DRX configuration and a second set of WUS monitoring opportunities according to a second DRX configuration during this time period.

[0158] UE 115-b can monitor WUS monitoring times within a first set or a second set of WUS monitoring times. Monitoring WUS monitoring times may include monitoring a portion of WUS monitoring times based on duty cycle, or monitoring the entire WUS monitoring time.

[0159] In some examples, the first set of WUS monitoring timings may include monitoring one or more first WUS corresponding to a first WUS index, and the second set of WUS monitoring timings may include monitoring one or more second WUS corresponding to a second WUS index.

[0160] UE 115-b can identify when a first WUS monitoring opportunity included in a first set of WUS monitoring opportunities associated with a first DRX configuration overlaps temporally with a second WUS monitoring opportunity included in a second set of WUS monitoring opportunities associated with a second DRX configuration. UE 115-b can monitor the first WUS monitoring opportunity based on its higher priority than the second WUS monitoring opportunity, while suppressing the monitoring of the second WUS monitoring opportunity.

[0161] UE 115-b may include a first radio component (e.g., MR) and a second radio component (e.g., LR) associated with lower active power consumption than the first radio component, and wherein at least one of a first set of WUS monitoring timings and a second set of WUS monitoring timings is performed via the second radio component. UE 115-b may receive WUS via the second radio component and wake up the first radio component in response to receiving WUS via the second radio component.

[0162] At 720, network entity 105-b may output the first WUS during the first WUS monitoring time period, which is included in the first set of WUS monitoring times.

[0163] At 725, network entity 105-b may output a second WUS during the second WUS monitoring time period, which is included in the second set of WUS monitoring times.

[0164] Figure 8 A block diagram 800 of a device 805 supporting DRX configurations for WUS monitoring according to one or more aspects of this disclosure is shown. In some examples, the multiple DRX configurations may be multiple CDRX configurations, multiple iDRX configurations, or any combination thereof. Device 805 may be an example of 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, and communication manager 820), may include at least one processor that can be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0165] 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, and information channels related to DRX configuration for WUS monitoring). The information may be passed to other components of device 805. Receiver 810 may utilize a single antenna or a collection of antennas.

[0166] 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 related to DRX configuration for WUS monitoring). 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.

[0167] The communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of DRX configuration for WUS monitoring as described herein. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

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

[0169] Additionally or alternatively, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., 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 a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0170] 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 both to acquire information, output information, or perform various other operations as described herein.

[0171] The communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for receiving control signaling indicative of multiple DRX configurations for a UE, wherein the multiple DRX configurations include a first DRX configuration associated with a first set of WUS monitoring opportunities and a second DRX configuration associated with a second set of WUS monitoring opportunities, and wherein both the first and second DRX configurations are active during a time period. The communication manager 820 may be capable of, configured to, or operable to support components for monitoring the first set of WUS monitoring opportunities according to the first DRX configuration during that time period. The communication manager 820 may be capable of, configured to, or operable to support components for monitoring the second set of WUS monitoring opportunities according to the second DRX configuration during that time period.

[0172] 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 multiple DRX configurations for WUS monitoring, which can achieve various advantages such as reduced processing, reduced power consumption and more efficient utilization of communication resources.

[0173] Figure 9 A block diagram 900 of a device 905 supporting DRX configurations for WUS monitoring according to one or more aspects of this disclosure is shown. In some examples, the multiple DRX configurations may be multiple CDRX configurations, multiple iDRX configurations, or any combination thereof. Device 905 may be an example of aspects of device 805 or UE 115 as described herein. Device 905 may include receiver 910, transmitter 915, and communication manager 920. Device 905, or one or more components of device 905 (e.g., receiver 910, transmitter 915, and 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).

[0174] 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, and information channels related to DRX configuration for WUS monitoring). The information may be passed to other components of device 905. Receiver 910 may utilize a single antenna or a collection of antennas.

[0175] 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 related to DRX configuration for WUS monitoring). 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.

[0176] Device 905 or its various components may be examples of parts used to perform various aspects of a DRX configuration for WUS monitoring as described herein. For example, communication manager 920 may include control signaling receiving component 925, WUS monitoring 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 in combination with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0177] The communication manager 920 may support wireless communication according to examples disclosed herein. The control signaling receiving component 925 is capable of, configured to, or operable to support components for receiving control signaling indicative of multiple DRX configurations for the UE, wherein the multiple DRX configurations include a first DRX configuration associated with a first set of WUS monitoring opportunities and a second DRX configuration associated with a second set of WUS monitoring opportunities, and wherein both the first and second DRX configurations are active during a time period. The WUS monitoring component 930 is capable of, configured to, or operable to support components for monitoring the first set of WUS monitoring opportunities according to the first DRX configuration during that time period. The WUS monitoring component 930 is capable of, configured to, or operable to support components for monitoring the second set of WUS monitoring opportunities according to the second DRX configuration during that time period.

[0178] Figure 10 A block diagram 1000 of a communication manager 1020 supporting DRX configurations for WUS monitoring according to one or more aspects of this disclosure is shown. In some examples, the multiple DRX configurations may be multiple CDRX configurations, multiple iDRX configurations, or any combination thereof. 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 parts for performing various aspects of DRX configurations for WUS monitoring as described herein. For example, the communication manager 1020 may include a control signaling receiving component 1025, a WUS monitoring component 1030, 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).

[0179] The communication manager 1020 may support wireless communication according to examples disclosed herein. The control signaling receiving component 1025 is capable of, configured to, or operable to support components for receiving control signaling indicating multiple discontinuous reception (DRX) configurations for the UE, wherein the multiple DRX configurations include a first DRX configuration associated with a first set of WUS monitoring opportunities and a second DRX configuration associated with a second set of WUS monitoring opportunities, and wherein both the first and second DRX configurations are active during a time period. The WUS monitoring component 1030 is capable of, configured to, or operable to support components for monitoring the first set of WUS monitoring opportunities according to the first DRX configuration during that time period. In some examples, the WUS monitoring component 1030 is capable of, configured to, or operable to support components for monitoring the second set of WUS monitoring opportunities according to the second DRX configuration during that time period.

[0180] In some examples, a first set of WUS monitoring times associated with a first DRX configuration has a first periodicity, and a second set of WUS monitoring times associated with a second DRX configuration has a second periodicity, which is different from the first periodicity.

[0181] In some examples, the timeline for a first set of WUS monitoring moments associated with a first DRX configuration is based on a first timing offset relative to a reference time, and the timeline for a second set of WUS monitoring moments associated with a second DRX configuration is based on a second timing offset relative to a reference time, the second timing offset being different from the first timing offset.

[0182] In some examples, a first set of WUS monitoring events associated with a first DRX configuration is associated with a first timer duration, and a second set of WUS monitoring events associated with a second DRX configuration is associated with a second timer duration, which is different from the first timer duration.

[0183] In some examples, the first timer duration and the second timer duration are used for the same type of timer, which includes inactive timers, monitoring duration timers, active duration timers, offset timers, uplink hybrid auto-repeat request timers, downlink hybrid auto-repeat request timers, uplink retransmission timers, or downlink retransmission timers.

[0184] In some examples, the WUS monitoring timings of a first set associated with a first DRX configuration each have a first duration, and the WUS monitoring timings of a second set associated with a second DRX configuration each have a second duration, which differs from the first duration.

[0185] In some examples, the monitoring component 1030 is capable of, configured to, or operable to support components for monitoring WUS monitoring times within a first set of WUS monitoring times associated with a first DRX configuration or a second set of WUS monitoring times associated with a second DRX configuration, monitoring WUS monitoring times including monitoring a portion of the WUS monitoring times according to a duty cycle, or including monitoring the entire WUS monitoring times.

[0186] In some examples, a first set of WUS monitoring opportunities associated with a first DRX configuration is associated with a first WUS index, and a second set of WUS monitoring opportunities associated with a second DRX configuration is associated with a second WUS index, which is different from the first WUS index. In some examples, to support components for monitoring the first set of WUS monitoring opportunities, the WUS monitoring component 1030 can be, configured, or operable to support components for monitoring one or more first WUS corresponding to the first WUS index. In some examples, to support components for monitoring the second set of WUS monitoring opportunities, the WUS monitoring component 1030 can be, configured, or operable to support components for monitoring one or more second WUS corresponding to the second WUS index.

[0187] In some examples, a first set of WUS monitoring events associated with a first DRX configuration is associated with a first transmission configuration indication state, and a second set of WUS monitoring events associated with a second DRX configuration is associated with a second transmission configuration indication state, which is different from the first transmission configuration indication state.

[0188] In some examples, a first set of WUS monitoring times associated with a first DRX configuration is associated with a first WUS bandwidth, and a second set of WUS monitoring times associated with a second DRX configuration is associated with a second WUS bandwidth, which is different from the first WUS bandwidth.

[0189] In some examples, the WUS monitoring component 1030 is capable of, configured to, or operable to support components for identifying when a first WUS monitoring event included in a first set of WUS monitoring events associated with a first DRX configuration overlaps temporally with a second WUS monitoring event included in a second set of WUS monitoring events associated with a second DRX configuration. In some examples, the WUS monitoring component 1030 is capable of, configured to, or operable to support components for monitoring the first WUS monitoring event based on its higher priority than the second WUS monitoring event, while suppressing the monitoring of the second WUS monitoring event.

[0190] In some examples, multiple DRX configurations also include a third DRX configuration associated with a third set of WUS monitoring times. In some examples, the third DRX configuration is also active during that time period.

[0191] In some examples, the first set of WUS monitoring opportunities and the second set of WUS monitoring opportunities are associated with the same frequency range.

[0192] In some examples, the UE includes a first radio component and a second radio component associated with lower active power consumption than the first radio component. In some examples, at least one of a first set of WUS monitoring timings and a second set of WUS monitoring timings is performed via the second radio component.

[0193] In some examples, the WUS monitoring component 1030 is capable of, configured to, or operable to support components for receiving WUS via a second radio component. In some examples, the WUS monitoring component 1030 is capable of, configured to, or operable to support components for waking up a first radio component in response to receiving WUS via a second radio component.

[0194] In some examples, the WUS monitoring component 1030 is capable of, configured to, or operable to support components for receiving second control signaling that activates the first DRX configuration and the second DRX configuration during that time period.

[0195] In some examples, the WUS monitoring component 1030 is capable of, configured to, or operable to support components for receiving third control signaling for disabling a first DRX configuration, a second DRX configuration, or both during a second time period after that time period.

[0196] In some examples, a first DRX configuration is used for a first service associated with a first service mode, and one or more parameters for a first set of WUS monitoring timing are based on the first service mode. In some examples, a second DRX configuration is used for a second service associated with a second service mode, and one or more parameters for a second set of WUS monitoring timing are based on a second service mode that differs from the first service mode.

[0197] Figure 11 A diagram of a system 1100 including a device 1105 supporting DRX configurations for WUS monitoring, according to one or more aspects of this disclosure, is shown. In some examples, the multiple DRX configurations may be multiple CDRX configurations, multiple iDRX configurations, or any combination thereof. 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 with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). 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 1110, a transceiver 1115, an antenna 1125, 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).

[0198] 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.

[0199] In some cases, device 1105 may include a single antenna 1125. However, in other cases, device 1105 may have more than one antenna 1125, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1115 may communicate bidirectionally via one or more antennas 1125 as described herein, a wired or wireless link. 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.

[0200] 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, computer-executable code 1135, including 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 enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 1130 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0201] At least one processor 1140 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 1140 may be configured to operate a memory array using a memory controller. 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 supporting DRX configuration for WUS monitoring). 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. 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 a plurality of processors may be coupled to one or more of a plurality of 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, 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 such 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, capable of being configured, 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,” and “operable 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 1130 or otherwise.

[0202] The communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for receiving control signaling indicative of multiple DRX configurations for a UE, wherein the multiple DRX configurations include a first DRX configuration associated with a first set of WUS monitoring opportunities and a second DRX configuration associated with a second set of WUS monitoring opportunities, and wherein both the first and second DRX configurations are active during a time period. The communication manager 1120 may be capable of, configured to, or operable to support components for monitoring the first set of WUS monitoring opportunities according to the first DRX configuration during that time period. The communication manager 1120 may be capable of, configured to, or operable to support components for monitoring the second set of WUS monitoring opportunities according to the second DRX configuration during that time period.

[0203] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 can support technologies that enable various benefits such as improved communication reliability, reduced latency, improved user experience associated with reduced processing, reduced power consumption, more efficient use of communication resources, improved coordination between devices, longer battery life, and improved utilization of processing power.

[0204] 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 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 the DRX configuration for WUS monitoring 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.

[0205] Figure 12A block diagram 1200 of a device 1205 supporting DRX configurations for WUS monitoring according to one or more aspects of this disclosure is shown. In some examples, the multiple DRX configurations may be multiple CDRX configurations, multiple iDRX configurations, or any combination thereof. 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, and communication manager 1220), may include at least one processor that can 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).

[0206] 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.

[0207] 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.

[0208] The communication manager 1220, receiver 1210, transmitter 1215, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of DRX configuration for WUS monitoring as described herein. For example, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

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

[0210] Additionally or alternatively, the communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., 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 a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0211] 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 in combination with the receiver 1210, the transmitter 1215, or both to acquire information, output information, or perform various other operations as described herein.

[0212] The communication manager 1220 may support wireless communication according to examples disclosed herein. For example, the communication manager 1220 may be capable of, configured to, or operable to support components for outputting control signaling indicating multiple DRX configurations for a UE, wherein the multiple DRX configurations include a first DRX configuration associated with a first set of WUS monitoring times for WUS monitoring and a second DRX configuration associated with a second set of WUS monitoring times, and wherein both the first and second DRX configurations are active during a time period. The communication manager 1220 may be capable of, configured to, or operable to support components for outputting a first WUS during a first WUS monitoring time included in the first set of WUS monitoring times during that time period. The communication manager 1220 may be capable of, configured to, or operable to support components for outputting a second WUS during a second WUS monitoring time included in the second set of WUS monitoring times during that time period.

[0213] 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 that enable various advantages such as reduced processing, lower power consumption, and more efficient use of communication resources.

[0214] Figure 13 A block diagram 1300 of a device 1305 supporting DRX configurations for WUS monitoring according to one or more aspects of this disclosure is shown. In some examples, the multiple DRX configurations may be multiple CDRX configurations, multiple iDRX configurations, or any combination thereof. 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, and 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).

[0215] 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.

[0216] 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.

[0217] Device 1305 or its various components may be examples of parts for performing various aspects of DRX configuration for WUS monitoring as described herein. For example, communication manager 1320 may include control signaling communication component 1325, WUS communication 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 in combination with receiver 1310, transmitter 1315, or both to acquire information, output information, or perform various other operations as described herein.

[0218] Communication manager 1320 may support wireless communication according to examples disclosed herein. Control signaling communication component 1325 is capable of, configured to, or operable to support components for outputting control signaling indicating multiple DRX configurations for the UE, wherein the multiple DRX configurations include a first DRX configuration associated with a first set of WUS monitoring times for WUS monitoring and a second DRX configuration associated with a second set of WUS monitoring times, and wherein both the first and second DRX configurations are active during the time period. WUS communication component 1330 is capable of, configured to, or operable to support components for outputting a first WUS during the first WUS monitoring time period included in the first set of WUS monitoring time periods. WUS communication component 1330 is capable of, configured to, or operable to support components for outputting a second WUS during the second WUS monitoring time period included in the second set of WUS monitoring time periods.

[0219] Figure 14 A block diagram 1400 is shown of a communication manager 1420 supporting DRX configurations for WUS monitoring according to one or more aspects of this disclosure. In some examples, the multiple DRX configurations may be multiple CDRX configurations, multiple iDRX configurations, or any combination thereof. 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 DRX configurations for WUS monitoring as described herein. For example, the communication manager 1420 may include a control signaling communication component 1425, a WUS communication component 1430, or any combination thereof. These components, or each of their 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), and such communication may include communication within the protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0220] Communication manager 1420 may support wireless communication according to examples disclosed herein. Control signaling communication component 1425 is capable of, configured to, or operable to support components for outputting control signaling indicating multiple DRX configurations for the UE, wherein the multiple DRX configurations include a first DRX configuration associated with a first set of WUS monitoring times for WUS monitoring and a second DRX configuration associated with a second set of WUS monitoring times, and wherein both the first and second DRX configurations are active during the time period. WUS communication component 1430 is capable of, configured to, or operable to support components for outputting a first WUS during a first WUS monitoring time included in the first set of WUS monitoring times during the time period. In some examples, WUS communication component 1430 is capable of, configured to, or operable to support components for outputting a second WUS during a second WUS monitoring time included in the second set of WUS monitoring times during the time period.

[0221] In some examples, a first set of WUS monitoring times associated with a first DRX configuration has a first periodicity, and a second set of WUS monitoring times associated with a second DRX configuration has a second periodicity, which is different from the first periodicity.

[0222] In some examples, the timeline for a first set of WUS monitoring moments associated with a first DRX configuration is based on a first timing offset relative to a reference time, and the timeline for a second set of WUS monitoring moments associated with a second DRX configuration is based on a second timing offset relative to a reference time, the second timing offset being different from the first timing offset.

[0223] In some examples, a first set of WUS monitoring events associated with a first DRX configuration is associated with a first timer duration, and a second set of WUS monitoring events associated with a second DRX configuration is associated with a second timer duration, which is different from the first timer duration.

[0224] In some examples, the first timer duration and the second timer duration are used for the same type of timer, which includes inactive timers, monitoring duration timers, active duration timers, offset timers, or retransmission timers.

[0225] In some examples, the WUS monitoring timings of a first set associated with a first DRX configuration each have a first duration, and the WUS monitoring timings of a second set associated with a second DRX configuration each have a second duration, which differs from the first duration.

[0226] In some examples, monitoring WUS monitoring times within a first set of WUS monitoring times associated with a first DRX configuration or a second set of WUS monitoring times associated with a second DRX configuration may include monitoring a portion of the WUS monitoring times based on the duty cycle, or may include monitoring the entire WUS monitoring times.

[0227] In some examples, a first set of WUS monitoring events associated with a first DRX configuration is associated with a first WUS index, and a second set of WUS monitoring events associated with a second DRX configuration is associated with a second WUS index, which is different from the first WUS index.

[0228] In some examples, a first set of WUS monitoring events associated with a first DRX configuration is associated with a first transmission configuration indication state, and a second set of WUS monitoring events associated with a second DRX configuration is associated with a second transmission configuration indication state, which is different from the first transmission configuration indication state.

[0229] In some examples, a first set of WUS monitoring times associated with a first DRX configuration is associated with a first WUS bandwidth, and a second set of WUS monitoring times associated with a second DRX configuration is associated with a second WUS bandwidth, which is different from the first WUS bandwidth.

[0230] In some examples, a first set of WUS monitoring events associated with a first DRX configuration is associated with a first priority, and a second set of WUS monitoring events associated with a second DRX configuration is associated with a second priority, which is different from the first priority.

[0231] In some examples, multiple DRX configurations also include a third DRX configuration associated with a third set of WUS monitoring times. In some examples, the third DRX configuration is also active during that time period.

[0232] In some examples, the first set of WUS monitoring opportunities and the second set of WUS monitoring opportunities are associated with the same frequency range.

[0233] In some examples, the WUS communication component 1430 is capable of, configured to, or operable to support components for outputting second control signaling that activates the first DRX configuration and the second DRX configuration during that time period.

[0234] In some examples, the WUS communication component 1430 is capable of, configured to, or operable to support components for outputting third control signaling for disabling a first DRX configuration, a second DRX configuration, or both during a second time period after that time period.

[0235] In some examples, a first DRX configuration is used for a first service associated with a first service mode, and one or more parameters for a first set of WUS monitoring timing are based on the first service mode. In some examples, a second DRX configuration is used for a second service associated with a second service mode, and one or more parameters for a second set of WUS monitoring timing are based on a second service mode that differs from the first service mode.

[0236] Figure 15 A diagram of a system 1500 including a device 1505 supporting DRX configurations for WUS monitoring, according to one or more aspects of this disclosure, is shown. In some examples, the multiple DRX configurations may be multiple CDRX configurations, multiple iDRX configurations, or any combination thereof. 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 one or more network entities 105, one or more UEs 115, or any combination thereof, and this 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, an antenna 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, or electrically) via one or more buses (e.g., bus 1540).

[0237] 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 be configured to couple to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or 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).

[0238] At least one memory 1525 may include RAM, ROM, or any combination thereof. At least one memory 1525 may store computer-readable, computer-executable code 1530 including instructions that, when executed by one or more of the at least one processor 1535, cause the device 1505 to perform the various functions described herein. The code 1530 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1530 may not be directly executable by one of the at least one processor 1535, but may enable the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1525 may contain a BIOS, etc., that 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).

[0239] At least one processor 1535 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1535 may be configured to operate a memory array using a memory controller. 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 supporting DRX configuration for WUS monitoring). For example, device 1505 or components of device 1505 may include at least one processor 1535 and at least one memory 1525 coupled to one or more processors in at least one processor 1535, wherein at least one processor 1535 and at least one memory 1525 are configured to perform the various functions described herein. 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. 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 at least one memory 1525). 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 can refer to a system 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 those inputs to produce, generate, or obtain outputs. 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 the 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.

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

[0241] 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 by client devices such as one or more UEs 115. In some examples, the communication manager 1520 can manage communication with other network entities 105 and may include a controller or scheduler for cooperating with other network entities 105 to control communication with UE 115. 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.

[0242] The communication manager 1520 may support wireless communication according to examples disclosed herein. For example, the communication manager 1520 may be capable of, configured to, or operable to support components for outputting control signaling indicating multiple DRX configurations for a UE, wherein the multiple DRX configurations include a first DRX configuration associated with a first set of WUS monitoring times for WUS monitoring and a second DRX configuration associated with a second set of WUS monitoring times, and wherein both the first and second DRX configurations are active during a time period. The communication manager 1520 may be capable of, configured to, or operable to support components for outputting a first WUS during a first WUS monitoring time included in the first set of WUS monitoring times during that time period. The communication manager 1520 may be capable of, configured to, or operable to support components for outputting a second WUS during a second WUS monitoring time included in the second set of WUS monitoring times during that time period.

[0243] By including or configuring a communication manager 1520 according to an example as described herein, device 1505 can support technologies that enable various benefits such as improved communication reliability, reduced latency, improved user experience associated with reduced processing, reduced power consumption, more efficient use of communication resources, improved coordination between devices, longer battery life, and improved utilization of processing power.

[0244] In some examples, the communication manager 1520 may be configured to use or otherwise 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 of at least one processor 1535 to cause device 1505 to perform various aspects of the DRX configuration for WUS monitoring 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.

[0245] Figure 16 A flowchart illustrating a method 1600 for supporting DRX configurations for WUS monitoring, according to various aspects of this disclosure, is shown. In some examples, the multiple DRX configurations may be multiple CDRX configurations, multiple iDRX configurations, or any combination thereof. 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.

[0246] At 1605, the method may include receiving control signaling indicating a plurality of DRX configurations for the UE, wherein the plurality of DRX configurations include a first DRX configuration associated with a first set of WUS monitoring times and a second DRX configuration associated with a second set of WUS monitoring times, and wherein both the first and second DRX configurations are active during a time period. The operation of block 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1605 may be provided by reference to [reference needed]. Figure 10 The control signaling receiving component 1025 described is executed.

[0247] At 1610, the method may include: during the time period, monitoring a first set of WUS monitoring timings according to a first DRX configuration. The operation of box 1610 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1610 may be provided by reference to [reference needed]. Figure 10 The WUS monitoring component 1030 described is executed.

[0248] At 1615, the method may include: during the time period, monitoring a second set of WUS monitoring timings according to a second DRX configuration. The operation of box 1615 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1615 may be provided by reference to [reference needed]. Figure 10 The WUS monitoring component 1030 described is executed.

[0249] Figure 17 A flowchart illustrating method 1700 for supporting DRX configurations for WUS monitoring according to various aspects of this disclosure is shown. In some examples, the multiple DRX configurations may be multiple CDRX configurations, multiple iDRX configurations, or any combination thereof. 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.

[0250] At 1705, the method may include outputting control signaling indicating multiple DRX configurations for the UE, wherein the multiple DRX configurations include a first DRX configuration associated with a first set of WUS monitoring times for WUS monitoring and a second DRX configuration associated with a second set of WUS monitoring times, and wherein both the first and second DRX configurations are active during the time period. The operation of block 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1705 may be provided by reference to [reference]. Figure 14 The control signaling communication component 1425 described herein is executed.

[0251] At 1710, the method may include: during the time period, outputting a first WUS during a first WUS monitoring time included in a first set of WUS monitoring times. The operation of block 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1710 may be as referenced... Figure 14 The WUS communication component 1430 described is executed.

[0252] At 1715, the method may include: during the time period, outputting a second WUS during a second WUS monitoring time period included in a second set of WUS monitoring times. The operation of box 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1715 may be derived from references... Figure 14 The WUS communication component 1430 described is executed.

[0253] The following provides an overview of the various aspects of this disclosure:

[0254] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving control signaling indicating a plurality of DRX configurations for the UE, wherein the plurality of DRX configurations include a first DRX configuration associated with a first set of wake-up signal monitoring opportunities and a second DRX configuration associated with a second set of wake-up signal monitoring opportunities, and wherein the first DRX configuration and the second DRX configuration are both active during a time period; during the time period, monitoring the first set of wake-up signal monitoring opportunities according to the first DRX configuration; and during the time period, monitoring the second set of wake-up signal monitoring opportunities according to the first DRX configuration.

[0255] Aspect 2: According to the method of aspect 1, wherein the first set of wake-up signal monitoring times associated with the first DRX configuration has a first periodicity, and the second set of wake-up signal monitoring times associated with the second DRX configuration has a second periodicity, the second periodicity being different from the first periodicity.

[0256] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the timeline of the first set of wake-up signal monitoring timings associated with the first DRX configuration is at least partially based on a first timing offset relative to a reference time, and the timeline of the second set of wake-up signal monitoring timings associated with the second DRX configuration is at least partially based on a second timing offset relative to the reference time, the second timing offset being different from the first timing offset.

[0257] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the first set of wake-up signal monitoring timings associated with the first DRX configuration is associated with a first timer duration, and the second set of wake-up signal monitoring timings associated with the second DRX configuration is associated with a second timer duration, the second timer duration being different from the first timer duration.

[0258] Aspect 5: According to the method described in aspect 4, wherein the first timer duration and the second timer duration are used for the same type of timer, the timer of the same type including an inactive timer, a monitoring duration timer, an active duration timer, an offset timer, an uplink hybrid automatic repeat request timer, a downlink hybrid automatic repeat request timer, an uplink retransmission timer, or a downlink retransmission timer.

[0259] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the wake-up signal monitoring timing of the first set associated with the first DRX configuration each has a first duration, and the wake-up signal monitoring timing of the second set associated with the second DRX configuration each has a second duration, the second duration being different from the first duration.

[0260] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the first set of wake-up signal monitoring opportunities associated with the first DRX configuration is associated with a first wake-up signal index, and the second set of wake-up signal monitoring opportunities associated with the second DRX configuration is associated with a second wake-up signal index, the second wake-up signal index being different from the first wake-up signal index; the first set of wake-up signal monitoring opportunities includes monitoring one or more first wake-up signals corresponding to the first wake-up signal index; and the second set of wake-up signal monitoring opportunities includes monitoring one or more second wake-up signals corresponding to the second wake-up signal index.

[0261] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the first set of wake-up signal monitoring timings associated with the first DRX configuration is associated with a first transmission configuration indication state, and the second set of wake-up signal monitoring timings associated with the second DRX configuration is associated with a second transmission configuration indication state, the second transmission configuration indication state being different from the first transmission configuration indication state.

[0262] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the first set of wake-up signal monitoring times associated with the first DRX configuration is associated with a first wake-up signal bandwidth, and the second set of wake-up signal monitoring times associated with the second DRX configuration is associated with a second wake-up signal bandwidth, the second wake-up signal bandwidth being different from the first wake-up signal bandwidth.

[0263] Aspect 10: The method according to any one of Aspects 1 to 9, the method further comprising: identifying a first wake-up signal monitoring moment included in the first set of wake-up signal monitoring moments associated with the first DRX configuration that overlaps temporally with a second wake-up signal monitoring moment included in the second set of wake-up signal monitoring moments associated with the second DRX configuration; and monitoring the first wake-up signal monitoring moment at least in part based on the priority of the first wake-up signal monitoring moment being higher than the priority of the second wake-up signal monitoring moment, while suppressing the monitoring of the second wake-up signal monitoring moment.

[0264] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the plurality of DRX configurations further includes a third DRX configuration associated with a third set of wake-up signal monitoring timings, and the third DRX configuration is also active during the time period.

[0265] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the first set of timings and the second set of timings are associated with the same frequency range.

[0266] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the UE includes a first radio component and a second radio component associated with a lower active power consumption than the first radio component, and at least one of the first set of timings and the second set of timings is performed via the second radio component.

[0267] Aspect 14: The method according to aspect 13, the method further comprising: receiving a wake-up signal via the second radio component; and waking up the first radio component in response to receiving the wake-up signal via the second radio component.

[0268] Aspect 15: The method according to any one of aspects 1 to 14, the method further comprising: receiving second control signaling that activates the first DRX configuration and the second DRX configuration during the time period.

[0269] Aspect 16: The method according to any one of Aspects 1 to 15, the method further comprising: receiving a third control signaling that disables the first DRX configuration, the second DRX configuration, or both during a second time period, the second time period being after the time period.

[0270] Aspect 17: The method according to any one of Aspects 1 to 16, wherein the first DRX configuration is used for a first service associated with a first service mode, and one or more parameters of the first set for timing are at least partially based on the first service mode; and the second DRX configuration is used for a second service associated with a second service mode, and one or more parameters of the second set for timing are at least partially based on the second service mode, which is different from the first service mode.

[0271] Aspect 18: A method for wireless communication at a network entity, the method comprising: outputting control signaling indicating a plurality of DRX configurations for a UE, wherein the plurality of DRX configurations include a first DRX configuration associated with a first set of wake-up signal monitoring times for wake-up signal monitoring and a second DRX configuration associated with a second set of wake-up signal monitoring times, and wherein the first DRX configuration and the second DRX configuration are both active during a time period; during the time period, outputting a first wake-up signal during a first wake-up signal monitoring time included in the first set of wake-up signal monitoring times; and during the time period, outputting a second wake-up signal during a second wake-up signal monitoring time included in the second set of wake-up signal monitoring times.

[0272] Aspect 19: According to the method of aspect 18, wherein the first set of wake-up signal monitoring timings associated with the first DRX configuration has a first periodicity, and the second set of wake-up signal monitoring timings associated with the second DRX configuration has a second periodicity, the second periodicity being different from the first periodicity.

[0273] Aspect 20: The method according to any one of Aspects 18 to 19, wherein the timeline of the first set of wake-up signal monitoring timings associated with the first DRX configuration is at least partially based on a first timing offset relative to a reference time, and the timeline of the second set of wake-up signal monitoring timings associated with the second DRX configuration is at least partially based on a second timing offset relative to the reference time, the second timing offset being different from the first timing offset.

[0274] Aspect 21: The method according to any one of Aspects 18 to 20, wherein the first set of wake-up signal monitoring timings associated with the first DRX configuration is associated with a first timer duration, and the second set of wake-up signal monitoring timings associated with the second DRX configuration is associated with a second timer duration, the second timer duration being different from the first timer duration.

[0275] Aspect 22: The method according to any one of Aspects 18 to 21, wherein the first timer duration and the second timer duration are for the same type of timer, the timer of which includes an inactive timer, a monitoring duration timer, an active duration timer, an offset timer, or a retransmission timer.

[0276] Aspect 23: The method according to any one of Aspects 18 to 22, wherein the wake-up signal monitoring timing of the first set associated with the first DRX configuration each has a first duration, and the wake-up signal monitoring timing of the second set associated with the second DRX configuration each has a second duration, the second duration being different from the first duration.

[0277] Aspect 24: The method according to any one of Aspects 18 to 23, wherein the first set of wake-up signal monitoring times associated with the first DRX configuration is associated with a first wake-up signal index, and the second set of wake-up signal monitoring times associated with the second DRX configuration is associated with a second wake-up signal index, the second wake-up signal index being different from the first wake-up signal index.

[0278] Aspect 25: The method according to any one of Aspects 18 to 24, wherein the first set of wake-up signal monitoring timings associated with the first DRX configuration is associated with a first transmission configuration indication state, and the second set of wake-up signal monitoring timings associated with the second DRX configuration is associated with a second transmission configuration indication state, the second transmission configuration indication state being different from the first transmission configuration indication state.

[0279] Aspect 26: The method according to any one of Aspects 18 to 25, wherein the first set of wake-up signal monitoring times associated with the first DRX configuration is associated with a first wake-up signal bandwidth, and the second set of wake-up signal monitoring times associated with the second DRX configuration is associated with a second wake-up signal bandwidth, the second wake-up signal bandwidth being different from the first wake-up signal bandwidth.

[0280] Aspect 27: The method according to any one of Aspects 18 to 26, wherein the first set of wake-up signal monitoring timings associated with the first DRX configuration is associated with a first priority, and the second set of wake-up signal monitoring timings associated with the second DRX configuration is associated with a second priority, the second priority being different from the first priority.

[0281] Aspect 28: The method according to any one of aspects 18 to 27, wherein the plurality of DRX configurations further includes a third DRX configuration associated with a third set of wake-up signal monitoring timings, and the third DRX configuration is also active during the time period.

[0282] Aspect 29: The method according to any one of aspects 18 to 28, wherein the first set of timings and the second set of timings are associated with the same frequency range.

[0283] Aspect 30: The method according to any one of aspects 18 to 29, the method further comprising: outputting a second control signaling that activates the first DRX configuration and the second DRX configuration during the time period.

[0284] Aspect 31: The method according to any one of Aspects 18 to 30, the method further comprising: outputting a third control signaling that disables the first DRX configuration, the second DRX configuration, or both during a second time period after the second time period.

[0285] Aspect 32: The method according to any one of Aspects 18 to 31, wherein the first DRX configuration is used for a first service associated with a first service mode, and one or more parameters of the first set for timing are at least partially based on the first service mode; and the second DRX configuration is used for a second service associated with a second service mode, and one or more parameters of the second set for timing are at least partially based on the second service mode, which is different from the first service mode.

[0286] Aspect 33: A UE for wireless communication, the UE 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 UE to perform a method according to any one of aspects 1 to 17.

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

[0288] 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 17.

[0289] 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 18 to 32.

[0290] 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 18 to 32.

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

[0292] It should be noted that the methods described herein describe possible specific implementations, and the 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.

[0293] 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.

[0294] The information and signals described herein can be represented using any of a variety of different techniques and methods. 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.

[0295] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, 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 cooperating 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 functions or operations individually or jointly.

[0296] 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 various portions distributed such that the functions are implemented in different physical locations.

[0297] 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.

[0298] 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".

[0299] 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” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as 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” can refer to any or all of the one or more components. For example, reference to "one or more components" in subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0300] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. 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, building, and other similar actions.

[0301] 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 numeral and a second reference numeral to differentiate them. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0302] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all implementable or within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," and 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 instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0303] 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. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: The system receives control signaling indicating multiple discontinuous reception (DRX) configurations for the UE, wherein the multiple DRX configurations include a first DRX configuration associated with a first set of wake-up signal monitoring times and a second DRX configuration associated with a second set of wake-up signal monitoring times, and wherein the first DRX configuration and the second DRX configuration are both active during the time period; During the said time period, the first set of wake-up signal monitoring timings is monitored according to the first DRX configuration; as well as During the said time period, the second set of wake-up signal monitoring timing is monitored according to the second DRX configuration.

2. The UE of claim 1, wherein the first set of wake-up signal monitoring times associated with the first DRX configuration has a first periodicity, and the second set of wake-up signal monitoring times associated with the second DRX configuration has a second periodicity, the second periodicity being different from the first periodicity.

3. The UE of claim 1, wherein the timeline of the first set of wake-up signal monitoring timings associated with the first DRX configuration is at least partially based on a first timing offset relative to a reference time, and the timeline of the second set of wake-up signal monitoring timings associated with the second DRX configuration is at least partially based on a second timing offset relative to the reference time, the second timing offset being different from the first timing offset.

4. The UE of claim 1, wherein the first set of wake-up signal monitoring times associated with the first DRX configuration is associated with a first timer duration, and the second set of wake-up signal monitoring times associated with the second DRX configuration is associated with a second timer duration, the second timer duration being different from the first timer duration.

5. The UE according to claim 4, wherein the first timer duration and the second timer duration are used for the same type of timer, the timer of the type including an inactive timer, a monitoring duration timer, an active duration timer, an offset timer, an uplink hybrid automatic repeat request timer, a downlink hybrid automatic repeat request timer, an uplink retransmission timer, or a downlink retransmission timer.

6. The UE of claim 1, wherein the wake-up signal monitoring timing of the first set associated with the first DRX configuration each has a first duration, and the wake-up signal monitoring timing of the second set associated with the second DRX configuration each has a second duration, the second duration being different from the first duration.

7. The UE according to claim 1, wherein: The first set of wake-up signal monitoring times associated with the first DRX configuration is associated with a first wake-up signal index, and the second set of wake-up signal monitoring times associated with the second DRX configuration is associated with a second wake-up signal index, which is different from the first wake-up signal index; In order to monitor the first set of wake-up signal monitoring opportunities, the one or more processors can operate individually or jointly to execute the code to cause the UE to monitor one or more first wake-up signals corresponding to the first wake-up signal index; and In order to monitor the second set of wake-up signal monitoring opportunities, the one or more processors can operate individually or jointly to execute the code so that the UE monitors one or more second wake-up signals corresponding to the second wake-up signal index.

8. The UE of claim 1, wherein the first set of wake-up signal monitoring times associated with the first DRX configuration is associated with a first transmission configuration indication state, and the second set of wake-up signal monitoring times associated with the second DRX configuration is associated with a second transmission configuration indication state, the second transmission configuration indication state being different from the first transmission configuration indication state.

9. The UE of claim 1, wherein the first set of wake-up signal monitoring times associated with the first DRX configuration is associated with a first wake-up signal bandwidth, and the second set of wake-up signal monitoring times associated with the second DRX configuration is associated with a second wake-up signal bandwidth, the second wake-up signal bandwidth being different from the first wake-up signal bandwidth.

10. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The first wake-up signal monitoring timing, identified as being included in the first set of wake-up signal monitoring timings associated with the first DRX configuration, overlaps in time with the second wake-up signal monitoring timings included in the second set of wake-up signal monitoring timings associated with the second DRX configuration; and The first wake-up signal monitoring timing is monitored at least in part based on the fact that the first wake-up signal monitoring timing has a higher priority than the second wake-up signal monitoring timing, while the monitoring of the second wake-up signal monitoring timing is suppressed.

11. The UE according to claim 1, wherein: The plurality of DRX configurations also include a third DRX configuration associated with a third set of wake-up signal monitoring timings, and The third DRX configuration was also active during the time period.

12. The UE of claim 1, wherein the first set of wake-up signal monitoring opportunities and the second set of wake-up signal monitoring opportunities are associated with the same frequency range.

13. The UE according to claim 1, wherein: The UE includes a first radio component and a second radio component associated with lower active power consumption than the first radio component, and The one or more processors can operate individually or jointly to execute the code so that the UE monitors at least one of the first set of wake-up signal monitoring opportunities and the second set of wake-up signal monitoring opportunities via the second radio component.

14. The UE of claim 13, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive a wake-up signal via the second radio component; and The first radio component is woken up in response to receiving the wake-up signal via the second radio component.

15. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive a second control signaling that activates the first DRX configuration and the second DRX configuration during the time period.

16. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive a third control signaling that disables the first DRX configuration, the second DRX configuration, or both during a second time period after the second time period.

17. The UE according to claim 1, wherein: The first DRX configuration is used for a first service associated with a first service mode, and one or more parameters of the first set used for wake-up signal monitoring timing are at least partially based on the first service mode; and The second DRX configuration is used for a second service associated with a second service mode, and one or more parameters of the second set used for wake-up signal monitoring timing are at least partially based on the second service mode, which is different from the first service mode.

18. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: The output indicates control signaling for multiple discontinuous reception (DRX) configurations for user equipment (UE), wherein the multiple DRX configurations include a first DRX configuration associated with a first set of wake-up signal monitoring timings for wake-up signal monitoring and a second DRX configuration associated with a second set of wake-up signal monitoring timings, and wherein the first DRX configuration and the second DRX configuration are active during the time period; During the time period, a first wake-up signal is output during a first wake-up signal monitoring period included in the first set of wake-up signal monitoring periods; as well as During the time period, a second wake-up signal is output during a second wake-up signal monitoring period included in the second set of wake-up signal monitoring periods.

19. The network entity of claim 18, wherein the first set of wake-up signal monitoring times associated with the first DRX configuration has a first periodicity, and the second set of wake-up signal monitoring times associated with the second DRX configuration has a second periodicity, the second periodicity being different from the first periodicity.

20. The network entity of claim 18, wherein the timeline of the first set of wake-up signal monitoring timings associated with the first DRX configuration is at least partially based on a first timing offset relative to a reference time, and the timeline of the second set of wake-up signal monitoring timings associated with the second DRX configuration is at least partially based on a second timing offset relative to the reference time, the second timing offset being different from the first timing offset.

21. The network entity of claim 18, wherein the first set of wake-up signal monitoring times associated with the first DRX configuration is associated with a first timer duration, and the second set of wake-up signal monitoring times associated with the second DRX configuration is associated with a second timer duration, the second timer duration being different from the first timer duration.

22. The network entity of claim 21, wherein the first timer duration and the second timer duration are for the same type of timer, the timer type including an inactive timer, a monitoring duration timer, an active duration timer, an offset timer, or a retransmission timer.

23. The network entity of claim 18, wherein the wake-up signal monitoring timing of the first set associated with the first DRX configuration each has a first duration, and the wake-up signal monitoring timing of the second set associated with the second DRX configuration each has a second duration, the second duration being different from the first duration.

24. The network entity of claim 18, wherein the first set of wake-up signal monitoring times associated with the first DRX configuration is associated with a first wake-up signal index, and the second set of wake-up signal monitoring times associated with the second DRX configuration is associated with a second wake-up signal index, the second wake-up signal index being different from the first wake-up signal index.

25. The network entity of claim 18, wherein the first set of wake-up signal monitoring times associated with the first DRX configuration is associated with a first transmission configuration indication state, and the second set of wake-up signal monitoring times associated with the second DRX configuration is associated with a second transmission configuration indication state, the second transmission configuration indication state being different from the first transmission configuration indication state.

26. The network entity of claim 18, wherein the first set of wake-up signal monitoring times associated with the first DRX configuration is associated with a first wake-up signal bandwidth, and the second set of wake-up signal monitoring times associated with the second DRX configuration is associated with a second wake-up signal bandwidth, the second wake-up signal bandwidth being different from the first wake-up signal bandwidth.

27. The network entity of claim 18, wherein the first set of wake-up signal monitoring times associated with the first DRX configuration is associated with a first priority, and the second set of wake-up signal monitoring times associated with the second DRX configuration is associated with a second priority, the second priority being different from the first priority.

28. The network entity according to claim 18, wherein: The first DRX configuration is used for a first service associated with a first service mode, and one or more parameters of the first set used for wake-up signal monitoring timing are at least partially based on the first service mode; and The second DRX configuration is used for a second service associated with a second service mode, and one or more parameters of the second set used for wake-up signal monitoring timing are at least partially based on the second service mode, which is different from the first service mode.

29. A method for conducting wireless communication at a user equipment (UE), the method comprising: The system receives control signaling indicating multiple discontinuous reception (DRX) configurations for the UE, wherein the multiple DRX configurations include a first DRX configuration associated with a first set of wake-up signal monitoring times and a second DRX configuration associated with a second set of wake-up signal monitoring times, and wherein the first DRX configuration and the second DRX configuration are both active during the time period; During the said time period, the first set of wake-up signal monitoring timings is monitored according to the first DRX configuration; as well as During the said time period, the second set of wake-up signal monitoring timing is monitored according to the second DRX configuration.

30. A method for conducting wireless communication at a network entity, the method comprising: The output indicates control signaling for multiple discontinuous reception (DRX) configurations for user equipment (UE), wherein the multiple DRX configurations include a first DRX configuration associated with a first set of wake-up signal monitoring timings for wake-up signal monitoring and a second DRX configuration associated with a second set of wake-up signal monitoring timings, and wherein the first DRX configuration and the second DRX configuration are active during the time period; During the time period, a first wake-up signal is output during a first wake-up signal monitoring period included in the first set of wake-up signal monitoring periods; as well as During the time period, a second wake-up signal is output during a second wake-up signal monitoring period included in the second set of wake-up signal monitoring periods.

Images