Selective wake-up signal monitoring for discontinuous reception

Abstract

This disclosure provides techniques for wireless communication. One method includes: configuring a plurality of sets of Wake-up Signal (WUS) monitoring instances, wherein the plurality of sets of WUS monitoring instances are associated with a plurality of Discontinuous Reception (DRX) on-states, wherein each set of WUS monitoring instances in the plurality of sets of WUS monitoring instances includes a plurality of WUS monitoring instances; receiving a first WUS before a first DRX on-state in the plurality of DRX on-states, wherein the first WUS includes: an indication of whether to start an on-state duration timer for the first DRX on-state; and an indication of one or more WUS monitoring instances in the plurality of WUS monitoring instances; and monitoring at least one additional WUS in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances in the plurality of sets of WUS monitoring instances, wherein at least one set of WUS monitoring instances is associated with at least one DRX on-state after the first DRX on-state.

Description

Technical Field

[0001] Various aspects of this disclosure relate to wireless communications, and more specifically to techniques for selective wake-up signal (WUS) monitoring for discontinuous reception (DRX). Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, broadcasting, or other similar services. These wireless communication systems may employ multiple access technologies that enable communication with several users by sharing available wireless communication system resources.

[0003] Despite significant technological advancements in wireless communication systems over the years, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and receivers. Therefore, there is a continuous expectation for improving the technical performance of wireless communication systems, including, for example: improving communication speed and data carrying capacity; improving the efficiency of shared communication media; reducing the power used by transmitters and receivers during communication; improving the reliability of wireless communication; avoiding redundant transmission and / or reception and related processing; improving the coverage area of ​​wireless communication; increasing the number and types of devices that can access the wireless communication system; increasing the ability of different types of devices to communicate with each other; and increasing the number and types of available wireless communication media. Therefore, there is a need for further improvements to wireless communication systems to overcome the aforementioned technical challenges and other obstacles. Summary of the Invention

[0004] One aspect provides a method for wireless communication by a device. The method includes: receiving from a network entity a configuration of a plurality of sets of WUS monitoring instances, wherein the plurality of sets of Wake-up Signal (WUS) monitoring instances are associated with a plurality of Discontinuous Reception (DRX) on-states, wherein each set of WUS monitoring instances in the plurality of sets of WUS monitoring instances includes a plurality of WUS monitoring instances; receiving from the network entity a first WUS prior to a first DRX on-state in the plurality of DRX on-states, wherein the first WUS includes: an indication of whether to initiate an on-state duration timer for the first DRX on-state; and an indication of one or more WUS monitoring instances in the plurality of WUS monitoring instances; and monitoring at least one additional WUS in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances in the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX on-state following the first DRX on-state.

[0005] Another aspect provides a method for wireless communication by a device. The method includes: transmitting to the device a configuration of a plurality of sets of WUS monitoring instances, wherein the plurality of sets of WUS monitoring instances are associated with a plurality of DRX enable cycles, wherein each set of the plurality of sets of WUS monitoring instances includes a plurality of WUS monitoring instances; transmitting to the device a first WUS prior to a first DRX enable cycle in the plurality of DRX enable cycles, wherein the first WUS includes: an indication of whether to start an enable duration timer for the first DRX enable cycle; and an indication of one or more WUS monitoring instances in the plurality of WUS monitoring instances; and transmitting to the device at least one additional WUS in at least one of the one or more WUS monitoring instances in at least one set of the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX enable cycle following the first DRX enable cycle.

[0006] Other aspects provide: one or more means capable of operating to, configured to, or otherwise adapted to perform any portion of any method described herein (e.g., such that performance can be implemented by only one means or in a distributed manner across multiple means); one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of the one or more means, cause the one or more means to perform any portion of any method described herein (e.g., such that instructions can be included in only one computer-readable medium or in a distributed manner across multiple computer-readable media, such that instructions can be executed by only one processor or by multiple processors in a distributed manner, such that in the one or more means...). Each device may include one or more processors, and / or enable execution to be performed by only one device or in a distributed manner across multiple devices; one or more computer program products embodied on one or more computer-readable storage media including code for performing any part of any method described herein (e.g., enabling the code to be stored in only one computer-readable medium or in a distributed manner across computer-readable media); and / or one or more devices including one or more components for performing any part of any method described herein (e.g., enabling execution to be performed by only one device or by multiple devices in a distributed manner). By way of example, a device may include a processing system, a device having a processing system, or a processing system cooperating via one or more networks. A device may include: one or more memories; and one or more processors configured to enable the device to perform any part of any method described herein. In some examples, one or more processors may be pre-configured to perform the various functions or operations described herein without being configured by software.

[0007] For illustrative purposes, the following description and figures illustrate certain features. Attached Figure Description

[0008] The accompanying drawings depict certain features of the various aspects described herein and should not be considered as limiting the scope of this disclosure.

[0009] Figure 1 An example wireless communication network is depicted.

[0010] Figure 2 An example decomposed base station architecture is described.

[0011] Figure 3 Various aspects of the example base station and example user equipment (UE) are described.

[0012] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various example aspects of data structures used in wireless communication networks are described.

[0013] Figure 5 An example wireless communication system is described, which conveys instructions for monitoring instances of wake-up signals (WUS) to be monitored.

[0014] Figure 6 An example wireless communication system is depicted that conveys a request to report a prediction corresponding to a WUS monitoring instance.

[0015] Figure 7A , Figure 7B and Figure 7C Various example aspects of communication with discontinuous reception (DRX) are described.

[0016] Figure 8 An example of a communication system with DRX is depicted.

[0017] Figure 9 An example of a DRX communication system with time beam prediction is depicted.

[0018] Figure 10 It describes the process flow for communication between network entities and devices in a network.

[0019] Figure 11 It describes the process flow for communication between network entities and devices in a network.

[0020] Figure 12 A method for wireless communication is described.

[0021] Figure 13 Another method for wireless communication is described.

[0022] Figure 14 Another method for wireless communication is described.

[0023] Figure 15 Another method for wireless communication is described.

[0024] Figure 16 Various aspects of the example communication device are described.

[0025] Figure 17 Various aspects of the example communication device are described. Detailed Implementation

[0026] Various aspects of this disclosure provide apparatus, methods, processing systems, and computer-readable media for indicating wake-up signal (WUS) monitoring instances to be monitored and / or requesting predictions corresponding to WUS monitoring instances via WUS. For example, some aspects provide techniques for indicating and / or requesting time beam predictions via WUS for discontinuous reception (DRX). Specifically, some aspects provide techniques for a network entity to transmit a first WUS to a device prior to a first DRX activation period associated with a first WUS, wherein the first WUS includes at least an indication of one or more WUS monitoring instances (e.g., one or more search space sets, one or more downlink channel monitoring opportunities (MOs), etc.) for the device to monitor at least one additional WUS in at least one of the one or more WUS monitoring instances, wherein the at least one additional WUS is associated with at least one DRX activation period following the first DRX activation period. In some aspects, the network entity may be configured to transmit multiple sets of WUS monitoring instances prior to transmitting the first WUS, and the multiple sets of WUS monitoring instances may be associated with multiple DRX activation periods, wherein each set of WUS monitoring instances (e.g., in the multiple sets of WUS monitoring instances) includes multiple WUS monitoring instances. Therefore, the device can monitor at least one additional WUS in at least one WUS monitoring instance in at least one set of WUS monitoring instances in a plurality of sets of WUS monitoring instances, wherein at least one set of WUS monitoring instances is associated with at least one DRX activation cycle after the first DRX activation cycle.

[0027] A wireless communication system may include multiple devices (e.g., terminals, network devices, and other devices) that exchange data, control information, reference signals, etc., with each other (e.g., communicate with each other). In some examples, a wireless communication system may typically include or refer to multiple devices employing technologies for wirelessly exchanging information. For example, a wireless communication system may include (e.g., depending on the specific implementation of various wireless communication systems) terminals (e.g., user equipment or user gear (UE)) and network entities (e.g., base stations (BS)) that wirelessly transmit data, control information, reference signals, etc. Devices operating in a wireless communication system may employ various techniques to improve throughput, achieve high data rates, and / or improve the energy efficiency of the wireless communication system. These techniques can allow the wireless communication system to support communication between an increased number of devices, support advanced functionality at various devices, improve the quality of communication between devices, etc.

[0028] As an example described herein, a device may employ DRX operation to reduce power consumption and / or conserve the device's battery. In DRX, the device may periodically alternate between an active mode (e.g., an "on" or wake-up period) and an inactive mode (e.g., an "off," sleep, or idle period) during a DRX enable cycle. During the active mode and the DRX enable cycle, the device may power on at least a portion of its internal circuitry to monitor messages or incoming data. Additionally or alternatively, in the inactive mode, the device may power off at least a portion of its internal circuitry to reduce power consumption (e.g., battery power consumption), and the device is not expected to receive messages or data in the inactive mode. In some examples, DRX may be employed based on parameters configured by the network. For example, network entities may configure timing information (e.g., the duration of wake-up and sleep modes, inactivity timers, retransmission timers, periodicity, etc.) based on semi-static signaling (e.g., Radio Resource Control (RRC) signaling) or dynamic signaling.

[0029] In some respects, DRX can be employed in both idle and connected modes of the device. For example, in idle mode DRX (e.g., paging cycle, paging DRX, etc.), the device periodically wakes up to monitor paging messages during the DRX on cycle, and returns to inactive mode if the paging message is not addressed to the device. For idle mode DRX, the device does not need to be connected to the network. Additionally or alternatively, for connected mode DRX (C-DRX), the device is connected to the network and is actively transmitting or receiving data with network entities. In C-DRX, the device periodically enters inactive mode (e.g., DRX mode) outside the DRX on cycle while maintaining a connection to the network, and enters active mode during the DRX on cycle to monitor the downlink channel for data or messages from network entities. In some respects, in C-DRX, before entering active mode and before the DRX activation cycle, the device can monitor a WUS from a network entity (e.g., outside of DRX active time (such as the DRX activation cycle)), where the WUS indicates whether the device should start an activation duration timer for the DRX activation cycle corresponding to the WUS (e.g., the next DRX activation cycle that occurs after the WUS).

[0030] One or more technical problems arise when a device is configured to monitor WUS from a network entity across multiple WUS monitoring instances (e.g., across multiple beams or beamforming transmissions from a network entity and / or across multiple sets of time-frequency resources). For example, to allow a network entity to sweep multiple transmission beams while transmitting WUS, the device may be configured using WUS detection based on multiple WUS monitoring instances, where resources (e.g., time-frequency resources) associated with different such WUS monitoring instances may correspond to different Transmit Configuration Indicator (TCI) states and / or transmission beams. In some aspects, the network entity may transmit WUS to various devices in different directions within such swept beams, but whether a particular device can detect all or a subset of the configured WUS monitoring instances may depend on the specific implementation at the network entity. Therefore, such transmit beam sweeping may require the device to perform potentially significant radio frequency (RF) on and downlink channel detection work, potentially incurring additional power consumption at the device (e.g., compared to situations where transmit beam sweeping might be less necessary).

[0031] Therefore, the techniques and signaling described herein provide a technical solution for supporting time beam prediction of one or more WUS monitoring instances, which a device can then use to monitor subsequent WUS associated with a corresponding DRX activation period (e.g., after receiving or transmitting a time beam prediction). In some aspects, the time beam prediction of one or more WUS monitoring instances can be determined by a network entity based on historical measurements received from the device (e.g., characteristics of synchronization signals and / or reference signals transmitted by the network entity and received by the device) and / or reports of prediction results associated with one or more WUS monitoring instances received from the device. Additionally or alternatively, the time beam prediction of one or more WUS monitoring instances can be determined by the device based on a request for the device to report one or more predictions corresponding to a plurality of WUS monitoring instances, wherein the plurality of WUS monitoring instances includes at least one or more WUS monitoring instances.

[0032] For a network entity determination of one or more WUS monitoring instances, the network entity may send a first WUS associated with a first DRX activation period, and the first WUS may include indications for one or more WUS monitoring instances for a device, such that the device may then use the one or more indicated WUS monitoring instances to monitor at least one additional WUS following the first WUS. Alternatively or additionally, for a device determination of the one or more WUS monitoring instances, the network entity may send a first WUS associated with the first DRX activation period, but the first WUS may include indications for the device to report one or more predictions corresponding to the plurality of WUS monitoring instances, wherein the device then monitors the one or more WUS monitoring instances based on the one or more predictions to locate the at least one additional WUS.

[0033] For the first WUS, the network entity may configure and indicate multiple sets of WUS monitoring instances associated with multiple DRX activation cycles, and each set of WUS monitoring instances (e.g., in the multiple sets of WUS monitoring instances) may include multiple WUS monitoring instances. Subsequently, the device may receive the first WUS prior to the first DRX activation cycle based on multiple WUS monitoring instances in the first set of the multiple sets of WUS monitoring instances.

[0034] However, instead of monitoring each of the multiple WUS monitoring instances for at least one additional WUS in at least one subsequent set of WUS monitoring instances in a plurality of sets of WUS monitoring instances, the device may limit its monitoring to at least one of one or more WUS monitoring instances indicated in the first WUS and / or determined according to one or more predictions requested in the first WUS, wherein at least one subsequent set of WUS monitoring instances is associated with at least one DRX on-cycle following the first DRX on-cycle.

[0035] The techniques described herein for supporting time-beam prediction of one or more WUS monitoring instances can provide any of a variety of beneficial effects and / or advantages. For example, a device can reduce power consumption by indicating and / or determining one or more WUS monitoring instances from one or more predictions requested in the first WUS for at least one additional WUS monitoring, rather than monitoring each of multiple WUS monitoring instances.

[0036] An introduction to wireless communication networks The techniques and methods described herein can be used in a variety of wireless communication networks. Although aspects herein may be described using terms commonly associated with 3G, 4G, 5G, 6G, and / or other generations of wireless technologies, aspects of this disclosure are equally applicable to other communication systems and standards not explicitly mentioned herein.

[0037] Figure 1 An example of a wireless communication network 100 in which the aspects described herein can be implemented is depicted.

[0038] Generally, wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). Network entities are typically communication devices and / or communication functions performed by communication devices (e.g., user equipment (UE), base station (BS), components of the BS, servers, etc.). Since such communication devices are part of wireless communication network 100 and facilitate wireless communication, they may be referred to as wireless communication devices. For example, various functions of the network and various devices associated with and interacting with the network may be considered network entities. Furthermore, wireless communication network 100 includes terrestrial aspects (also referred to herein as non-terrestrial network entities) and non-terrestrial aspects. Terrestrial aspects include terrestrial network entities such as terrestrial network entities (e.g., BS 102), and non-terrestrial aspects include satellite 140 and / or airborne or spaceborne platforms, which may include onboard network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and UEs.

[0039] In the depicted example, wireless communication network 100 includes BS 102, UE 104 and one or more core networks (such as Evolved Packet Core (EPC) 160 and 5G Core (5GC) network 190) that interoperate to provide communication services over various communication links, including wired and wireless links.

[0040] Figure 1Various example UE 104s are described, which may more generally include: cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players, cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, Internet of Things (IoT) devices, always-on (AON) devices, edge processing devices, data centers, or other similar devices. UE 104 may also be more generally referred to as mobile devices, wireless devices, stations, mobile stations, subscriber stations, mobile subscriber stations, mobile units, subscriber units, wireless units, remote units, remote devices, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, and others.

[0041] BS 102 communicates wirelessly with UE 104 via communication link 120 (e.g., sending or receiving signals to or from UE 104). Communication link 120 between BS 102 and UE 104 may include uplink (UL) transmission (also referred to as reverse link) from UE 104 to BS 102 and / or downlink (DL) transmission (also referred to as forward link) transmission from BS 102 to UE 104. In various aspects, communication link 120 may utilize multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity.

[0042] BS 102 may typically include: Node B, Enhanced Node B (eNB), Next Generation Enhanced Node B (ng-eNB), Next Generation Node B (gNB or gNodeB), access point, transceiver base station, radio base station, radio transceiver, transceiver functionality, transmit / receive point, and / or others. Each of BS 102 provides communication coverage for a corresponding coverage area 110, which may sometimes be referred to as a cell, and in some cases may overlap (e.g., a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macro cell). For example, BS may provide communication coverage for macro cells (covering a relatively large geographic area), pico cells (covering a relatively small geographic area, such as a stadium), femtocells (covering a relatively small geographic area (e.g., a home)), and / or other types of cells.

[0043] Generally, a cell can refer to a portion, partition, or segment of wireless communication coverage served by network entities within a wireless communication network. A cell can have geographical characteristics (such as a geographical coverage area) and radio frequency characteristics (such as time and / or frequency resources dedicated to the cell). For example, multiple cells employing different frequency resources (e.g., bandwidth portions) and / or different time resources can cover a specific geographical coverage area. As another example, a single cell can cover a specific geographical coverage area. In some contexts (e.g., carrier aggregation scenarios and / or multi-connectivity scenarios), the terms "cell" or "serving cell" can refer to or correspond to a specific carrier frequency (e.g., component carrier) used for wireless communication, and "cell group" can refer to or correspond to multiple carriers used for wireless communication. As an example, in a carrier aggregation scenario, a UE can communicate on multiple component carriers corresponding to multiple (serving) cells in the same cell group, and in a multi-connectivity (e.g., dual-connectivity) scenario, a UE can communicate on multiple component carriers corresponding to multiple cell groups.

[0044] Although BS 102 is described as a single communication device in various aspects, it can be implemented in a variety of configurations. For example, to give a few examples, one or more components of the base station can be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. In another example, various aspects of the base station can be virtualized. More generally, a base station (e.g., BS 102) can include components located at a single physical location or components located at various physical locations. In examples where the base station includes components located at various physical locations, the various components can each perform functions, such that the various components collectively achieve functionality similar to a base station located at a single physical location. In some aspects, a base station including components located at various physical locations can be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture). Figure 2 An example decomposed base station architecture is depicted and described.

[0045] Different BSs 102 within the wireless communication network 100 can also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) can interface with 5GC 190 via a second backhaul link 184. BSs 102 can communicate directly or indirectly (e.g., via EPC 160 or 5GC 190) on a third backhaul link 134 (e.g., X2 interface), which can be wired or wireless.

[0046] Wireless communication network 100 can subdivide the electromagnetic spectrum into various categories, bands, channels, or other characteristics. In some aspects, subdivision is provided based on wavelength and frequency, where frequency may also be referred to as carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410MHz to 7125MHz, which is often (interchangeably) referred to as “sub-6GHz”. Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250MHz to 71,000MHz, which is sometimes (interchangeably) referred to as “millimeter wave” (“mmW” or “mmWave”). In some cases, FR2 can be further defined according to subranges (such as a first subrange FR2-1 including 24,250MHz to 52,600MHz and a second subrange FR2-2 including 52,600MHz to 71,000MHz). Base stations configured to communicate using mmWave / near mmWave radio bands (e.g., mmWave base stations such as BS 180) can utilize beamforming (e.g., 182) with UEs (e.g., 104) to improve path loss and range.

[0047] The communication link 120 between BS 102 and, for example, UE 104 can be via one or more carriers, which may have different bandwidths (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz and / or other MHz) and may be aggregated in various ways. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric relative to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL).

[0048] Compared to lower-frequency communication, communication using higher frequency bands may have higher path loss and shorter range. Therefore, some base stations (e.g., Figure 1 The beamforming 182 of the BS 180 (180) with the UE 104 can be used to improve path loss and range. For example, the BS 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, the BS 180 may transmit beamformed signals to the UE 104 in one or more transmit directions 182''. The UE 104 may receive beamformed signals from the BS 180 in one or more receive directions 182''. The UE 104 may also transmit beamformed signals to the BS 180 in one or more transmit directions 182''. The BS 180 may also receive beamformed signals from the UE 104 in one or more receive directions 182''. The BS 180 and UE 104 may then perform beamforming training to determine the optimal receive and transmit directions for each of the BS 180 and UE 104. It is worth noting that the transmit and receive directions of the BS 180 may be the same or different. Similarly, the sending and receiving directions of UE 104 can be the same or different.

[0049] The wireless communication network 100 also includes a Wi-Fi AP 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, unlicensed spectrum in 2.4 GHz and / or 5 GHz.

[0050] Some UEs 104 may use device-to-device (D2D) communication link 158 to communicate with each other. The D2D communication link 158 may use one or more sidelink channels, such as physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), physical sidelink control channel (PSCCH), and / or physical sidelink feedback channel (PSFCH).

[0051] EPC 160 may include various functional components, including: Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and / or Packet Data Network (PDN) Gateway 172, as in the illustrated example. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connectivity management.

[0052] Generally, user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP services 176, which may include, for example, the Internet, intranets, IP Multimedia Subsystem (IMS), packet-switched (PS) streaming services, and / or other IP services.

