Low power cell wake-up signal for cell discontinuous reception

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive, from a network node, an indication of network capabilities received for a low power cell wake-up signal (LP-C-WUS). The UE may send, to the network node, an indication of UE capabilities for the LP-C-WUS transmission. The UE may receive, from the network node, a cell discontinuous reception (DRX) configuration indicating one or more LP-C-WUS monitoring opportunities in a cell DRX cycle. The UE may transmit an LP-C-WUS to the network node in an LP-C-WUS opportunity of the one or more LP-C-WUS opportunities. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. non-provisional patent application No. 18 / 168,270, filed on February 13, 2023, entitled “LOW-POWER CELL WAKE-UPSIGNAL FOR CELL DISCONTINUOUS RECEPTION,” which is hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for cell discontinuous reception (DRX) utilizing a low-power cell wake-up signal (LP-C-WUS). Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services, such as telephony, video, data, messaging, broadcasts, or other similar types of services. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available wireless communication system resources with those users.

[0005] Despite the tremendous 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 wireless receivers. Accordingly, there is a continuing desire to improve the technical performance of wireless communication systems, including, for example, improving the speed and data carrying capacity of communications, improving the efficiency of shared communication media usage, reducing the power used by transmitters and receivers when performing communications, improving the reliability of wireless communications, avoiding redundant transmission and / or reception and related processing, improving the coverage area of ​​wireless communications, increasing the number and types of devices that can access wireless communication systems, increasing the ability of different types of devices to communicate with each other, and increasing the number and types of wireless communication media available for use. Therefore, there is a need for further improvements in wireless communication systems to overcome the aforementioned technical challenges and others. Summary of the Invention

[0006] One aspect provides a method for wireless communication by a user equipment (UE). The method includes receiving an indication of network capabilities for low-power cell wake-up signal (LP-C-WUS) reception from a network node. The method includes sending an indication of UE capabilities for LP-C-WUS transmission to the network node. The method includes receiving a cell discontinuous reception (DRX) configuration from the network node indicating one or more LP-C-WUS monitoring opportunities in a cell DRX cycle. The method may include sending the LP-C-WUS to the network node during one of the one or more LP-C-WUS opportunities.

[0007] Another aspect provides a method for wireless communication by a network node. The method includes sending an indication of network capabilities for LP-C-WUS reception. The method may include receiving an indication of UE capabilities sent for LP-C-WUS. The method may include sending a cell DRX configuration indicating one or more LP-C-WUS monitoring opportunities in a cell DRX cycle. The method may include receiving an LP-C-WUS in an LP-C-WUS opportunity of the one or more LP-C-WUS opportunities.

[0008] Other aspects provide: an apparatus operable to, configured to, or otherwise adapted to perform any one or more of the aforementioned methods and / or those described herein with reference to the drawings and the specification and as illustrated in the drawings and the specification; a non-transitory computer-readable medium comprising computer-executable instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the aforementioned methods and / or those described herein with reference to the drawings and the specification and as illustrated in the drawings and the specification; a computer program product embodied on a computer-readable storage medium comprising code for performing the aforementioned methods and / or those described herein with reference to the drawings and the specification and as illustrated in the drawings and the specification; and / or an apparatus comprising components for performing the aforementioned methods and / or those described herein with reference to the drawings and the specification and as illustrated in the drawings and the specification. By way of example, an apparatus may comprise a processing system, a device having a processing system, or a processing system cooperating through one or more networks.

[0009] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above so that the detailed description that follows may be better understood. Additional features and advantages will be described below. The concepts and specific examples disclosed may be readily used as a basis for modifying or designing other structures for achieving the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0010] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporated into the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and compositions. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order that the above-mentioned features of the present disclosure may be fully understood, a more particular description of the invention briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). It should be noted, however, that the drawings illustrate only certain typical aspects of the present disclosure and are not therefore to be considered limiting of its scope, as the description may admit to other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0012] Figure 1 An example of a wireless communication network according to the present disclosure is depicted.

[0013] Figure 2 Aspects of an example base station (BS) and user equipment (UE) according to the present disclosure are depicted.

[0014] Figure 3 Depicted is an example disaggregated base station architecture according to the present disclosure.

[0015] Figure 4A 、 Figure 4B 、 Figure 4C and Figure 4D Described is a method for wireless communication networks such as Figure 1 Various aspects of data structures of wireless communication networks).

[0016] Figure 5 is a diagram illustrating an example of a discontinuous reception (DRX) configuration according to the present disclosure.

[0017] Figure 6 is a diagram illustrating an example of cell DRX according to the present disclosure.

[0018] Figure 7 is a diagram illustrating an example of a network node with a low power wake-up radio component (LP-WUR) according to the present disclosure.

[0019] Figures 8A to 8E is a diagram illustrating an example associated with cell DRX with a low-power cell wake-up signal (LP-C-WUS) according to the present disclosure.

[0020] Figure 9 is a diagram illustrating an example associated with a coverage area for LP-C-WUS transmission in a cell according to the present disclosure.

[0021] Figure 10 is a diagram illustrating an example associated with cell wake-up signal (C-WUS) transmission assistance according to the present disclosure.

[0022] Figure 11 A method of wireless communication by a UE according to the present disclosure is shown.

[0023] Figure 12 A method of wireless communication by a network node according to the present disclosure is shown.

[0024] Figure 13 is a diagram illustrating an example of a specific implementation of code and circuits for a communication device according to the present disclosure.

[0025] Figure 14 is a diagram illustrating an example of a specific implementation of code and circuits for a communication device according to the present disclosure. DETAILED DESCRIPTION

[0026] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for cell discontinuous reception (DRX) with a low-power cell wake-up signal (LP-C-WUS).

[0027] For various reasons, including climate change mitigation, environmental sustainability, and network cost reduction, network energy savings (NES) and / or network energy efficiency measures are expected to become increasingly important in wireless network operations. For example, while New Radio (NR) generally offers significant energy efficiency improvements per gigabyte over previous generations (e.g., Long Term Evolution (LTE)), the adoption of new NR use cases and / or millimeter-wave frequencies may require more network sites, more network antennas, greater bandwidth, and / or more frequency bands, potentially resulting in more efficient wireless networks that still have higher energy requirements and / or generate more emissions than previous generations. Furthermore, energy accounts for a significant portion of wireless network operating costs. For example, it is estimated that energy costs account for approximately a quarter of the total cost of wireless network operations, and over 90% of network operating costs are spent on energy (e.g., fuel and electricity). The largest contributor to energy consumption and / or energy costs is the radio access network (RAN), which accounts for approximately half of wireless network energy consumption, with data centers and fiber transport contributing smaller proportions. Therefore, measures to increase network energy savings and / or improve network energy efficiency are important factors that could drive the adoption and / or expansion of wireless networks.

[0028] One potential technique for improving energy efficiency in the RAN is to enable a cell DRX mechanism. For example, the cell DRX mechanism may include: a cell DRX on duration (or active time), during which a network node (e.g., a base station or one or more components of a disaggregated base station architecture) transmits and / or receives one or more channels or signals; and an opportunity for the network node to enter a sleep state during times when the entire cell (e.g., including the network node 110 and any connected mode user equipment (UE)) is asleep (e.g., a cell DRX off duration or inactive time). In some examples, the network node may not transmit or receive while in the sleep state. However, the UE may need to communicate with the network node. In some examples, the UE may send a cell wake-up signal (C-WUS) to proactively wake up the network node. The C-WUS may be a physical layer signal, such as a physical random access channel (PRACH) or a scheduling request (SR). The network node may periodically switch to an active state to monitor for C-WUS, and if a C-WUS is detected, the network node may remain in the active state. If a non-C-WUS is detected, the network node may return to the sleep state after monitoring for C-WUS. However, using the physical channel C-WUS to wake up the network node from a sleep state may result in increased latency in communications between the UE and the network node, as the UE may have to wait for a C-WUS monitoring opportunity to send a C-WUS to the network node. In addition, reducing the time period between C-WUS monitoring opportunities may reduce network power savings from cell DRX.

[0029] Some techniques described herein provide LP-C-WUS to cell DRX to wake up the network node from a sleep state. In some aspects, the network node may include a low power wake-up radio (LP-WUR) and a main radio. The main radio may switch to a sleep state according to the cell DRX cycle. The LP-WUR may be a radio receiver circuit with very low energy consumption that is capable of receiving transmissions of the LP-C-WUS when the main radio is in a sleep state. In some aspects, the UE may receive a cell DRX configuration including one or more LP-C-WUS monitoring opportunities from the network node, wherein the LP-WUR of the network node monitors the LP-C-WUS sent by the UE. The UE may send the LP-C-WUS in the LP-C-WUS monitoring opportunity.

[0030] Therefore, by using the LP-WUR to monitor the LP-C-WUS, the network node can reduce network power consumption compared to switching the main radio component to an active state to monitor non-low power (non-LP) C-WUS (e.g., physical channel layer C-WUS). This can also allow the network to increase the time period between monitoring opportunities for non-LP C-WUS or replace non-LP C-WUS monitoring opportunities with LP-C-WUS monitoring, which can further reduce network power consumption. In addition, because the LP-WUR of the network node can monitor the LP-C-WUS while the main radio component remains in a sleep state, the LP-WUR can monitor the LP-C-WUS between monitoring opportunities for non-LP C-WUS, which can improve the latency of communications between one or more UEs and the network node.

[0031] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and will fully convey the scope of the present disclosure to those skilled in the art. It will be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or practice method. Furthermore, the scope of the present disclosure is intended to encompass such apparatus or methods implemented using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present claims.

[0032] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0033] Although various aspects may be described herein using terminology generally associated with 5G or NR radio access technologies (RATs), aspects of the present disclosure may be applied to other RATs, such as 3G RATs, 4G RATs, and / or post-5G RATs (e.g., 6G).

[0034] Figure 1 An example of a wireless communication network 100 according to the present disclosure is depicted.

[0035] Generally speaking, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is typically a communication device and / or a communication function performed by a communication device (e.g., a UE, a base station (BS), a component of a BS, a server, etc.). For example, various functions of a network and various devices associated with and interacting with the network can be considered network entities. In addition, the wireless communication network 100 includes terrestrial aspects, such as ground-based network entities (e.g., BS 110), and non-terrestrial aspects, such as satellites 140 and aircraft 145. The non-terrestrial aspects may include airborne network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., ground BSs) and UEs.

[0036] In the depicted example, the wireless communication network 100 includes a BS 110, a UE 120, and one or more core networks (such as an evolved packet core (EPC) 160 and a 5G core (5GC) 190) that interoperate to provide communication services over various communication links (including wired and wireless links).

[0037] Figure 1 Various example UEs 120 are depicted, which may include a cellular phone, a smartphone, a Session Initiation Protocol (SIP) phone, a laptop computer, a personal digital assistant (PDA), a satellite radio, a global positioning system (GPS), a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an Internet of Things (IoT) device, an always-on (AON) device, an edge processing device, or another similar device. A UE 120 may also be referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, or a handset, among others.

[0038] BS 110 may communicate wirelessly with (e.g., transmit signals to or receive signals from) UE 120 via communication link 170. Communication link 170 between BS 110 and UE 120 may carry uplink (UL) (also known as a reverse link) transmissions from UE 120 to BS 110 and / or downlink (DL) (also known as a forward link) transmissions from BS 110 to UE 120. In various aspects, communication link 170 may employ multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity.

[0039] BS 110 may include, for example, a NodeB, an enhanced NodeB (eNB), a next-generation enhanced NodeB (ng-eNB), a next-generation NodeB (gNB or gNodeB), an access point, a base transceiver station, a radio base station, a radio transceiver, transceiver functionality, a transmit / receive point, and / or the like. BS 110 may provide communication coverage for a corresponding geographic coverage area 112, which may sometimes be referred to as a cell and may overlap in some cases (e.g., a small cell provided by BS 110a may have a coverage area 112' that overlaps with the coverage area 112 of a macro cell). For example, BS 110 may provide communication coverage for a macro cell (covering a relatively large geographic area), a pico cell (covering a relatively small geographic area, such as a stadium), a femto cell (covering a relatively small geographic area (e.g., a home)), and / or other types of cells.

[0040] Although BS 110 is depicted in various aspects as a single communication device, BS 110 can be implemented in various configurations. For example, one or more components of the base station may be disaggregated, including a central unit (CU), one or more distributed units (DUs), one or more radio units (RUs), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, to name a few examples. In another example, various aspects of the base station may be virtualized. More generally, a BS (e.g., BS 110) may include components located at a single physical location or components located at various physical locations. In examples where the BS includes components located at various physical locations, the various components may each perform a function such that the various components collectively implement functions similar to a BS located at a single physical location. In some aspects, a BS including components located at various physical locations may be referred to as having a disaggregated RAN architecture, such as an open RAN (O-RAN) architecture or a virtualized RAN (vRAN) architecture. Figure 3 An example decomposed BS architecture is depicted and described.

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

[0042] The wireless communication network 100 may subdivide the electromagnetic spectrum into various categories, frequency bands, channels, or other characteristics. In some aspects, the subdivisions are based on wavelength and frequency, where frequency may also be referred to as a carrier, subcarrier, channel, tone, or subband. For example, the Third Generation Partnership Project (3GPP) currently defines Frequency Range 1 (FR1) as including 410 MHz to 7125 MHz, which is often (interchangeably) referred to as "sub-6 GHz." Similarly, 3GPP currently defines Frequency Range 2 (FR2) as including 24,250 MHz-52,600 MHz, which is sometimes (interchangeably) referred to as "millimeter wave" ("mmW" or "mmWave"). A base station configured to communicate using mmWave or near-mmWave radio bands (e.g., a mmWave base station such as BS110b) may utilize beamforming (e.g., as shown by 182) with a UE (e.g., 120) to improve path loss and range.

[0043] The communication link 170 between the BS 110 and, for example, the UE 120 may be through one or more carriers, which may have different bandwidths (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, and / or other bandwidths) and may be aggregated in various aspects. The carriers may or may not be adjacent to each other. In some examples, the allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL).