[0053] The BM-SC 170 provides functionality for MBMS user service dispatch and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and / or schedule MBMS transmissions. The MBMS Gateway 168 can distribute MBMS services to BS 102 within a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and / or be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0054] 5GC 190 may include various functional components, including: Access and Mobility Management Function (AMF) 192, other AMFs 193, Session Management Function (SMF) 194, and User Plane Function (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196.

[0055] AMF 192 is the control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides services such as Quality of Service (QoS) flow and session management.

[0056] Internet Protocol (IP) packets are transmitted via UPF 195, which connects to IP service 197 and provides UE IP address allocation and other functions for 5GC 190. IP service 197 may include, for example, the Internet, intranet, IMS, PS streaming service, and / or other IP services.

[0057] In various aspects, to give a few examples, network entities or network nodes can be implemented as aggregated base stations, decomposed base stations, components of base stations, integrated access and backhaul (IAB) nodes, relay nodes, and sidelink nodes.

[0058] Figure 2An example decomposed base station 200 architecture is depicted. The decomposed base station 200 architecture may include one or more central units (CUs) 210, which may communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 through one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) framework 205, or both. CUs 210 may communicate with one or more distributed units (DUs) 230 via corresponding midhaul links (such as F1 interfaces). DUs 230 may communicate with one or more radio units (RUs) 240 via corresponding fronthaul links. RUs 240 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some specific implementations, UE 104 may be served simultaneously by multiple RUs 240.

[0059] Each unit in a cell (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO frame 205) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the cells, or an associated processor or controller that provides instructions to the cell's communication interface, may be configured to communicate with one or more other cells via the transmission medium. For example, these cells may include a wired interface configured to receive signals or transmit signals to one or more other cells via a wired transmission medium. Additionally or alternatively, a cell may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive signals on a wireless transmission medium or transmit signals to one or more other cells, or both.

[0060] In some aspects, CU 210 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to communicate signaling with other control functions hosted by CU 210. CU 210 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP)), control plane functions (e.g., Central Unit-Control Plane (CU-CP)), or combinations thereof. In some implementations, CU 210 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, CU-UP units can communicate bidirectionally with CU-CP units via an interface such as an E1 interface. CU 210 can be implemented to communicate with DU 230 for network control and signaling purposes, as needed.

[0061] DU 230 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 240s. In some aspects, DU 230 may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part, according to functional splits (such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 230 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.

[0062] Lower-layer functionality can be implemented by one or more RU 240s. In some deployments, an RU240 controlled by a DU 230 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration allows the DU 230 and CU 210 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0063] SMO framework 205 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 205 can be configured to interact with cloud computing platforms such as Open Cloud (O-Cloud) 290 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 210, DU 230, RU 240, and near-RT RIC 225. In some specific implementations, SMO framework 205 may communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 211) via the O1 interface. Additionally, in some implementations, the SMO framework 205 may communicate directly with one or more DU 230s and / or one or more RU 240s via the O1 interface. The SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205.

[0064] The non-RT RIC 215 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 225. The non-RT RIC 215 can be coupled to or communicate with the near-RT RIC 225 (e.g., via an A1 interface). The near-RT RIC 225 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions through an interface (e.g., via an E2 interface) connecting one or more CU 210s, one or more DU 230s, or both, and O-eNBs to the near-RT RIC 225.

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

[0066] Figure 3 Various aspects of examples BS 102 and UE 104 are described.

[0067] Generally, BS 102 includes various processors (e.g., 318, 320, 330, 338, and 340), antennas 334a to 334t (collectively referred to as 334), transceivers 332a to 332t (collectively referred to as 332) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., data source 312) and the wireless reception of data (e.g., data sink 314). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement the various wireless communication-related functions described herein. Note that BS 102 may have the features described herein. Figure 2 The decomposed architecture described.

[0068] Generally, UE 104 includes various processors (e.g., 358, 364, 366, 370, and 380), antennas 352a to 352r (collectively referred to as 352), transceivers 354a to 354r (collectively referred to as 354) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., retrieval from data source 362) and the wireless reception of data (e.g., provision to data sink 360). UE 104 includes a controller / processor 380 that can be configured to implement the various wireless communication-related functions described herein.

[0069] Regarding example downlink transmission, BS 102 includes a transmission processor 320 that can receive data from data source 312 and control information from controller / processor 340. This control information may be for a Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid Automatic Repeat Request (HARQ) Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Common PDCCH (GC PDCCH), and / or others. In some examples, this data may be for a Physical Downlink Shared Channel (PDSCH).

[0070] The transmitter processor 320 can process data and control information (e.g., encoding and symbol mapping) to obtain data symbols and control symbols, respectively. The transmitter processor 320 can also generate reference symbols (such as those for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS)).

[0071] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, and / or reference symbols where applicable, and can provide the output symbol stream to the modulators (MODs) in transceivers 332a to 332t. Each modulator in transceivers 332a to 332t can process the corresponding output symbol stream to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signal from the modulators in transceivers 332a to 332t can be transmitted via antennas 334a to 334t, respectively.

[0072] To receive downlink transmissions, UE 104 includes antennas 352a to 352r that receive downlink signals from BS 102 and provide the received signals to demodulators (DEMODs) in transceivers 354a to 354r, respectively. Each demodulator in transceivers 354a to 354r can adjust (e.g., filter, amplify, down-convert, and digitize) the corresponding received signal to obtain an input sample. Each demodulator can further process the input sample to obtain the received symbols.

[0073] The RX MIMO detector 356 acquires received symbols from all demodulators in transceivers 354a to 354r, performs MIMO detection on the received symbols where applicable, and provides the detected symbols. The receive processor 358 processes the detected symbols (e.g., demodulation, deinterleaving, and decoding), provides the decoded data of UE 104 to data sink 360, and provides the decoded control information to controller / processor 380.

[0074] Regarding example uplink transmission, UE 104 also includes a transmit processor 364 that receives and processes data from data source 362 (e.g., for PUSCH) and control information from controller / processor 380 (e.g., for Physical Uplink Control Channel (PUCCH)). Transmit processor 364 may also generate reference symbols for reference signals (e.g., for Sounding Reference Signal (SRS)). Symbols from transmit processor 364 may be pre-decoded by TX MIMO processor 366 where applicable, further processed by modulators in transceivers 354a to 354r (e.g., for SC-FDM), and transmitted to BS 102.

[0075] At BS 102, uplink signals from UE 104 can be received by antennas 334a to 334t, processed by demodulators in transceivers 332a to 332t, detected where applicable by RX MIMO detector 336, and further processed by receiver processor 338 to obtain decoded data and control information transmitted by UE 104. Receiver processor 338 can provide the decoded data to data sink 314 and the decoded control information to controller / processor 340.

[0076] Memory 342 and memory 382 can store data and program code for BS 102 and UE 104, respectively.

[0077] Scheduler 344 can schedule UE to send data on the downlink and / or uplink.

[0078] In various respects, BS 102 can be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms that output data, such as from data source 312, scheduler 344, memory 342, transmit processor 320, controller / processor 340, TX MIMO processor 330, transceivers 332a to 332t, antennas 334a to 334t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antennas 334a to 334t, transceivers 332a to 332t, RX MIMO detector 336, controller / processor 340, receive processor 338, scheduler 344, memory 342, and / or other aspects described herein.

[0079] In various respects, UE 104 can also be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms that output data, such as from data source 362, memory 382, ​​transmit processor 364, controller / processor 380, TX MIMO processor 366, transceivers 354a to 354t, antennas 352a to 352t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antennas 352a to 352t, transceivers 354a to 354t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, ​​and / or other aspects described herein.

[0080] In some respects, the processor can be configured to perform various operations (such as those associated with the methods described herein) and to send (output) data to or receive data from another interface configured to send or receive data, respectively.

[0081] In various aspects, artificial intelligence (AI) processors 318 and 370 may perform AI processing for BS 102 and / or UE 104, respectively. AI processor 318 may include AI accelerator hardware or circuitry, such as one or more neural processing units (NPUs), one or more neural network processors, one or more tensor processors, one or more deep learning processors, etc. AI processor 370 may similarly include AI accelerator hardware or circuitry. As an example, AI processor 370 may perform AI-based beam management, AI-based channel state feedback (CSF), AI-based antenna tuning, and / or AI-based localization (e.g., non-line-of-sight localization prediction). In some cases, AI processor 318 may use hardware-accelerated AI inference and / or AI training to process feedback (e.g., CSF) from UE 104. AI processor 318 may, for example, use hardware-accelerated AI inference associated with the CSF to decode compressed CSF from UE 104. In some cases, AI processor 318 may perform certain RAN-based functions, including, for example, network planning, network performance management, energy-efficient network operation, etc.

[0082] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes the use of wireless communication networks (such as Figure 1 All aspects of the data structure of the wireless communication network 100.

[0083] Specifically, Figure 4A Figure 400 is an example of the first subframe within a 5G (e.g., 5G NR) frame structure. Figure 4B Figure 430 illustrates an example of a DL channel within a 5G subframe. Figure 4C Figure 450 illustrates an example of the second subframe within a 5G frame structure, and Figure 4D Figure 480 illustrates an example of a UL channel within a 5G subframe.

[0084] Wireless communication systems can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems can also support half-duplex operation using Time Division Duplex (TDD). OFDM and Single-Carrier Frequency Division Multiplexing (SC-FDM) will (e.g., as...) Figure 4B and Figure 4D The system bandwidth (as depicted in the text) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0085] Wireless communication frame structures can be frequency division duplex (FDD), where for a specific set of subcarriers, subframes within that set are dedicated to either deep (DL) or ultra-low (UL). Wireless communication frame structures can also be time division duplex (TDD), where for a specific set of subcarriers, subframes within that set are dedicated to both DL and UL.

[0086] exist Figure 4A and Figure 4C In this example, the wireless communication frame structure is TDD, where D stands for DL, U for UL, and X is flexibly used between DL and UL. The UE can configure the time slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). In the depicted example, a 10ms frame is divided into 10 equal-sized 1ms subframes. Each subframe may include one or more time slots. In some examples, each time slot may include 12 or 14 symbols, depending on the Cyclic Prefix (CP) type (e.g., 12 symbols per time slot for extended CP, or 14 symbols per time slot for regular CP). Subframes may also include micro-slots, which typically have fewer symbols than the entire time slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0087] In some respects, the number of time slots within a subframe (e.g., the time slot duration within a subframe) is based on a parameter set that defines the frequency-domain subcarrier spacing and symbol duration, as further described herein. In some respects, given a parameter set μ, each subframe has 2 μ The number of time slots is 1. Therefore, parameter sets (µ) 0 through 6 allow for 1, 2, 4, 8, 16, 32, and 64 time slots per subframe, respectively. In some cases, extended CP (e.g., 12 symbols per time slot) can be used with specific parameter sets; for example, parameter set 2 allows for 4 time slots per subframe. Subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to... kHz, where μ is the parameter set from 0 to 6. As an example, the parameter set... Corresponding to a subcarrier spacing of 15 kHz, and the parameter set This corresponds to a subcarrier spacing of 960 kHz. Symbol length / duration is negatively correlated with subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D It provides a slot format with 14 symbols per slot (e.g., regular CP) and a parameter set with 4 slots per subframe. An example. In this case, the slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0088] like Figure 4A , Figure 4B , Figure 4C and Figure 4D As depicted, the resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)) extending for, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme, including, for example, quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM).

[0089] like Figure 4A As illustrated in the example, some REs in the RE carry information for the UE (e.g., Figure 1 and Figure 3 The reference (pilot) signal (RS) for the UE (104) may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0090] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0091] The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific subframe of the frame. The PSS is generated by the UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identifier.

[0092] The Supplemental Synchronization Signal (SSS) can be located in symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identifier group number and radio frame timing.

[0093] Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The Physical Broadcast Channel (PBCH) carrying the Master Information Block (MIB) can be logically combined with the PSS and SSS to form a Synchronization Signal (SS) / PBCH Block (SSB), and in some cases, it is called the Synchronization Signal Block (SSB). The MIB provides the number of RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as System Information Block (SIB)) not transmitted via the PBCH, and / or paging messages.

[0094] like Figure 4C As illustrated, some REs in the REs carry DMRS for channel estimation at the base station (indicated as R for a particular configuration, but other DMRS configurations are possible). The UE can transmit DMRS for PUCCH and DMRS for PUSCH. PUSCH DMRS can be transmitted, for example, in the first or second symbol before the PUSCH. PUCCH DMRS can be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and depending on the specific PUCCH format used. UE104 can transmit a Sounding Reference Signal (SRS). SRS can be transmitted, for example, in the last symbol of a subframe. SRS can have a comb structure, and the UE can transmit SRS on one of the comb teeth. SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0095] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.

[0096] Aspects related to WUS monitoring and prediction via WUS indications and / or requests used for DRX communication Figure 5 An example wireless communication system 500 for transmitting instructions to a WUS monitoring instance to be monitored, according to various aspects of this disclosure, is described. In some aspects, the wireless communication system 500 can implement... Figures 1 to 4D These aspects may be implemented or can be achieved by these aspects. For example, wireless communication system 500 may include network entity 502 and at least one device 504, wherein network entity 502 may represent as referenced Figures 1 to 3The described base station or similar network entity (e.g., BS 102, BS 180, etc.), and device 504 may represent as referenced. Figures 1 to 3 The described UE or similar terminal device (e.g., UE 104). Additionally, network entity 502 and device 504 can wirelessly communicate via downlink communication link 506 (e.g., one or more carriers, communication link 120, beamforming 182, etc.) and via uplink communication link 508 (e.g., one or more carriers, communication link 120, beamforming 182, etc.). Although in Figure 5 The example depicts only one (1) device 504, but network entity 502 can communicate with multiple devices. In some respects, device 504 can be configured for C-DRX mode operation as described herein.