[0044] Communications using higher frequency bands may have higher path loss and shorter range than communications using lower frequencies. Accordingly, some base stations (e.g., Figure 1182 . BS 110b and UE 120 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, BS 110b may transmit beamformed signals to UE 120 in one or more transmit directions 182 ′. UE 120 may receive beamformed signals from BS 110b in one or more receive directions 182 ″. UE 120 may also transmit beamformed signals to BS 110b in one or more transmit directions 182 ″. BS 110b may also receive beamformed signals from UE 120 in one or more receive directions 182 ′. BS 110b and UE 120 may then perform beam training to determine optimal receive and transmit directions for each of BS 110b and UE 120. Notably, the transmit direction and receive direction of BS 110b may or may not be the same. Similarly, the transmit direction and receive direction of UE 120 may or may not be the same.

[0045] Wireless communication network 100 also includes a Wi-Fi AP 150 that communicates with Wi-Fi stations (STAs) 152 via communication links 154 in, for example, the 2.4 GHz and / or 5 GHz unlicensed spectrum.

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

[0047] EPC 160 may include various functional components, including: a mobility management entity (MME) 161, other MMEs 162, a serving gateway 163, a multimedia broadcast multicast service (MBMS) gateway 164, a broadcast multicast service center (BM-SC) 165, and / or a packet data network (PDN) gateway 166, such as in the depicted example. MME 161 may communicate with a home subscriber server (HSS) 167. MME 161 is a control node that handles signaling between UE 120 and EPC 160. Generally speaking, MME 161 provides bearer and connection management.

[0048] Generally, user Internet Protocol (IP) packets are delivered through a serving gateway 163, which is connected to a PDN gateway 166. The PDN gateway 166 provides UE IP address allocation and other functions. The PDN gateway 166 and the BM-SC 165 are connected to IP services 168, which may include, for example, the Internet, an intranet, an IP multimedia subsystem (IMS), packet-switched (PS) streaming services, and / or other IP services.

[0049] BM-SC 165 can provide functionality for MBMS user service provisioning and delivery. BM-SC 165 can serve as the entry point for content providers' MBMS delivery, can be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and / or can be used to schedule MBMS delivery. MBMS Gateway 164 can distribute MBMS services to BSs 110 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a specific service, and / or can be responsible for session management (start / stop) and collecting eMBMS-related charging information.

[0050] 5GC 190 may include various functional components, including: access and mobility management function (AMF) 191, other AMFs 192, session management function (SMF) 193, and user plane function (UPF) 194. AMF 191 may communicate with unified data management (UDM) 195.

[0051] AMF 191 is a control node that processes signaling between UE 120 and 5GC 190. AMF 191 provides, for example, Quality of Service (QoS) flow and session management.

[0052] The IP packets are passed through UPF 194, which connects to IP services 196 and provides UE IP address allocation and other functions for 5GC 190. IP services 196 may include, for example, the Internet, intranet, IMS, PS streaming services, and / or other IP services.

[0053] In various aspects, a network entity or network node may be implemented as a converged base station, a decomposed base station, a component of a base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a transmit receive point (TRP), or a combination thereof, to name a few examples.

[0054] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0055] Figure 2 Aspects of an example BS 110 and UE 120 according to the present disclosure are depicted.

[0056] Generally speaking, BS 110 includes various processors (e.g., 220, 230, 238, and 240), antennas 234a-234t (collectively 234), transceivers 232a-232t (collectively 232) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 212) and wireless reception of data (e.g., data sink 239). For example, BS 110 can transmit and receive data between BS 110 and UE 120. BS 110 includes a controller / processor 240 that can be configured to implement various functions described herein related to wireless communication.

[0057] Generally speaking, the UE 120 includes various processors (e.g., 258, 264, 266, and 280), antennas 252a-252r (collectively, 252), transceivers 254a-254r (collectively, 254) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., retrieved from a data source 262) and wireless reception of data (e.g., provided to a data sink 260). The UE 120 includes a controller / processor 280 that can be configured to implement various functions described herein related to wireless communications.

[0058] Regarding example downlink transmissions, BS 110 includes a transmit processor 220 that can receive data from a data source 212 and control information from a controller / processor 240. The control information can be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid automatic repeat request (HARQ) indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), and / or other channels. In some examples, the data can be for a physical downlink shared channel (PDSCH).

[0059] The transmit processor 220 may process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmit processor 220 may also generate reference symbols such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH demodulation reference signal (DMRS), or a channel state information reference signal (CSI-RS).

[0060] The transmit (TX) MIMO processor 230 may perform spatial processing (e.g., pre-coding) on ​​the data symbols, control symbols, and / or reference symbols, as applicable, and may provide an output symbol stream to a modulator (MOD) in the transceivers 232a-232t. Each modulator in the transceivers 232a-232t may process a corresponding output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in the transceivers 232a-232t may be transmitted via the antennas 234a-234t, respectively.

[0061] UE 120 includes antennas 252a-252r that can receive downlink signals from BS 110 and provide received signals to demodulators (DEMODs) in transceivers 254a-254r, respectively. Each demodulator in transceivers 254a-254r can condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator can further process the input samples to obtain received symbols.

[0062] A receive (RX) MIMO detector 256 may obtain received symbols from all demodulators in transceivers 254a-254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information to a controller / processor 280.

[0063] For example uplink transmissions, the UE 120 also includes a transmit processor 264 that can receive and process data from a data source 262 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 280 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 264 can also generate reference symbols for reference signals (e.g., for a sounding reference signal (SRS)). The symbols from the transmit processor 264 can be pre-decoded by the TX MIMO processor 266, if applicable, further processed by the modulators in the transceivers 254a-254r (e.g., for SC-FDM), and transmitted to the BS 110.

[0064] At BS 110, uplink signals from UE 120 may be received by antennas 234a-234t, processed by demodulators in transceivers 232a-232t, detected by MIMO detector 236 where applicable, and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller / processor 240. Memory 242 and memory 282 may store data and program codes (e.g., processor-executable instructions, computer-executable instructions) for BS 110 and UE 120, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink and / or uplink.

[0065] In various aspects, the BS 110 may be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" may refer to various mechanisms for outputting data, such as from a data source 212, a scheduler 244, a memory 242, a transmit processor 220, a controller / processor 240, a TX MIMO processor 230, transceivers 232a-232t, antennas 234a-234t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as from antennas 234a-234t, transceivers 232a-232t, an RX MIMO detector 236, a controller / processor 240, a receive processor 238, a scheduler 244, a memory 242, a network interface, and / or other aspects described herein.

[0066] In various aspects, the UE 120 may also be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" may refer to various mechanisms for outputting data, such as from a data source 262, memory 282, transmit processor 264, controller / processor 280, TX MIMO processor 266, transceivers 254a-254t, antennas 252a-252t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as from antennas 252a-252t, transceivers 254a-254t, RX MIMO detector 256, controller / processor 280, receive processor 258, memory 282, and / or other aspects described herein.

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

[0068] Although Figure 2 The blocks in FIG. 2 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0069] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0070] The deployment of a communication system such as a 5G NR system can be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of the network, a RAN node, a core network node, a network element, a base station or network equipment may be implemented in an aggregated architecture or a decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functions may be implemented as an aggregated base station (also known as an independent base station or a monolithic base station) or a decomposed base station. A “network entity” or a “network node” may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs or a combination thereof).

[0071] A converged base station (e.g., a converged network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually spread across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among others.

[0072] Base station type operation or network design can take into account the aggregated nature of base station functionality. For example, a disaggregated base station can be utilized in an IAB network, O-RAN (such as a network configuration initiated by the O-RAN Alliance), or vRAN (also known as a cloud radio access network (C-RAN)) to facilitate scaling of the communication system by separating base station functionality into one or more units that can be deployed separately. A disaggregated base station can include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which can enable flexibility in network design. Each unit of the disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0073] Figure 3 An example decomposed base station 300 architecture according to the present disclosure is depicted. The decomposed base station 300 architecture may include one or more CUs 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units (such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links, such as an F1 interface. The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. The RU 340 may communicate with corresponding UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0074] Each of the units (e.g., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) 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 these units, or an associated processor or controller that provides instructions to the communication interface of the unit, may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium. Additionally or alternatively, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals or transmit signals to one or more of the other units via a wireless transmission medium, or both.

[0075] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may 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 a combination thereof. In some specific implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0076] The DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on a functional split such as that defined by 3GPP. In some aspects, the DU 330 may also host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0077] Lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functionality or low PHY layer functionality (such as performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, PRACH extraction and filtering, etc.), or both, based at least in part on a functional partitioning (such as a lower layer functional partitioning). In such an architecture, a RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control and user plane communications with a RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and CU 310 in a cloud-based RAN architecture, such as a vRAN architecture.

[0078] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as Open Cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0079] The non-RT RIC 315 can be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or in communication with the near-RT RIC 325 (e.g., via an A1 interface). The near-RT RIC 325 can be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions via an interface (e.g., via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

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

[0081] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0082] Figure 4A 、 Figure 4B 、 Figure 4C and Figure 4D Described is a method for wireless communication networks such as Figure 1 Various aspects of the data structure of the wireless communication network 100). Figure 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, Figure 4B is a diagram 430 illustrating an example of a DL channel within a 5G subframe, Figure 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and Figure 4D FIG480 is a diagram illustrating an example of UL channels within a 5G subframe.

[0083] 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. OFDM and Single Carrier Frequency Division Multiplexing (SC-FDM) will (for example, Figure 4B and Figure 4D The system bandwidth (as depicted in FIG) 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.

[0084] The wireless communication frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to either DL or UL. The wireless communication frame structure may also be time division duplex (TDD), where for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to both DL and UL.

[0085] exist Figure 4A and Figure 4C In the embodiment of the present invention, the wireless communication frame structure is TDD, where D is DL, U is UL, and F is flexibly used between DL / UL. The UE can be configured with a time slot format (dynamically configured by DL control information (DCI) or semi-statically / statically configured by RRC signaling) through a received time slot format indicator (SFI). In the depicted example, the 10ms frame is divided into 10 equally sized 1ms subframes. Each subframe may include one or more time slots. In some examples, each time slot may include 7 or 14 symbols, depending on the time slot format. The subframe may also include micro slots, which typically have fewer symbols than a whole time slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0086] In certain aspects, the number of slots within a subframe is based on the slot configuration and parameter set. For example, for slot configuration 0, different parameter sets (μ) 0 through 5 allow for 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 through 2 allow for 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and parameter set μ, there are 14 symbols per slot and 2 per subframe. μ time slots. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to 2 μ × 15 kHz, where μ is the parameter set index, which can be selected from values ​​0 to 5. Thus, the subcarrier spacing for parameter set μ = 0 is 15 kHz, and the subcarrier spacing for parameter set μ = 5 is 480 kHz. Other parameter sets and subcarrier spacings can be used. The symbol length / duration is inversely related to the subcarrier spacing. Figure 4A 、 Figure 4B 、 Figure 4C and Figure 4D An example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ = 2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0087] like Figure 4A 、 Figure 4B 、 Figure 4C and Figure 4D As depicted in FIG, a resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also called a physical RB (PRB)) extending over, for example, 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0088] like Figure 4AAs illustrated, some of the REs carry reference (pilot) signals (RSs) for a UE (e.g., UE 120). The RSs may include DMRSs and / or CSI-RSs for channel estimation at the UE. The RSs may also include beamforming RSs (BRSs), beam refinement RSs (BRRSs), and / or phase tracking RSs (PT-RSs).

[0089] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated.The PDCCH carries 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.

[0090] The PSS may be within symbol 2 of a particular subframe of a frame. The PSS is used by a UE (eg, UE 120) to determine subframe / symbol timing and physical layer identification.

[0091] The SSS may be within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing.

[0092] Based on the physical layer identity and the physical layer cell identity 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 PBCH carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The PDSCH carries user data, broadcast system information not sent via the PBCH (such as the system information block (SIB)), and / or paging messages.

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

[0094] Figure 4DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at the position indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding 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 (BSRs), power headroom reports (PHRs), and / or UCI.

[0095] Figure 5 is a diagram illustrating an example 500 of a DRX configuration according to the present disclosure.