[0097] In some respects, device 504 (e.g., configured to operate in C-DRX mode) can be configured to monitor WUS outside of DRX active periods, where a set of WUS monitoring instances is associated with each DRX cycle. WUS is a type of power-saving mechanism that attempts to conserve device power by keeping the device dormant (e.g., not waking up) even when there is no data for the device, and network entity 502 notifying the device of "not waking up" (e.g., this may be referred to as a negative WUS indication). When any data for the device is present, network entity 502 may notify the device of "wake up" (e.g., this may be referred to as a positive WUS indication), causing the device to "wake up" and receive data during the DRX active period / cycle. That is, WUS instructs the media access control (MAC) entity of device 504 whether it should start an active period timer for the next DRX cycle (e.g., ...). drx-onDurationTimer WUS does not affect other timers (e.g., bwp- inactivityTimer , dataInactivityTimer and sCellDeactivationTimer In some respects, WUS is a PDCCH defined by DCI format 2_6, where cyclic redundancy check (CRC) is scrambled by a temporary identifier (e.g., Power Saving Radio Network Temporary Identifier (PS-RNTI)) configured for DRX mode operation. In some respects, WUS can be shared by a set of devices and monitored in a common WUS monitoring instance (e.g., a common search space set, a common PDCCH MO, etc.).

[0098] As described herein, in order for network entity 502 to sweep one or more transmit beams when transmitting WUS, device 504 may be configured with WUS (e.g., WUS configured to monitor for DRX) based on multiple WUS monitoring instances (e.g., search space sets, downlink channel monitoring timing (MO), etc.), wherein reference signals (e.g., control resource sets (CORESET)) associated with different such WUS monitoring instances may correspond to different TCI states. For example, multiple WUS monitoring instances may include multiple search space sets, wherein the search space sets include multiple downlink time-frequency resources. Device 504 may then perform blind decoding in multiple downlink time-frequency resources in multiple search space sets to identify WUS (e.g., PDCCH with DCI format 2_6). That is, a specific time-frequency resource (e.g., a specific symbol) that includes WUS may be located somewhere in one or more of the multiple search space sets, and device 504 may attempt to find WUS based on receiving indications of multiple search space sets to be monitored and performing blind decoding on the multiple search space sets.

[0099] Additionally, each search space set may include an associated CORESET (e.g., a set of time-frequency resources designed to carry control information such as PDCCH and / or DCI in the search space set), and the associated CORESET may correspond to a TCI state, wherein the TCI state may include a source reference signal and the expected quasi-co-address (QCL) type to be applied.

[0100] The TCI state can correspond to the downlink transmit beam from network entity 502. For example, in beam management using a TCI signaling framework, the beam for the target channel or signal to be received by device 504 can be indicated by the TCI state. That is, network entity 502 can signal to device 504 the DCI (e.g., in the associated CORESET of the search space set), where the DCI can select and / or indicate the TCI state to be used for receiving the downlink channel. Subsequently, device 504 can set one or more analog beamforming coefficients based on the indicated TCI state to receive the downlink channel on the corresponding downlink transmit beam.

[0101] In some aspects, each search space set may also correspond to an SSB. For example, different source reference signals relative to the TCI state of a corresponding CORESET (e.g., linked to the corresponding search space set) may include a QCL relationship with the corresponding SSB. In some aspects, the QCL relationship may be a type D-QCL relationship, which may indicate spatial receiver parameters between the source reference signal of the TCI state and the SSB. For example, spatial receiver parameters may include beamforming properties for the received signal on the downlink, such as the main angle of arrival, average angle of arrival, or other properties for the downlink transmit beam received by device 504.

[0102] Additionally, network entity 502 may transmit the corresponding SSB via each downlink transmit beam (e.g., as part of an SSB beam sweep). Therefore, each search space set may correspond to each downlink transmit beam based on which SSB is identified in each search space set and on which downlink transmit beam the SSB is received. For example, if the first search space set corresponds to the first SSB and the first downlink transmit beam is used to transmit the first SSB, then device 504 may determine that the first search space set corresponds to the first downlink transmit beam.

[0103] Additionally or alternatively, different TCI states may be associated with different downlink channel MOs (e.g., PDCCH MOs) of one or more corresponding search space sets (e.g., for PDCCH repetition purposes). For example, WUS can be configured based on a single search space set while still supporting transmit beam sweep. If different MOs across a single search space set are associated with multiple TCI states, then instead of multiple WUS monitoring instances corresponding to different search space sets, multiple WUS monitoring instances may be associated with: different MOs in a single search space set or multiple such search space sets, or different TCI states and / or QCL source reference signals associated with such different MOs in a single search space set or multiple such search space sets.

[0104] In some respects, network entities can use such swept transmit beams to send WUS in different directions toward various devices. Whether a particular device 504 can detect all or a subset of the configured WUS monitoring instances may depend on the specific implementation at network entity 502. Therefore, such transmit beam sweeping may require device 504 to potentially perform a significant amount of RF on and downlink channel (e.g., Physical Downlink Control Channel (PDCCH)) detection work, thus incurring additional device power (e.g., compared to situations where transmit beam sweeping might be less necessary).

[0105] In some respects, considering WUS monitoring instances associated with an upcoming DRX activation cycle, it is possible to predict the preferred transmission beams associated with one or more WUS monitoring instances in one or more more distant DRX activation cycles (e.g., based on historical measurements). For example, artificial intelligence (AI) and / or machine learning (ML) can be used in air interface communications, such as for beam management (e.g., beam prediction in the temporal and / or spatial domains for overhead and latency reduction, improved beam selection accuracy, etc.). In some respects, the AI / ML approaches used for selecting sub-use cases (e.g., beam management) need to be sufficiently diverse to support various requirements for the level of network entity-device collaboration.

[0106] For AI / ML-based beam management, various beam management scenarios can be supported for characterization and baseline performance evaluation. For example, a first beam management use case using AI / ML-based beam management may include spatial domain downlink beam prediction for a first set of beams (e.g., set A) based on measurements from a second set of beams (e.g., set B). Additionally or alternatively, a second beam management use case using AI / ML-based beam management may include temporal downlink beam prediction for a first set of beams (e.g., set A) based on historical measurements from a second set of beams (e.g., set B). In some aspects, the beams in the first set and the beams in the second set may be in the same frequency range. In some aspects, the beams in the second set may be a subset of the beams in the first set, or the beams in the first set may differ from the beams in the second set (e.g., set A includes narrow beams, while set B includes wide beams). In some aspects, the beams in the first set can be used for downlink beam prediction, and the beams in the second set can be used for beam measurement.

[0107] As described herein, prediction of the preferred transmission beam associated with one or more WUS monitoring instances, which are associated with one or more more distant DRX activation periods, can be performed by network entity 502 and / or device 504. Figure 5 In the example, network entity 502 may perform a prediction and indicate that prediction to device 504. For example, when such a prediction is performed by network entity 502, the historical measurements used for the prediction may be based on characteristics reported by the device (e.g., power measurements, signal quality measurements, etc.) of the synchronization signal (e.g., SSB, CSI-RS, etc.) sent by network entity 502, such as, but not limited to, reports via Layer 1 (L1)-Reference Signal Received Power (RSRP) (e.g., other signal power and / or signal characteristic reports may be used). Therefore, network entity 502 may signal a preferred beam transmission in one or more considered WUS monitoring instances associated with an upcoming DRX activation period.

[0108] To enable prediction of preferred transmission beams and allow network entity 502 to sweep multiple transmission beams while transmitting WUS, network entity 502 may (e.g., via RRC signaling) send configuration 510 to device 504. Configuration 510 includes indications of multiple sets of WUS monitoring instances (e.g., a first number of multiple search space sets, a first number of multiple PDCCH MOs, etc.) for monitoring DCI formats associated with the transmission of WUS signals, and CORESET associated with different such WUS monitoring instances corresponds to various different TCI states and / or transmission beams. In some aspects, the multiple sets of WUS monitoring instances may be associated with multiple DRX on cycles, and each set of WUS monitoring instances (e.g., in the multiple sets of WUS monitoring instances) may include multiple WUS monitoring instances. That is, configuration 510 may include a set of WUS monitoring instances associated with each of the multiple DRX on cycles, thereby generating multiple sets of WUS monitoring instances.

[0109] In some aspects, network entity 502 may configure multiple sets of WUS monitoring instances and indicate multiple sets of WUS monitoring instances to device 504 (e.g., via configuration 510), wherein the multiple sets of WUS monitoring instances are configured and used to monitor WUS for a corresponding DRX activation period among multiple DRX activation periods. For example, device 504 may use a first set of WUS monitoring instances associated with a first DRX activation period to monitor a first WUS, a second set of WUS monitoring instances associated with a second DRX activation period to monitor a second WUS, a third set of WUS monitoring instances associated with a third DRX activation period to monitor a third WUS, etc., wherein each set of WUS monitoring instances includes the same multiple WUS monitoring instances (e.g., indicated in configuration 510).

[0110] Therefore, in Figure 5In the example, after receiving configuration 510, device 505 may monitor and receive a first WUS 512 based on multiple WUS monitoring instances in a first set of multiple sets of monitored WUS monitoring instances, wherein the first WUS 512 and the first set of WUS monitoring instances are associated with a first DRX enable cycle. The first WUS 512 may include at least a WUS indication 514, which may indicate whether device 504 should start an enable duration timer for the first DRX enable cycle (e.g., whether device 504 should wake up for the first DRX enable cycle). In some aspects, network entity 502 may transmit the first WUS 512 in each of the multiple WUS monitoring instances in the first set of WUS monitoring instances, or may transmit the first WUS 512 in a subset (e.g., one or more subsets) of the multiple WUS monitoring instances in the first set of WUS monitoring instances.

[0111] As previously described, network entity 502 may perform prediction of a preferred transmission beam associated with one or more WUS monitoring instances among a plurality of WUS monitoring instances associated with one or more more distant DRX activation periods (e.g., after the first DRX activation period). That is, network entity 502 may determine one or more WUS monitoring instances among a plurality of WUS monitoring instances (e.g., using AI / ML-based beam management), wherein one or more WUS monitoring instances are associated with a preferred transmission beam. For example, as previously described, network entity 502 may determine one or more WUS monitoring instances based on historical measurements received from device 504 (such as in one or more measurement reports 516 of synchronization signals, reference signals, and / or other signals transmitted by network entity 502 and received by device 504 (e.g., L1-RSRP reports)). Additionally or alternatively, as referenced... Figure 6 In more detail, device 504 may perform a prediction of a preferred transmission beam (e.g., based on a request to perform the prediction received from network entity 502), and may transmit an indication of the prediction result 518 to network entity 502, and network entity 502 may determine one or more WUS monitoring instances based on the prediction result 518.

[0112] Subsequently, network entity 502 may indicate one or more WUS monitoring instances (e.g., and associated transmit beams) to device 504. For example, network entity 502 may transmit an indication 520 to device 504 in the first WUS 512 for one or more WUS monitoring instances (e.g., among a plurality of WUS monitoring instances). Thus, device 504 may monitor at least one additional WUS 522 in at least one or more WUS monitoring instances (e.g., included in indication 520) in at least one set of WUS monitoring instances in a plurality of sets of WUS monitoring instances, wherein at least one set of WUS monitoring instances is associated with at least one DRX activation period following the first DRX activation period. For example, for one or more DRX activation periods (e.g., after the first DRX activation period), device 504 may be expected to monitor such DCIs, including the WUS indication for device 504, in the corresponding one or more WUS monitoring instances (e.g., search space set, PDCCH MO, etc.) for the corresponding future DRX activation period.

[0113] In other words, device 504 may limit its monitoring to at least one of the one or more WUS monitoring instances included in indication 520 in the first WUS 512, rather than monitoring each of the multiple WUS monitoring instances for at least one additional WUS 522 in at least one subsequent set of WUS monitoring instances in a plurality of sets of WUS monitoring instances (e.g., after the first set of WUS monitoring instances), wherein at least one subsequent set of WUS monitoring instances is associated with at least one DRX on cycle after the first DRX on cycle. Therefore, device 504 may potentially reduce power consumption by monitoring one or more WUS monitoring instances (e.g., included in indication 520) for at least one additional WUS 522 instead of monitoring each of the multiple WUS monitoring instances.

[0114] In some aspects, network entity 502 may use different types of identifiers to indicate one or more WUS monitoring instances in indication 520 in the first WUS 512. For example, in the first WUS 512 decoded from at least one WUS monitoring instance from a first set of WUS monitoring instances associated with a first DRX activation cycle, device 504 may receive from network entity 502 (e.g., as indicated in configuration 510) a suggested search space set identifier (e.g., indication 520 for one or more WUS monitoring instances) from the multiple WUS monitoring instances. Additionally or alternatively, device 504 may receive from network entity 502 a selective TCI status identifier for CORESET associated with the multiple WUS monitoring instances (e.g., indication 520 for one or more WUS monitoring instances).

[0115] In some respects, to indicate search space set identifiers, network entity 502 may explicitly indicate one or more search space set identifiers in indication 520. For example, network entity 502 may assign and / or configure a corresponding search space set identifier for each search space set corresponding to multiple WUS monitoring instances (e.g., indicated in configuration 510). As an example, network entity 502 may (e.g., via RRC signaling) configure and / or indicate four (4) search space sets for multiple WUS monitoring instances, and may configure and / or indicate search space set IDs {#1, #2, #5, #7} for the four (4) search space sets respectively.

[0116] In some respects, network entity 502 may then reorder the search space set identifiers corresponding to multiple WUS monitoring instances in ascending / descending order based on information provided in one or more measurement reports 516 and / or prediction results 518 to determine which transmit beams of network entity 502 are preferred (e.g., which transmit beams from network entity 502 have the highest signal quality and / or are predicted to have the highest signal quality in measurement reports 516 and / or prediction results 518). For example, network entity 502 may reorder four (4) search space sets into the {1st, 2nd, 3rd, 4th} most preferred search space sets for which device 504 should monitor at least one additional WUS 522. Subsequently, instruction 520 may instruct and / or select one or more of these four (4) search space sets (e.g., based on the reordering).

[0117] In some respects, network entity 502 may signal such indication of a search space set identifier in indication 520 based on a signaling notification of an explicit candidate search space set ID, a bitmap, a combined index, or a combination thereof. For example, based on the previously provided example, where four (4) search space sets have been configured with search space set IDs {#1, #2, #5, #7}, network entity 502 may explicitly instruct device 504 in indication 520 to monitor one or more of the configured search space set IDs of one or more WUS monitoring instances (e.g., a single search space set ID, such as search space set ID #5, or multiple search space set IDs, such as search space set IDs #2 and #5).

[0118] To signal explicit search space set IDs, network entity 502 may configure and / or indicate (e.g., via RRC signaling) the number of search space set IDs expected to be received by device 504 in indication 520. In some respects, the DCI payload size of device 504 regarding such indication of explicit search space set IDs in indication 520 may depend on the number of search space set IDs expected to be received by device 504 and the total number of search space sets configured and / or indicated for multiple WUS monitoring instances in configuration 510. As an example, four (4) search space sets may be configured for the total number of search space sets in configuration 510, and two (2) search space set IDs may be configured for the number of search space set IDs expected to be received by device 504 in indication 520. Therefore, device 504 can anticipate four (4) bits of indicator 520 for explicit search space set ID indication based on log2X, where “X” represents the total number of configured search space sets (e.g., log24 = 2 bits for each explicitly indicated search space set ID in indicator 520, resulting in a total of four (4) bits for two (2) search space set IDs).

[0119] Additionally or alternatively, in order to signal the number of search space set IDs expected to be received by device 504 in indication 520 in order to signal the number of search space set IDs in indication 520. Therefore, the DCI payload size of device 504 with respect to such indication of the bitmap may depend on the total number of search space sets in configuration 510 and which search space sets are left to network entity 502 as indicated in indication 520. For example, if a total of four (4) search space sets are configured in configuration 510 for multiple WUS monitoring instances, the network entity may signal a 4-bit bitmap in indication 520 to indicate that device 502 should monitor at least one additional WUS 522 search space set. As an example, network entity 502 may signal bitmaps 1000, 0100, 0010, 0001, 1100, 1010, 1001, 0110, 0101, 0011, 1110, 1011, 0111, or 1111, where “1” indicates that device 504 should monitor at least one additional WUS 522 search space set based on the configured search space set ID. For example, using the previously provided example, where four (4) search space sets are configured using search space set IDs {#1, #2, #5, #7} respectively, bitmap “0110” in indication 520 may indicate that device 504 should monitor the search space sets with search space set IDs #2 and #5. In some respects, if the total number of configured candidate search space set IDs is relatively small, network entity 502 may use bitmaps for indication 520.

[0120] Additionally or alternatively, in order to signal the composite index in indication 520 to indicate a search space set identifier, network entity 502 may signal an index value in indication 520 that selects a first number of search space sets (e.g., "K" search space sets) from the total number of configured search space sets (e.g., "N" search space sets) based on a lookup table (e.g., configured via RRC). In some aspects, signaling the composite index may result in higher decoding complexity for device 504 (e.g., compared to signaling an explicit search space set ID or bitmap).

[0121] In some aspects, as previously described, network entity 502 may indicate a TCI status identifier in indication 520 to signal one or more WUS monitoring instances. For example, each TCI status associated with a CORESET for each search space set (e.g., corresponding to multiple WUS monitoring instances indicated in configuration 510) may include a TCI status identifier. As an example, a search space set with configuration search space set IDs of {#1, #2, #5, #7, #8, #9} considered for the total number of search space sets in configuration 510 may respectively include the associated TCI status IDs of {#5, #2, #3, #2, #7, #5}.

[0122] In some respects, network entity 502 may then reorder the associated TCI state IDs in ascending / descending order based on information provided from one or more measurement reports 516 and / or prediction results 518 to determine which transmit beams of network entity 502 are preferred (e.g., which transmit beams from network entity 502 have the highest signal quality and / or are predicted to have the highest signal quality in measurement reports 516 and / or prediction results 518), where duplicate TCI states may be removed. For example, based on the previously provided example, network entity 502 may reorder candidate TCI state IDs to {#2, #3, #5, #7}, which may also be considered as the {1st, 2nd, 3rd, 4th} most preferred TCI state IDs that device 504 should monitor for at least one additional WUS 522. Accordingly, indication 520 may indicate and / or select one or more of these four (4) candidate TCI state IDs (e.g., based on the reordering).

[0123] Similar to the indication of the search space set identifier described above, signaling indicating one or more TCI state IDs in 520 may be based on signaling explicit candidate TCI state IDs, bitmaps, or combined indexes. In some respects, whether network entity 502 indicates a search space set or TCI state IDs may be predefined or configured by network entity 502.

[0124] As previously described, configuration 510 may include a set of WUS monitoring instances (e.g., a set of search space sets, a set of PDCCH MOs, etc.) associated with each of a plurality of DRX activation cycles, wherein each set of WUS monitoring instances includes a plurality of individual WUS monitoring instances. Therefore, the indication 520 for one or more WUS monitoring instances may refer to one or more individual WUS monitoring instances among each of the respective plurality of individual WUS monitoring instances. Based on the previously described techniques, each WUS monitoring instance among the individual WUS monitoring instances may be associated with a value such as a search space set ID and / or a TCI status ID. Therefore, indication 520 for one or more WUS monitoring instances may include indications of one or more values ​​corresponding to one or more individual WUS monitoring instances (e.g., via explicit indication of a value / ID, a bitmap indicating a value / ID, a combined index indicating a value / ID, or a combination thereof), such as the search space set ID and / or TCI status ID for each WUS monitoring instance among the one or more WUS monitoring instances in the set of WUS monitoring instances.

[0125] In some respects, network entity 502 may indicate the number of DRX enable cycles for indication 520 for and / or applicable to device 504 for monitoring one or more WUS monitoring instances of at least one additional WUS 522. For example, network entity 502 may indicate how many DRX enable cycles of indication 520 for one or more WUS monitoring instances will be used by device 504 in the first WUS 512 and / or in indication 520.

[0126] In some aspects, network entity 502 may instruct one or more WUS monitoring instances (e.g., those indicated in indication 520) to be monitored by device 504 for a future DRX activation cycle. For example, network entity 502 may instruct device 504 to monitor one or more WUS monitoring instances for a single DRX activation cycle following a first DRX activation cycle, wherein the indication for the applicable single DRX activation cycle is addressed by a DCI including a first WUS 512 for the device 504 under consideration. In some aspects, for monitoring at least one additional WUS 522 for a single DRX activation cycle using one or more WUS monitoring instances indicated in indication 520, device 504 may anticipate the same DCI payload size for such indication with respect to each DRX activation cycle.

[0127] Additionally or alternatively, network entity 502 may instruct (e.g., as indicated in instruction 520) that one or more WUS monitoring instances will be monitored by device 504 for multiple future DRX activation cycles. For example, network entity 502 may instruct device 504 to monitor one or more WUS monitoring instances for multiple DRX activation cycles following a first DRX activation cycle, wherein the indication for the applicable multiple DRX activation cycles is addressed by a DCI including a first WUS 512 for the device 504 under consideration. In some aspects, for monitoring at least one additional WUS 522 for multiple DRX activation cycles using one or more WUS monitoring instances indicated in instruction 520, device 504 may anticipate such indication regarding selective DRX activation cycles.

[0128] As an example, assuming the number of future DRX activation periods is three (3), device 504 can anticipate indications 520 for one or more WUS monitoring instances to be monitored in the first, fourth, seventh, etc., DRX activation periods. Additionally, indicating that one or more WUS monitoring instances will be monitored by device 504 for multiple future DRX activation periods may mean that the WUS payload size can be different for different DRX activation periods. In some respects, network entity 502 can be configured (e.g., RRC configuration) for a specific future DRX activation period among the multiple future DRX activation periods. Additionally, indicating that one or more WUS monitoring instances will be monitored by device 504 for multiple future DRX activation periods may also be based on the assumption that device 504 anticipates receiving the same number of search space set IDs and / or TCI state IDs for each future DRX activation period in indication 520.

[0129] In some aspects, device 504 can successfully decode the first WUS 512 and can identify one or more WUS monitoring instances in indication 520. Accordingly, device 504 can use one or more WUS monitoring instances to detect one or more WUS in one or more future DRX on cycles (e.g., a single future DRX on cycle or multiple future DRX on cycles) addressed in indication 520. That is, device 504 can monitor one or more WUS monitoring instances and can ignore other WUS monitoring instances from the multiple WUS monitoring instances indicated in configuration 510 (e.g., besides one or more WUS monitoring instances). In some aspects, if device 504 cannot successfully decode the first WUS 512 and / or cannot identify one or more WUS monitoring instances in indication 520, device 504 can monitor the multiple WUS monitoring instances indicated in configuration 510 to detect WUS associated with a future DRX on cycle.

[0130] Additionally or alternatively, if device 504 fails to successfully decode the first WUS 512 and / or fails to identify one or more WUS monitoring instances in indication 520, device 504 may follow previously and most recently decoded WUS to determine which WUS monitoring instances should be monitored to detect WUS associated with a future DRX on-state. For example, device 504 may have received a previous WUS prior to the first WUS 512 and may have decoded the previous WUS to identify one or more previous WUS monitoring instances for which device 504 intends to monitor for at least one previous DRX on-state associated with the previous WUS. Subsequently, device 504 may use one or more previous WUS monitoring instances to monitor for at least one additional WUS 522 based on the failure to successfully decode the first WUS 512 and / or the failure to identify one or more WUS monitoring instances in indication 520.

[0131] In some aspects, network entity 502 may use device common fields (e.g., UE common fields) of each group of shared (GC) DCIs for indication 520. For example, instead of addressing indication 520 in device-specific subfields of the DCI that includes WUS, the GC-DCI may include device common fields that include indication 520 applicable to all devices decoding the GC-DCI (e.g., for groups of devices centered and / or near each other). In some aspects, the GC-DCI may be used for WUS transmission (e.g., WUS may be transmitted for a group of devices to indicate whether all devices in that group should be woken up). Reference Figures 7A to 7C A more detailed description of GC-DCI.

[0132] In some respects, device 504 may receive indication 520 in the first WUS 512, regardless of whether the WUS indication 514 is a positive indication (e.g., "wake up") or a negative indication (e.g., "no wake up"). For example, device 504 may anticipate indication 520 in the first WUS 512, regardless of whether the applicable WUS includes a positive or negative wake-up indication (e.g., because indication 520 is used to monitor, receive, and decode one or more subsequent WUSs rather than the current WUS).

[0133] In some aspects, device 504 can make a default Type D-QCL assumption about the downlink channel (e.g., PDCCH or Physical Downlink Shared Channel (PDSCH), often referred to as PDxCH) transmitted during a DRX activation period based on which WUS monitoring instance is used to receive the associated WUS for a DRX activation period. For example, indication 520 can identify a single TCI state for device 504 to monitor WUS for one or more future DRX activation periods. That is, indication 520 can indicate a single TCI state ID and / or one or more search space set IDs linked to the single TCI state ID. Device 504 can then use one or more WUS monitoring instances associated with the single TCI state to monitor WUS for at least one DRX activation period in the future DRX activation periods. If device 504 detects a WUS and decodes a positive wake-up indication for a future DRX activation period, device 504 can assume a Type D-QCL relationship for PDxCH during the future DRX activation period based on the Type D-QCL source reference signal for the single TCI state.

[0134] In other words, device 504 can determine which transmit beam from network entity 502 is expected to carry the downlink channel during a future DRX activation period based on which transmit beam of network entity 502 and / or the WUS monitoring instance is used to transmit a WUS with a positive wake-up indication for a future DRX activation period. For example, if network entity 502 transmits a WUS via a first beam (e.g., corresponding to a single TCI state), and the WUS includes a positive wake-up indication for a first DRX activation period associated with the WUS, device 504 can expect network entity 502 to transmit a PDxCH via the first beam in the first DRX activation period based on the Type D-QCL assumption. In some aspects, device 504 can decode a negative wake-up indication from one or more WUS monitoring instances relative to multiple TCI states, but device 504 can still make the Type D-QCL assumption. For example, device 504 may fail to receive a first WUS 512 including an indication 520 as previously described, so device 504 can attempt beam sweeping for WUS detection to receive at least one additional WUS 522. Additionally, it is denied that WUS may have no impact on the associated DRX activation cycle.

[0135] In some aspects, network entity 502 may provide device 504 with dynamic updates to indication 520 for one or more WUS monitoring instances via MAC control element (CE) and / or DCI signaling relative to parameters of indication 520. For example, the information and / or parameters previously described for indication 520 (e.g., the total number of WUS monitoring instances, the total number of search space set IDs, the indicated number of WUS monitoring instances or search space set IDs, etc.) may be RRC-configured, but this information and / or parameters may be updated and / or indicated via downlink MAC-CE or DCI (e.g., downlink grant). As an example, if network entity 502 indicates search space set IDs in indication 520 as previously described, network entity 502 may use MAC-CE / DCI signaling to update the number of search space set IDs that device 504 expects to indicate in indication 520 (e.g., based on network entity 502 determining whether device 504 is moving faster or slower).

[0136] In some respects, refer to Figure 5 The techniques and signaling described in the configuration 510 for multiple sets of WUS monitoring instances (e.g., multiple WUS monitoring instances for each set of WUS monitoring instances) and the indication 520 for one or more WUS monitoring instances are scalable to other types of transmit beamsweeping for WUS detection. For example, if a single search space set is associated with multiple TCI states of different MOs across the search space set, as previously described, the indication 520 for one or more WUS monitoring instances can be associated with different MOs or different TCI states and / or QCL sources associated with such different MOs, rather than associating the indication 520 for one or more WUS monitoring instances with different search space sets.

[0137] In some respects, reserved sites may be used and / or included in subsequent WUS transmissions (e.g., after the first WUS 512) to indicate whether device 504 should fall back to a mode that monitors multiple WUS monitoring instances for the next DRX activation cycle and / or multiple future DRX cycles (e.g., multiple sets of indications or configurations for WUS monitoring instances included in configuration 510), rather than monitoring one or more WUS monitoring instances included in indication 520. That is, if indication 520 includes, as previously described, an indication that device 504 intends to monitor one or more WUS monitoring instances for multiple future DRX activation cycles, the reserved site may invalidate or supersede indication 520, such that device 504 monitors multiple WUS monitoring instances for future DRX activation cycles after receiving the reserved site.

[0138] Figure 6An example wireless communication system 600 for transmitting a request for WUS prediction is described according to various aspects of this disclosure. In some aspects, the wireless communication system 600 may implement Figures 1 to 5 These aspects may be implemented through or by these aspects. For example, wireless communication system 600 may include network entity 602 and at least one device 604, wherein network entity 602 may represent as referenced. Figures 1 to 3 and Figure 5 The described base station or similar network entity (e.g., BS 102, BS 180, network entity 502, etc.), and device 604 may represent as referenced. Figures 1 to 3 and Figure 5 The described UE or similar terminal device (e.g., UE 104, device 504, etc.). Additionally, network entity 602 and device 604 can wirelessly communicate via downlink communication link 606 (e.g., one or more carriers, communication link 120, beamforming 182, downlink communication link 506, etc.) and via uplink communication link 608 (e.g., one or more carriers, communication link 120, beamforming 182, uplink communication link 508, etc.). Although in Figure 6 The example depicts only one (1) device 604, but network entity 602 can communicate with multiple devices.

[0139] Additionally, in Figure 6 In the examples and as referenced Figure 5 As described herein, device 604 can be configured for C-DRX and / or DRX mode operation (e.g., periodically alternating between active and inactive modes during a DRX enable cycle). As described herein and referenced Figure 5 Device 604 can also be configured to monitor WUS outside of DRX active periods to indicate whether device 604 may continue to sleep during the corresponding DRX active period (e.g., if there is no data for device 604) or whether device 604 should “wake up” during the corresponding DRX active period to receive data.

[0140] As described in this article and as referenced Figure 5 As described, in order for network entity 602 to sweep one or more transmit beams when transmitting WUS, device 604 may be configured to use WUS (e.g., configured to monitor WUS for DRX) based on multiple WUS monitoring instances (e.g., search space set, downlink channel MO, etc.), wherein reference signals (e.g., CORESET) associated with different such WUS monitoring instances may correspond to different TCI states.

[0141] In some respects, considering WUS monitoring instances associated with an upcoming DRX activation period, it is possible to predict the preferred transmission beams associated with one or more WUS monitoring instances in one or more more distant DRX activation periods (e.g., based on historical measurements). For example, as referenced Figure 5 As described, AI and / or ML can be used for air interface communications, such as for beam management (e.g., beam prediction in the time and / or spatial domains for reduced overhead and latency, improved beam selection accuracy, etc.).

[0142] As described herein, prediction of the preferred transmission beam associated with one or more WUS monitoring instances, which are associated with one or more more distant DRX activation periods, can be performed by network entity 602 and / or device 604. Figure 6 In the example, device 604 may perform a prediction based on a request received from network entity 602, and may indicate the prediction to network entity 602.

[0143] As previously referenced Figure 5 As described, in order to enable device 604 to predict the preferred transmit beam and so that network entity 602 can sweep multiple transmit beams when transmitting WUS, network entity 602 may send configuration 610 to device 604 (e.g., via RRC signaling), wherein configuration 610 may include, as referenced Figure 5 The same information as the described configuration 510. Additionally, in Figure 6 In the example, after receiving configuration 610, device 605 can monitor and receive a first WUS 612 based on multiple WUS monitoring instances in a first set of multiple sets of monitoring WUS monitoring instances.

[0144] As previously described, device 604 may perform prediction of a preferred transmission beam associated with one or more WUS monitoring instances among a plurality of WUS monitoring instances associated with one or more more distant DRX activation periods (e.g., after the first DRX activation period). When such prediction is to be performed by device 604, network entity 602 may request device 604 to perform the prediction based on an indication 616 (e.g., a request) transmitted in the first WUS 612 for device 604 to report one or more predictions corresponding to the plurality of WUS monitoring instances, and device 604 may transmit an indication 618 including one or more predictions after receiving such a request.

[0145] In some aspects, device 604 may monitor at least one additional WUS 620 in at least one of a plurality of WUS monitoring instances based on one or more predictions included in indication 618, wherein device 604 monitors at least one additional WUS 620 in at least one set of WUS monitoring instances in a plurality of sets of WUS monitoring instances, and wherein at least one set of WUS monitoring instances is associated with at least one DRX on-cycle following a first DRX on-cycle. For example, device 504 may monitor at least one additional WUS 620 in one or more WUS monitoring instances associated with one or more predictions.

[0146] Additionally or alternatively, the device 604 that performs the prediction of the preferred transmission beam can be referenced. Figure 5 The described instruction signaling and techniques are used in combination. For example, network entity 602 may transmit instruction 616 to device 604 in a first WUS 612 to instruct device 604 to report one or more predictions corresponding to multiple WUS monitoring instances, may receive instruction 618 for one or more predictions, and may transmit a second WUS that includes instructions for one or more WUS monitoring instances for device 604 to monitor subsequent WUS, wherein the one or more WUS monitoring instances are determined according to instruction 618.

[0147] In some respects, if the measurement reports transmitted by device 604 (e.g., historical measurements, L1-RSRP reports, etc.) lack receive beam information for device 604 and / or the number of beams addressed in such measurement reports is limited, network entity 602 may trigger a device-side prediction for the preferred transmit beam. Additionally, device 604 may be triggered to transmit indication 618 even if the first WUS 612 includes a negative wake-up indication for the WUS indication 614 for the current DRX on period. That is, device 604 may receive indication 616 from the first WUS 612 even if device 604 decodes the negative wake-up indication for WUS indication 614. Additionally or alternatively, network entity 602 may activate and / or trigger such reports for one or more predictions via other types of signaling (e.g., triggering / activating Channel State Information (CSI) reports via MAC-CE / DCI signaling). However, such triggering and / or activation may only be received via signaling during active DRX on periods, which may be limited in some scenarios for device 604.

[0148] exist Figure 6In the example, during the first WUS 612 decoded from multiple WUS monitoring instances in a first set of WUS monitoring instances associated with the first DRX activation cycle, device 604 may receive an indication 616 including a request for device 604 to report one or more predictions. Accordingly, in the indication 618 for one or more predictions, device 604 may report predicted characteristics (e.g., power measurements, signal quality measurements, SINR measurements, etc.) of synchronization signals and / or reference signals transmitted by network entity 602 and received by device 604. For example, device 604 may transmit an L1-RSRP report including RSRP measurements of synchronization signals and / or reference signals, an L1-Signal-to-Interference-plus-Noise Ratio (SINR) report including SINR measurements of synchronization signals and / or reference signals, and the top K reference signals relative to the L1-RSRP / L1-SINR report (e.g., which "K" reference signals have the highest RSRP and / or SINR measurements, where "K" is an integer). In some respects, the predictive characteristics of the synchronization signal and / or reference signal can be indicated for one or more DRX activation cycles following the first DRX activation cycle relative to one or more reference signals (e.g., Type D-QCL source reference signals) of the TCI state of the CORESET associated with multiple WUS monitoring instances (e.g., search space set, PDCCH MO, etc.).

[0149] In some aspects, device 604 may include different types of reports and / or predictions in indication 618. For example, indication 618 may include one or more CSI report-based predictions for one or more WUS monitoring instances out of a plurality of WUS monitoring instances (e.g., indicated in configuration 610). As an example, device 604 may be pre-configured (e.g., RRC pre-configured) with periodic CSI reporting settings associated with WUS reception, wherein the number of reports associated with the CSI reporting settings (e.g., reportQuantity This includes at least one of the different types reported by device 604.

[0150] In some respects, the number of reports set in the periodic CSI report setting may instruct device 604 to report predicted future measurement reports (e.g., L1-RSRP reports, L1-SINR reports, or other types of measurement reports not explicitly listed herein) for one or more reference signals (e.g., Type D-QCL source reference signals) that report the TCI status of the CORESET associated with multiple WUS monitoring instances for one or more DRX on-time cycles following the first DRX on-time cycle. Additionally or alternatively, the number of reports set in the periodic CSI report setting may instruct device 604 to report the first K resources (e.g., in terms of L1-RSRP, L1-SINR, or another type of measurement report) of reference signals (e.g., Type D-QCL source reference signals) that report the TCI status of the CORESET associated with multiple WUS monitoring instances for one or more DRX on-time cycles following the first DRX on-time cycle.

[0151] For predictions based on CSI reports, the first WUS 612 may include an additional single bit indicating whether device 604 should transmit a periodic CSI report during the corresponding DRX activation period (e.g., the first DRX activation period) and / or in one or more subsequent DRX activation periods (e.g., the second DRX activation period, the third DRX activation period, etc.). In some aspects, whether device 604 transmits the periodic CSI report in the corresponding DRX activation period or in one or more subsequent DRX activation periods may be predefined or based on a separate network configuration. If the periodic CSI report will be sent in several subsequent DRX activation periods, the indication 618 for the prediction result may use the DRX activation period in which the CSI report is sent as the first DRX activation period, rather than the DRX activation period in which the considered WUS (e.g., the first WUS 612) is received. In some respects, device 604 may be configured and / or instructed to transmit periodic CSI reports several DRX start cycles later after receiving the first WUS 612 and the associated indication 616, based on measurements of synchronization signals and / or reference signals (e.g., SSB, CSI-RS, etc.) by device 604 relative to a time series (e.g., once the first WUS 612 and the associated indication 616 are received), to achieve more reliable time prediction performance.

[0152] In some aspects, indication 618 may include one or more MAC-CE-based predictions. For example, device 604 may report one or more of the previously described information (e.g., predicted future measurement reports, such as L1-RSRP reports and / or L1-SINR reports and / or top K resources) via uplink MAC-CE. Similar to CSI-based predictions, and as an example, the first WUS 612 may include an additional single bit indicating whether device 604 should transmit the MAC-CE during the corresponding DRX-enabled period and / or in a few subsequent DRX-enabled periods. Additionally, whether device 604 transmits the MAC-CE during the corresponding DRX-enabled period or in a few subsequent DRX-enabled periods may be predefined or based on a separate network configuration. If the MAC-CE is transmitted in a few subsequent DRX-enabled periods, the prediction result should take the DRX-enabled period in which the MAC-CE is sent, rather than the DRX-enabled period in which the considered WUS (e.g., the first WUS 612) is received, as the first DRX-enabled period.

[0153] In some respects, device 604 may have different expectations for UL grant when transmitting indication 618 for the requested prediction result. For example, if the DRX enable period in which device 604 transmits indication 618 (e.g., periodic CSI report, uplink MAC-CE, etc.) is associated with a positive wake-up indication (e.g., WUS indication 614 includes an indication for device 604 to start an enable duration timer), then device 604 may expect a correctly scheduled uplink channel (e.g., Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), etc.) for transmitting indication 618. Otherwise, device 604 may expect a configuration grant (CG) for the uplink channel (e.g., CG-PUSCH) to be configured for this transmission of indication 618.

[0154] In some aspects, network entity 602 may provide device 604 with dynamic updates to indication 616 for one or more WUS monitoring instances via MAC-CE and / or DCI signaling relative to parameters of indication 616. For example, the information and / or parameters of indication 616 previously described (e.g., information and / or parameters of periodic CSI reports) may be RRC configured, but this information and / or parameters may be updated and / or indicated via downlink MAC-CE or DCI (e.g., downlink grant). As an example, network entity 602 may use MAC-CE / DCI signaling to update CSI reporting settings linked to indication 616 in the first WUS 612 (e.g., a request to report one or more predictions). In some aspects, different candidate CSI reporting settings may be associated with different measurement resources and / or prediction targets and / or AI / ML functional forms or model IDs.

[0155] Additionally, in some respects, and as referenced Figure 5 As described, the configuration 610 of multiple sets of WUS monitoring instances (e.g., multiple WUS monitoring instances for each set of WUS monitoring instances) and the indication 618 for one or more predictions can be extended to other types of transmit beamsweeps for WUS detection. For example, instead of associating the configuration 610 of multiple sets of WUS monitoring instances with different search space sets, if a single search space set is associated with multiple TCI states of different MOs across the search space set, the configuration 610 of multiple sets of WUS monitoring instances can be associated with different MOs or different TCI states and / or QCL sources associated with such different MOs.

[0156] Example aspects associated with DRX communication Figure 7A , Figure 7B and Figure 7C Various example aspects of communication with DRX are described. For example, Figure 7A An example of a DRX 700 with WUS is depicted. Figure 7B An example of configuration 701 for WUS is depicted, and Figure 7C An example of WUS monitoring instance configuration 702 is depicted. In some aspects, DRX configuration 700, configuration 701 for WUS, and WUS monitoring instance configuration 702 can be implemented. Figures 1 to 6 These aspects may be implemented through or by these aspects. For example, as described herein, devices (e.g., UE104, device 504, device 604, or as referenced) Figures 1 to 3 and Figures 5 to 6The described similar terminal equipment can be configured for C-DRX and / or DRX mode operation (e.g., periodically alternating between active and inactive modes during a DRX activation period) for use with network entities (e.g., BS 102, BS 180, network entity 502, network entity 602, base stations, or as referenced). Figures 1 to 3 and Figures 5 to 6 The communication of the described network entities, wherein C-DRX and / or DRX mode operation is performed based on DRX configuration 700, configuration 701 for WUS and WUS monitoring instance configuration 702.

[0157] In some respects and such Figure 7A As illustrated in the example, the device can be configured to operate in DRX mode based on DRX configuration 700, and can be configured to monitor WUS (e.g., DRX activity time) in a set 704 of WUS monitoring instances outside of one or more DRX on-cycles 706. For example, the set 704 of WUS monitoring instances can be associated with a DRX on-cycle 706, where the DRX on-cycle 706 is part of a corresponding DRX cycle. For example, a first set 704A of WUS monitoring instances can be associated with a first DRX on-cycle 706A, and the first DRX on-cycle 706A is part of a DRX cycle 708. Additionally, a second set 704B of WUS monitoring instances can be associated with a second DRX on-cycle 706B and a second DRX cycle (e.g., in...). Figure 7A not shown in the example).

[0158] WUS can instruct the device's MAC entity whether to start an enable duration timer for the next DRX cycle (e.g., drx-onDurationTimer For example, WUS received and decoded in the first set 704A of the WUS monitoring instance can indicate whether the device (e.g., the device's MAC entity) should start an on-duration timer for the first DRX on-cycle 706A. Additionally, WUS may not affect other timers of the device (e.g., bwp-inactivityTimer , dataInactivityTimer , sCellDeactivationTimer wait).

[0159] In some respects, WUS can be a PDCCH defined by DCI format 2_6, where the CRC is scrambled by PS-RNTI. Additionally, WUS can be shared by a set of devices and can be monitored in a common search space set (e.g., a set of 704 WUS monitoring instances). In some respects, WUS can be configured on a primary cell (PCell) and / or a primary / secondary cell (PSCell). Additionally, WUS can indicate the dormant behavior of a group of secondary cells (SCells) (up to five (5)).

[0160] exist Figure 7B In the example, the configuration 701 for WUS may include one or more device-specific fields, which include a corresponding wake-up indicator bit 710 and a corresponding content field 712. For example, a first device-specific field 714A may include a first wake-up indicator bit 710A and a first content field 712A, a second device-specific field 714B may include a second wake-up indicator bit 710B and a second content field 712B, and so on, up to an nth device-specific field including an nth wake-up indicator bit 710C and an nth content field 712C. One or more device-specific fields may be considered as the payload size 716 for WUS. Additionally, the configuration 701 for WUS may include a CRC 718.

[0161] In some respects, the position of the wake-up indicator bit 710 within the payload size 716 of the WUS can indicate the location of the device-specific field 712. For example, the position of the wake-up indicator bit 710 (such as the time-frequency resources for sending the wake-up indicator bit 710 within the payload size 716) can indicate the start of each device-specific field 712. Additionally, the WUS (e.g., PDCCH-WUS, DCI format 2_6, etc.) can be shared by a group of devices, and each device in the group can be assigned a device-specific field 712 in the DCI. In some respects, the WUS can be used for SCell groups (e.g., up to five (5)) for indication of sleep behavior outside of active time, as referenced Figure 7A As described. Additionally or alternatively, indications for SCell groups of hibernation behavior during active periods can be configured individually (e.g., via scheduling DCI).

[0162] In some aspects, for monitoring DCI format 2_6 (e.g., WUS), the device may be provided with a PS-RNTI for scrambling DCI format 2_6 using CRC 718. Additionally, the device may be provided with one or more common search spaces (CSS) (e.g., Type 3-PDCCH CSS) for monitoring DCI format 2_6 with PS-RNTI. In some aspects, more than one search space set may be configured for DCI format 2_6, and the CORESET associated with the search space set may have different TCI states (e.g., for WUS beam sweeping in a frequency domain range such as frequency domain range 2 (FR2)).

[0163] In some aspects, each device-specific field 714 may include a wake-up indicator bit 710 and an SCell sleep bitmap 720 (e.g., in the content field 712). For example, once a device detects DCI format 2_6 in a WUS monitoring instance, the device can find an assigned field for itself in the content field 712 and / or the SCell sleep bitmap 720. In some aspects, the SCell sleep bitmap 720 may be of a configurable size (e.g., 0 bits to 5 bits). Table 1 below indicates device behavior based on the wake-up indicator bit 710.

[0164] Additionally, a time offset for DRX mode operation can be provided to the device (e.g., ps_Offset The time offset indicates the time at which the device begins positioning a DCI format 2_6 WUS monitoring instance before the time slot at the start of the DRX cycle. In some respects, the time offset can be a value between 0.125 milliseconds (ms) and 15 ms (e.g., ) exist Figure 7C In the example, WUS monitoring instance configuration 702 may include a search space set period 724, the duration of WUS monitoring instance 728 726, one or more monitoring symbols 730 within the duration 726, the minimum time interval 732 between WUS monitoring instances 728 (e.g., based on device capabilities), time offset 734, and the next occurring DRX period 736.

[0165] For WUS monitoring instance 728, for each WUS monitoring instance 728 configured to monitor DCI format 2_6 (e.g., the configured search space set), the device can monitor monitoring symbols 730 (e.g., PDCCH MO) in duration 726, which are offset by time 734 (e.g., ps_Offset It begins at or after the start of the duration timer (e.g., drx- onDurationTimer The starting time slot (e.g., time slot) The minimum time gap 732 can be defined as the time duration preceding the time slot that the start-up timer will initiate, during which the device does not need to monitor DCI format 2_6. In some respects, the minimum time gap 732 can be a device capability and can be in units of time slots (e.g., depending on the subcarrier spacing (SCS)). For example, for each SCS supported by the device, the device can report one of two candidate values ​​(e.g., the maximum value of 3ms).

[0166] If the device detects DCI format 2_6 in at least one WUS monitoring instance 728 (e.g., in one or more monitoring symbols 730), the device may follow the instructions in the device-specific fields of the DCI as described in Table 1. Additionally or alternatively, if the device monitors WUS monitoring instance 728 but does not detect DCI format 2_6 (e.g., discontinuous transmissions (DTX) from network entities and / or false detections at the device), then higher-layer parameters (e.g., ps-WakeupOrNot This option indicates whether the device should start the enable duration timer for the next DRX cycle 736. If no higher-level parameter is provided, the device may not start the enable duration timer for the next DRX cycle 736.

[0167] If the device is configured with both short and long DRX periods, it can monitor DCI format 2_6 for the long DRX period. For the short DRX period, the device can always start an on-time timer for the short DRX period. In some cases, it may not be necessary for the device to monitor DCI format 2_6 during DRX activity periods.

[0168] In some respects, the device may start an on-time timer for the next DRX cycle 736 if any of the following are true: the currently active BWP is not configured to monitor DCI format 2_6; for all WUS monitoring instances, the device is not required to monitor the PDCCH used to detect DCI format 2_6 (e.g., due to overlap with SSB, other PDCCH timings with different QCL-TypeD attributes, measurement gaps, BWP switching delays, etc.); for the DRX cycle, there are no WUS monitoring instances.

[0169] In some respects, the device may or may not perform one or more background activities with DRX. For example, if DRX is configured, the corresponding device may not need to perform Radio Resource Management (RRM) measurements except during DRX activity periods. If the DRX period is greater than a threshold (e.g., greater than 80 ms), the device may not expect CSI-RS resources for mobility to be available except during DRX activity periods. Additionally or alternatively, for CSI measurement and reporting, if DRX is configured, the corresponding device may not need to measure CSI except during DRX activity periods, and the device may not report CSI on the PUCCH (e.g., periodic / semi-periodic CSI reporting) except during DRX activity periods.

[0170] In some respects, if the activation duration timer is not triggered by DCI format 2_6 (e.g., due to a lack of downlink traffic), the device can remain active for extended periods outside of DRX activity time. Therefore, the device may not perform RRM measurements outside of activity time, and its mobility performance may degrade. Additionally, the device may not perform CSI measurements and reporting outside of activity time, and link performance may degrade or beam-paired links may fail.

[0171] Table 2 indicates the time-domain status associated with DRX: Table 2 - Time Domain Status of DRX

[0172] In some aspects, the device can perform RRM measurements during a configured on-duration period outside of DRX activity time, and CSI-RS resources for mobility can be available during a configured on-duration period outside of DRX activity time. Additionally or alternatively, the device can perform CSI measurements and periodic CSI reporting during the configured on-duration period. In some aspects, higher-level parameters (e.g., PS_Periodic_CSI_TransmitOrNot This allows enabling or disabling periodic CSI reporting for the device (e.g., in addition to L1-RSRP reporting) during the configured on-time period. Additionally or alternatively, another higher-level parameter (e.g., PS_Periodic_L1-RSRP_TransmitOrNot This allows you to enable or disable periodic L1-RSRP reports for beam management.

[0173] Figure 8 An example of a communication system 800 with DRX is depicted. In some aspects, the communication system 800 can implement... Figures 1 to 7C These aspects may be implemented or can be achieved through these aspects. For example, communication system 800 may include network entity 802, first device 804A, and second device 804B, wherein network entity 802 may represent as referenced. Figures 1 to 3 and Figures 5 to 7C The described base station or similar network entity (e.g., BS 102, BS 180, network entity 502, network entity 602, etc.), and devices 804A and 804B may represent as referenced. Figures 1 to 3 and Figures 5 to 7C The UE or similar terminal device described (e.g., UE 104, device 504, device 604, etc.).

[0174] Additionally, in Figure 8 In the examples and as referenced Figure 5 and Figure 6As described, devices 804A and 804B can be configured for C-DRX and / or DRX mode operation (e.g., periodically alternating between active and inactive modes during a DRX activation cycle). As described herein and referenced Figure 5 and Figure 6 As described, devices 804A and 804B can also be configured to monitor WUS outside of DRX active periods to indicate whether devices 804A and / or 804B may continue to sleep during the corresponding DRX on-duration period (e.g., if no data is available for devices 804A and / or 804B) or whether devices 804A and / or 804B should “wake up” during the corresponding DRX on-duration period to receive data.

[0175] In some aspects, the communication system 800 may represent CSI measurements and reporting for devices 804A and 804B when WUS is configured. Additionally, devices 804A and 804B may be provided with higher-level parameters that enable or disable periodic CSI reporting during the on-time period of the configuration for the respective devices (e.g., ...). PS_Periodic_CSI_ TransmitOrNot ).exist Figure 8 In the example, device 804A can be disabled from sending periodic CSI reports during the configured on period (e.g., PS_Periodic_CSI_TransmitOrNot = "Disabled"), and device 804B can be enabled to send periodic CSI reports during the configured on period (e.g., PS_Periodic_CSI_TransmitOrNot = "Enable").

[0176] exist Figure 8In the example, network entity 802 may send multiple CSI-RS 806 (e.g., periodically), where devices 804A and 804B are configured to transmit one or more CSI reports 808 (e.g., periodic CSI reports) for CSI-RS 806 based on whether WUS 810 (e.g., DCI format 2_6) is received and based on higher-layer parameters. For example, network entity 802 may send WUS 810 before the DRX activity time 812 of DRX cycle 814, where WUS 810 instructs devices 804A and 804B to start an on-duration timer for DRX activity time 812. Therefore, based on detecting and receiving WUS 810, devices 804A and 804B may perform one or more measurements 816 during the DRX activity time 812 of the CSI-RS 806 sent by network entity 802. Subsequently, device 804A may transmit one or more CSI reports 808A based on one or more measurements 816 during DRX activity time 812, and device 804B may transmit one or more CSI reports 808B based on one or more measurements 816 during DRX activity time 812. In some respects, devices 804A and 804B may avoid performing any measurements at one or more time points 818 of CSI-RS 806 outside of DRX activity time.

[0177] In some respects, during WUS monitoring instance 820, network entity 802 may avoid transmitting WUS to devices 804A and 804B. Even without WUS transmission, the time duration 822 may be indicated by the on-duration timer, but time duration 822 is not the DRX active time. Therefore, based on the fact that no WUS was received during the configured on-duration period and that sending periodic CSI reports is disabled, device 804A may not transmit any CSI reports during time duration 822. Additionally or alternatively, based on being enabled to send periodic CSI reports during the configured on-duration period, device 804B may perform one or more measurements 816 on CSI-RS 806 sent by network entity 802 and may transmit one or more CSI reports 808B during time duration 822.

[0178] Example operation via WUS indication and / or request for time beam prediction for DRX communication Figure 9 An example of a DRX communication system 900 with time beam prediction according to various aspects of this disclosure is depicted. In some aspects, the DRX communication system 900 can implement Figures 1 to 8 These aspects or can be achieved through these aspects. For example, a network entity can configure multiple sets 902 of WUS monitoring instances for a device (e.g., as shown in the reference). Figure 5 and Figure 6The described configurations 510 and 610, wherein each set of WUS monitoring instances (e.g., each set of WUS monitoring instances in a plurality of sets of WUS monitoring instances) includes a plurality of WUS monitoring instances 904. In some aspects, the plurality of WUS monitoring instances 904 may correspond to those previously referenced. Figure 5 The multiple transmit beams 906 are described. Additionally, multiple sets 902 of WUS monitoring instances may be associated with multiple DRX activation cycles 908. In some aspects, each of the multiple WUS monitoring instances 904 may include and / or correspond to a respective SSB.

[0179] As described herein, a network entity may transmit a first WUS to a device in one or more of a plurality of WUS monitoring instances 904 within an associated first DRX enable cycle 908A, such that the device receives the first WUS via one or more of a transmit beam 906. For example, the network entity may transmit the first WUS in a second WUS monitoring instance 904B, which may correspond to a second transmit beam 906B. The first WUS may include an indication of whether the device initiates an enable duration timer for the first associated DRX enable cycle 908A. Additionally, in Figure 9 In one example, the first WUS may include an instruction 910 for a third WUS monitoring instance 904C, which anticipates that the device will monitor at least one additional WUS in at least one set of WUS monitoring instances from a plurality of sets of WUS monitoring instances, wherein at least one set of WUS monitoring instances is associated with at least one DRX on-cycle 908B following the first DRX on-cycle 908A.

[0180] In some respects, network entities may determine a third WUS monitoring instance 904C for monitoring at least one additional WUS for the device, based on historical measurements received from the device and / or predictive reports transmitted by the device, as referenced. Figure 5 As described. Additionally or alternatively, the device may determine, based on a received request to perform prediction, that a network entity expects to transmit at least one additional WUS in the third WUS monitoring instance 904C, as referenced. Figure 6 As described. Subsequently, prior to at least one DRX activation cycle 908B, the device may monitor and receive at least one additional WUS in a third WUS monitoring instance 904C, which may correspond to a third transmit beam 906C.

[0181] In some aspects, the device may use the Type D-QCL assumption to receive downlink channels from network entities during at least one DRX enable period 908B. For example, if at least one additional WUS received based on monitoring a third WUS monitoring instance 904C includes a positive indication for the device to initiate an enable duration timer for at least one DRX enable period 908B, the device may also receive downlink channels during at least one DRX enable period 908B using a third transmit beam 906C. Additionally, the multiple WUS monitoring instances 904 may include multiple search space sets, multiple PDCCH MOs, or combinations thereof.

[0182] Example operation of an entity for time beam prediction via WUS for DRX communication in a communication network Figure 10 A process flow 1000 for communication between network entities and devices in a network, with an indication of time beam prediction, according to various aspects of this disclosure, is described. In some aspects, process flow 1000 can implement... Figures 1 to 9 These aspects or can be implemented by these aspects. For example, the process flow may include network entity 1002 and at least one device 1004, wherein network entity 1002 represents, as referenced... Figures 1 to 3 and Figures 5 to 9 The described base station or similar network entity (e.g., BS 102, BS 180, network entity 502, network entity 602, network entity 802, etc.), and device 1004 may represent as referenced. Figures 1 to 3 and Figures 5 to 9 The described UE or similar terminal device (e.g., UE 104, device 504, device 604, device 804, etc.). In some aspects, process flow 1000 may represent network entity 1002 transmitting an instruction for time beam prediction to device 1004, as referenced. Figure 5 As described.

[0183] In the following description of process flow 1000, the operations between network entity 1002 and device 1004 may be performed in different orders or at different times. Some operations may also be excluded from process flow 1000, or other operations may be added to process flow 1000. It will be understood that although network entity 1002 and device 1004 are shown to perform several operations of process flow 1000, any wireless device may perform the operations shown.

[0184] At 1006, device 1004 can receive configurations for multiple sets of WUS monitoring instances from network entity 1002 (e.g., as referenced). Figure 5The described configuration 510 involves multiple sets of WUS monitoring instances associated with multiple DRX enable cycles, and each set of WUS monitoring instances (e.g., within the multiple sets of WUS monitoring instances) includes multiple WUS monitoring instances. In some aspects, the multiple WUS monitoring instances may include multiple search space sets, multiple PDCCH MOs, or combinations thereof. In some aspects, device 1004 may receive the configuration via RRC signaling. Additionally or alternatively, device 1004 may receive the configuration via MAC-CE, DCI messages, or combinations thereof.

[0185] At 1008, device 1004 may transmit to network entity 1002 one or more measurement reports on signals received from network entity 1002 (e.g., as referenced). Figure 5 The described measurement report 516). For example, one or more measurement reports for signals received from network entity 1002 may include characteristics of SSB received from network entity 1002 (e.g., SSB power measurement and / or signal quality measurement), characteristics of CSI-RS received from network entity 1002 (e.g., CSI-RS power measurement and / or signal quality measurement), L1 measurement reports for reference signals received from network entity 1002 (e.g., L1-RSRP report, L1-SINR report, etc.), or combinations thereof.

[0186] At 1010, device 1004 may transmit to network entity 1002 the prediction results associated with one or more WUS monitoring instances (e.g., as referenced). Figure 5 The report describes the predicted results (518).

[0187] At 1012, network entity 1002 can determine one or more WUS monitoring instances for device 1004 to monitor at least one additional WUS in at least one or more WUS monitoring instances in at least one set of WUS monitoring instances from a plurality of sets of WUS monitoring instances, wherein at least one set of WUS monitoring instances is associated with at least one DRX activation period following a first DRX activation period. For example, network entity 1002 can determine one or more WUS monitoring instances based on one or more measurement reports. Additionally or alternatively, network entity 1002 can determine one or more WUS monitoring instances based on reports of prediction results.

[0188] At 1014, device 1004 may receive a first WUS from network entity 1002 before the first DRX enable cycle in a plurality of DRX enable cycles (e.g., as referenced). Figure 5The first WUS 512 described herein. In some aspects, the first WUS may include an indication of whether to start an on-duration timer for a first DRX on-cycle (e.g., as referenced). Figure 5 The described WUS instruction 514) and instructions for one or more WUS monitoring instances among a plurality of WUS monitoring instances (e.g., as referenced). Figure 5 The described indication 520). In some aspects, the indication for one or more WUS monitoring instances may include indications for one or more search space sets associated with one or more WUS monitoring instances, indications for PDCCH MOs associated with search space sets, indications for one or more TCI states associated with search space sets, or combinations thereof.

[0189] In some respects, the indication of whether to start the enable duration timer may indicate to device 1004 that the enable duration timer for the first DRX enable cycle is not started. Additionally or alternatively, the indication of whether to start the enable duration timer may indicate that the enable duration timer for the first DRX enable cycle is started.

[0190] In some aspects, an indication of one or more WUS monitoring instances may include one or more corresponding search space set identifiers associated with one or more WUS monitoring instances or one or more TCI status identifiers associated with one or more WUS monitoring instances. In some aspects, an indication of one or more WUS monitoring instances may include one or more identifiers associated with one or more WUS monitoring instances, a bitmap indicating one or more WUS monitoring instances, a combined index indicating one or more WUS monitoring instances, or a combination thereof.

[0191] In some respects, the first WUS may include common fields for multiple devices, including device 1004. Additionally, the common fields may include indications of one or more WUS monitoring instances.

[0192] At 1016, device 1004 may receive an indication of the number of identifiers intended to be used for association with one or more identifiers of one or more WUS monitoring instances. In some aspects, device 1004 may receive the indication of the number of identifiers to be intended via RRC signaling, MAC-CE, DCI messages, or a combination thereof.

[0193] At 1018, device 1004 can monitor at least one additional WUS (e.g., as referenced) in at least one of one or more WUS monitoring instances in at least one set of multiple sets of WUS monitoring instances. Figure 5The at least one additional WUS 522 described herein, wherein at least one set of WUS monitoring instances is associated with at least one DRX activation cycle following the first DRX activation cycle.

[0194] In some aspects, at least one set of WUS monitoring instances may be a single set of WUS monitoring instances, and at least one DRX activation period following the first DRX activation period may be a single DRX activation period. In some aspects, each WUS that can be received in a single set of WUS monitoring instances may include the same payload size.

[0195] Additionally or alternatively, at least one set of WUS monitoring instances may include multiple sets of WUS monitoring instances, and at least one DRX activation period following the first DRX activation period may include multiple DRX activation periods associated with the multiple sets of WUS monitoring instances. In some aspects, device 1004 may monitor at least one additional WUS based on: the expectation of monitoring multiple sets of WUS monitoring instances, the configuration of the number of sets of WUS monitoring instances corresponding to the multiple sets of WUS monitoring instances (e.g., signaling via RRC signaling, MAC-CE, DCI messages, or combinations thereof), and the fact that the number of one or more WUS monitoring instances is the same for each set of WUS monitoring instances in the multiple sets of WUS monitoring instances, or a combination thereof.

[0196] In some aspects, device 1004 may monitor at least one additional WUS in at least one of the plurality of WUS monitoring instances, in addition to one or more WUS monitoring instances, based on unsuccessful decoding of the first WUS, unsuccessful identification of one or more WUS monitoring instances indicated in the first WUS (e.g., device 1004 may successfully decode a portion of the first WUS (such as an indication of whether to start an on-timer), but may fail to decode other portions of the first WUS (such as an indication of one or more WUS monitoring instances)), or a combination thereof.

[0197] In some aspects, device 1004 may receive a second WUS from network entity 1002 after receiving a first WUS, wherein the second WUS includes an indication of whether to start an on-duration timer for a second DRX on-duration period corresponding to the second WUS and an indication of one or more second WUS monitoring instances among a plurality of WUS monitoring instances. Subsequently, after receiving the second WUS, device 1004 may monitor at least one additional WUS in at least one of the one or more WUS monitoring instances based on unsuccessful decoding of the second WUS, unsuccessful identification of one or more second WUS monitoring instances indicated in the second WUS, or a combination thereof.

[0198] At 1020, network entity 1002 may transmit at least one additional WUS to device 1004 from at least one of one or more WUS monitoring instances in at least one set of multiple sets of WUS monitoring instances.

[0199] In some aspects, device 1004 may receive at least one additional WUS (e.g., a second WUS) from network entity 1002 based on monitoring at least one WUS monitoring instance. In some aspects, the at least one additional WUS may include an indication of whether to start an on-duration timer for a second DRX on-duration period corresponding to the at least one additional WUS, and an indication of monitoring a plurality of WUS monitoring instances for a subsequent set of WUS monitoring instances associated with a DRX on-duration period following the second DRX on-duration period.

[0200] At 1022, device 1004 may, based on the successful reception and decoding of a first WUS including an indication of one or more WUS monitoring instances, ignore the remaining WUS monitoring instances among the plurality of WUS monitoring instances in addition to the one or more WUS monitoring instances, in order to monitor and receive at least one additional WUS.

[0201] At 1024, device 1004 may receive a downlink channel from network entity 1002 in at least one DRX activation period following the first DRX activation period. For example, device 1004 may receive at least one additional WUS (e.g., a second WUS) from network entity 1002 via a first beam associated with a first WUS monitoring instance in one or more WUS monitoring instances, wherein the at least one additional WUS includes an indication to initiate an activation duration timer for a second DRX activation period among a plurality of DRX activation periods, and device 1004 may receive a downlink channel from network entity 1002 via the first beam in the second DRX activation period.

[0202] Example operation of an entity requesting time beam prediction via WUS for DRX communication in a communication network Figure 11 A process flow 1100 is described according to various aspects of this disclosure for communication between network entities and devices in a network, requesting time beam prediction. In some aspects, process flow 1100 can implement Figures 1 to 9 These aspects or can be implemented by these aspects. For example, the process flow may include network entity 1102 and at least one device 1104, wherein network entity 1102 represents, as referenced... Figures 1 to 3 and Figures 5 to 9 The described base station or similar network entity (e.g., BS 102, BS 180, network entity 502, network entity 602, network entity 802, etc.), and device 1104 may represent as referenced. Figures 1 to 3 and Figures 5 to 9 The described UE or similar terminal device (e.g., UE 104, device 504, device 604, device 804, etc.). In some aspects, process flow 1100 may represent network entity 1102 requesting device 1104 to determine time beam prediction, as referenced. Figure 6 As described.

[0203] In the following description of process flow 1100, the operations between network entity 1102 and device 1104 may be performed in different orders or at different times. Some operations may also be excluded from process flow 1100, or other operations may be added to process flow 1100. It will be understood that although network entity 1102 and device 1104 are shown to perform several operations of process flow 1100, any wireless device may perform the operations shown.

[0204] At 1106, device 1104 can receive configurations for multiple sets of WUS monitoring instances from network entity 1102 (e.g., as referenced). Figure 6 The described configuration 610) includes multiple sets of WUS monitoring instances associated with multiple DRX enable cycles, and each set of WUS monitoring instances (e.g., in the multiple sets of WUS monitoring instances) comprises multiple WUS monitoring instances. In some aspects, the multiple WUS monitoring instances may include multiple search space sets, multiple PDCCH MOs, or combinations thereof. In some aspects, device 1104 may receive the configuration via RRC signaling. Additionally or alternatively, device 1104 may receive the configuration via MAC-CE, DCI messages, or combinations thereof.

[0205] At 1108, device 1104 can receive configuration for periodic CSI reporting settings associated with WUS reception. In some aspects, the configuration for periodic CSI reporting settings can be received via RRC signaling, MAC CE, DCI messages, or a combination thereof.

[0206] At 1110, device 1104 may receive a first WUS from network entity 1102 before the first DRX enable cycle in a plurality of DRX enable cycles (e.g., as referenced). Figure 6 The first WUS (612) described herein includes an indication of whether to start an on-duration timer for a first DRX on-cycle (e.g., as referenced). Figure 6 The described WUS instruction 614) and the instructions for reporting one or more predictions corresponding to multiple WUS monitoring instances (e.g., as referenced) Figure 6The described instruction 616). In some aspects, the instruction to report one or more predictions may include bits indicating whether the device 1104 should transmit the instruction to one or more predictions in a first DRX on cycle or in a DRX on cycle after the first DRX on cycle.

[0207] In some aspects, one or more predictions may include channel characteristics of one or more predictions for each of the multiple WUS monitoring instances. For example, the channel characteristics of one or more predictions for each WUS monitoring instance may include L1-RSRP measurements, L1-SINR measurements, or combinations thereof associated with one or more QCL source reference signals for one or more TCI states of one or more CORESETs associated with each WUS monitoring instance.

[0208] At 1112, device 1104 may receive configuration permission for the uplink shared channel from network entity 1102 based on an indication of whether to start the enable duration timer for the first DRX enable cycle, including a negative indication of not starting the enable duration timer.

[0209] At 1114, device 1104 may transmit an indication of the one or more predictions to network entity 1102 (e.g., as referenced). Figure 6 The described indication 618). In some aspects, the indication for one or more predictions may include an indication for one or more WUS monitoring instances among a plurality of WUS monitoring instances. In some aspects, device 1104 may transmit the indication for one or more predictions in a CSI report based on a configuration received at 1108 for periodic CSI report settings. Additionally or alternatively, device 1104 may transmit the indication for the one or more predictions in an uplink MAC-CE.

[0210] In some aspects, the indication of whether to start the activation duration timer for the first DRX activation period may include a positive indication to start the activation duration timer, and device 1104 may transmit an indication of one or more predictions in a scheduled uplink channel based on the positive indication. Additionally or alternatively, the indication of whether to start the activation duration timer for the first DRX activation period may include a negative indication to start the activation duration timer, and device 1104 may transmit an indication of one or more predictions in an uplink shared channel based on the configured permission for reception at 1112.

[0211] At 1116, device 1104 and / or network entity 1102 may determine one or more WUS monitoring instances from a plurality of WUS monitoring instances based on one or more predictions. For example, at 1116A, network entity 1102 may determine one or more WUS monitoring instances from a plurality of WUS monitoring instances based on one or more predictions. Additionally or alternatively, at 1116B, device 1104 may determine one or more WUS monitoring instances from a plurality of WUS monitoring instances based on one or more predictions.

[0212] At 1118, if network entity 1102 determines one or more WUS monitoring instances among a plurality of WUS monitoring instances based on one or more predictions, then device 1104 can monitor a second WUS.

[0213] At 1120, device 1104 may receive a second WUS from network entity 1102 prior to a second DRX activation cycle among a plurality of DRX activation cycles, wherein the second WUS includes an indication of whether to initiate an activation duration timer for the second DRX activation cycle and an indication of one or more WUS monitoring instances among a plurality of WUS monitoring instances. For example, the indication of one or more WUS monitoring instances may include an indication of a sorted list of resources according to: L1-RSRP measurements, L1-SINR measurements, or combinations thereof associated with one or more QCL source reference signals for one or more TCI states of one or more CORESETs associated with one or more WUS monitoring instances.

[0214] At 1122, device 1104 can monitor at least one additional WUS in at least one of one or more WUS monitoring instances in at least one set of WUS monitoring instances in a plurality of sets of WUS monitoring instances, wherein at least one set of WUS monitoring instances is associated with at least one DRX activation cycle following a first DRX activation cycle.

[0215] At 1124, network entity 1102 may transmit at least one additional WUS to device 1104 from at least one of one or more WUS monitoring instances in at least one set of multiple sets of WUS monitoring instances.

[0216] Example Operation Figure 12 It shows a device (such as) Figure 1 and Figure 3 Method 1200 for wireless communication of UE 104.

[0217] Method 1200 begins at block 1205 with a configuration of receiving multiple sets of WUS monitoring instances from a network entity, wherein the multiple sets of WUS monitoring instances are associated with multiple DRX enable cycles, and each set of WUS monitoring instances in the multiple sets of WUS monitoring instances includes multiple WUS monitoring instances.

[0218] Method 1200 then proceeds to block 1210, receiving a first WUS from the network entity prior to the first DRX activation cycle of the plurality of DRX activation cycles, wherein the first WUS includes: an indication of whether to start an activation duration timer for the first DRX activation cycle; and an indication of one or more WUS monitoring instances of the plurality of WUS monitoring instances.

[0219] Method 1200 then proceeds to box 1215, where at least one additional WUS is monitored in at least one of one or more WUS monitoring instances in at least one set of WUS monitoring instances in a plurality of sets of WUS monitoring instances, wherein at least one set of WUS monitoring instances is associated with at least one DRX activation cycle following the first DRX activation cycle.

[0220] In some respects, method 1200 also includes transmitting to the network entity one or more measurement reports of signals received from the network entity.

[0221] In some respects, the one or more measurement reports of signals received from the network entity include characteristics of the SSB received from the network entity, characteristics of the CSI-RS received from the network entity, layer 1 measurement reports of reference signals received from the network entity, or combinations thereof.

[0222] In some respects, method 1200 also includes transmitting to network entities a report on the prediction results associated with one or more WUS monitoring instances.

[0223] In some respects, indications for one or more WUS monitoring instances include one or more corresponding search space set identifiers associated with one or more WUS monitoring instances or one or more TCI status identifiers associated with one or more WUS monitoring instances.

[0224] In some respects, indications of one or more WUS monitoring instances include one or more identifiers associated with one or more WUS monitoring instances, bitmaps indicating one or more WUS monitoring instances, combined indexes indicating one or more WUS monitoring instances, or combinations thereof.

[0225] In some respects, method 1200 also includes receiving an indication of the number of identifiers intended for the one or more identifiers.

[0226] In some respects, the at least one set of WUS monitoring instances is a single set of WUS monitoring instances, and at least one DRX activation period after the first DRX activation period is a single DRX activation period.

[0227] In some respects, each WUS received in a single set of WUS monitoring instances includes the same payload size.

[0228] In some respects, at least one set of WUS monitoring instances includes multiple sets of WUS monitoring instances, and at least one DRX activation period following the first DRX activation period includes multiple DRX activation periods associated with multiple sets of WUS monitoring instances.

[0229] In some respects, box 1215 includes monitoring the at least one additional WUS based on: the expectation of the plurality of sets of monitoring WUS monitoring instances, the configuration of the number of sets of WUS monitoring instances corresponding to the plurality of sets of WUS monitoring instances, and the fact that the number of the one or more WUS monitoring instances is the same or a combination thereof for each set of WUS monitoring instances in the plurality of sets of WUS monitoring instances.

[0230] In some aspects, method 1200 also includes monitoring the at least one additional WUS by ignoring the remaining WUS monitoring instances other than the one or more WUS monitoring instances based on the successful reception and decoding of the first WUS including the indication of the one or more WUS monitoring instances.

[0231] In some respects, box 1215 includes monitoring the at least one additional WUS in at least one of the plurality of WUS monitoring instances other than the one or more WUS monitoring instances, based on unsuccessful decoding of the first WUS, unsuccessful identification of the one or more WUS monitoring instances indicated in the first WUS, or a combination thereof.

[0232] In some aspects, method 1200 further includes receiving a second WUS from the network entity after receiving the first WUS, the second WUS including: an indication of whether to start an on-duration timer for a second DRX on-duration period corresponding to the second WUS; and an indication of one or more second WUS monitoring instances among a plurality of WUS monitoring instances; and wherein block 1215 includes, after receiving the second WUS, monitoring at least one additional WUS in at least one of the one or more WUS monitoring instances based on unsuccessful decoding of the second WUS, unsuccessful identification of one or more second WUS monitoring instances indicated in the second WUS, or a combination thereof.

[0233] In some respects, the first WUS includes common fields for multiple devices; the common fields include indications of one or more WUS monitoring instances; and the multiple devices include apparatuses.

[0234] In some respects, this indication of whether to start the start duration timer is used to indicate that the start duration timer should not be started.

[0235] In some respects, this indication of whether to start the start duration timer is used to indicate whether to start the start duration timer.

[0236] In some aspects, method 1200 further includes receiving a second WUS from the network entity via a first beam associated with a first WUS monitoring instance in the one or more WUS monitoring instances, wherein the second WUS includes an indication to initiate an on-duration timer for a second DRX on-duration of the plurality of DRX on-durations.

[0237] In some respects, method 1200 also includes receiving a downlink channel from the network entity via the first beam during the second DRX activation period.

[0238] In some respects, box 1205 includes configuration for receiving via RRC signaling.

[0239] In some respects, box 1205 includes receiving configuration via MAC-CE, DCI messages, or a combination thereof.

[0240] In some respects, multiple WUS monitoring instances include multiple search space sets, multiple PDCCH monitoring times, or a combination thereof.

[0241] In some aspects, method 1200 further includes receiving a second WUS from the network entity based on monitoring the at least one WUS monitoring instance, the second WUS including: an indication of whether to start an on-duration timer for a second DRX on-duration period corresponding to the second WUS; and an indication of monitoring a plurality of WUS monitoring instances for a subsequent set of WUS monitoring instances associated with a DRX on-duration period following the second DRX on-duration period.

[0242] In some respects, the indication for the one or more WUS monitoring instances includes indications for one or more search space sets associated with the one or more WUS monitoring instances, indications for PDCCH monitoring timings associated with search space sets, indications for one or more TCI states associated with search space sets, or combinations thereof.

[0243] In some respects, method 1200 can be performed by an apparatus to achieve one or more technical effects or a solution to the aforementioned technical problems. For example, based on method 1200, the apparatus can reduce power consumption by monitoring at least one additional WUS instead of monitoring each of a plurality of WUS monitoring instances, using one or more WUS monitoring instances indicated in the first WUS.

[0244] In some respects, method 1200 or any aspect thereof may be made possible by means of a device (such as...) Figure 16 The communication device 1600 performs the operation, and the device includes various components that are operable to, configured to, or adapted to perform the method 1200. The communication device 1600 is described in further detail below.

[0245] It should be noted that Figure 12 This is merely one example of a method, and other methods that include fewer, additional, or alternative operations may also be consistent with this disclosure.

[0246] Figure 13 It shows a device (such as) Figure 1 and Figure 3 BS 102 or about Figure 2 The method 1300 for wireless communication using a decomposed base station (discussed in this paper).

[0247] Method 1300 begins at block 1305 with the configuration of transmitting a plurality of sets of WUS monitoring instances to the device, wherein the plurality of sets of WUS monitoring instances are associated with a plurality of DRX enable cycles, wherein each set of WUS monitoring instances in the plurality of sets of WUS monitoring instances includes a plurality of WUS monitoring instances.

[0248] Method 1300 then proceeds to block 1310, transmitting a first WUS to the device prior to the first DRX enable cycle of the plurality of DRX enable cycles, wherein the first WUS includes: an indication of whether to start an enable duration timer for the first DRX enable cycle; and an indication of one or more WUS monitoring instances of the plurality of WUS monitoring instances.

[0249] Method 1300 then proceeds to block 1315, transmitting at least one additional WUS to the device in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances in the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX on cycle following the first DRX on cycle.

[0250] In some respects, method 1300 also includes receiving from the device one or more measurement reports on signals transmitted by the device.

[0251] In some respects, method 1300 also includes determining one or more WUS monitoring instances based on one or more measurement reports.

[0252] In some respects, the one or more measurement reports of the signals transmitted by the device include characteristics of the SSB transmitted by the device, characteristics of the CSI-RS transmitted by the device, layer 1 measurement reports of the reference signals transmitted by the device, or combinations thereof.

[0253] In some respects, method 1300 also includes receiving from the device a report on the prediction results associated with one or more WUS monitoring instances.

[0254] In some respects, method 1300 also includes identifying one or more WUS monitoring instances based on reports of the forecast results.

[0255] In some respects, indications for one or more WUS monitoring instances include one or more corresponding search space set identifiers associated with one or more WUS monitoring instances or one or more TCI status identifiers associated with one or more WUS monitoring instances.

[0256] In some respects, indications of one or more WUS monitoring instances include one or more identifiers associated with one or more WUS monitoring instances, bitmaps indicating one or more WUS monitoring instances, combined indexes indicating one or more WUS monitoring instances, or combinations thereof.

[0257] In some respects, method 1300 also includes transmitting an indication of the number of identifiers that the device intends to use for one or more identifiers.

[0258] In some respects, the at least one set of WUS monitoring instances is a single set of WUS monitoring instances, and at least one DRX activation period after the first DRX activation period is a single DRX activation period.

[0259] In some respects, each WUS that can be transmitted within a single set of WUS monitoring instances includes the same payload size.

[0260] In some respects, at least one set of WUS monitoring instances includes multiple sets of WUS monitoring instances, and at least one DRX activation period following the first DRX activation period includes multiple DRX activation periods associated with multiple sets of WUS monitoring instances.

[0261] In some respects, method 1300 also includes a configuration of the number of sets of WUS monitoring instances that correspond to multiple sets of WUS monitoring instances.

[0262] In some respects, the first WUS includes common fields for multiple devices; the common fields include indications of one or more WUS monitoring instances; and the multiple devices include devices.

[0263] In some respects, the indication of whether to start the start duration timer indicates to the device that the start duration timer should not be started.

[0264] In some respects, the indication of whether to start the start duration timer instructs the device to start the start duration timer.

[0265] In some aspects, block 1315 includes transmitting a second WUS via a first beam associated with a first WUS monitoring instance in the one or more WUS monitoring instances, wherein the second WUS includes an indication for the device to initiate an on-duration timer for a second DRX on-duration of the plurality of DRX on-durations; and wherein method 1300 further includes transmitting a downlink channel to the device via the first beam during the second DRX on-duration.

[0266] In some respects, box 1305 includes configuration transmission via RRC signaling.

[0267] In some respects, box 1305 includes the transmission of configuration via MAC-CE, DCI messages, or a combination thereof.

[0268] In some respects, multiple WUS monitoring instances include multiple search space sets, multiple PDCCH monitoring times, or a combination thereof.

[0269] In some respects, the at least one additional WUS includes a second WUS, the second WUS including: an indication of whether to start an on-duration timer for a second DRX on-cycle corresponding to the second WUS; and an indication of the device to monitor a plurality of WUS monitoring instances for a subsequent set of WUS monitoring instances associated with a DRX on-cycle after the second DRX on-cycle.

[0270] In some respects, the indication for the one or more WUS monitoring instances includes indications for one or more search space sets associated with the one or more WUS monitoring instances, indications for PDCCH monitoring timings associated with search space sets, indications for one or more TCI states associated with search space sets, or combinations thereof.

[0271] In some respects, method 1300 or any aspect thereof may be made possible by means of a device (such as...) Figure 17 The communication device 1700 is used to perform the method, which includes various components that are operable to, configured to, or adapted to perform the method 1300. The communication device 1700 is described in further detail below.

[0272] It should be noted that Figure 13 This is merely one example of a method, and other methods that include fewer, additional, or alternative operations may also be consistent with this disclosure.

[0273] Figure 14 It shows a device (such as) Figure 1 and Figure 3 Method 1400 for wireless communication of UE 104.

[0274] Method 1400 begins at block 1405 with a configuration of receiving multiple sets of WUS monitoring instances from a network entity, wherein the multiple sets of WUS monitoring instances are associated with multiple DRX enable cycles, and each set of WUS monitoring instances in the multiple sets of WUS monitoring instances includes multiple WUS monitoring instances.

[0275] Method 1400 then proceeds to block 1410, receiving a first WUS from the network entity prior to the first DRX activation cycle of the plurality of DRX activation cycles, wherein the first WUS includes: an indication of whether to start an activation duration timer for the first DRX activation cycle; and an indication of reporting one or more predictions corresponding to the plurality of WUS monitoring instances.

[0276] Method 1400 then proceeds to box 1415 to transmit instructions for one or more predictions to the network entity.

[0277] In some respects, one or more predictions include channel characteristics of one or more predictions for each of the multiple WUS monitoring instances.

[0278] In some respects, the one or more predicted channel characteristics for each WUS monitoring instance include L1-RSRP measurements, L1-SINR measurements, or combinations thereof associated with one or more QCL source reference signals for one or more TCI states of one or more CORESETs associated with each WUS monitoring instance.

[0279] In some respects, method 1400 also includes determining one or more WUS monitoring instances among a plurality of WUS monitoring instances based on one or more predictions.

[0280] In some aspects, method 1400 further includes monitoring at least one additional WUS in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances in the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX activation cycle following the first DRX activation cycle.

[0281] In some aspects, method 1400 further includes receiving a second WUS from the network entity prior to a second DRX activation cycle among the plurality of DRX activation cycles, the second WUS including: an indication of whether to start the activation duration timer for the second DRX activation cycle; and an indication of one or more WUS monitoring instances among the plurality of WUS monitoring instances.

[0282] In some aspects, method 1400 further includes monitoring at least one additional WUS in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances in the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX activation cycle following the first DRX activation cycle.

[0283] In some respects, indications for one or more forecasts include indications for one or more WUS monitoring instances out of a plurality of WUS monitoring instances.

[0284] In some aspects, method 1400 further includes monitoring at least one additional WUS in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances in the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX activation cycle following the first DRX activation cycle.

[0285] In some respects, the indication of one or more WUS monitoring instances includes an indication of an ordered list of resources according to: L1-RSRP measurements, L1-SINR measurements, or combinations thereof associated with one or more QCL source reference signals for one or more TCI states of one or more CORESETs associated with one or more WUS monitoring instances.

[0286] In some respects, the indication for reporting the one or more predictions includes bits indicating whether the indication for the one or more predictions is transmitted during the first DRX enable cycle or during a DRX enable cycle following the first DRX enable cycle.

[0287] In some respects, box 1415 includes conveying indications for one or more forecasts in the CSI report.

[0288] In some respects, method 1400 also includes receiving a configuration for setting periodic CSI reports associated with reception of WUS, wherein the indication of the one or more predictions is based on the reception of the configuration transmitted in the CSI report.

[0289] In some respects, box 1415 includes transmitting an indication of one or more predictions in the uplink MAC-CE.

[0290] In some respects, the indication of whether to start the activation duration timer for the first DRX activation period includes an affirmative indication of starting the activation duration timer; and box 1415 includes transmitting an indication of the one or more predictions in the scheduled uplink channel.

[0291] In some aspects, the indication of whether to start the activation duration timer for the first DRX activation period includes a negative indication of not starting the activation duration timer; and method 1400 further includes receiving configuration permission for the uplink shared channel from the network entity, wherein the indication of the one or more predictions is based on the reception of the configuration permission transmitted in the uplink shared channel.

[0292] In some respects, box 1405 includes configuration for receiving via RRC signaling.

[0293] In some respects, box 1405 includes receiving configuration via MAC-CE, DCI messages, or a combination thereof.

[0294] In some respects, multiple WUS monitoring instances include multiple search space sets, multiple PDCCH monitoring times, or a combination thereof.

[0295] In some respects, method 1400 can be performed by an apparatus to achieve one or more technical effects or a solution to the aforementioned technical problem. For example, based on method 1400, the apparatus can reduce power consumption by using one or more WUS monitoring instances from one or more prediction indications and / or determinations to monitor at least one additional WUS instead of monitoring each of multiple WUS monitoring instances.

[0296] In some respects, method 1400 or any aspect thereof may be made by means of a device (such as...) Figure 16 The communication device 1600 performs the operation, and the device includes various components that are operable to, configured to, or adapted to perform the method 1400. The communication device 1600 is described in further detail below.

[0297] It should be noted that Figure 14 This is merely one example of a method, and other methods that include fewer, additional, or alternative operations may also be consistent with this disclosure.

[0298] Figure 15 It shows a device (such as) Figure 1 and Figure 3 BS 102 or about Figure 2The method for wireless communication using the decomposed base station discussed in the article 1500.

[0299] Method 1500 begins at block 1505 with the configuration of transmitting a plurality of sets of WUS monitoring instances to the device, wherein the plurality of sets of WUS monitoring instances are associated with a plurality of DRX enable cycles, wherein each set of WUS monitoring instances in the plurality of sets of WUS monitoring instances includes a plurality of WUS monitoring instances.

[0300] Method 1500 then proceeds to block 1510, transmitting a first WUS to the device prior to the first DRX activation cycle of the plurality of DRX activation cycles, wherein the first WUS includes: an indication of whether to start an activation duration timer for the first DRX activation cycle; and an indication of reporting one or more predictions corresponding to the plurality of WUS monitoring instances.

[0301] Method 1500 then proceeds to box 1515 to receive instructions from the device for one or more predictions.

[0302] In some respects, one or more predictions include channel characteristics of one or more predictions for each of the multiple WUS monitoring instances.

[0303] In some respects, the one or more predicted channel characteristics for each WUS monitoring instance include L1-RSRP measurements, L1-SINR measurements, or combinations thereof associated with one or more QCL source reference signals for one or more TCI states of one or more CORESETs associated with each WUS monitoring instance.

[0304] In some respects, method 1500 also includes determining one or more WUS monitoring instances among a plurality of WUS monitoring instances based on one or more predictions.

[0305] In some aspects, method 1500 further includes transmitting at least one additional WUS to the device in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances in the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX activation cycle following the first DRX activation cycle.

[0306] In some respects, method 1500 also includes determining one or more WUS monitoring instances among a plurality of WUS monitoring instances based on one or more predictions.

[0307] In some aspects, method 1500 further includes transmitting a second WUS to the device prior to a second DRX enable cycle among the plurality of DRX enable cycles, the second WUS including: an indication of whether to start the enable duration timer for the second DRX enable cycle; and an indication of the one or more WUS monitoring instances.

[0308] In some aspects, method 1500 further includes transmitting at least one additional WUS to the device in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances in the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX activation cycle following the first DRX activation cycle.

[0309] In some respects, indications for one or more forecasts include indications for one or more WUS monitoring instances out of a plurality of WUS monitoring instances.

[0310] In some aspects, method 1500 further includes transmitting at least one additional WUS to the device in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances in the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX activation cycle following the first DRX activation cycle.

[0311] In some respects, the indication of one or more WUS monitoring instances includes an indication of an ordered list of resources according to: L1-RSRP measurements, L1-SINR measurements, or combinations thereof associated with one or more QCL source reference signals for one or more TCI states of one or more CORESETs associated with one or more WUS monitoring instances.

[0312] In some respects, the indication to report the one or more predictions includes bits indicating whether the device transmits the indication to the one or more predictions during the first DRX on cycle or during a DRX on cycle following the first DRX on cycle.

[0313] In some respects, box 1515 includes receiving instructions on one or more forecasts in a CSI report.

[0314] In some respects, method 1500 also includes transmitting a configuration for setting periodic CSI reports associated with the reception of WUS at the device, wherein the indication of the one or more predictions is based on the communication of the configuration received in the CSI report.

[0315] In some respects, box 1515 includes receiving an indication of one or more predictions in the uplink MAC-CE.

[0316] In some respects, the indication of whether to start the activation duration timer for the first DRX activation period includes an affirmative indication of starting the activation duration timer; and block 1515 includes receiving an indication of the one or more predictions in a scheduled uplink channel.

[0317] In some aspects, the indication of whether to start the enable duration timer for the first DRX enable cycle includes a negative indication of not starting the enable duration timer; and method 1500 further includes transmitting configuration permission for the uplink shared channel to the device, wherein the indication of the one or more predictions is based on a communication of the configuration permission received in the uplink shared channel.

[0318] In some respects, box 1505 includes configuration transmission via RRC signaling.

[0319] In some respects, box 1505 includes the transmission of configuration via MAC-CE, DCI messages, or a combination thereof.

[0320] In some respects, multiple WUS monitoring instances include multiple search space sets, multiple PDCCH monitoring times, or a combination thereof.

[0321] In some respects, method 1500 or any aspect thereof may be made by means of a device (such as...) Figure 17 The communication device 1700 performs the operation, and the device includes various components that are operable to, configured to, or adapted to perform the method 1500. The communication device 1700 is described in further detail below.

[0322] It should be noted that Figure 15 This is merely one example of a method, and other methods that include fewer, additional, or alternative operations may also be consistent with this disclosure.

[0323] Example communication device Figure 16 Various aspects of the example communication device 1600 are described. In some aspects, the communication device 1600 is user equipment, such as those described above. Figure 1 and Figure 3 The UE 104 described.

[0324] Communication device 1600 includes a processing system 1605 coupled to a transceiver 1675 (e.g., a transmitter and / or receiver). Transceiver 1675 is configured to transmit and receive signals for communication device 1600 via antenna 1680, such as the various signals described herein. Processing system 1605 may be configured to perform processing functions for communication device 1600, including processing signals received by and / or to be transmitted by communication device 1600.

[0325] Processing system 1605 includes one or more processors 1610. In various aspects, the one or more processors 1610 may represent one or more of a receive processor 358, a transmit processor 364, a TX MIMO processor 366, and / or a controller / processor 380, as per [reference to...]. Figure 3 As described. One or more processors 1610 are coupled to a computer-readable medium / memory 1640 via a bus 1670. In some aspects, the computer-readable medium / memory 1640 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1610, enable the one or more processors 1610 to execute and cause the one or more processors to perform: regarding Figure 12 The described method 1200 or any aspect thereof, including regarding Figure 12 Any operation described; and relative to Figure 14 The described method 1400 or any aspect thereof, including regarding Figure 14 Any operation described. Note that references to processors performing the functions of communication device 1600 may include one or more processors, such as performing the functions of communication device 1600 in a distributed manner.

[0326] In the depicted example, computer-readable medium / memory 1640 stores code 1645 for receiving, code 1650 for monitoring, code 1655 for transmitting, code 1660 for ignoring, and code 1665 for determining. Processing of codes 1645 to 1665 enables communication device 1600 to execute and allows the communication device to perform: regarding Figure 12 The described method 1200 or any aspect thereof; and regarding Figure 14 The described method 1400 or any aspect related to that method.

[0327] One or more processors 1610 include circuitry configured to implement (e.g., execute) code stored in computer-readable medium / memory 1640, including circuitry 1615 for receiving, circuitry 1620 for monitoring, circuitry 1625 for transmitting, circuitry 1630 for ignoring, and circuitry 1635 for determining. Processing using circuitry 1615 to 1635 enables communication device 1600 to perform and allow the communication device to perform: regarding Figure 12 The described method 1200 or any aspect thereof; and regarding Figure 14 The described method 1400 or any aspect related to that method.

[0328] More generally, components used for conveying, sending, transmitting, or outputting for transmission may include Figure 3 The UE104 illustrated includes a transceiver 354, an antenna 352, a transmit processor 364, a TX MIMO processor 366, an AI processor 370, and / or a controller / processor 380. Figure 16 The transceiver 1675 and / or antenna 1680 of the communication device 1600 in the middle. Figure 16 One or more processors 1610 of the communication device 1600. Components for transmitting, receiving, or acquiring may include... Figure 3 The UE 104 illustrated includes a transceiver 354, an antenna 352, a receiver processor 358, an AI processor 370, and / or a controller / processor 380. Figure 16 The transceiver 1675 and / or antenna 1680 of the communication device 1600 in the middle. Figure 16 One or more processors 1610 of the communication device 1600 in the middle.

[0329] Figure 17 Various aspects of the example communication device 1700 are described. In some aspects, the communication device 1700 is a network entity, such as... Figure 1 and Figure 3 BS 102 or as about Figure 2 The decomposed base station under discussion.

[0330] Communication device 1700 includes a processing system 1705 coupled to a transceiver 1755 (e.g., a transmitter and / or receiver) and / or a network interface 1765. Transceiver 1755 is configured to transmit and receive signals for communication device 1700 via antenna 1760, such as various signals as described herein. Network interface 1765 is configured to transmit and receive signals for communication device 1700 via a communication link (such as those described herein). Figure 2The described backhaul link, midhaul link, and / or fronthaul link acquire and transmit signals for communication device 1700. Processing system 1705 can be configured to perform processing functions for communication device 1700, including processing signals received by and / or to be transmitted by communication device 1700.

[0331] Processing system 1705 includes one or more processors 1710. In various aspects, the one or more processors 1710 may represent one or more of a receive processor 338, a transmit processor 320, a TX MIMO processor 330, and / or a controller / processor 340, as per [reference to...]. Figure 3 As described. One or more processors 1710 are coupled to a computer-readable medium / memory 1730 via a bus 1750. In some aspects, the computer-readable medium / memory 1730 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1710, enable the one or more processors 1710 to execute and cause the one or more processors to perform: regarding Figure 13 The described method 1300 or any aspect thereof, including regarding Figure 13 Any operation described; and relative to Figure 15 The described method 1500 or any aspect thereof, including regarding Figure 15 Any operation described. Note that references to the processor performing the function of the communication device 1700 may include one or more processors of the communication device 1700, such as performing the function in a distributed manner.

[0332] In the depicted example, computer-readable medium / memory 1730 stores code 1735 for transmission, code 1740 for reception, and code 1745 for determination. Processing of codes 1735 to 1745 enables communication device 1700 to execute and allows the communication device to perform: regarding Figure 13 The described method 1300 or any aspect thereof; and regarding Figure 15 The described method 1500 or any aspect related to that method.

[0333] One or more processors 1710 include circuitry configured to implement (e.g., execute) code stored in computer-readable medium / memory 1730, the circuitry including circuitry 1715 for transmission, circuitry 1720 for reception, and circuitry 1725 for determination. Processing using circuitry 1715 to 1725 enables communication device 1700 to execute and perform the following: Regarding Figure 13 The described method 1300 or any aspect thereof; and regarding Figure 15The described method 1500 or any aspect related to that method.

[0334] More generally, components used for conveying, sending, transmitting, or outputting for transmission may include Figure 3 The BS102 illustrated includes transceiver 332, antenna 334, transmit processor 320, TX MIMO processor 330, AI processor 318, and / or controller / processor 340. Figure 17 The transceiver 1755, antenna 1760, and / or network interface 1765 of the communication device 1700 in the middle. Figure 17 One or more processors 1710 of the communication device 1700. Components for transmitting, receiving, or acquiring may include... Figure 3 The BS 102 illustrated includes transceiver 332, antenna 334, receiver processor 338, AI processor 318, and / or controller / processor 340. Figure 17 The transceiver 1755, antenna 1760, and / or network interface 1765 of the communication device 1700 in the middle. Figure 17 One or more processors 1710 of the communication device 1700 in the middle.

[0335] Example Terms Specific implementation examples are described in the following numbered clauses: Clause 1: A method for wireless communication by a device, the method comprising: receiving from a network entity the configuration of a plurality of sets of WUS monitoring instances, wherein the plurality of sets of WUS monitoring instances are associated with a plurality of DRX enable cycles, wherein each set of WUS monitoring instances in the plurality of sets of WUS monitoring instances includes a plurality of WUS monitoring instances; receiving from the network entity a first WUS prior to a first DRX enable cycle in the plurality of DRX enable cycles, wherein the first WUS includes: an indication of whether to start an enable duration timer for the first DRX enable cycle; and an indication of one or more WUS monitoring instances in the plurality of WUS monitoring instances; and monitoring at least one additional WUS in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances in the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX enable cycle following the first DRX enable cycle.

[0336] Clause 2: The method described in Clause 1 further includes transmitting to the network entity one or more measurement reports on signals received from the network entity.

[0337] Clause 3: The method according to Clause 2, wherein the one or more measurement reports of the signal received from the network entity include characteristics of the SSB received from the network entity, characteristics of the CSI-RS received from the network entity, Layer 1 measurement reports of the reference signal received from the network entity, or a combination thereof.

[0338] Clause 4: The method according to any one of Clauses 1 to 3 further includes transmitting to the network entity a report on the prediction results associated with the one or more WUS monitoring instances.

[0339] Clause 5: The method according to any one of Clauses 1 to 4, wherein the indication for the one or more WUS monitoring instances includes one or more corresponding search space set identifiers associated with the one or more WUS monitoring instances or one or more TCI status identifiers associated with the one or more WUS monitoring instances.

[0340] Clause 6: The method according to any one of Clauses 1 to 5, wherein the indication of the one or more WUS monitoring instances includes one or more identifiers associated with the one or more WUS monitoring instances, a bitmap indicating the one or more WUS monitoring instances, a combined index indicating the one or more WUS monitoring instances, or a combination thereof.

[0341] Clause 7: The method according to Clause 6 further includes receiving an indication of the number of identifiers intended for use with the one or more identifiers.

[0342] Clause 8: The method according to any one of Clauses 1 to 7, wherein the at least one set of WUS monitoring instances is a single set of WUS monitoring instances, and the at least one DRX activation period following the first DRX activation period is a single DRX activation period.

[0343] Clause 9: The method described in Clause 8, wherein each WUS that can be received in the single set of WUS monitoring instances includes the same payload size.

[0344] Clause 10: The method according to any one of Clauses 1 to 9, wherein the at least one set of WUS monitoring instances comprises a plurality of sets of WUS monitoring instances, and the at least one DRX activation period following the first DRX activation period comprises a plurality of DRX activation periods associated with the plurality of sets of WUS monitoring instances.

[0345] Clause 11: The method according to Clause 10, wherein monitoring the at least one additional WUS comprises monitoring the at least one additional WUS based on: the expectation of the plurality of sets of monitoring WUS monitoring instances, the configuration of the number of sets of WUS monitoring instances corresponding to the plurality of sets of WUS monitoring instances, and the fact that the number of the one or more WUS monitoring instances is the same or a combination thereof for each set of WUS monitoring instances in the plurality of sets of WUS monitoring instances.

[0346] Clause 12: The method according to any one of Clauses 1 to 11 further includes, based on the successful reception and decoding of the first WUS including the indication to the one or more WUS monitoring instances, ignoring the remaining WUS monitoring instances other than the one or more WUS monitoring instances among the plurality of WUS monitoring instances to monitor the at least one additional WUS.

[0347] Clause 13: The method according to any one of Clauses 1 to 12, wherein monitoring the at least one additional WUS comprises monitoring the at least one additional WUS in at least one of the plurality of WUS monitoring instances other than the one or more WUS monitoring instances based on unsuccessful decoding of the first WUS, unsuccessful identification of the one or more WUS monitoring instances indicated in the first WUS, or a combination thereof.

[0348] Clause 14: The method according to any one of Clauses 1 to 13, the method further comprising receiving a second WUS from the network entity after receiving the first WUS, the second WUS comprising: an indication of whether to start an activation duration timer for a second DRX activation period corresponding to the second WUS; and an indication of one or more second WUS monitoring instances among the plurality of WUS monitoring instances; and wherein monitoring the at least one additional WUS comprises, after receiving the second WUS, monitoring the at least one additional WUS in the at least one of the one or more WUS monitoring instances based on unsuccessful decoding of the second WUS, an unsuccessful identifier of the one or more second WUS monitoring instances indicated in the second WUS, or a combination thereof.

[0349] Clause 15: The method according to any one of Clauses 1 to 14, wherein: the first WUS includes a common field for a plurality of devices; the common field includes the indication for the one or more WUS monitoring instances; and the plurality of devices includes the apparatus.

[0350] Clause 16: The method according to any one of Clauses 1 to 15, wherein the indication of whether to start the start duration timer is used to indicate that the start duration timer is not started.

[0351] Clause 17: The method according to any one of Clauses 1 to 16, wherein the indication of whether to start the start duration timer is used to indicate the start duration timer to be started.

[0352] Clause 18: The method according to any one of Clauses 1 to 17, the method further comprising: receiving a second WUS from the network entity via a first beam associated with a first WUS monitoring instance in one or more WUS monitoring instances, wherein the second WUS includes an indication to initiate an activation duration timer for a second DRX activation period in one of the plurality of DRX activation periods; and receiving a downlink channel from the network entity via the first beam in the second DRX activation period.

[0353] Clause 19: The method according to any one of Clauses 1 to 18, wherein receiving the configuration of the plurality of sets of WUS monitoring instances includes receiving the configuration via RRC signaling.

[0354] Clause 20: The method according to any one of Clauses 1 to 19, wherein receiving the configuration of the plurality of sets of WUS monitoring instances includes receiving the configuration via MAC-CE, DCI messages, or a combination thereof.

[0355] Clause 21: The method according to any one of Clauses 1 to 20, wherein the plurality of WUS monitoring instances comprises a plurality of search space sets, a plurality of PDCCH monitoring times, or a combination thereof.

[0356] Clause 22: The method according to any one of Clauses 1 to 21, the method further comprising: receiving a second WUS from the network entity based on monitoring the at least one WUS monitoring instance, the second WUS including: an indication of whether to start an activation duration timer for a second DRX activation period corresponding to the second WUS; and an indication of monitoring the plurality of WUS monitoring instances for a subsequent set of WUS monitoring instances associated with a DRX activation period following the second DRX activation period.

[0357] Clause 23: The method according to any one of Clauses 1 to 22, wherein the indication to the one or more WUS monitoring instances includes an indication to one or more search space sets associated with the one or more WUS monitoring instances, an indication to a PDCCH monitoring timing associated with a search space set, an indication to one or more TCI states associated with a search space set, or a combination thereof.

[0358] Clause 24: A method for wireless communication by a device, the method comprising: transmitting to the device the configuration of a plurality of sets of WUS monitoring instances, wherein the plurality of sets of WUS monitoring instances are associated with a plurality of DRX enable cycles, wherein each set of WUS monitoring instances in the plurality of sets of WUS monitoring instances includes a plurality of WUS monitoring instances; transmitting to the device a first WUS prior to a first DRX enable cycle in the plurality of DRX enable cycles, wherein the first WUS includes: an indication of whether to start an enable duration timer for the first DRX enable cycle; and an indication of one or more WUS monitoring instances in the plurality of WUS monitoring instances; and transmitting to the device at least one additional WUS in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances in the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX enable cycle following the first DRX enable cycle.

[0359] Clause 25: The method according to Clause 24 further includes: receiving from the device one or more measurement reports on signals transmitted by the device; and determining the one or more WUS monitoring instances based on the one or more measurement reports.

[0360] Clause 26: The method according to Clause 25, wherein the one or more measurement reports of the signal transmitted by the device include characteristics of the SSB transmitted by the device, characteristics of the CSI-RS transmitted by the device, layer 1 measurement reports of the reference signal transmitted by the device, or a combination thereof.

[0361] Clause 27: The method according to any one of Clauses 24 to 26, the method further comprising: receiving from the device a report of a prediction result associated with the one or more WUS monitoring instances; and determining the one or more WUS monitoring instances based on the report of the prediction result.

[0362] Clause 28: The method according to any one of Clauses 24 to 27, wherein the indication for the one or more WUS monitoring instances includes one or more corresponding search space set identifiers associated with the one or more WUS monitoring instances or one or more TCI status identifiers associated with the one or more WUS monitoring instances.

[0363] Clause 29: The method according to any one of Clauses 24 to 28, wherein the indication of the one or more WUS monitoring instances includes one or more identifiers associated with the one or more WUS monitoring instances, a bitmap indicating the one or more WUS monitoring instances, a combined index indicating the one or more WUS monitoring instances, or a combination thereof.

[0364] Clause 30: The method according to Clause 29 further includes transmitting an indication of the number of identifiers that the device is intended to use for the one or more identifiers.

[0365] Clause 31: The method according to any one of Clauses 24 to 30, wherein the at least one set of WUS monitoring instances is a single set of WUS monitoring instances, and the at least one DRX activation period following the first DRX activation period is a single DRX activation period.

[0366] Clause 32: The method described in Clause 31, wherein each WUS capable of being transmitted in the single set of WUS monitoring instances comprises the same payload size.

[0367] Clause 33: The method according to any one of Clauses 24 to 32, wherein the at least one set of WUS monitoring instances comprises a plurality of sets of WUS monitoring instances, and the at least one DRX activation period following the first DRX activation period comprises a plurality of DRX activation periods associated with the plurality of sets of WUS monitoring instances.

[0368] Clause 34: The method according to Clause 33 further includes a configuration of the number of sets of WUS monitoring instances corresponding to the plurality of sets of WUS monitoring instances.

[0369] Clause 35: The method according to any one of Clauses 24 to 34, wherein: the first WUS includes a common field for a plurality of devices; the common field includes the indication for the one or more WUS monitoring instances; and the plurality of devices includes the device.

[0370] Clause 36: The method according to any one of Clauses 24 to 35, wherein the indication of whether to start the start duration timer indicates to the device not to start the start duration timer.

[0371] Clause 37: The method according to any one of Clauses 24 to 36, wherein the indication of whether to start the start duration timer instructs the device to start the start duration timer.

[0372] Clause 38: The method according to any one of Clauses 24 to 37, wherein transmitting the at least one additional WUS includes transmitting a second WUS via a first beam associated with a first WUS monitoring instance among the one or more WUS monitoring instances, wherein the second WUS includes an indication to the device to initiate an on-duration timer for a second DRX on-duration of the plurality of DRX on-durations; and wherein the method further includes transmitting a downlink channel to the device via the first beam during the second DRX on-duration.

[0373] Clause 39: The method according to any one of Clauses 24 to 38, wherein the configuration for transmitting the plurality of sets of WUS monitoring instances includes transmitting the configuration via RRC signaling.

[0374] Clause 40: The method according to any one of Clauses 24 to 39, wherein the configuration for transmitting the plurality of sets of WUS monitoring instances includes transmitting the configuration via MAC-CE, DCI messages, or a combination thereof.

[0375] Clause 41: The method according to any one of Clauses 24 to 40, wherein the plurality of WUS monitoring instances comprises a plurality of search space sets, a plurality of PDCCH monitoring times, or a combination thereof.

[0376] Clause 42: The method according to any one of Clauses 24 to 41, wherein the at least one additional WUS includes a second WUS, the second WUS including: an indication of whether to start an on-time timer for a second DRX on-time cycle corresponding to the second WUS; and an indication of the device to monitor the plurality of WUS monitoring instances for a subsequent set of WUS monitoring instances associated with a DRX on-time cycle after the second DRX on-time cycle.

[0377] Clause 43: The method according to any one of Clauses 24 to 42, wherein the indication to the one or more WUS monitoring instances includes an indication to one or more search space sets associated with the one or more WUS monitoring instances, an indication to a PDCCH monitoring timing associated with a search space set, an indication to one or more TCI states associated with a search space set, or a combination thereof.

[0378] Clause 44: A method for wireless communication by a device, the method comprising: receiving from a network entity the configuration of a plurality of sets of WUS monitoring instances, wherein the plurality of sets of WUS monitoring instances are associated with a plurality of DRX enable cycles, wherein each set of WUS monitoring instances in the plurality of sets of WUS monitoring instances includes a plurality of WUS monitoring instances; receiving from the network entity a first WUS prior to a first DRX enable cycle in the plurality of DRX enable cycles, wherein the first WUS includes: an indication of whether to initiate an enable duration timer for the first DRX enable cycle; and an indication of reporting one or more predictions corresponding to the plurality of WUS monitoring instances; and transmitting an indication of the one or more predictions to the network entity.

[0379] Clause 45: The method according to Clause 44, wherein the one or more predictions include one or more predicted channel characteristics of each of the plurality of WUS monitoring instances.

[0380] Clause 46: The method according to Clause 45, wherein the one or more predicted channel characteristics for each WUS monitoring instance include L1-RSRP measurements, L1-SINR measurements, or combinations thereof associated with one or more QCL source reference signals for one or more TCI states of one or more CORESETs associated with each WUS monitoring instance.

[0381] Clause 47: The method according to any one of Clauses 44 to 46, the method further comprising: determining one or more WUS monitoring instances among the plurality of WUS monitoring instances based on the one or more predictions; and monitoring at least one additional WUS in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances among the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX activation period following the first DRX activation period.

[0382] Clause 48: The method according to any one of Clauses 44 to 47, the method further comprising: receiving a second WUS from the network entity prior to a second DRX activation period in the plurality of DRX activation periods, the second WUS including: an indication of whether to initiate the activation duration timer for the second DRX activation period; and an indication of one or more WUS monitoring instances in the plurality of WUS monitoring instances; and monitoring at least one additional WUS in at least one of the one or more WUS monitoring instances in at least one set of at least one set of WUS monitoring instances in the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX activation period following the first DRX activation period.

[0383] Clause 49: The method according to any one of Clauses 44 to 48, wherein the indication for the one or more predictions includes an indication for one or more WUS monitoring instances among the plurality of WUS monitoring instances.

[0384] Clause 50: The method according to Clause 49 further includes monitoring at least one additional WUS in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances in the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX activation period following the first DRX activation period.

[0385] Clause 51: The method according to Clause 49, wherein the indication for the one or more WUS monitoring instances includes an indication for an ordered list of resources according to: an L1-RSRP measurement, an L1-SINR measurement, or a combination thereof associated with one or more QCL source reference signals for one or more TCI states of one or more CORESETs associated with the one or more WUS monitoring instances.

[0386] Clause 52: The method according to any one of Clauses 44 to 51, wherein the indication for reporting the one or more predictions includes a bit indicating whether the indication for the one or more predictions is transmitted in the first DRX enable cycle or in a DRX enable cycle after the first DRX enable cycle.

[0387] Clause 53: The method according to any one of Clauses 44 to 52, wherein transmitting the indication for the one or more predictions includes transmitting the indication for the one or more predictions in a CSI report.

[0388] Clause 54: The method according to Clause 53 further includes receiving a configuration for setting periodic CSI reports associated with reception of WUS, wherein the indication of the one or more predictions is transmitted in the CSI report based on the reception of the configuration.

[0389] Clause 55: The method according to any one of Clauses 44 to 54, wherein transmitting the indication for the one or more predictions includes transmitting the indication for the one or more predictions in the uplink MAC-CE.

[0390] Clause 56: The method according to any one of Clauses 44 to 55, wherein: the indication of whether to start the start duration timer for the first DRX start period includes an affirmative indication of starting the start duration timer; and transmitting the indication of the one or more predictions includes transmitting the indication of the one or more predictions in a scheduled uplink channel.

[0391] Clause 57: The method according to any one of Clauses 44 to 56, wherein: the indication of whether to start the start duration timer for the first DRX start period includes a negative indication of not starting the start duration timer; and the method further includes receiving configuration permission for the uplink shared channel from the network entity, and wherein the indication of the one or more predictions is based on the reception of the configuration permission transmitted in the uplink shared channel.

[0392] Clause 58: The method according to any one of Clauses 44 to 57, wherein the configuration for receiving the plurality of sets of WUS monitoring instances includes receiving the configuration via RRC signaling.

[0393] Clause 59: The method according to any one of Clauses 44 to 58, wherein receiving the configuration of the plurality of sets of WUS monitoring instances includes receiving the configuration via MAC-CE, DCI messages, or a combination thereof.

[0394] Clause 60: The method according to any one of Clauses 44 to 59, wherein the plurality of WUS monitoring instances comprises a plurality of search space sets, a plurality of PDCCH monitoring times, or a combination thereof.

[0395] Clause 61: A method for wireless communication by a device, the method comprising: transmitting to the device a configuration of a plurality of sets of WUS monitoring instances, wherein the plurality of sets of WUS monitoring instances are associated with a plurality of DRX enable cycles, wherein each set of WUS monitoring instances in the plurality of sets of WUS monitoring instances includes a plurality of WUS monitoring instances; transmitting to the device a first WUS prior to a first DRX enable cycle in the plurality of DRX enable cycles, wherein the first WUS includes: an indication of whether to start an enable duration timer for the first DRX enable cycle; and an indication of reporting one or more predictions corresponding to the plurality of WUS monitoring instances; and receiving from the device an indication of the one or more predictions.

[0396] Clause 62: The method according to Clause 61, wherein the one or more predictions include one or more predicted channel characteristics of each of the plurality of WUS monitoring instances.

[0397] Clause 63: The method according to Clause 62, wherein the one or more predicted channel characteristics for each WUS monitoring instance include L1-RSRP measurements, L1-SINR measurements, or combinations thereof associated with one or more QCL source reference signals for one or more TCI states of one or more CORESETs associated with each WUS monitoring instance.

[0398] Clause 64: The method according to any one of Clauses 61 to 63, the method further comprising: determining one or more WUS monitoring instances among the plurality of WUS monitoring instances based on the one or more predictions; and transmitting at least one additional WUS to the device in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances among the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX on-cycle following the first DRX on-cycle.

[0399] Clause 65: The method according to any one of Clauses 61 to 64, the method further comprising: determining one or more WUS monitoring instances among the plurality of WUS monitoring instances based on the one or more predictions; transmitting a second WUS to the device prior to a second DRX activation cycle among the plurality of DRX activation cycles, the second WUS including: an indication of whether to start the activation duration timer for the second DRX activation cycle; and an indication of the one or more WUS monitoring instances; and transmitting at least one additional WUS to the device in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances among the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX activation cycle following the first DRX activation cycle.

[0400] Clause 66: The method according to any one of Clauses 61 to 65, wherein the indication for the one or more predictions includes an indication for one or more WUS monitoring instances among the plurality of WUS monitoring instances.

[0401] Clause 67: The method according to Clause 66 further includes transmitting at least one additional WUS to the device in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances in the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX on-cycle following the first DRX on-cycle.

[0402] Clause 68: The method according to Clause 66, wherein the indication for the one or more WUS monitoring instances includes an indication of an ordered list of resources according to: an L1-RSRP measurement, an L1-SINR measurement, or a combination thereof associated with one or more QCL source reference signals for one or more TCI states of one or more CORESETs associated with the one or more WUS monitoring instances.

[0403] Clause 69: The method according to any one of Clauses 61 to 68, wherein the indication for reporting the one or more predictions includes a bit indicating whether the device transmits the indication for the one or more predictions during the first DRX enable cycle or during a DRX enable cycle after the first DRX enable cycle.

[0404] Clause 70: The method according to any one of Clauses 61 to 69, wherein receiving the indication for the one or more forecasts includes receiving the indication for the one or more forecasts in a CSI report.

[0405] Clause 71: The method according to Clause 70 further includes transmitting a configuration for periodic CSI report settings associated with the reception of WUS at the device, and wherein the indication of the one or more predictions is based on the communication of the configuration received in the CSI report.

[0406] Clause 72: The method according to any one of Clauses 61 to 71, wherein receiving the indication for the one or more predictions includes receiving the indication for the one or more predictions in the uplink MAC-CE.

[0407] Clause 73: The method according to any one of Clauses 61 to 72, wherein: the indication of whether to start the start duration timer for the first DRX start period includes an affirmative indication of starting the start duration timer; and receiving the indication of the one or more predictions includes receiving the indication of the one or more predictions in a scheduled uplink channel.

[0408] Clause 74: The method according to any one of Clauses 61 to 73, wherein: the indication of whether to start the enable duration timer for the first DRX enable period includes a negative indication of not starting the enable duration timer; and the method further includes transmitting configuration permission for the uplink shared channel to the device, and wherein the indication of the one or more predictions is based on a communication of the configuration permission received in the uplink shared channel.

[0409] Clause 75: The method according to any one of Clauses 61 to 74, wherein the configuration for transmitting the plurality of sets of WUS monitoring instances includes transmitting the configuration via RRC signaling.

[0410] Clause 76: The method according to any one of Clauses 61 to 75, wherein the configuration for transmitting the plurality of sets of WUS monitoring instances includes transmitting the configuration via MAC-CE, DCI messages, or a combination thereof.

[0411] Clause 77: The method according to any one of Clauses 61 to 76, wherein the plurality of WUS monitoring instances comprises a plurality of search space sets, a plurality of PDCCH monitoring times, or a combination thereof.

[0412] Clause 78: One or more means comprising: one or more memories including executable instructions; and one or more processors configured to execute the executable instructions and cause the one or more means to perform the method according to any one of Clauses 1 to 77.

[0413] Clause 79: One or more means comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the one or more means to perform the method according to any one of Clauses 1 to 77.

[0414] Clause 80: One or more means comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to perform the method according to any one of Clauses 1 to 77.

[0415] Clause 81: One or more apparatuses, said one or more apparatuses comprising components for performing the method according to any one of Clauses 1 to 77.

[0416] Clause 82: One or more non-transitory computer-readable media, the one or more non-transitory computer-readable media comprising executable instructions that, when executed by one or more processors of one or more devices, cause the one or more devices to perform the method according to any one of Clauses 1 to 77.

[0417] Clause 83: One or more computer program products embodied on one or more computer-readable storage media, the one or more computer-readable storage media including code for performing the method according to any one of Clauses 1 to 77.

[0418] Additional Notes The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, the function and arrangement of the elements discussed may be changed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in various examples. For example, the described methods may be performed in a different order than described, and various actions may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in others. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Moreover, the scope of this disclosure is intended to cover such apparatuses or methods practiced using other structures, functionalities, or structures and functionalities that complement or replace the various aspects of this disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0419] The various exemplary logic blocks, modules, and circuits described in this disclosure can be implemented or executed using a general-purpose processor, AI processor, digital signal processor (DSP), ASIC, field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. While the general-purpose processor may be a microprocessor, in alternative embodiments, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, a system-on-a-chip (SoC), or any other such configuration.

[0420] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including individual components. For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0421] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, operation, processing, deduction, investigation, searching (e.g., searching in a table, database, or other data structure), and probing. Additionally, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and so on. Furthermore, "determine" can include parsing, selecting, picking, and building.

[0422] As used herein, unless otherwise stated, “coupled to” and “coupled with” generally encompass both direct and indirect coupling (e.g., including intermediate aspects of coupling). For example, stating that a processor is coupled to memory allows for direct coupling or coupling via an intermediate aspect such as a bus.

[0423] The methods disclosed herein include one or more actions for implementing the methods. These method actions may be interchanged without departing from the scope of the claims. In other words, unless a specified order of actions is given, the order and / or use of a particular action may be modified without departing from the scope of the claims. Furthermore, the various operations of the methods described above may be performed by any suitable component capable of performing the corresponding function. This component may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors.

[0424] The following claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims. References to singular elements are not intended to mean “only one” (unless specifically stated as “only one”), but rather “one or more”. Unless otherwise specified, definite articles (e.g., “the” or “described”) subsequently used with an element (e.g., “processor”) are not intended to give that element a singular meaning (e.g., “only one”). For example, unless otherwise specified, references to elements (e.g., “processor”, “controller”, “memory”, “transceiver”, “antenna”, “the processor”, “the controller”, “the memory”, “the transceiver”, “the antenna”, etc.) should be understood to refer to one or more elements (e.g., “one or more processors”, “one or more controllers”, “one or more memories”, “a plurality of transceivers”, etc.). The terms “set” and “group” are intended to include one or more elements and may be used interchangeably with “one or more”. In the case of references to one or more elements performing a function (e.g., steps of a method), one element may perform all the functions, or more than one element may collectively perform those functions. When more than one element performs these functions together, each function does not need to be performed by every single element (e.g., different functions can be performed by different elements), and / or each function does not need to be performed by only one element as a whole (e.g., different elements can perform different sub-functions of a function). Similarly, when referring to one or more elements configured to cause another element (e.g., a device) to perform a function, one element may be configured to cause another element to perform all functions, or more than one element may be jointly configured to cause another element to perform these functions. Unless otherwise specifically stated, the term "some" means one or more. All structural and functional equivalents of the various aspects described throughout this disclosure that are currently or hereafter known to those skilled in the art are intended to be covered by the claims. Moreover, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly recited in the claims.