[0096] like Figure 5 As shown, a network node (eg, BS110 or Figure 3 5. The decomposed base station discussed herein may send a DRX configuration to the UE 120 to configure a DRX cycle 505 for the UE 120. In some cases, the DRX configuration may be a connected mode DRX configuration (C-DRX) provided to the UE 120 when the UE 120 is in connected mode. In addition, the DRX configuration may be specific to the UE 120 (e.g., the network node may configure separate DRX cycles 505 for different UEs 120). As described herein, the DRX cycle 505 may include a DRX on-duration 510 (e.g., during which the UE 120 is awake or active) and an opportunity to enter a DRX sleep state 515. As used herein, the time during which the UE 120 is configured to be active (e.g., during the DRX on-duration 510 and any time while the DRX inactivity timer 530 is running) may be referred to as active time or DRX active time, and the time during which the UE 120 is configured to be in the DRX sleep state 515 may be referred to as inactive time or DRX inactive time. As described below, UE 120 may monitor the PDCCH during DRX active time and may avoid monitoring the PDCCH during DRX inactive time.

[0097] During the DRX on-duration 510 (e.g., active time), the UE 120 may monitor a downlink control channel (e.g., PDCCH), as indicated by reference numeral 520. For example, the UE 120 may monitor the PDCCH for DCI related to the UE 120. If the UE 120 does not detect any PDCCH communication intended for the UE 120 and / or does not successfully decode any PDCCH communication during the DRX on-duration 510, the UE 120 may enter a sleep state 515 at the end of the DRX on-duration 510 (e.g., during inactive time), as indicated by reference numeral 525. In this way, the UE 120 may conserve battery power and reduce power consumption. As shown, the DRX cycle 505 may repeat at a configured periodicity according to the DRX configuration.

[0098] If the UE 120 detects a PDCCH communication intended for the UE 120 and / or successfully decodes the PDCCH communication, the UE 120 may remain in an active state (e.g., awake) for the duration of the DRX inactivity timer 530 (e.g., which may extend the DRX active time). The UE 120 may start the DRX inactivity timer 530 at the time the PDCCH communication is received (e.g., in a transmit time interval (TTI), such as a timeslot or subframe, in which the PDCCH communication is received). The UE 120 may remain in the active state until the DRX inactivity timer 530 expires, at which point the UE 120 may enter the sleep state 515 (e.g., within the DRX inactivity time), as indicated by reference numeral 535. During the duration of the DRX inactivity timer 530, the UE 120 may continue to monitor PDCCH communications, may obtain downlink data communications scheduled by the PDCCH communications (e.g., on a downlink data channel such as the PDSCH), and / or may prepare for and / or transmit uplink communications scheduled by the PDCCH communications (e.g., on the PUSCH). The UE 120 may restart the DRX inactivity timer 530 each time a PDCCH communication of the UE 120 is detected for an initial transmission (e.g., but not for a retransmission). By operating in this manner, the UE 120 may conserve battery power and reduce power consumption by entering the sleep state 515 during the DRX inactivity time.

[0099] Figure 6 is a diagram illustrating an example 600 of cell DRX according to the present disclosure.

[0100] One potential technique for improving energy efficiency in a RAN may be to enable cell DRX. In some aspects, a network node may send a cell DRX configuration (e.g., to one or more UEs) to configure a cell DRX cycle. The cell DRX configuration may configure a time period during which the network node does not receive transmissions from UEs in the cell, allowing the network node to enter a sleep state. The cell DRX configuration may configure discontinuous transmission (DTX) for one or more UEs in the cell. The cell DRX configuration may also be referred to as a DTX / DRX configuration or a DTX configuration for the UE. The cell DRX configuration may have similar characteristics to a DRX configuration that may be configured for a UE. For example, a cell DRX cycle may include: a cell DRX on duration (or active time), during which the network node is awake and in an active state; and a cell DRX off duration (or inactive time), during which the network node is configured to be in a sleep state. The network node may not transmit or receive channels or signals while in the sleep state. For example, during the cell DRX inactive time, the network node may not receive or monitor uplink channel communications, random access channel (RACH) communications, or uplink reference signals, etc.

[0101] In some examples, the cell DRX configuration may be activated during times of the day when there is no traffic or the traffic load is light in the cell (e.g., off-peak hours). However, the network node may still need to periodically broadcast signals and / or channels, such as SSBs and system information (SI). In addition, the network node may still need to periodically monitor PRACH opportunities to look for possible RACH or small data transmissions (SDTs) from UEs that are not in RRC connected mode. All of this periodic transmission and monitoring requires the network node to be in an active state and therefore limits the network power savings that can be achieved from cell DRX. In some examples, if the network node knows that there are no connected UEs or light traffic loads in the cell, the network node may stop or slow down periodic transmission and / or periodic monitoring to achieve network power savings. However, in some cases, the network node may not know whether one or more UEs need to switch to a connected state (e.g., RRC connected mode) or perform some SDT, so the network node may transition to an active state. In some aspects, such UEs may actively wake up the network node by transmitting a C-WUS. The C-WUS may be a physical layer signal, such as a PRACH or SR.

[0102] like Figure 6As shown, the cell DRX cycle may be configured with periodic C-WUS monitoring opportunities 605 aligned with the cell DRX on duration. The network node may switch to an active state to monitor for C-WUS during each C-WUS monitoring opportunity 605. As shown at reference numeral 610, if the network node does not detect a C-WUS during a C-WUS monitoring opportunity, the network node may enter a sleep state at the end of the C-WUS monitoring opportunity (e.g., for the duration of the inactivity time or the cell DRX off duration). As shown at reference numeral 615, the UE may send a C-WUS to the UE during the C-WUS monitoring opportunity 605. As shown at reference numeral 620, if the network node detects a C-WUS during the C-WUS monitoring opportunity 605, the network node may remain in the active state after the C-WUS monitoring opportunity. For example, the network node may remain in the active state for the duration of a timer that extends the cell DRX active time (e.g., the cell DRX inactivity timer). While in the active state, the network node may communicate with the UE that sent the C-WUS. For example, the network node may send an SSB, SIB type 1 (SIB1), and / or serve the UE for uplink data reception, etc.

[0103] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0104] Figure 7 7 is a diagram illustrating an example 700 of a network node with LP-WUR according to the present disclosure. Figure 7 As shown, in some aspects, a network node (e.g., BS 110 or as described with respect to Figure 3 The discussed one or more components of the decomposed base station may be equipped with a communication system including a main radio component (MR) and a LP-WUR. The network node may typically use the MR to send and / or receive data to the UE and / or other wireless communication devices. For example, the MR may include the above-mentioned Figure 2 Components of the described BS 110. In some cases, the MR may be turned off or operated in a sleep state unless there is a channel or signal to be sent or received by the network node. For example, the MR may be turned off or operated in a sleep state during the cell DRX inactivity time. In some aspects, the LP-WUR may be used as a simple wake-up receiver for the MR of the network node (e.g., the LP-WUR does not include a transmitter). When the MR is in a sleep state (e.g., during the cell DRX inactivity time), the LP-WUR may be active and monitor the LP-C-WUS. The LP-C-WUS is a low power wake-up signal (LP-WUS) sent by the UE or other device to wake up the network node (e.g., the MR of the network node).

[0105] For example, reference numeral 710 depicts a first state associated with the MR and the LP-WUR in the absence of a signal or channel to be transmitted or received by the MR (e.g., during a cell DRX inactivity time). In this case, the MR may be turned off or in a sleep state (e.g., a deep sleep state) unless there is a signal or channel to be transmitted or received, and the LP-WUR may actively monitor for the LP-C-WUS (e.g., continuously or periodically in time-separated monitoring opportunities). Reference numeral 720 depicts a second state associated with the MR and the LP-WUR in the presence of a signal or channel to be transmitted or received by the MR. In this case, the LP-WUR may receive the LP-C-WUS (e.g., from the UE) and may provide a trigger to wake up or otherwise activate the MR based on detecting the LP-C-WUS. In some examples, the LP-WUR may provide a trigger to cause the MR to remain in an active state after a C-WUS monitoring opportunity for a physical layer C-WUS (e.g., a non-LP C-WUS) configured in the cell DRX configuration. Once the MR is awake or in an active state, the MR may send and / or receive signals and / or channels.

[0106] The LP-WUR may be a simple radio receiver circuit designed to have very low energy consumption. For example, the LP-WUR of a network node may be an RF envelope detector receiver (e.g., a non-coherent envelope detector), a zero intermediate frequency (IF) receiver, a low IF receiver, a super regenerative receiver (SRR), or a discrete Fourier transform (DFT) receiver. The LP-WUR may consume very little power (e.g., a target power consumption of less than 100 microwatts (μW) in an active state), which may be achieved using a simple modulation scheme (e.g., on-off keying (OOK)), a narrow bandwidth (e.g., less than 5 MHz), and / or other suitable techniques.

[0107] LP-WUR can be used to reduce the time an MR spends in an active state and / or can avoid unnecessarily waking the MR from a sleep state when there are no signals or channels to be transmitted or received by the MR, which is often expensive from a power consumption perspective. For example, monitoring of an LP-C-WUS by an LP-WUR of a network node can be used to replace monitoring a non-LP C-WUS (e.g., a physical layer C-WUS) during a cell DRX cycle (e.g., by the MR), or can allow the time period between monitoring opportunities for a non-LP C-WUS to be increased, thereby reducing network power consumption. Furthermore, because the LP-WUR has very low power consumption, the LP-WUR can be used to perform LP-WUS monitoring frequently or continuously, which can improve latency because the LP-WUR can receive the LP-C-WUS and wake up the MR during the time period between configured monitoring opportunities for a non-LP C-WUS.

[0108] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0109] Figures 8A to 8E 8 is a diagram illustrating an example 800 associated with cell DRX with LP-C-WUS according to the present disclosure. Figure 8A As shown, example 800 includes a network node (e.g., BS 110 or Figure 3 In some aspects, the network node and the UE may be included in a wireless network, such as the wireless network 100. The network node and the UE may communicate via a wireless access link, which may include an uplink and a downlink. The network node may include an MR and an LP-WUR, such as in conjunction with Figure 7 described.

[0110] like Figure 8AIn the embodiment of the present invention, and as indicated by reference numeral 805, the network node may send, and the UE may receive, an indication of network capabilities for LP-C-WUS reception. For example, the indication of network capabilities for LP-C-WUS reception may be included in an SSB, SIB1, other SIB (OSIB), or layer 1 (L1), layer 2 (L2), or layer 3 (L3) signaling (e.g., included in an RRC message, a MAC control element (MAC-CE), or a DCI). In some aspects, the indication of network capabilities may indicate whether the network node supports LP-C-WUS reception. Depending on the capabilities of the network node, there may be different categories and designs of LP-C-WUS. In some aspects, the indication of network capabilities may indicate which types or formats of LP-C-WUS are supported by the network node. For example, the indication of network capabilities may indicate one or more types / formats of LP-C-WUS supported by the network node. In some aspects, the indication of network capabilities may include information identifying supported waveforms and / or modulations to be used for the LP-C-WUS. For example, the network capability information may indicate a class of LP-WUR of the network node, and the class of LP-WUR may identify waveforms and / or modulations that may be received by the LP-WUR. The LP-C-WUS may be a signal that is capable of being received by the LP-WUR of the network node. In some aspects, the indication of network capability may include information indicating what content may be included in the payload of the LP-C-WUS sent by the UE. In some aspects, the indication of network capability may indicate that the network node supports certain frequency bands and / or frequency ranges for LP-C-WUS reception. For example, the indication of network capability may identify one or more frequency ranges (e.g., FR1 and / or FR2, etc.) that support LP-C-WUS reception, one or more frequency bands (BWPs) that support LP-C-WUS reception, and / or one or more frequencies within each configured BWP or frequency band that supports LP-C-WUS.

[0111] In some aspects, the type or format of LP-C-WUS supported by the network node may include at least one of the following: an OOK-based waveform (e.g., an OFDM-based waveform, such as a CP OFDM waveform and / or a DFT-spread OFDM (DFT-S-OFDM) waveform), a frequency shift keying (FSK)-based OFDM signal, a sequence-based signal processed in the time domain (e.g., a DFT-based sequence, a Zadoff sequence, a Gold sequence, an m-sequence, a pulse amplitude modulation (PAM)-based sequence, or a pulse position modulation (PPM)-based sequence, etc.), a DFT-based sequence processed in the frequency domain, or a PDCCH-based signal. A PDCCH-based LP-C-WUS may have higher power consumption than other types of LP-C-WUS described herein, but may still provide network power savings if the network node supports a sleep state lower than a deep sleep state (where power savings are still maintained) but allows the network node to wake up from processing faster than a deep sleep state.

[0112] like Figure 8A In and as indicated by reference numeral 810, the UE may transmit, and the network node may receive, an indication of UE capabilities for LP-C-WUS transmission. In some aspects, the indication of UE capabilities may indicate whether the UE supports LP-C-WUS transmission. In some aspects, the indication of UE capabilities may indicate whether the UE supports transmission of a type / format of LP-C-WUS per frequency band and / or frequency band combination, per frequency range and / or frequency range combination, and / or per component carrier (CC) and / or CC combination. The indication of UE capabilities may be included in a RACH message, a response to an indication of network capabilities received for LP-C-WUS, UE assistance information (UAI), or L1, L2, or L3 signaling (e.g., included in an RRC message, MAC-CE, or UCI).

[0113] In some aspects, the indication of the UE's capability for LP-C-WUS transmission may be based at least in part on an indication of the network's capability for LP-C-WUS reception. For example, the UE may indicate support for LP-C-WUS transmission in conjunction with support for at least one type / format of LP-C-WUS that is also supported by the network node. In some aspects, the UE selects between supporting LP-C-WUS transmission and supporting non-LP C-WUS transmission. Non-LP C-WUS refers to C-WUS received by a MR of the network node (e.g., C-WUS that requires the MR to be in an active state to be received by the network node). For example, as described above in conjunction with Figure 6 The physical layer C-WUS described herein (e.g., PRACH or SR) may be referred to herein as non-LP C-WUS. Figure 9As discussed in more detail, LP-C-WUS transmission may be activated or enabled in a partial coverage area or a full coverage area of ​​a cell associated with a network node. In some examples, the UE may support LP-C-WUS transmission to achieve better power savings (e.g., compared to non-LP C-WUS transmission), for example, due to support for a simpler receiver and / or lower transmit power in the partial coverage area, etc. In some other examples, such as in a full coverage area case, LP-C-WUS transmission may come at the expense of increased repetitiveness of power boosting from the UE, and thus may utilize more power to achieve the same coverage as non-LP C-WUS. In such examples, the UE may not support LP-C-WUS transmission. In some aspects, the indication that the UE supports LP-C-WUS transmission may be dynamic, and the UE may change the indication, for example, based at least in part on the UE's location in the cell or a mobility measurement of the UE.

[0114] like Figure 8A In and as further indicated by reference numeral 815, the network node may send and the UE may receive a cell DRX configuration. In some aspects, the cell DRX configuration may indicate one or more LP-C-WUS monitoring opportunities in the cell DRX cycle. The LP-C-WUS monitoring opportunity is a time window during which the LP-WUS of the network node monitors LP-C-WUS from the UE and / or other UEs in the cell. In some aspects, when the MR of the network node is configured (e.g., according to the cell DRX configuration) to be in a sleep state, one or more LP-C-WUS monitoring opportunities may be scheduled. That is, when the MR of the network node is in a sleep state (e.g., during the cell DRX inactivity time for the MR), the LP-WUS of the network node may monitor the LP-C-WUS. In some aspects, the cell DRX configuration may configure periodic LP-C-WUS monitoring opportunities. In some aspects, in addition to the LP-C-WUS monitoring opportunities, the cell DRX configuration may also configure (e.g., by the MR in an active state) C-WUS monitoring opportunities for non-LP C-WUS monitoring. In some aspects, timing of one or more LP-C-WUS monitoring opportunities can be configured based at least in part on non-LP C-WUS monitoring opportunities. For example, one or more LP-C-WUS monitoring opportunities can be scheduled between non-LP C-WUS monitoring opportunities.

[0115] As in Figure 8BIn and as shown by reference numeral 840, in some aspects, the cell DRX configuration may configure LP-C-WUS monitoring opportunities 842 as consecutive LP-C-WUS monitoring time windows between non-LPC-WUS monitoring opportunities 844. The cell DRX configuration may configure a cell DRX cycle with active times (cell DRX on duration) and inactive times (cell DRX off duration) to be followed by the MR of the network node. That is, the MR of the network node may enter a sleep state during the cell DRX inactive time, and the MR of the network node may switch to an active state during the cell DRX active time. For example, the MR of the network node may switch to an active state to monitor the non-LP C-WUS monitoring opportunities 844, and may enter a sleep state after the non-LP C-WUS monitoring opportunities if no C-WUS is detected. When the MR is in the sleep state, the LP-WUS may monitor the LP-C-WUS during the LP-C-WUS monitoring 842. In Figure 8B In the example of , where the LP-C-WUS monitoring opportunity 842 is a continuous LP-C-WUS monitoring time window between non-LP C-WUS monitoring opportunities 844, the LP-WUS continuously monitors the LP-C-WUS when the MR is in the sleep state.

[0116] A UE supporting LP-C-WUS transmission may transmit the LP-C-WUS during an LP-C-WUS monitoring opportunity 842 (e.g., Figure 8B In one embodiment, the MR may receive an LP-C-WUS (e.g., a LP-WUS) and send an LP-C-WUS (e.g., in a compatible format with an indication of network capabilities) at any time the MR is in a sleep state. The LP-WUR may trigger an activity duration of the MR of the network node in conjunction with the LP-WUR receiving / detecting the LP-C-WUS during the LP-C-WUS monitoring opportunity 842. In some aspects, the MR may enter an active state at the next scheduled activity time after the LP-C-WUS monitoring opportunity 842 in which the LP-WUR detects the LP-C-WUS (e.g., at the start time of the next non-LP C-WUS monitoring opportunity 844), and the LP-WUR may trigger the MR to extend the activity time in conjunction with the LP-WUR detecting the LP-C-WUS. In some other aspects, the LP-WUR in conjunction with receiving the LP-C-WUS may trigger the MR to activate the MR from the sleep state at a time that does not correspond to a configured non-LP C-WUS monitoring opportunity (such as at a time offset from the time of detecting / receiving the LP-C-WUS or based on the configured activity duration of the LP-C-WUS monitoring opportunity 842).

[0117] As in Figure 8CIn some aspects, and as shown by reference numeral 850, the cell DRX configuration may configure multiple LP-C-WUS monitoring opportunities 852 between non-LP-C-WUS monitoring opportunities 854. In this case, rather than continuously monitoring the LP-C-WUS while the MR is in a sleep state, the LP-C-WUS may monitor the LP-C-WUS during configured monitoring opportunities 854 that may be separated by specific durations.

[0118] In some aspects, the LP-WUR of the network node may be turned off or switched to a dormant state between scheduled LP-C-WUS monitoring opportunities 852 (and / or when the MR is in an active state), and the LP-WUR of the network node may be turned on or switched to an active state during scheduled LP-C-WUS monitoring opportunities 852. For example, the LP-WUR may follow a DRX cycle configured for the LP-WUR, and the LP-C-WUS monitoring opportunities may correspond to active times in the DRX cycle for the LP-WUR. In some aspects, the cell DRX configuration sent to the UE may include a first cell DRX configuration associated with the LP-WUR of the network node (e.g., indicating a configuration of a first cell DRX cycle for the LP-WUR) and a second cell DRX configuration associated with the MR of the network node (e.g., indicating a configuration of a second cell DRX cycle for the MR). The first cell DRX cycle may include the LP-C-WUS monitoring opportunities 852, and the second cell DRX cycle may include non-LP C-WUS monitoring opportunities 854. The network node and the UE may send and / or receive downlink and / or uplink communications involving the MR (e.g., communications other than the LP-C-WUS) in accordance with the second cell DRX configuration (e.g., the cell DRX configuration for the MR). In some aspects, the first cell DRX cycle and the second cell DRX cycle may be aligned such that the active duration of the LP-WUR (e.g., corresponding to the LP-C-WUS monitoring opportunity) is configured to occur when the MR is in a sleep state, and the LP-WUR is configured to be in a sleep state during the active duration configured for the MR. In some other aspects, the first cell DRX cycle (e.g., the cell DRX cycle of the LP-WUR) may be independent of the second cell DRX cycle (e.g., the cell DRX cycle of the MR).

[0119] A UE supporting LP-C-WUS transmission may transmit an LP-C-WUS during any of the LP-C-WUS monitoring opportunities 852. The LP-WUR may trigger an active duration of a MR of the network node in conjunction with the LP-WUR receiving / detecting an LP-C-WUS during the LP-C-WUS monitoring opportunity 852. In some aspects, the MR may enter an active state at the next scheduled active time after the LP-C-WUS monitoring opportunity 852 in which the LP-WUR detects the LP-C-WUS (e.g., at the start time of the next non-LP C-WUS monitoring opportunity 854), and the LP-WUR may trigger the MR to extend the active time in conjunction with the LP-WUR detecting the LP-C-WUS. In some other aspects, the LP-WUR in conjunction with receiving an LP-C-WUS may trigger the MR to activate the MR from a sleep state at a time that does not correspond to a configured non-LP C-WUS monitoring opportunity (such as at a time offset from the time of detecting / receiving the LP-C-WUS or based on the configured active duration of the LP-C-WUS monitoring opportunity 842).

[0120] As in Figure 8D In and as indicated by reference numeral 860, in some aspects, the cell DRX configuration may configure different LP-C-WUS monitoring opportunities for different types of LP-C-WUS supported by the network node. The LP-WUS of the network node may support various signals, and the LP-C-WUS monitoring opportunities may be configured such that the LP-WUS supports different types of signals at different times. For example, the configured LP-C-WUS monitoring opportunities in the cell DRX cycle may include a first LP-C-WUS monitoring opportunity associated with a first type of LP-C-WUS and a second LP-C-WUS monitoring opportunity associated with a second type of LP-C-WUS. Figure 8DAs shown, the configured LP-C-WUS monitoring opportunities (e.g., in each cell DRX cycle) may include an LP-C-WUS monitoring opportunity 862 associated with OOK-based LP-C-WUS and an LP-C-WUS monitoring opportunity 864 associated with PDCCH-based LP-C-WUS. The LP-WUR of the network node may support OOK-based LP-C-WUS during the OOK-based LP-C-WUS monitoring opportunity 864, and the LP-WUR may support PDCCH-based LP-C-WUS during the PDCCH-based LP-C-WUS monitoring opportunity 864. That is, the LP-WUR may monitor OOK-based LP-C-WUS during the OOK-based LP-C-WUS monitoring opportunity and monitor PDCCH-based LP-C-WUS during the PDCCH-based LP-C-WUS monitoring opportunity. In some aspects, there may be a time gap between different types of LP-C-WUS monitoring opportunities to allow the LP-WUS to switch between the two modes (e.g., transition time and energy) to receive different types of signals. This time gap can be configured and reported to the UE (e.g., in the cell DRX configuration) so that the UE can then use the appropriate LP-C-WUS format at the appropriate time. In some aspects, different types of monitoring opportunities can be configured to occur during the MR's inactive time according to the cell DRX cycle. For example, Figure 8D As shown, the OOK-based LP-C-WUS monitoring opportunity 864 and the PDCCH-based LP-C-WUS monitoring opportunity 864 may be configured to occur during the inactivity time of the MR between the non-LPC-WUS monitoring opportunities 866 .

[0121] A UE supporting an LP-C-WUS type associated with an LP-C-WUS monitoring opportunity may transmit an LP-C-WUS of that type during the LP-C-WUS monitoring opportunity. For example, the UE may transmit an OOK-based LP-C-WUS during an OOK-based LP-C-WUS monitoring opportunity 862. The UE may transmit a PDCCH-based LP-C-WUS during a PDCCH-based LP-C-WUS monitoring opportunity 864. The LP-WUR may trigger the active duration of the MR of the network node by receiving / detecting an OOK-based LP-C-WUS during the OOK-based LP-C-WUS monitoring opportunity 862 or receiving / detecting a PDCCH-based LP-C-WUS during the PDCCH-based LP-C-WUS monitoring opportunity 864 in conjunction with the LP-WUR. In some aspects, the MR may enter an active state at the next scheduled active time after the LP-WUR detects an LP-C-WUS (e.g., at the start time of the next non-LP C-WUS monitoring opportunity 866), and the LP-WUR may trigger the MR to extend the active time in conjunction with the LP-WUR detecting the LP-C-WUS. In some other aspects, the LP-WUR in conjunction with receiving the LP-C-WUS may trigger the MR to activate the MR from a sleep state at a time that does not correspond to a configured non-LP C-WUS monitoring opportunity (such as at a time offset from the time of detecting / receiving the LP-C-WUS or based on the configured active duration of the LP-C-WUS monitoring opportunity in which the LP-C-WUS was received).

[0122] As in Figure 8E In some aspects, and as indicated by reference numeral 870, a configured LP-C-WUS monitoring opportunity 872 can be associated with a configured cell DRX on time window 874. Each configured cell DRX on time window 874 is a potential time window for a cell DRX on duration of the MR, conditional upon the LP-WUS detecting the LP-C-WUS in the LP-C-WUS monitoring opportunity 872 associated with the cell DRX on time window 874. In some examples, each LP-C-WUS monitoring opportunity 872 can be associated with a respective DRX on time window 874. In other examples, a cell DRX on time window 874 can be associated with multiple LP-C-WUS monitoring opportunities 872. In some aspects, the cell DRX on time window 874 associated with a configured LP-C-WUS monitoring opportunity 872 can be independent of any configured cell DRX on duration (e.g., activity duration) corresponding to a non-LP-C-WUS monitoring opportunity in the cell DRX cycle. In some other aspects, a configured start time of the Cell DRX On time window 874 associated with at least one configured LP-C-WUS monitoring opportunity may be aligned with a start time of a non-LP C-WUS monitoring opportunity.

[0123] The LP-WUR of the network node may monitor for LP-C-WUS during an LP-C-WUS monitoring opportunity 872. As shown by reference numeral 876, if the LP-WUR does not detect an LP-C-WUS during the LP-C-WUS monitoring opportunity 872, the MR is not activated (e.g., the MR does not switch to an active state) during a cell DRX on time window 874 associated with the LP-C-WUS monitoring opportunity 872. As shown by reference numeral 878, if the LP-WUR detects an LP-C-WUS during the LP-C-WUS monitoring opportunity 872, the LP-WUR may trigger the MR so that the MR switches to an active state within the cell DRX on time window 874 associated with the LP-C-WUS monitoring opportunity 872. In this case, the cell DRX on time window 874 defines an active time (e.g., a cell DRX on duration) for the MR of the network node.

[0124] In some aspects, the UE may indicate, in the contents of the payload of the LP-C-WUS, an adjustment to the configured cell DRX On time window 874 associated with the monitoring opportunity 872. For example, the LP-C-WUS payload may include an indication of an offset (e.g., a delta value) between the start time of the configured cell DRX On time window 874 and the requested start time of the active time for the MR and / or an offset (e.g., a delta value) between the duration of the configured cell DRX On time window 874 and the requested duration of the active time for the MR.

[0125] return Figure 8A As shown in reference numeral 820, the UE may send an LP-C-WUS during an LP-C-WUS monitoring opportunity. The network node may receive the LP-C-WUS during the LP-C-WUS monitoring opportunity. For example, when the MR is in a sleep state, the LP-WUS of the network node may monitor one or more configured LP-C-WUS monitoring opportunities. The LP-C-WUS of the network node may receive / detect the LP-C-WUS sent by the UE during the LP-C-WUS monitoring opportunity. The signal type used by the UE for the LP-C-WUS may be based at least in part on an indication of network capabilities received for the LP-C-WUS. For example, the UE may send an LP-C-WUS of a type supported by the network node.

[0126] In some aspects, a UE may transmit an LP-C-WUS based at least in part on receiving an indication from a network node that LP-C-WUS transmission is enabled. For example, the network node may indicate whether the network node will support only one of LP-C-WUS transmission or non-LP C-WUS transmission at a given time, or support both LP-C-WUS transmission and non-LP C-WUS transmission. In the event that the network node only supports one of LP-C-WUS transmission or non-LP C-WUS transmission at a time, the network node may transmit an indication that LP-C-WUS transmission or non-LP C-WUS transmission is enabled or disabled for UEs in the cell. For example, the indication may be included in an MIB, SIB1, OSIB, RACH message, or L1, L2, or L3 signaling (e.g., RRC message, MAC-CE, or DCI). In such examples, the UE may transmit the LP-C-WUS in conjunction with LP-C-WUS transmission being enabled. Alternatively, the UE may transmit a non-LP C-WUS in conjunction with non-LP C-WUS transmission being enabled and / or LP-C-WUS transmission being disabled.

[0127] In some aspects, when a UE supports both LP-C-WUS transmission and non-LP C-WUS transmission and a network node supports the use of both LP-C-WUS transmission and non-LP C-WUS transmission, the UE may select whether to transmit an LP-C-WUS in an LP-C-WUS monitoring opportunity or to transmit a non-LP C-WUS in a non-LP C-WUS monitoring opportunity. In some aspects, the UE may select whether to transmit an LP-C-WUS (e.g., LP-WUS communication with a network node) or a non-LP C-WUS (e.g., MR communication with a network node) based at least in part on one or more traffic characteristics of traffic associated with the UE (e.g., uplink traffic to be transmitted by the UE and / or downlink traffic to be received by the UE) and / or an RRC mode of the UE (e.g., connected, idle, or inactive). For example, the one or more traffic characteristics may include L1 / L2 priority, QoS, and / or delay parameters (e.g., remaining packet delay budget (PDB)), etc.

[0128] In some aspects, a network node may transmit and a UE may receive a configuration of transmission parameters for an LP-C-WUS. The UE may transmit the LP-C-WUS using the configured transmission parameters received from the network node. In some aspects, the configuration of the transmission parameters may include configuration of a first transmission parameter for the LP-C-WUS and a second transmission parameter for a non-LP C-WUS. In this case, the UE may transmit the LP-C-WUS using the first transmission parameter or transmit the non-LP C-WUS using the second transmission parameter in conjunction with selecting whether to transmit the LP-C-WUS or the non-LP C-WUS. In some examples, the configuration of the transmission parameters may indicate different transmission parameters for different LP-C-WUS types supported by the network node. In some aspects, the transmission parameters (for each LP-C-WUS type and / or for the non-LP C-WUS) may indicate, for example, the transmit power, guard band, and / or transmit beam used by the UE to transmit the LP-C-WUS (or non-LP C-WUS). In some aspects, the configuration of transmission parameters may be sent using L1, L2, or L3 signaling so that the configuration can effectively capture environmental and / or channel variations over time. In some aspects, the UE may add a guard band around the LP-C-WUS to reduce adjacent channel interference (ACI) and / or co-channel interference. For example, the guard band may be indicated in the configuration of transmission parameters for the LP-C-WUS.

[0129] In some aspects, the UE may transmit in time resources that are dedicated time resources configured for the signal type used for LP-C-WUS. For example, the LP-C-WUS monitoring occasion may include dedicated time resources configured for LP-C-WUS transmission. Additionally or alternatively, the UE may transmit the LP-C-WUS in a dedicated frequency band configured for LP-C-WUS transmission. In some cases, if the LP-C-WUS is not OFDM-based, there may be coexistence issues between OFDM-based signals and LP-C-WUS signals (e.g., because OFDM signal orthogonality may be impaired). In this case, the network node may configure dedicated time resources for LP-C-WUS signals (e.g., not for OFDM-based signals) and / or a dedicated frequency band for LP-C-WUS. The configuration of the dedicated time resources and / or dedicated frequency band for LP-C-WUS may be indicated in an indication of network capabilities received for LP-C-WUS, a cell DRX configuration, and / or some other configuration information sent from the network node to the UE.

[0130] The LP-WUR of the network node may have low clock accuracy. In some aspects, the network node may perform synchronization of the LP-WUR using a synchronization signal received at the network node. For example, the synchronization signal may be sent by the UE or another network node. The synchronization signal may be a periodic synchronization signal, a preamble signal sent together with the LP-C-WUS (e.g., sent by the UE), or a combination thereof. The synchronization method may be semi-statically or dynamically configured using L1, L2, or L3 indications. The UE's transmission of the synchronization signal may be affected by the UE's capabilities. The synchronization signal for synchronization of the LP-WUR (e.g., sent by the UE or another network node) may be received by the LP-WUR, or the MR of the network node may occasionally (e.g., periodically) wake up to receive the synchronization signal. In some aspects, the LP-WUR of the network node may support a signal format / type for synchronization that is different from the signal format / type supported for the LP-C-WUS. For example, the low-power synchronization signal and / or preamble signal used for synchronization of LP-WUR may be an OOK or FSK waveform or reference signal (e.g., SRS, tracking reference signal (TRS), CSI-RS, or SSB). In some aspects, the time or opportunity at which the UE sends a low-power synchronization signal (e.g., a periodic or aperiodic synchronization signal) to be used for synchronization of LP-WUR may be configured / indicated in the MIB, SIB1, RACH message, OSIB via an L1, L2, or L3 indication from the network node to the UE. For example, the L1, L2, or L3 indication from the network node to the UE may be based on the preference and / or capability indicated by the UE via L1, L2, or L3 signaling (e.g., in UAI), or multiplexed with L1, L2, or L3 signaling (e.g., multiplexed with SR, BSR, channel state information (CSI), HARQ-ACK, or PHR, etc.).

[0131] In some aspects, the transmit beam used by the UE to transmit the LP-C-WUS may be based on a quasi-co-location (QCL) relationship between the LP-C-WUS and a non-LP C-WUS. For example, the QCL relationship between the LP-C-WUS and the non-LP C-WUS may be configured by the network node (e.g., in a configuration of transmission parameters or other configuration information), or may be defined (e.g., in a wireless communication standard). In some aspects, the LP-C-WUS may be QCLed with an SSB, an SRS, another LP-C-WUS, or a synchronization signal used for synchronization of the network node's LP-WUS.

[0132] The LP-C-WUS may have a low rate and / or a low payload size to achieve, for example, coverage reliability similar to that of the PUCCH. Consequently, the LP-C-WUS may include relatively few bits per LP-C-WUS packet. A network node may define / configure different formats for the LP-C-WUS that include different indications in the bits / payload of the LP-C-WUS. In some aspects, the bits / payload of the LP-C-WUS may indicate at least one of: a wake-up indication; a requested duration of the network node's active time (e.g., a delta value relative to a configured duration or an explicit indication of the requested duration); a requested start time of the network node's active time (e.g., an offset from the transmission of the LP-C-WUS, a delta value relative to a configured start time, or an explicit indication of the requested start time); an SSB request; an SIB1 request; a search space set group (SSSG) configuration index for PDCCH monitoring by the UE; an energy request for wireless charging by the UE (e.g., if the UE is a wireless charging device and the network node supports at least one wireless charging technology (such as laser or RF wireless charging)); an indication of the service to be sent by the UE (e.g., uplink service); a priority or QoS of the service to be sent by the UE; a type of service to be sent by the UE; the capabilities of the UE (e.g., if the UE changes capabilities, such as moving to or from enhanced reduced capability (eRedCap) UE capability or another capability); an uplink BSR; or a maximum size of a downlink BSR supported by the UE in a subsequent time period. In some examples, the start time and / or duration of the active node indicated in the payload of the LP-C-WUS may indicate the start time and / or duration of the expected active time of the MR for the network node determined by the UE at least in part based on jitter and / or traffic statistics.

[0133] As in Figure 8A In the embodiment and as further indicated by reference numeral 825, the network node may switch the MR to an active state based at least in part on receiving the LP-C-WUS during the LP-C-WUS monitoring opportunity. In some aspects, a LP-WUR of the network node may receive the LP-C-WUS during the LP-C-WUS monitoring opportunity, and the LP-WUR may provide a trigger to wake up or otherwise activate the MR of the network node based on detecting the LP-C-WUS.

[0134] As in Figure 8A In the embodiment of the present invention and as further indicated by reference numeral 830, when the MR is in the active mode, the network node may communicate with the UE using the MR of the network node. In some aspects, the network node may communicate with the UE using the MR based at least in part on an indication included in the payload of the LP-C-WUS, such as a request for the network node to send a downlink channel or signal or an indication of uplink traffic to be sent by the UE.

[0135] As indicated above, Figures 8A to 8E are provided as examples. Other examples may be used with respect to Figures 8A to 8E The examples described are different.

[0136] Figure 9 is a diagram illustrating an example 900 associated with a coverage area for LP-C-WUS transmission in a cell according to the present disclosure. Figure 9 As shown, example 900 includes a network node (e.g., BS 110 or Figure 3 The decomposed base station in question), a first UE (UE1) (eg, UE 120) and a second UE (UE2) (eg, UE 120).

[0137] like Figure 9 As shown, in some aspects, the LP-C-WUS sends (e.g., as described above with respect to Figures 8A to 8E As discussed above, a cell associated with the network node may have full coverage. In this case, LP-C-WUS transmission may be enabled for UEs in a full coverage area 905 of the cell. For example, the full coverage area 905 may be similar to the coverage area used for PUCCH coverage or any other NR coverage (e.g., as defined in a wireless communication standard). In some other aspects, LP-C-WUS transmission may have partial coverage in a cell associated with the network node. In this case, LP-C-WUS transmission may be enabled for UEs in a partial coverage area 910 of the cell. There may be a mismatch between the partial coverage area 910 in which the LP-C-WUS is covered and the full coverage area 905 used for PUCCH and / or other NR coverage in the cell. For example, the partial coverage area 910 may be a first coverage area, the full coverage area 905 may be a second coverage area, and the first coverage area (e.g., the partial coverage area 910) may be within and smaller than the second coverage area (e.g., the full coverage area 905).

[0138] In some aspects, LP-C-WUS transmission with partial coverage may be associated with / configured with different transmission parameters (e.g., power control and repetition parameters) from LP-C-WUS transmission with full coverage. For example, the UE may enable transmission of the LP-C-WUS using a first set of transmission parameters (e.g., configured by a network node) in conjunction with LP-C-WUS transmission in the partial coverage area 910, or may enable transmission of the LP-C-WUS using a second set of transmission parameters (e.g., configured by a network node) in conjunction with LP-C-WUS transmission in the full coverage area 905.

[0139] In some aspects, when LP-C-WUS transmission has partial coverage in a cell, LP-C-WUS transmission may be enabled for UEs in the partial coverage area 910, and non-LP C-WUS transmission may be enabled for UEs in the full coverage area 905 and outside of the partial coverage area 910. UEs in the partial coverage area 910 (e.g., near-cell UEs) may transmit LP-C-WUS. For example, UE1 may transmit LP-C-WUS in conjunction with LP-C-WUS monitoring opportunities within the partial coverage area 910. UEs outside the partial coverage area 910 and within the full coverage area 905 (e.g., far-cell UEs) may transmit non-LP C-WUS. For example, UE2 may transmit non-LP C-WUS in conjunction with being outside the partial coverage area 910 and within the full coverage area 905.

[0140] In some aspects, in the case of partial coverage of LP-C-WUS transmission, the UE may select whether to transmit an LP-C-WUS or a non-LP C-WUS based at least in part on one or more UE measurements (such as distance measurements, path loss measurements, CSI measurements, channel metric measurements, mobility measurements, and / or location measurements and / or the UE's knowledge of the UE's relative location relative to the network node). In this case, the UE may switch between LP-C-WUS transmission and non-LP C-WUS transmission based at least in part on the UE location and / or the measurements performed by the UE. In some other aspects, in the case of partial coverage of LP-C-WUS, the network node may send, and the UE may receive, an indication that the UE is configured for LP-C-WUS transmission or non-LP C-WUS transmission based at least in part on network measurements (e.g., performed by the network node). For example, the network node may send the indication to the UE using L1, L2, or L3 signaling. In this case, the network node may indicate to the UE when to switch between LP-C-WUS transmission and non-LP C-WUS transmission.

[0141] As indicated above, Figure 9 are provided as examples. Other examples can be found in the Figure 9 The examples described are different.

[0142] Figure 10 1 is a diagram illustrating an example 1000 associated with C-WUS transmission assistance according to the present disclosure. Figure 10 As shown, example 1000 includes a network node (e.g., BS 110 or Figure 3 The decomposed base station in question), a first UE (UE1) (eg, UE 120) and a second UE (UE2) (eg, UE 120).

[0143] like Figure 10As shown, in some aspects, a secondary device (such as a UE (e.g., UE1) or another network device) may assist a UE (e.g., UE2) in transmitting an LP-C-WUS (or non-LP C-WUS) to wake up a network node (e.g., an MR of the network node) from a sleep state. For example, in a situation where LP-C-WUS transmission has partial coverage in a cell associated with the network node, a far-cell UE (e.g., a UE outside the partial coverage area 910 and having the full coverage area 905) may request a secondary device (e.g., a near-cell UE or another network device) to transmit a C-WUS (e.g., an LP-C-WUS or non-LP C-WUS) on behalf of the far-cell UE to wake up the network node. The secondary device may transmit the LP-C-WUS or non-LP C-WUS on behalf of the far-cell UE based at least in part on receiving the request from the far-cell UE. For example, if the secondary device supports LP-C-WUS transmission and is in the near-cell (e.g., in the partial coverage area 910 for LP-C-WUS transmission), the secondary device may transmit the LP-C-WUS on behalf of the far-cell UE. Alternatively, if the secondary device does not support LP-C-WUS transmission or the secondary device is outside the partial coverage area 910 for LP-C-WUS transmission (for example, the secondary device may be a far-cell device but still closer to the network node than the far-cell UE requesting assistance), the secondary device may transmit a non-LP C-WUS.

[0144] As in Figure 10 In the example shown in FIG1005 , and as indicated by reference numeral 1005 , UE2 may transmit, and UE1 may receive, a request to transmit a C-WUS (e.g., LP-C-WUS) on behalf of UE2. For example, UE2 may be a far-cell UE outside the partial coverage area 910 for LP-C-WUS transmission (and within the full coverage area 905 of the cell). UE1 may be a near-cell UE within the partial coverage area 910 for LP-C-WUS transmission, and UE1 may support LP-C-WUS transmission. As indicated by reference numeral 1010 , UE1 may transmit the LP-C-WUS based at least in part on receiving a message from UE2. That is, based at least in part on receiving a request from UE2, UE1 may transmit the LP-C-WUS on behalf of UE2.

[0145] As indicated above, Figure 10 are provided as examples. Other examples can be found in the Figure 10 The examples described are different.

[0146] Figure 11 A method 1100 for wireless communications by a UE, such as UE 120, is shown.

[0147] Method 1100 begins, at 1110, by receiving, from a network node, an indication of network capabilities for LP-C-WUS reception.

[0148] The method 1100 then proceeds to step 1120 by sending an indication of the UE's capabilities for LP-C-WUS transmission to the network node.

[0149] The method 1100 then proceeds to step 1130 by receiving a cell DRX configuration from a network node indicating one or more LP-C-WUS monitoring opportunities in the cell DRX cycle.

[0150] The method 1100 then proceeds to step 1140 by sending an LP-C-WUS to the network node in an LP-C-WUS opportunity in one of the one or more LP-C-WUS opportunities.

[0151] In one aspect, the indication of the network capabilities received for the LP-C-WUS is included in an SSB, SIB1, another SIB, an RRC message, a MAC-CE, or a DCI.

[0152] In one aspect, the indication of network capabilities for LP-C-WUS reception indicates whether the network node supports LP-C-WUS reception.

[0153] In one aspect, the indication of network capabilities received for the LP-C-WUS indicates one or more types of LP-C-WUS supported by the LP-WUR of the network node, and the LP-C-WUS is a type of LP-C-WUS from one or more types of LP-C-WUS supported by the LP-WUR of the network node.

[0154] In one aspect, the one or more types of LP-C-WUS supported by the LP-WUR of the network node include one or more of an OOK-based waveform, an FSK-based OFDM signal, a sequence-based signal, a DFT-based sequence, or a PDCCH-based signal.

[0155] In one aspect, the indication of network capabilities for LP-C-WUS reception indicates at least one of one or more frequency bands or one or more frequency ranges that support LP-C-WUS reception.

[0156] In one aspect, the indication of UE capability for LP-C-WUS transmission indicates whether the UE supports LP-C-WUS transmission.

[0157] In one aspect, the indication of UE capabilities for LP-C-WUS transmission indicates whether the UE supports transmission of one or more types of LP-C-WUS per frequency band, frequency band combination, frequency range, frequency range combination, component carrier, or component carrier combination.

[0158] In one aspect, the indication of UE capabilities sent for LP-C-WUS is included in a RACH message, a response to an indication of network capabilities received for LP-C-WUS, UAI, an RRC message, a MAC-CE, or UCI.

[0159] In one aspect, LP-C-WUS transmission is enabled for the UE in a full coverage area of ​​a cell associated with the network node, or LP-C-WUS transmission is enabled for the UE in a partial coverage area that is within and less than the full coverage area.

[0160] In one aspect, sending an LP-C-WUS in an LP-C-WUS opportunity in one or more LP-C-WUS opportunities includes enabling use of a first set of transmission parameters in conjunction with LP-C-WUS transmission in a full coverage area or enabling use of a second set of transmission parameters in conjunction with LP-C-WUS transmission in a partial coverage area.

[0161] In one aspect, LP-C-WUS transmission is enabled in a first coverage area of ​​a cell associated with the network node, non-LP C-WUS transmission is enabled in a second coverage area of ​​the cell associated with the network node, and the first coverage area is within and smaller than the second coverage area.

[0162] In one aspect, sending the LP-C-WUS in a LP-C-WUS opportunity in the one or more LP-C-WUS opportunities includes sending the LP-C-WUS in the LP-C-WUS opportunity in conjunction with the UE being within the first coverage area.

[0163] In one aspect, method 1100 further includes sending a non-LP C-WUS to the network node in conjunction with the UE being outside of the first coverage area and within the second coverage area.

[0164] In one aspect, method 1100 further comprises selecting whether to transmit the LP-C-WUS or the non-LP C-WUS based at least in part on at least one of a distance measurement, a path loss measurement, a CSI measurement, a channel metric, a mobility measurement, a position measurement, or a relative position of the UE with respect to a network node.

[0165] In one aspect, method 1100 further includes receiving an indication to configure LP-C-WUS transmission or non-LP C-WUS transmission for the UE, wherein the indication is based at least in part on one or more network measurements.

[0166] In one aspect, the UE supports LP-C-WUS transmission and non-LP C-WUS transmission, and method 1100 also includes selecting whether to send LP-C-WUS in one of one or more LP-C-WUS monitoring opportunities or to send non-LP C-WUS in a non-LP C-WUS monitoring opportunity based at least in part on one or more service characteristics of a service associated with the UE or at least one of an RRC mode of the UE.

[0167] In one aspect, the method 1100 further includes receiving a configuration of at least one of a first transmission parameter for an LP-C-WUS or a second transmission parameter for a non-LP C-WUS.

[0168] In one aspect, the cell DRX configuration indicates one or more LP-C-WUS monitoring opportunities in the cell DRX cycle and one or more non-LP C-WUS monitoring opportunities in the cell DRX cycle.

[0169] In one aspect, the one or more non-LP C-WUS monitoring opportunities in the cell DRX cycle include a first non-LP C-WUS monitoring opportunity and a second non-LP C-WUS monitoring opportunity, and the one or more non-LP C-WUS monitoring opportunities are between the first non-LP C-WUS monitoring opportunity and the second non-LP C-WUS monitoring opportunity.

[0170] In one aspect, the one or more LP-C-WUS monitoring opportunities include a first LP-C-WUS monitoring opportunity associated with a first type of LP-C-WUS and a second LP-C-WUS monitoring opportunity associated with a second type of LP-C-WUS.

[0171] In one aspect, the cell DRX configuration indicates a time gap between a first LP-C-WUS monitoring opportunity and a second LP-C-WUS monitoring opportunity.

[0172] In one aspect, the cell DRX configuration includes: a first cell DRX configuration of a first cell DRX cycle associated with an LP-WUR of the network node, the first cell DRX cycle including one or more LP-C-WUS monitoring opportunities; and a second cell DRX configuration of a second cell DRX cycle associated with a primary radio component of the network node, the second DRX cycle including one or more non-LPC-WUS monitoring opportunities.

[0173] In one aspect, the method 1100 further includes receiving an indication from the network node to enable LP-C-WUS transmission, wherein transmitting the LP-C-WUS is based at least in part on receiving the indication to enable LP-C-WUS transmission.

[0174] In one aspect, the method 1100 further includes receiving a request to send the LP-C-WUS from another UE, wherein sending the LP-C-WUS is based at least in part on receiving the request to send the LP-C-WUS.

[0175] In one aspect, the one or more LP-C-WUS monitoring opportunities include dedicated time resources configured for transmission of the LP-C-WUS, or a dedicated frequency band is configured for transmission of the LP-C-WUS.

[0176] In one aspect, the method 1100 further comprises sending one or more synchronization signals to the network node for synchronization of the LP-WUR of the network node, wherein the one or more synchronization signals comprise at least one of a periodic synchronization signal or a preamble symbol sent with the LP-C-WUS.

[0177] In one aspect, sending the LP-C-WUS includes sending the LP-C-WUS based at least in part on a QCL relationship between the LP-C-WUS and a non-LP C-WUS, a QCL relationship between the LP-C-WUS and an SSB, a QCL relationship between the LP-C-WUS and an SRS, a QCL relationship between the LP-C-WUS and another LP-C-WUS, or a QCL relationship between the LP-C-WUS and a synchronization signal for synchronization of an LP-WUR of a network node.

[0178] In one aspect, the payload of the LP-C-WUS indicates at least one of: a wake-up indication, a requested duration of the active time for the network node, a requested start time of the active time for the network node, an SSB request, an SIB1 request, an SSSG configuration index to be used for PDCCH monitoring, an energy request for wireless charging by the UE, an indication of the service to be sent by the UE, a priority or QoS of the service to be sent by the UE, a type of service to be sent by the UE, the capabilities of the UE, an uplink BSR, or a maximum size of a downlink BSR supported by the UE in a subsequent time period.

[0179] In one aspect, method 1100 or any aspect related thereto may be performed by an apparatus such as Figure 13 The method 1100 is performed by a communication device 1300 comprising various components operable, configured, or adapted to perform the method 1100. The communication device 1300 is described in more detail below.

[0180] Please note that Figure 11 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible in light of the present disclosure.

[0181] Figure 12 shows a method for use by a network node such as BS 110 or as described with respect to Figure 3 A method 1200 of performing wireless communications with a decomposed base station is discussed.

[0182] Method 1200 begins, at 1210, by sending an indication of network capabilities received for an LP-C-WUS.

[0183] The method 1200 then proceeds to step 1220 by receiving an indication of UE capabilities for LP-C-WUS transmission.

[0184] The method 1200 then proceeds to step 1230 to transmit a cell DRX configuration indicating one or more LP-C-WUS monitoring opportunities in the cell DRX cycle.

[0185] The method 1200 then proceeds to step 1240 to receive an LP-C-WUS in an LP-C-WUS opportunity in one of the one or more LP-C-WUS opportunities.

[0186] In one aspect, the indication of the network capabilities received for the LP-C-WUS is included in an SSB, SIB1, another SIB, an RRC message, a MAC-CE, or a DCI.

[0187] In one aspect, the indication of network capabilities for LP-C-WUS reception indicates whether the network node supports LP-C-WUS reception.

[0188] In one aspect, the indication of network capabilities received for the LP-C-WUS indicates one or more types of LP-C-WUS supported by the LP-WUR of the network node, and the LP-C-WUS is a type of LP-C-WUS from one or more types of LP-C-WUS supported by the LP-WUR of the network node.

[0189] In one aspect, the one or more types of LP-C-WUS supported by the LP-WUR of the network node include one or more of an OOK-based waveform, an FSK-based OFDM signal, a sequence-based signal, a DFT-based sequence, or a PDCCH-based signal.

[0190] In one aspect, the indication of network capabilities for LP-C-WUS reception indicates at least one of one or more frequency bands or one or more frequency ranges that support LP-C-WUS reception.

[0191] In one aspect, the indication of UE capability for LP-C-WUS transmission indicates whether the UE supports LP-C-WUS transmission.

[0192] In one aspect, the indication of UE capabilities for LP-C-WUS transmission indicates whether the UE supports transmission of one or more types of LP-C-WUS per frequency band, frequency band combination, frequency range, frequency range combination, component carrier, or component carrier combination.

[0193] In one aspect, the indication of UE capabilities sent for LP-C-WUS is included in a RACH message, a response to an indication of network capabilities received for LP-C-WUS, UAI, an RRC message, a MAC-CE, or UCI.

[0194] In one aspect, LP-C-WUS transmission is enabled for the UE in a full coverage area of ​​a cell associated with the network node, or LP-C-WUS transmission is enabled for the UE in a partial coverage area that is within and less than the full coverage area.

[0195] In one aspect, LP-C-WUS transmission is enabled in a first coverage area of ​​a cell associated with the network node, non-LP C-WUS transmission is enabled in a second coverage area of ​​the cell associated with the network node, and the first coverage area is within and smaller than the second coverage area.

[0196] In one aspect, receiving the LP-C-WUS in a LP-C-WUS opportunity in the one or more LP-C-WUS opportunities includes receiving the LP-C-WUS in the LP-C-WUS opportunity in conjunction with the UE being within the first coverage area.

[0197] In one aspect, the method 1200 further includes receiving a non-LP C-WUS to the network node in conjunction with the UE being outside of the first coverage area and within the second coverage area.

[0198] In one aspect, the method 1200 further includes transmitting an indication to configure the UE for LP-C-WUS transmission or non-LP C-WUS transmission, wherein the indication is based at least in part on one or more network measurements.

[0199] In one aspect, the method 1200 further includes transmitting configuration of at least one of a first transmission parameter for an LP-C-WUS or a second transmission parameter for a non-LP C-WUS.

[0200] In one aspect, the cell DRX configuration indicates one or more LP-C-WUS monitoring opportunities in the cell DRX cycle and one or more non-LP C-WUS monitoring opportunities in the cell DRX cycle.

[0201] In one aspect, the one or more non-LP C-WUS monitoring opportunities in the cell DRX cycle include a first non-LP C-WUS monitoring opportunity and a second non-LP C-WUS monitoring opportunity, and the one or more non-LP C-WUS monitoring opportunities are between the first non-LP C-WUS monitoring opportunity and the second non-LP C-WUS monitoring opportunity.

[0202] In one aspect, the one or more LP-C-WUS monitoring opportunities include a first LP-C-WUS monitoring opportunity associated with a first type of LP-C-WUS and a second LP-C-WUS monitoring opportunity associated with a second type of LP-C-WUS.

[0203] In one aspect, the cell DRX configuration indicates a time gap between a first LP-C-WUS monitoring opportunity and a second LP-C-WUS monitoring opportunity.

[0204] In one aspect, the cell DRX configuration includes: a first cell DRX configuration of a first cell DRX cycle associated with an LP-WUR of the network node, the first cell DRX cycle including one or more LP-C-WUS monitoring opportunities; and a second cell DRX configuration of a second cell DRX cycle associated with a primary radio component of the network node, the second DRX cycle including one or more non-LP C-WUS monitoring opportunities.

[0205] In one aspect, the method 1200 further includes sending an indication to enable LP-C-WUS transmission, wherein receiving the LP-C-WUS is based at least in part on sending the indication to enable LP-C-WUS transmission.

[0206] In one aspect, the one or more LP-C-WUS monitoring opportunities include dedicated time resources configured for LP-C-WUS, or a dedicated frequency band is configured for LP-C-WUS.

[0207] In one aspect, the method 1200 further includes receiving one or more synchronization signals for synchronization of the LP-WUR of the network node, wherein the one or more synchronization signals include at least one of a periodic synchronization signal or a preamble symbol sent with the LP-C-WUR.

[0208] In one aspect, sending the LP-C-WUS includes receiving the LP-C-WUS based at least in part on a QCL relationship between the LP-C-WUS and a non-LP C-WUS, a QCL relationship between the LP-C-WUS and an SSB, a QCL relationship between the LP-C-WUS and an SRS, a QCL relationship between the LP-C-WUS and another LP-C-WUS, or a QCL relationship between the LP-C-WUS and a synchronization signal for synchronization of an LP-WUS of a network node.

[0209] In one aspect, the payload of the LP-C-WUS indicates at least one of: a wake-up indication, a requested duration of the active time for the network node, a requested start time of the active time for the network node, an SSB request, an SIB1 request, an SSSG configuration index to be used for PDCCH monitoring, an energy request for wireless charging by the UE, an indication of the service to be sent by the UE, a priority or QoS of the service to be sent by the UE, a type of service to be sent by the UE, the capabilities of the UE, an uplink BSR, or a maximum size of a downlink BSR supported by the UE in a subsequent time period.

[0210] In one aspect, receiving the LP-C-WUS includes receiving the LP-C-WUS using the LP-WUR of the network node while the primary radio of the network node is in a sleep state, and method 1200 also includes switching the primary radio to an active state in conjunction with receiving the LP-C-WUS, and communicating with the UE using the primary radio while the primary radio is in the active state.

[0211] In one aspect, method 1200 or any aspect related thereto may be performed by an apparatus such as Figure 14 The method 1200 is performed by a communication device 1400 comprising various components operable, configured, or adapted to perform the method 1200. The communication device 1400 is described in more detail below.

[0212] Please note that Figure 12 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible in light of the present disclosure.

[0213] Figure 13 is a diagram illustrating an example of a specific implementation of codes and circuits for a communication device 1300 according to the present disclosure. The communication device 1300 may be a UE, or a UE may include the communication device 1300.

[0214] The communication device 1300 includes a processing system 1302 coupled to a transceiver 1308 (e.g., a transmitter and / or receiver). The transceiver 1308 is configured to transmit and receive signals for the communication device 1300, such as the various signals described herein, via an antenna 1310. The processing system 1302 may be configured to perform processing functions for the communication device 1300, including processing signals received by the communication device 1300 and / or to be transmitted by the communication device.

[0215] The processing system 1302 includes one or more processors 1320. In various aspects, the one or more processors 1320 may represent one or more of the receive processor 258, the transmit processor 264, the TX MIMO processor 266, and / or the controller / processor 280, as described with respect to FIG. Figure 2 One or more processors 1320 are coupled to a computer readable medium / memory 1330 via bus 1306. In various aspects, computer readable medium / memory 1330 may represent memory 282, as described with respect to FIG. Figure 2 In some aspects, the computer-readable medium / memory 1330 is configured to store instructions (e.g., computer-executable code, processor-executable code) that, when executed by the one or more processors 1320, cause the one or more processors 1320 to perform operations related to Figure 11 The method 1100 or any aspect related thereto is described. Note that reference to a processor performing a function of the communication device 1300 may include one or more processors performing that function of the communication device 1300.

[0216] like Figure 13 As shown, the communications device 1300 may include circuitry for receiving an indication of network capabilities for LP-C-WUS reception from a network node (circuitry 1335 ).

[0217] like Figure 13 As shown, communications device 1300 may include code (code 1340) stored in computer-readable medium / memory 1330 for receiving, from a network node, an indication of network capabilities for LP-C-WUS reception.

[0218] like Figure 13 As shown, the communications device 1300 may include circuitry for sending an indication of UE capabilities for LP-C-WUS transmission to a network node (circuitry 1345).

[0219] like Figure 13 As shown, communications device 1300 may include code (code 1350) stored in computer-readable medium / memory 1330 for sending an indication of UE capabilities for LP-C-WUS transmission to a network node.

[0220] like Figure 13 As shown, the communications device 1300 may include circuitry (circuitry 1355 ) for receiving a cell DRX configuration from a network node indicating one or more LP-C-WUS monitoring opportunities in a cell DRX cycle.

[0221] like Figure 13As shown, communications device 1300 may include code (code 1360 ) stored in computer-readable medium / memory 1330 for receiving, from a network node, a cell DRX configuration indicating one or more LP-C-WUS monitoring opportunities in a cell DRX cycle.

[0222] like Figure 13 As shown, the communications device 1300 may include circuitry (circuitry 1365) for sending an LP-C-WUS to a network node in an LP-C-WUS opportunity in one or more LP-C-WUS opportunities.

[0223] like Figure 13 As shown, the communication device 1300 may include code (code 1370) stored in the computer-readable medium / memory 1330 for sending an LP-C-WUS to a network node in an LP-C-WUS opportunity in one or more LP-C-WUS opportunities.

[0224] The various components of the communication device 1300 may provide for performing Figure 11 Means for transmitting, conveying, or outputting for transmission may include the transceiver 254 and / or antenna 252 of the UE 120, and / or Figure 13 The transceiver 1308 and antenna 1310 of the communication device 1300 in FIG. The means for receiving or obtaining may include the transceiver 254 and / or antenna 252 of the UE 120, and / or Figure 13 The transceiver 1308 and antenna 1310 of the communication device 1300 in FIG.

[0225] Figure 13 is provided as an example. Other examples can be combined with Figure 13 The examples described are different.

[0226] Figure 14 1 is a diagram illustrating an example of a specific implementation of codes and circuits for a communication device 1400 according to the present disclosure. The communication device 1400 may be a network node (such as BS 110 or a network node related to Figure 3 The described decomposed base station), or a network node may include the communication device 1400.

[0227] The communication device 1400 includes a processing system 1402 coupled to a transceiver 1408 (e.g., a transmitter and / or receiver). The transceiver 1408 is configured to transmit and receive signals for the communication device 1400, such as the various signals described herein, via an antenna 1410. The network interface 1412 is configured to communicate with the communication device 1400 via a communication link (such as those described herein). Figure 3The processing system 1402 may be configured to perform processing functions for the communication device 1400, including processing signals received by the communication device 1400 and / or to be transmitted by the communication device 1400.

[0228] The processing system 1402 includes one or more processors 1420. In various aspects, the one or more processors 1420 may represent one or more of the receive processor 238, the transmit processor 220, the TX MIMO processor 230, and / or the controller / processor 240, as described with respect to FIG. Figure 2 One or more processors 1420 are coupled to a computer readable medium / memory 1430 via bus 1406. In various aspects, computer readable medium / memory 1430 may represent memory 242, as described with respect to FIG. Figure 2 In some aspects, the computer-readable medium / memory 1430 is configured to store instructions (e.g., computer-executable code, processor-executable code) that, when executed by the one or more processors 1420, cause the one or more processors 1420 to perform operations related to Figure 12 The method 1200 or any aspect related thereto is described. Note that reference to a processor performing a function of the communication device 1400 may include one or more processors performing that function of the communication device 1400.

[0229] like Figure 14 As shown, the communications device 1400 may include circuitry for sending an indication of network capabilities received for the LP-C-WUS (circuitry 1435 ).

[0230] like Figure 14 As shown, the communication device 1400 may include code (code 1440) stored in the computer-readable medium / memory 1430 for transmitting an indication of network capabilities received for the LP-C-WUS.

[0231] like Figure 14 As shown, the communications device 1400 may include circuitry for receiving an indication of UE capabilities transmitted for LP-C-WUS (circuitry 1445 ).

[0232] like Figure 14 As shown, communications device 1400 may include code (code 1450) stored in computer-readable medium / memory 1430 for receiving an indication of UE capabilities transmitted for LP-C-WUS.

[0233] like Figure 14As shown, the communications device 1400 may include circuitry (circuitry 1455 ) for transmitting a cell DRX configuration indicating one or more LP-C-WUS monitoring opportunities in a cell DRX cycle.

[0234] like Figure 14 As shown, the communications device 1400 may include code (code 1460 ) stored in the computer-readable medium / memory 1430 for transmitting a cell DRX configuration indicating one or more LP-C-WUS monitoring opportunities in a cell DRX cycle.

[0235] like Figure 14 As shown, the communication device 1400 may include circuitry (circuitry 1465) for receiving an LP-C-WUS in an LP-C-WUS opportunity in one or more LP-C-WUS opportunities.

[0236] like Figure 14 As shown, the communication device 1400 may include code (code 1470) stored in the computer-readable medium / memory 1430 for receiving an LP-C-WUS in an LP-C-WUS opportunity in one or more LP-C-WUS opportunities.

[0237] The various components of the communication device 1400 may provide for performing Figure 12 Components of the described method 1200 or any aspect thereof. For example, components for sending, transmitting, or outputting for transmission may include the transceiver 232 and / or antenna 234 of the BS 110, and / or Figure 14 The transceiver 1408 and antenna 1410 of the communication device 1400 in the embodiment of the present invention may be used to receive or obtain the transceiver 232 and / or antenna 234 of the BS 110, and / or Figure 14 The transceiver 1408 and antenna 1410 of the communication device 1400 are shown in FIG.

[0238] Figure 14 is provided as an example. Other examples can be combined with Figure 14 The examples described are different.

[0239] The following provides an overview of some aspects of the disclosure:

[0240] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving an indication of network capabilities for low power cell wake-up signal (LP-C-WUS) reception from a network node; sending an indication of UE capabilities for LP-C-WUS transmission to the network node; receiving a cell discontinuous reception (DRX) configuration indicating one or more LP-C-WUS monitoring opportunities in a cell DRX cycle from the network node; and sending an LP-C-WUS to the network node in an LP-C-WUS opportunity among the one or more LP-C-WUS opportunities.

[0241] Aspect 2: The method of aspect 1, wherein the indication of the network capabilities received for the LP-C-WUS is included in a synchronization signal block (SSB), a system information block (SIB) type 1 (SIB1), another SIB, a radio resource control (RRC) message, a medium access control (MAC) control element (MAC-CE), or downlink control information (DCI).

[0242] Aspect 3: The method according to any one of aspects 1 to 2, wherein the indication of the network capability for LP-C-WUS reception indicates whether the network node supports LP-C-WUS reception.

[0243] Aspect 4: A method according to any one of Aspects 1 to 3, wherein the indication of the network capability received for LP-C-WUS indicates one or more types of LP-C-WUS supported by a low power wake-up radio component (LP-WUR) of the network node, and wherein the LP-C-WUS is a type of LP-C-WUS of the one or more types of LP-C-WUS supported by the LP-WUR from the network node.

[0244] Aspect 5: A method according to aspect 4, wherein the one or more types of LP-C-WUS supported by the LP-WUR of the network node include one or more of the following: a waveform based on on-off keying (OOK), an orthogonal frequency division multiplexing (OFDM) signal based on frequency shift keying (FSK), a sequence-based signal, a discrete Fourier transform (DFT)-based sequence, or a physical downlink control channel (PDCCH)-based signal.

[0245] Aspect 6: The method according to any one of aspects 1 to 5, wherein the indication of the network capability for LP-C-WUS reception indicates at least one of one or more frequency bands or one or more frequency ranges supporting LP-C-WUS reception.

[0246] Aspect 7: The method according to any one of aspects 1 to 6, wherein the indication of the UE capability for LP-C-WUS transmission indicates whether the UE supports LP-C-WUS transmission.

[0247] Aspect 8: A method according to any one of Aspects 1 to 7, wherein the indication of the UE capability for LP-C-WUS transmission indicates whether the UE supports the transmission of one or more types of LP-C-WUS per frequency band, frequency band combination, frequency range, frequency range combination, component carrier or component carrier combination.

[0248] Aspect 9: A method according to any one of aspects 1 to 8, wherein the indication of the UE capabilities sent for LP-C-WUS is included in a random access channel (RACH) message, a response to the indication of the network capabilities received for LP-C-WUS, UE assistance information (UAI), a radio resource control (RRC) message, a medium access control (MAC) control element (MAC-CE) or uplink control information (UCI).

[0249] Aspect 10: A method according to any one of Aspects 1 to 9, wherein LP-C-WUS transmission is enabled for the UE in a full coverage area of ​​a cell associated with the network node, or LP-C-WUS transmission is enabled for the UE in a partial coverage area located within the full coverage area and smaller than the full coverage area.

[0250] Aspect 11: A method according to aspect 10, wherein sending the LP-C-WUS in the LP-C-WUS opportunity in one or more LP-C-WUS opportunities includes: enabling the use of a first set of transmission parameters in the full coverage area in combination with the LP-C-WUS sending or enabling the use of a second set of transmission parameters in the partial coverage area in combination with the LP-C-WUS sending.

[0251] Aspect 12: A method according to any one of Aspects 1 to 11, wherein LP-C-WUS transmission is enabled in a first coverage area of ​​a cell associated with the network node, wherein non-low power (non-LP) cell wake-up signal (C-WUS) transmission is enabled in a second coverage area of ​​the cell associated with the network node, and wherein the first coverage area is within the second coverage area and is smaller than the second coverage area.

[0252] Aspect 13: The method according to aspect 12, wherein sending the LP-C-WUS in the LP-C-WUS opportunity in the one or more LP-C-WUS opportunities includes sending the LP-C-WUS in the LP-C-WUS opportunity in combination with the UE being within the first coverage area.

[0253] Aspect 14: The method according to aspect 12, further comprising: sending a non-LP C-WUS to the network node in conjunction with the UE being outside the first coverage area and within the second coverage area.

[0254] Aspect 15: The method according to aspect 12 further includes: selecting whether to send the LP-C-WUS or the non-LP C-WUS based at least in part on at least one of a distance measurement, a path loss measurement, a channel state information (CSI) measurement, a channel metric, a mobility measurement, a position measurement, or a relative position of the UE with respect to the network node.

[0255] Aspect 16: The method according to aspect 12, further comprising: receiving an indication to configure LP-C-WUS transmission or non-LP C-WUS transmission for the UE, wherein the indication is based at least in part on one or more network measurements.

[0256] Aspect 17: A method according to any one of Aspects 1 to 16, wherein the UE supports LP-C-WUS transmission and non-low power (non-LP) cell wake-up signal (C-WUS) transmission, and wherein the method further comprises: selecting whether to send the LP-C-WUS in one of the one or more LP-C-WUS monitoring opportunities or to send a non-LP C-WUS in a non-LP C-WUS monitoring opportunity based at least in part on one or more service characteristics of a service associated with the UE or at least one of a radio resource control (RRC) mode of the UE.

[0257] Aspect 18: The method according to aspect 17, further comprising: receiving configuration of at least one of a first transmission parameter for the LP-C-WUS or a second transmission parameter for the non-LP C-WUS.

[0258] Aspect 19: A method according to any one of Aspects 1 to 18, wherein the cell DRX configuration indicates the one or more LP-C-WUS monitoring opportunities in the cell DRX cycle and one or more non-low power (non-LP) cell wake-up signal (C-WUS) monitoring opportunities in the cell DRX cycle.

[0259] Aspect 20: A method according to Aspect 19, wherein the one or more non-LPC-WUS monitoring opportunities in the cell DRX cycle include a first non-LP C-WUS monitoring opportunity and a second non-LP C-WUS monitoring opportunity, and wherein the one or more LP C-WUS monitoring opportunities are between the first non-LP C-WUS monitoring opportunity and the second non-LP C-WUS monitoring opportunity.

[0260] Aspect 21: A method according to any one of Aspects 1 to 20, wherein the one or more LP-C-WUS monitoring opportunities include a first LP-C-WUS monitoring opportunity associated with a first type of LP-C-WUS and a second LP-C-WUS monitoring opportunity associated with a second type of LP-C-WUS.

[0261] Aspect 22: The method according to aspect 21, wherein the cell DRX configuration indicates a time gap between the first LP-C-WUS monitoring opportunity and the second LP-C-WUS monitoring opportunity.

[0262] Aspect 23: A method according to any one of Aspects 1 to 22, wherein the cell DRX configuration includes: a first cell DRX configuration of a first cell DRX cycle associated with a low power wake-up radio component (LP-WUR) of the network node, the first cell DRX cycle including the one or more LP-C-WUS monitoring opportunities; and a second cell DRX configuration of a second cell DRX cycle associated with a main radio component of the network node, the second DRX cycle including one or more non-low power (non-LP) cell wake-up signal (C-WUS) monitoring opportunities.

[0263] Aspect 24: The method according to any one of aspects 1 to 23, further comprising: receiving an indication from the network node to enable LP-C-WUS transmission, wherein sending the LP-C-WUS is at least partially based on receiving the indication to enable LP-C-WUS transmission.

[0264] Aspect 25: The method according to any one of aspects 1 to 24, further comprising: receiving a request to send the LP-C-WUS from another UE, wherein sending the LP-C-WUS is at least partially based on receiving the request to send the LP-C-WUS.

[0265] Aspect 26: The method according to any one of aspects 1 to 25, wherein the one or more LP-C-WUS monitoring opportunities include dedicated time resources configured for transmission of the LP-C-WUS, or a dedicated frequency band is configured for transmission of the LP-C-WUS.

[0266] Aspect 27: According to the method described in any one of Aspects 1 to 26, the method further includes: sending one or more synchronization signals for synchronization of a low power wake-up radio component (LP-WUR) of the network node to the network node, wherein the one or more synchronization signals include a periodic synchronization signal or at least one of the preamble symbols sent together with the LP-C-WUS.

[0267] Aspect 28: A method according to any one of Aspects 1 to 27, wherein sending the LP-C-WUS includes: sending the LP-C-WUS based at least in part on a quasi-co-location (QCL) relationship between the LP-C-WUS and a non-low-power (non-LP) cell wake-up signal (C-WUS), a QCL relationship between the LP-C-WUS and a synchronization signal block (SSB), a QCL relationship between the LP-C-WUS and a sounding reference signal (SRS), a QCL relationship between the LP-C-WUS and another LP-C-WUS, or a QCL relationship between the LP-C-WUS and a synchronization signal for synchronization of a low-power wake-up radio component (LP-WUR) of the network node.

[0268] Aspect 29: A method according to any one of Aspects 1 to 28, wherein the payload of the LP-C-WUS indicates at least one of the following: a wake-up indication, a requested duration of the active time for the network node, a requested start time of the active time for the network node, a synchronization signal block (SSB) request, a system information block (SIB) type 1 (SIB1) request, a search space set group (SSSG) configuration index to be used for physical downlink control channel (PDCCH) monitoring, an energy request for wireless charging of the UE, an indication of the service to be sent by the UE, the priority or quality of service (QoS) of the service to be sent by the UE, the type of the service to be sent by the UE, the capability of the UE, an uplink buffer status report (BSR), or the maximum size of a downlink BSR supported by the UE in a subsequent time period.

[0269] Aspect 30: A method of wireless communication performed by a network node, the method comprising: sending an indication of network capabilities for low power cell wake-up signal (LP-C-WUS) reception; receiving an indication of user equipment (UE) capabilities for LP-C-WUS transmission; sending a cell discontinuous reception (DRX) configuration indicating one or more LP-C-WUS monitoring opportunities in a cell DRX cycle; and receiving an LP-C-WUS in an LP-C-WUS opportunity among the one or more LP-C-WUS opportunities.

[0270] Aspect 31: A method according to aspect 30, wherein the indication of the network capabilities received for LP-C-WUS is included in a synchronization signal block (SSB), a system information block (SIB) type 1 (SIB1), another SIB, a radio resource control (RRC) message, a medium access control (MAC) control element (MAC-CE) or downlink control information (DCI).

[0271] Aspect 32: The method according to any one of aspects 30 to 31, wherein the indication of the network capability for LP-C-WUS reception indicates whether the network node supports LP-C-WUS reception.

[0272] Aspect 33: A method according to any one of Aspects 30 to 32, wherein the indication of the network capability received for LP-C-WUS indicates one or more types of LP-C-WUS supported by a low power wake-up radio component (LP-WUR) of the network node, and wherein the LP-C-WUS is a type of LP-C-WUS of the one or more types of LP-C-WUS supported by the LP-WUR from the network node.

[0273] Aspect 34: A method according to Aspect 33, wherein the one or more types of LP-C-WUS supported by the LP-WUR of the network node include one or more of the following: a waveform based on on-off keying (OOK), an orthogonal frequency division multiplexing (OFDM) signal based on frequency shift keying (FSK), a sequence-based signal, a discrete Fourier transform (DFT)-based sequence, or a physical downlink control channel (PDCCH)-based signal.

[0274] Aspect 35: The method according to any one of aspects 30 to 34, wherein the indication of the network capabilities for LP-C-WUS reception indicates at least one of one or more frequency bands or one or more frequency ranges that support LP-C-WUS reception.

[0275] Aspect 36: The method according to any one of aspects 30 to 35, wherein the indication of the UE capability for LP-C-WUS transmission indicates whether the UE supports LP-C-WUS transmission.

[0276] Aspect 37: A method according to any one of Aspects 30 to 36, wherein the indication of the UE capability for LP-C-WUS transmission indicates whether the UE supports the transmission of one or more types of LP-C-WUS per frequency band, frequency band combination, frequency range, frequency range combination, component carrier or component carrier combination.

[0277] Aspect 38: A method according to any one of aspects 30 to 37, wherein the indication of the UE capabilities sent for LP-C-WUS is included in a random access channel (RACH) message, a response to the indication of the network capabilities received for LP-C-WUS, UE assistance information (UAI), a radio resource control (RRC) message, a medium access control (MAC) control element (MAC-CE), or uplink control information (UCI).

[0278] Aspect 39: A method according to any one of Aspects 30 to 38, wherein LP-C-WUS transmission is enabled for the UE in a full coverage area of ​​a cell associated with the network node, or LP-C-WUS transmission is enabled for the UE in a partial coverage area located within the full coverage area and smaller than the full coverage area.

[0279] Aspect 40: A method according to any one of Aspects 30 to 39, wherein LP-C-WUS transmission is enabled in a first coverage area of ​​a cell associated with the network node, wherein non-low power (non-LP) cell wake-up signal (C-WUS) transmission is enabled in a second coverage area of ​​the cell associated with the network node, and wherein the first coverage area is within the second coverage area and is smaller than the second coverage area.

[0280] Aspect 41: The method of aspect 40, wherein receiving the LP-C-WUS in the LP-C-WUS opportunity in the one or more LP-C-WUS opportunities comprises receiving the LP-C-WUS in the LP-C-WUS opportunity in conjunction with the UE being within the first coverage area.

[0281] Aspect 42: The method of aspect 40, further comprising: receiving a non-LP C-WUS from a network node in conjunction with the UE being outside the first coverage area and within the second coverage area.

[0282] Aspect 43: The method according to aspect 40 further comprising: sending an indication to configure LP-C-WUS transmission or non-LP C-WUS transmission for the UE, wherein the indication is based at least in part on one or more network measurements.

[0283] Aspect 44: According to any one of aspects 30 to 43, the method further includes: receiving a configuration of at least one of a first transmission parameter for the LP-C-WUS or a second transmission parameter for a non-low power (non-LP) cell wake-up signal (C-WUS).

[0284] Aspect 45: A method according to any one of Aspects 30 to 44, wherein the cell DRX configuration indicates the one or more LP-C-WUS monitoring opportunities in the cell DRX cycle and one or more non-low power (non-LP) cell wake-up signal (C-WUS) monitoring opportunities in the cell DRX cycle.

[0285] Aspect 46: A method according to Aspect 45, wherein the one or more non-LPC-WUS monitoring opportunities in the cell DRX cycle include a first non-LP C-WUS monitoring opportunity and a second non-LP C-WUS monitoring opportunity, and wherein the one or more LP C-WUS monitoring opportunities are between the first non-LP C-WUS monitoring opportunity and the second non-LP C-WUS monitoring opportunity.

[0286] Aspect 47: A method according to any one of Aspects 30 to 46, wherein the one or more LP-C-WUS monitoring opportunities include a first LP-C-WUS monitoring opportunity associated with a first type of LP-C-WUS and a second LP-C-WUS monitoring opportunity associated with a second type of LP-C-WUS.

[0287] Aspect 48: The method according to aspect 47, wherein the cell DRX configuration indicates a time gap between the first LP-C-WUS monitoring opportunity and the second LP-C-WUS monitoring opportunity.

[0288] Aspect 49: A method according to any one of Aspects 30 to 48, wherein the cell DRX configuration includes: a first cell DRX configuration of a first cell DRX cycle associated with a low power wake-up radio component (LP-WUR) of the network node, the first cell DRX cycle including the one or more LP-C-WUS monitoring opportunities; and a second cell DRX configuration of a second cell DRX cycle associated with a main radio component of the network node, the second DRX cycle including one or more non-low power (non-LP) cell wake-up signal (C-WUS) monitoring opportunities.

[0289] Aspect 50: The method according to any one of aspects 30 to 49, further comprising: sending an indication to enable LP-C-WUS transmission, wherein receiving the LP-C-WUS is based at least in part on sending the indication to enable LP-C-WUS transmission.

[0290] Aspect 51: The method according to any one of aspects 30 to 50, wherein the one or more LP-C-WUS monitoring opportunities include dedicated time resources configured for the LP-C-WUS, or a dedicated frequency band configured for the LP-C-WUS.

[0291] Aspect 52: According to the method described in any one of Aspects 30 to 51, the method further includes: receiving one or more synchronization signals for synchronization of a low power wake-up radio component (LP-WUR) of the network node, wherein the one or more synchronization signals include a periodic synchronization signal or at least one of the preamble symbols sent together with the LP-C-WUS.

[0292] Aspect 53: A method according to any one of Aspects 30 to 52, wherein sending the LP-C-WUS includes: receiving the LP-C-WUS based at least in part on a quasi-co-location (QCL) relationship between the LP-C-WUS and a non-low-power (non-LP) cell wake-up signal (C-WUS), a QCL relationship between the LP-C-WUS and a synchronization signal block (SSB), a QCL relationship between the LP-C-WUS and a sounding reference signal (SRS), a QCL relationship between the LP-C-WUS and another LP-C-WUS, or a QCL relationship between the LP-C-WUS and a synchronization signal for synchronization of a low-power wake-up radio component (LP-WUR) of the network node.

[0293] Aspect 54: A method according to any one of Aspects 30 to 53, wherein the payload of the LP-C-WUS indicates at least one of the following: a wake-up indication, a requested duration of the active time for the network node, a requested start time of the active time for the network node, a synchronization signal block (SSB) request, a system information block (SIB) type 1 (SIB1) request, a search space set group (SSSG) configuration index to be used for physical downlink control channel (PDCCH) monitoring, an energy request for wireless charging of the UE, an indication of the service to be sent by the UE, the priority or quality of service (QoS) of the service to be sent by the UE, the type of the service to be sent by the UE, the capability of the UE, an uplink buffer status report (BSR), or the maximum size of a downlink BSR supported by the UE in a subsequent time period.

[0294] Aspect 55: A method according to any one of Aspects 30 to 54, wherein receiving the LP-C-WUS includes using a low power wake-up radio component (LP-WUR) of the network node to receive the LP-C-WUS when the main radio component of the network node is in a sleep state, and wherein the method further includes: switching the main radio component to an active state in conjunction with receiving the LP-C-WUS; and using the main radio component to communicate with the UE when the main radio component is in the active state.

[0295] Aspect 56: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 55.

[0296] Aspect 57: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 55.

[0297] Aspect 58: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 55.

[0298] Aspect 59: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 55.

[0299] Aspect 60: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 55.

[0300] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the various aspects.

[0301] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of different forms of hardware and / or hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, no reference is made herein to specific software code to describe the operation and behavior of the systems and / or methods, as those skilled in the art will appreciate that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.

[0302] As used herein, "satisfying a threshold" may mean that a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0303] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner not specifically described in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b, or c" is intended to encompass a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination of multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other arrangement of a, b, and c).

[0304] Any element, action or instruction used herein should not be interpreted as key or necessary, unless explicitly described as such. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more projects and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more projects connected with the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "group" and "cluster" are intended to include one or more projects and can be used interchangeably with "one or more". If only want to refer to a project, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to represent "at least partially based on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

[0305] 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 functions and arrangements of the elements discussed may be changed without departing from the scope of this disclosure. Various examples may omit, replace, or add various processes or components as appropriate. For example, the methods described may be performed in an order different from that described, and various actions may be added, omitted, or combined. In addition, the features described with respect to some examples may be combined in some other examples. For example, a device or method of practice may be implemented using any number of the aspects set forth herein. In addition, the scope of this disclosure is intended to cover such devices or methods practiced using other structures, functionalities, or structures and functionalities that supplement or replace the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present claims.

[0306] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. Although a general purpose processor may be a microprocessor, in an alternative embodiment, 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 (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration).

[0307] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or another data structure), ascertaining, etc. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. Furthermore, "determining" may include resolving, selecting, choosing, establishing, etc.

[0308] The method disclosed herein includes one or more actions for implementing the method. Method actions can be interchangeable with each other without departing from the scope of the claims. In other words, unless a specified order of actions is specified, the order and / or use of specific actions can be modified without departing from the scope of the claims. In addition, the various operations of the method described above can be performed by any appropriate component that can perform the corresponding function. These components may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs) or processors.