Claims

1. An apparatus configured for wireless communication, the apparatus comprising: One or more memories, the one or more memories including processor-executable instructions; and one or more processors, said one or more processors being configured to execute processor-executable instructions and cause the device to: The configuration of receiving multiple sets of Wake-up Signal (WUS) monitoring instances from network entities, wherein the multiple sets of WUS monitoring instances are associated with multiple Discontinuous Receive (DRX) enable cycles, and each set of WUS monitoring instances in the multiple sets of WUS monitoring instances includes multiple WUS monitoring instances. The first WUS is received from the network entity before the first DRX activation cycle in the plurality of DRX activation cycles. The first WUS includes: An indication of whether to start the enable duration timer for the first DRX enable cycle; and Instructions for one or more WUS monitoring instances among the plurality of WUS monitoring instances; and At least one additional WUS is monitored in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances in the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX activation period after the first DRX activation period.

2. The apparatus of claim 1, wherein the one or more processors are configured to execute processor-executable instructions and cause the apparatus to transmit to the network entity one or more measurement reports of signals received from the network entity.

3. The apparatus of claim 2, wherein the one or more measurement reports of the signals received from the network entity include characteristics of the synchronization signal block (SSB) received from the network entity, characteristics of the channel state information reference signal (CSI-RS) received from the network entity, layer 1 measurement reports of the reference signal received from the network entity, or combinations thereof.