[0309] 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. Within the claims, unless specifically stated otherwise, reference to an element in the singular is not intended to mean "one and only one", but "one or more". Unless otherwise specifically stated, the term "some" refers to one or more. No claim element is to be interpreted under the provisions of 35 U.SC § 112 (f) unless the element is explicitly stated using the phrase "parts for...". All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or will later be known to one of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims.

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: receiving, from a network node, an indication of network capability for low power cell wake-up signal (LP-C-WUS) reception; sending an indication of UE capabilities sent for LP-C-WUS to the network node; receiving, from the network node, a cell discontinuous reception (DRX) configuration indicating one or more LP-C-WUS monitoring opportunities in a cell DRX cycle; and An LP-C-WUS is sent to the network node in an LP-C-WUS opportunity of the one or more LP-C-WUS opportunities.

2. The UE of claim 1 , wherein the indication of the network capabilities received for LP-C-WUS is included in a synchronization signal block (SSB), a system information block (SIB) type 1 (SIB1), another SIB, a radio resource control (RRC) message, a medium access control (MAC) control element (MAC-CE), or downlink control information (DCI). 3 . The UE of claim 1 , wherein the indication of the network capability for LP-C-WUS reception indicates whether the network node supports LP-C-WUS reception.

4. The UE of claim 1 , wherein the indication of the network capabilities received for LP-C-WUS indicates one or more types of LP-C-WUS supported by a low power wake-up radio (LP-WUR) of the network node, and wherein the LP-C-WUS is a type of LP-C-WUS of the one or more types of LP-C-WUS supported by the LP-WUR from the network node.

5. The UE according to claim 4, wherein the one or more types of LP-C-WUS supported by the LP-WUR of the network node include one or more of the following: Based on On-Off Keying (OOK) waveform, Orthogonal frequency division multiplexing (OFDM) signal based on frequency shift keying (FSK), Sequence-based signals, a sequence based on the Discrete Fourier Transform (DFT), or Signaling based on the Physical Downlink Control Channel (PDCCH). 6 . The UE of claim 1 , wherein the indication of the network capability for LP-C-WUS reception indicates at least one of one or more frequency bands or one or more frequency ranges supporting LP-C-WUS reception. 7 . The UE of claim 1 , wherein the indication of the UE capability for LP-C-WUS transmission indicates whether the UE supports LP-C-WUS transmission.

8. The UE of claim 1 , wherein the indication of the UE capability for LP-C-WUS transmission indicates whether the UE supports transmission of one or more types of LP-C-WUS per frequency band, frequency band combination, frequency range, frequency range combination, component carrier, or component carrier combination.

9. The UE of claim 1 , wherein the indication of the UE capabilities sent for LP-C-WUS is included in a random access channel (RACH) message, a response to the indication of the network capabilities received for LP-C-WUS, UE assistance information (UAI), a radio resource control (RRC) message, a medium access control (MAC) control element (MAC-CE), or uplink control information (UCI).