4. The apparatus of claim 1, wherein the one or more processors are configured to execute processor-executable instructions and cause the apparatus to transmit to the network entity a report of prediction results associated with the one or more WUS monitoring instances.

5. The apparatus of claim 1, wherein the indication to the one or more WUS monitoring instances includes one or more corresponding search space set identifiers associated with the one or more WUS monitoring instances or one or more transmit configuration indicator (TCI) status identifiers associated with the one or more WUS monitoring instances.

6. The apparatus of claim 1, wherein the indication of the one or more WUS monitoring instances comprises one or more identifiers associated with the one or more WUS monitoring instances, a bitmap indicating the one or more WUS monitoring instances, a combined index indicating the one or more WUS monitoring instances, or a combination thereof.

7. The apparatus of claim 6, wherein the one or more processors are configured to execute processor-executable instructions and cause the apparatus to receive an indication of the number of identifiers intended for the one or more identifiers.

8. The apparatus of claim 1, wherein the at least one set of WUS monitoring instances is a single set of WUS monitoring instances, and the at least one DRX activation period following the first DRX activation period is a single DRX activation period.

9. The apparatus of claim 8, wherein each WUS capable of being received in the single set of WUS monitoring instances comprises the same payload size.

10. The apparatus of claim 1, wherein the at least one set of WUS monitoring instances comprises a plurality of sets of WUS monitoring instances, and the at least one DRX activation period following the first DRX activation period comprises a plurality of DRX activation periods associated with the plurality of sets of WUS monitoring instances.