10. The UE of claim 1 , wherein LP-C-WUS transmission is enabled for the UE in a full coverage area of ​​a cell associated with the network node, or LP-C-WUS transmission is enabled for the UE in a partial coverage area that is within the full coverage area and is smaller than the full coverage area.

11. The UE of claim 10 , wherein to transmit the LP-C-WUS in the LP-C-WUS opportunity among the one or more LP-C-WUS opportunities, the one or more processors are configured to: Transmission of the LP-C-WUS is enabled in the full coverage area using a first set of transmission parameters in conjunction with transmission of the LP-C-WUS or in the partial coverage area using a second set of transmission parameters in conjunction with transmission of the LP-C-WUS.

12. The UE of claim 1 , wherein LP-C-WUS transmission is enabled in a first coverage area of ​​a cell associated with the network node, wherein non-low power (non-LP) cell wake-up signal (C-WUS) transmission is enabled in a second coverage area of ​​the cell associated with the network node, and wherein the first coverage area is within the second coverage area and is smaller than the second coverage area.

13. The UE of claim 12 , wherein to transmit the LP-C-WUS in the LP-C-WUS opportunity among the one or more LP-C-WUS opportunities, the one or more processors are configured to: The LP-C-WUS is sent in the LP-C-WUS opportunity in conjunction with the UE being located in the first coverage area.

14. The UE of claim 12, wherein the one or more processors are further configured to: In conjunction with the UE being outside the first coverage area and within the second coverage area, a non-LP C-WUS is sent to the network node.

15. The UE of claim 12, wherein the one or more processors are further configured to: Whether to transmit the LP-C-WUS or a non-LP C-WUS is selected based at least in part on at least one of a distance measurement, a path loss measurement, a channel state information (CSI) measurement, a channel metric, a mobility measurement, a position measurement, or a relative position of the UE with respect to the network node.

16. The UE of claim 12, wherein the one or more processors are further configured to: An indication is received to configure LP-C-WUS transmission or non-LP C-WUS transmission for the UE, wherein the indication is based at least in part on one or more network measurements.

17. The UE of claim 1 , wherein the UE supports LP-C-WUS transmission and non-low power (non-LP) cell wake-up signal (C-WUS) transmission, and wherein the one or more processors are further configured to: Whether to send the LP-C-WUS in one of the one or more LP-C-WUS monitoring opportunities or to send a non-LP C-WUS in a non-LP C-WUS monitoring opportunity is selected based at least in part on one or more traffic characteristics of a traffic associated with the UE or at least one of a radio resource control (RRC) mode of the UE.

18. The UE of claim 17, wherein the one or more processors are further configured to: A configuration of at least one of a first transmission parameter for the LP-C-WUS or a second transmission parameter for the non-LP C-WUS is received.