11. The apparatus of claim 10, wherein, in order to monitor the at least one additional WUS, the one or more processors are configured to execute processor-executable instructions and cause the apparatus to monitor the at least one additional WUS based on: an expectation of the plurality of sets of WUS monitoring instances to be monitored, a configuration of the number of sets of WUS monitoring instances corresponding to the plurality of sets of WUS monitoring instances, and the number of the one or more WUS monitoring instances being the same or a combination thereof for each set of WUS monitoring instances in the plurality of sets of WUS monitoring instances.

12. The apparatus of claim 1, wherein the one or more processors are configured to execute processor-executable instructions and cause the apparatus to monitor the at least one additional WUS by ignoring the remaining WUS monitoring instances other than the one or more WUS monitoring instances based on successful reception and decoding of the first WUS, including the indication to the one or more WUS monitoring instances.

13. The apparatus of claim 1, wherein, in order to monitor the at least one additional WUS, the one or more processors are configured to execute processor-executable instructions and cause the apparatus to monitor the at least one additional WUS in at least one of the plurality of WUS monitoring instances other than the one or more WUS monitoring instances, based on unsuccessful decoding of the first WUS, unsuccessful identification of the one or more WUS monitoring instances indicated in the first WUS, or a combination thereof.

14. The apparatus according to claim 1, wherein: The one or more processors are configured to execute processor-executable instructions and cause the device to receive a second WUS from the network entity after receiving the first WUS, the second WUS comprising: An indication of whether to start the on-time timer for the second DRX on-cycle corresponding to the second WUS; and Instructions for one or more second WUS monitoring instances among the plurality of WUS monitoring instances; and In order to monitor the at least one additional WUS, the one or more processors are configured to execute processor-executable instructions and cause the device, after receiving the second WUS, to monitor the at least one WUS monitoring instance among the one or more WUS monitoring instances based on unsuccessful decoding of the second WUS, unsuccessful identification of the one or more second WUS monitoring instances indicated in the second WUS, or a combination thereof.