19. The UE of claim 1, wherein the cell DRX configuration indicates the one or more LP-C-WUS monitoring opportunities in the cell DRX cycle and one or more non-low power (non-LP) cell wake-up signal (C-WUS) monitoring opportunities in the cell DRX cycle.

20. The UE according to claim 19, wherein the one or more non-LP C-WUS monitoring opportunities in the cell DRX cycle include a first non-LP C-WUS monitoring opportunity and a second non-LP C-WUS monitoring opportunity, and wherein the one or more LP C-WUS monitoring opportunities are between the first non-LP C-WUS monitoring opportunity and the second non-LP C-WUS monitoring opportunity.

21. The UE of claim 1, wherein the one or more LP-C-WUS monitoring opportunities include a first LP-C-WUS monitoring opportunity associated with a first type of LP-C-WUS and a second LP-C-WUS monitoring opportunity associated with a second type of LP-C-WUS.

22. The UE according to claim 21, wherein the cell DRX configuration indicates a time gap between the first LP-C-WUS monitoring opportunity and the second LP-C-WUS monitoring opportunity.

23. The UE according to claim 1, wherein the cell DRX configuration comprises: a first cell DRX configuration of a first cell DRX cycle associated with a low power wake-up radio (LP-WUR) of the network node, the first cell DRX cycle comprising the one or more LP-C-WUS monitoring opportunities, and A second cell DRX configuration of a second cell DRX cycle associated with a primary radio component of the network node, the second DRX cycle comprising one or more non-low power (non-LP) cell wake-up signal (C-WUS) monitoring opportunities.

24. The UE of claim 1 , wherein the one or more processors are further configured to: An indication to enable LP-C-WUS transmission is received from the network node, wherein transmitting the LP-C-WUS is based at least in part on receiving the indication to enable LP-C-WUS transmission.

25. The UE of claim 1 , wherein the one or more processors are further configured to: One or more synchronization signals for synchronization of a low power wake-up radio (LP-WUR) of the network node are sent to the network node, wherein the one or more synchronization signals include at least one of a periodic synchronization signal or a preamble symbol sent with the LP-C-WUR.

26. The UE according to claim 1, wherein a payload of the LP-C-WUS indicates at least one of the following: Wake-up instructions, the requested duration of activity time for the network node, a requested start time for said activity time of said network node, Synchronization Signal Block (SSB) request, System Information Block (SIB) Type 1 (SIB1) request, Search Space Set Group (SSSG) configuration index to be used for Physical Downlink Control Channel (PDCCH) monitoring, The UE performs an energy request for wireless charging, an indication of the service to be sent by the UE, the priority or quality of service (QoS) of the service to be sent by the UE, The type of the service to be sent by the UE, the capabilities of the UE, Uplink Buffer Status Report (BSR), or The maximum size of a downlink BSR supported by the UE in a subsequent time period.

27. A network node for wireless communication, the network node comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: sending an indication of network capability for low power cell wake-up signal (LP-C-WUS) reception; receiving an indication of user equipment (UE) capabilities sent for LP-C-WUS; transmitting a cell discontinuous reception (DRX) configuration indicating one or more LP-C-WUS monitoring opportunities in a cell DRX cycle; and An LP-C-WUS is received in an LP-C-WUS opportunity of the one or more LP-C-WUS opportunities.

28. The network node of claim 27 , wherein receiving the LP-C-WUS comprises receiving the LP-C-WUS using a low power wake-up radio (LP-WUR) of the network node while a main radio of the network node is in a sleep state, and wherein the one or more processors are further configured to: switching the primary radio component to an active state in conjunction with receiving the LP-C-WUS; and Communicating with the UE using the primary radio component while the primary radio component is in the active state.

29. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving, from a network node, an indication of network capability for low power cell wake-up signal (LP-C-WUS) reception; sending an indication of UE capabilities sent for LP-C-WUS to the network node; receiving, from the network node, a cell discontinuous reception (DRX) configuration indicating one or more LP-C-WUS monitoring opportunities in a cell DRX cycle; and An LP-C-WUS is sent to the network node in an LP-C-WUS opportunity of the one or more LP-C-WUS opportunities.

30. A method of wireless communication performed by a network node, the method comprising: sending an indication of network capability for low power cell wake-up signal (LP-C-WUS) reception; receiving an indication of user equipment (UE) capabilities sent for LP-C-WUS; transmitting a cell discontinuous reception (DRX) configuration indicating one or more LP-C-WUS monitoring opportunities in a cell DRX cycle; and An LP-C-WUS is received in an LP-C-WUS opportunity of the one or more LP-C-WUS opportunities.

Images