15. The apparatus according to claim 1, wherein: The first WUS includes common fields for multiple devices; The public fields include the indications for the one or more WUS monitoring instances; and The plurality of devices includes the apparatus.

16. The apparatus of claim 1, wherein the indication of whether to start the start duration timer is used to indicate that the start duration timer is not started.

17. The apparatus of claim 1, wherein the indication of whether to start the start duration timer is used to indicate the start duration timer to be started.

18. The apparatus of claim 1, wherein the one or more processors are configured to execute processor-executable instructions and cause the apparatus to: A second WUS is received from the network entity via a first beam associated with a first WUS monitoring instance in one or more WUS monitoring instances, wherein the second WUS includes an indication to initiate an on-duration timer for a second DRX on-duration of the plurality of DRX on-durations; and During the second DRX activation period, the downlink channel is received from the network entity via the first beam.

19. The apparatus of claim 1, wherein, in order to receive the configuration of the plurality of sets of WUS monitoring instances, the one or more processors are configured to execute processor-executable instructions and cause the apparatus to receive the configuration via Radio Resource Control (RRC) signaling.

20. The apparatus of claim 1, wherein, in order to receive the configuration of the plurality of sets of WUS monitoring instances, the one or more processors are configured to execute processor-executable instructions and cause the apparatus to receive the configuration via a Media Access Control (MAC) Control Element (CE), a Downlink Control Information (DCI) message, or a combination thereof.

21. The apparatus of claim 1, wherein the plurality of WUS monitoring instances comprise a plurality of search space sets, a plurality of physical downlink control channel (PDCCH) monitoring events, or a combination thereof.

22. The apparatus of claim 1, wherein the one or more processors are configured to execute processor-executable instructions and cause the apparatus to: Based on monitoring the at least one WUS monitoring instance, a second WUS is received from the network entity, the second WUS comprising: Indication on whether to start the start duration timer for the second DRX start cycle corresponding to the second WUS; as well as Instructions for monitoring the plurality of WUS monitoring instances in subsequent sets of monitoring for a DRX activation cycle associated with the second DRX activation cycle.

23. The apparatus of claim 1, wherein the indication to the one or more WUS monitoring instances comprises an indication to one or more search space sets associated with the one or more WUS monitoring instances, an indication to the timing of physical downlink control channel (PDCCH) monitoring associated with the search space sets, an indication to one or more TCI states associated with the search space sets, or a combination thereof.

24. A method for wireless communication by a device, the method comprising: The configuration of receiving multiple sets of Wake-up Signal (WUS) monitoring instances from network entities, wherein the multiple sets of WUS monitoring instances are associated with multiple Discontinuous Receive (DRX) enable cycles, and each set of WUS monitoring instances in the multiple sets of WUS monitoring instances includes multiple WUS monitoring instances. The first WUS is received from the network entity before the first DRX activation cycle in the plurality of DRX activation cycles. The first WUS includes: An indication of whether to start the enable duration timer for the first DRX enable cycle; and Instructions for one or more WUS monitoring instances among the plurality of WUS monitoring instances; and At least one additional WUS is monitored in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances in the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX activation period after the first DRX activation period.

25. An apparatus configured for wireless communication, the apparatus comprising: One or more memories, the one or more memories including processor-executable instructions; and one or more processors, said one or more processors being configured to execute processor-executable instructions and cause the device to: A configuration of multiple sets of Wake-up Signal (WUS) monitoring instances that transmit to a device, wherein the multiple sets of WUS monitoring instances are associated with multiple Discontinuous Receive (DRX) enable cycles, wherein each set of WUS monitoring instances in the multiple sets of WUS monitoring instances includes multiple WUS monitoring instances. A first WUS is transmitted to the device before the first DRX activation cycle in the plurality of DRX activation cycles. The first WUS includes: An indication of whether to start the enable duration timer for the first DRX enable cycle; and Instructions for one or more WUS monitoring instances among the plurality of WUS monitoring instances; and At least one additional WUS is transmitted to the device in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances in the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX on-cycle following the first DRX on-cycle.

26. The apparatus of claim 25, wherein the one or more processors are configured to execute processor-executable instructions and cause the apparatus to: Receive one or more measurement reports from the device for the signals transmitted by the apparatus; and The one or more WUS monitoring instances are determined based on the one or more measurement reports.

27. The apparatus of claim 26, wherein the one or more measurement reports of the signals transmitted by the apparatus include characteristics of the synchronization signal block (SSB) transmitted by the apparatus, characteristics of the channel state information reference signal (CSI-RS) transmitted by the apparatus, layer 1 measurement reports of the reference signal transmitted by the apparatus, or combinations thereof.

28. The apparatus of claim 25, wherein the one or more processors are configured to execute processor-executable instructions and cause the apparatus to: Receive reports from the device on the prediction results associated with the one or more WUS monitoring instances; and The one or more WUS monitoring instances are determined based on the report of the prediction results.

29. The apparatus of claim 25, wherein the indication to the one or more WUS monitoring instances includes one or more corresponding search space set identifiers associated with the one or more WUS monitoring instances or one or more transmit configuration indicator (TCI) status identifiers associated with the one or more WUS monitoring instances.

30. A method for wireless communication by a device, the method comprising: A configuration of multiple sets of Wake-up Signal (WUS) monitoring instances that transmit to a device, wherein the multiple sets of WUS monitoring instances are associated with multiple Discontinuous Receive (DRX) enable cycles, wherein each set of WUS monitoring instances in the multiple sets of WUS monitoring instances includes multiple WUS monitoring instances. A first WUS is transmitted to the device before the first DRX activation cycle in the plurality of DRX activation cycles. The first WUS includes: An indication of whether to start the enable duration timer for the first DRX enable cycle; and Instructions for one or more WUS monitoring instances among the plurality of WUS monitoring instances; and At least one additional WUS is transmitted to the device in at least one of the one or more WUS monitoring instances in at least one set of WUS monitoring instances in the plurality of sets of WUS monitoring instances, wherein the at least one set of WUS monitoring instances is associated with at least one DRX on-cycle following the first DRX on-cycle.

Images