Collision handling for WUS

By designing a unified radio architecture in user equipment (UE), monitoring low-power WUS with a low-power wake-up receiver, and turning on the main radio when WUS is detected, the collision problem between WUS monitoring and main radio communication in wireless communication systems is solved, and power saving and system efficiency improvement is achieved.

CN119586229APending Publication Date: 2025-03-07QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380054571.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-07-29
Filing Date
2023-07-14
Publication Date
2025-03-07

AI Technical Summary

Technical Problem

In wireless communication systems, there may be collisions between low power wake-up signal (WUS) monitoring and main radio communication, resulting in increased power consumption and hardware costs.

Method used

By designing a unified radio architecture in user equipment (UE), low-power wake-up receivers are used to monitor low-power WUS and turn on the main radio when WUS is detected to perform potential communication.

Benefits of technology

The power savings associated with the low-power wake-up receiver architecture are achieved, avoiding collisions between WUS monitoring and main radio communications, and improving system efficiency and reliability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119586229A_ABST
    Figure CN119586229A_ABST
Patent Text Reader

Abstract

A UE may identify potential communications associated with a first radio of the UE while a second radio of the UE is turned on. The potential communication may be independent of an indication received via the second radio. The UE may select whether to perform the potential communication. Performing the potential communication may be associated with turning on the first radio. A single radio between the first radio and the second radio may be turned on at a time. The first radio of the UE may be a primary radio. The second radio of the UE may be a wake-up receiver.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application serial number 17 / 816,351, filed on July 29, 2022, entitled “COLLISION HANDLINGFORWUS,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly, to a wake-up signal (WUS) in a wireless communication system. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, or even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continued mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] The following presents a summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not a comprehensive review of all contemplated aspects. This summary is neither intended to identify the key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a user equipment (UE). The apparatus may identify a potential communication associated with a first radio of the UE while a second radio of the UE is turned on. The potential communication may be independent of an indication received via the second radio. The apparatus may select whether to perform the potential communication. Performing the potential communication may be associated with turning on the first radio. A single radio between the first radio and the second radio may be turned on at a time.

[0008] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0010] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0011] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0012] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0013] Figure 2D is a diagram illustrating an example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

[0014] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0015] Figure 4 is a block diagram illustrating example radio components in a UE according to one or more aspects of the present disclosure.

[0016] Figure 5 is a diagram illustrating an example timeline associated with the transmission of a scheduling request in accordance with one or more aspects of the present disclosure.

[0017] Figure 6 The present invention is a diagram showing a communication flow of a wireless communication method.

[0018] Figure 7 is a flow chart of a method of wireless communication.

[0019] Figure 8 is a flow chart of a method of wireless communication.

[0020] Fig. 9 is a flow chart of a method of wireless communication.

[0021] Fig.10 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities. DETAILED DESCRIPTION

[0022] Low-power WUS can be used to indicate random data arrival time and / or whether there is data scheduling for UE in the upcoming discontinuous reception (DRX) cycle. In order to achieve these two purposes, a unified UE design including both the main radio and the low-power wake-up receiver can be used. In particular, the UE can use the low-power wake-up receiver to continuously monitor the low-power WUS. While the UE monitors the low-power WUS, the main radio of the UE can be turned off. Once the low-power WUS is detected, the UE can turn on the main radio (and turn off the low-power wake-up receiver) to communicate with the network node as usual. For example, after the main radio is turned on, the UE can receive a scheduling physical downlink control channel (PDCCH) / downlink control information (DCI) message, and can exchange data (in UL and / or DL) with the network node based on the scheduling information. However, there may be a collision between low-power WUS monitoring and other potential wireless communications because the main radio is turned off when the UE uses a low-power wake-up receiver to monitor the low-power WUS. For example, if there is an UL interruption to the low-power WUS monitoring, a collision may occur. In another example, a collision may occur if there is a conflict between operations configured at a higher layer (e.g., operations configured by radio resource control (RRC)), such as communications based on semi-persistent scheduling (SPS) or configuration grant (CG), and low-power WUS monitoring.

[0023] The UE may identify potential communications associated with a first radio of the UE while a second radio of the UE is turned on. The potential communications may be independent of indications received via the second radio. The UE may choose whether to perform the potential communications. Performing the potential communications may be associated with turning on the first radio. A single radio between the first radio and the second radio may be turned on at a time. The first radio of the UE may be a primary radio. The second radio of the UE may be a wake-up receiver. Thus, collisions between WUS monitoring and wireless communications via the primary radio may be resolved based on one or more factors and / or criteria. In addition, power savings associated with a low-power wake-up receiver architecture may be achieved.

[0024] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations in which the concepts described herein may be practiced. In order to provide a thorough understanding of the various concepts, the detailed description includes specific details. However, these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0025] Several aspects of the telecommunication system are also presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any 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.

[0026] As an example, an element, or any part of an element, or any combination of elements, may be implemented as a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chips (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic pieces, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0027] Thus, in one or more example aspects, specific implementations and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other media that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0028] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases can be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some practical environments, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0029] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or network equipment (such as a base station (BS)), or one or more units (or one or more components) performing base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0030] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0031] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0032] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0033] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units 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 from one or more of the other units or send signals to one or more of the other units on a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units on a wireless transmission medium.

[0034] In some aspects, CU 110 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 CU 110. CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 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, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0035] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) coding and decoding, scrambling, modulation, demodulation, etc.) at least in part according to a functional split (such as a functional split defined by 3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0036] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0037] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0038] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or communicate with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

[0039] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0040] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may or may not be included in the base station 102). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0041] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. 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), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0042] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0043] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) that is identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0044] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz to 24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0045] With the above in mind, unless otherwise specifically stated, if the term "sub-6 GHz" or the like is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, if the term "millimeter wave" or the like is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0046] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or different. The transmit direction and receive direction of the UE 104 may be the same or different.

[0047] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a clustered (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include decomposed base stations and / or clustered base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0048] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, the LMF 166, the position determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurement and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may determine the location of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, position estimation, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0049] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0050] Reference again Figure 1 In some aspects, the UE 104 may include a communication management component 198 that may be configured to identify potential communications associated with a first radio of the UE while a second radio of the UE is turned on. The potential communication may be independent of an indication received via the second radio. The communication management component 198 may be configured to select whether to perform the potential communication. Performing the potential communication may be associated with turning on the first radio. A single radio between the first radio and the second radio may be turned on at a time. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0051] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and both UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The slot format is configured for the UE by a received slot format indicator (SFI) (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0052] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of the same size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is conventional or extended. For a conventional CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled with 1 / SCS.

[0053]

[0054] Table 1: Parameter set, SCS and CP

[0055] For normal CP (14 symbols / slot), different parameter sets μ 0 to 4 allow 1, 2, 4, 8 and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Therefore, for normal CP and parameter set μ, there are 14 symbols / slot and 2μ slots / subframe. The subcarrier spacing can be equal to 2μ*15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a conventional CP is provided, where there are 14 symbols per slot and the parameter set μ=2, where there are 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. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0056] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 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.

[0057] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0058] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. 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 DM-RS. The physical broadcast channel (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 referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information such as system information blocks (SIBs) that are not sent via the PBCH, and paging messages.

[0059] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the comb structures in the comb structure. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0060] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as 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 hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0061] Figure 3 375. The Controller / Processor 375 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0062] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0063] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbol on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point most likely to be sent by the base station 310. These soft decisions can be based on the channel estimate calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0064] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0065] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0066] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 to select the appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via corresponding transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0067] UL transmissions are processed at the base station 310 in a manner similar to that described in connection with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0068] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0069] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 Various aspects related to the communication trigger component 198.

[0070] The wake-up signal may be used to indicate to the UE whether there is data scheduling for the UE in the upcoming DRX on duration (e.g., whether there is a DCI message scheduled for UL or DL ​​transmission for the UE). If the WUS is designed based on the PDCCH (e.g., WUS via the PDCCH), the UE may save power if the UE does not always receive scheduling information (i.e., DCI messages scheduled for UL or DL ​​transmission) in the DRX cycle. In addition, if the data arrival time is known to the network node (e.g., base station) at the start of the DRX on duration, the network may use cross-slot scheduling and PDCCH skipping between the scheduling DCI message and the scheduled data to achieve a similar effect as the WUS PDCCH (e.g., similar power savings). In addition, if the data arrival time is unknown to the network node at the start of the DRX on duration, the network may transmit a scheduling DCI message to the UE whenever appropriate. Sending a scheduling DCI message to the UE whenever appropriate may be more power efficient for the UE than using the WUS PDCCH, because decoding the WUS PDCCH at the UE may consume additional power.

[0071] Another approach to WUS may be based on low-power design. In particular, the UE may be equipped with low-power radio hardware to detect low-power WUS (e.g., sequence-based WUS), wherein the low-power radio hardware may be separate from the main radio and may consume much less power than the main radio (e.g., the low-power radio hardware may consume 1 / 100 of the power consumed by the main radio for communication). By using separate low-power radio hardware, overall power savings may be significantly improved. The low-power WUS may be used to indicate whether data is scheduled for the UE in the upcoming DRX on-duration or in the random data arrival time, as appropriate. In the absence of a low-power WUS, the UE may need to detect and decode the PDCCH to learn whether the data is scheduled for the UE in the upcoming DRX on-duration or in the random data arrival time. Therefore, if a low-power WUS is available, the connected mode DRX may be completely replaced by a specific implementation based on the low-power WUS, wherein the UE may receive the scheduling PDCCH based on the indication conveyed by the low-power WUS. In other words, the UE may keep monitoring the low power WUS using the low power radio hardware, and may, based on the indication conveyed by the low power WUS, turn on the primary radio (and turn off the low power radio hardware) when there is a scheduled PDCCH for the UE.

[0072] Figure 44 is a block diagram 400 illustrating an example radio in a UE according to one or more aspects of the present disclosure. The UE may include a main radio 402 for conventional wireless communications and a low-power wake-up receiver 404. Both the main radio 402 and the low-power wake-up receiver 404 may be connected to one or more antennas 406 of the UE. The low-power wake-up receiver 404 may correspond to a radio unit separate from the main radio 402 and may correspond to the low-power radio hardware described above. Therefore, the low-power wake-up receiver 404 may perform low-power WUS detection 408. Based on the indication conveyed by the low-power WUS, the UE may turn on the main radio 402 (and turn off the low-power wake-up receiver 404) to receive the scheduling PDCCH / DCI message and / or perform other wireless communication tasks. In some configurations herein, the main radio 402 and the low-power wake-up receiver 404 may not be turned on at the same time. In other words, a single radio between the main radio 402 and the low-power wake-up receiver 404 may be turned on at a time. If the UE turns on the main radio 402, the UE may turn off the low-power wake-up receiver 404 at the same time. Similarly, if the UE turns on the low power wake-up receiver 404, the UE may simultaneously turn off the primary radio 402. When the primary radio 402 is turned off, the UE may not be able to perform conventional wireless communications, and when the low power wake-up receiver 404 is turned off, the UE may not be able to perform low power WUS detection 408.

[0073] In various aspects, virtual reality (VR), augmented reality (AR), or extended reality (XR) video communications may be characterized by high throughput (e.g., 30 Mbps or 45 Mbps for video delivery), strict latency specifications (e.g., 10 ms packet delay budget (PDB) before video frame expiration), and random data arrival times (which may be caused by adaptive video compression algorithms and / or data delivery through application servers and the RAN).

[0074] The low-power wake-up receiver architecture is particularly useful for VR / AR / XR video exchange because the low-power WUS can be used to indicate random data arrival times (which can be attributed to jitter) and / or whether there is data scheduling for the UE in the upcoming DRX cycle. To achieve these two purposes, a unified UE design including both a main radio (e.g., main radio 402) and a low-power wake-up receiver (e.g., low-power wake-up receiver 404) can be used. In particular, the UE can use a low-power wake-up receiver to continuously monitor the low-power WUS. While the UE monitors the low-power WUS, the main radio of the UE can be turned off. Once the low-power WUS is detected, the UE can turn on the main radio (and turn off the low-power wake-up receiver) to communicate with the network node as usual. For example, after turning on the main radio, the UE can receive a scheduling PDCCH / DCI message and can exchange data or reference signals (in UL and / or DL) with the network node based on the scheduling information. However, there may be a collision between low-power WUS monitoring and other potential wireless communications because the main radio is turned off when the UE uses a low-power wake-up receiver to monitor the low-power WUS. For example, if there is a transmission that interrupts low-power WUS monitoring via the primary radio, a collision may occur. In another example, if there is a conflict between an operation configured at a higher layer (e.g., an RRC configured operation) (such as SPS or CG-based communication) and low-power WUS monitoring, a collision may occur.

[0075] As described above, the low power wake-up receiver and the primary radio of the UE may correspond to separate hardware and may be turned on or off separately. For reasons including saving power, reducing hardware costs, and / or reducing implementation difficulty, a single radio / receiver between the low power wake-up receiver and the primary radio may be turned on (activated) at any time. Generally speaking, if the low power wake-up receiver detects a WUS prompting the UE to turn on the primary radio to perform wireless communication (e.g., the WUS may convey an indication of upcoming wireless communication that may be performed using the primary radio), the UE may turn on the primary radio.

[0076] In one configuration, the UE may need to initiate an UL transmission without having received any indication from the network node via a WUS. For example, the application layer at the UE may have data packets to send to the network, and the UE may need to first request resources by transmitting a scheduling request on the UL. Therefore, the UE may need to turn on the primary radio in order to send the scheduling request. However, turning on the primary radio may interrupt or interfere with the WUS monitoring performed by the low power wake-up receiver because the low power wake-up receiver may be turned off when the primary radio is turned on. Therefore, if the network node sends a WUS to the UE during a period when the UE autonomously turns on the primary radio to send a scheduling request, the UE may miss the WUS and the associated scheduling PDCCH indicated by the WUS.

[0077] Figure 5 5 is a diagram illustrating an example timeline associated with the transmission of a scheduling request according to one or more aspects of the present disclosure. For a UE including a wake-up receiver and a primary radio corresponding to separate hardware, the UE may autonomously switch from the wake-up receiver to the primary radio (i.e., turn on the primary radio and turn off the wake-up receiver), for example, when the UE intends to initiate an UL transmission to the network. In different configurations, the UE may perform different operations associated with the switch to the primary radio. In one configuration, as shown at 510, after switching to the primary radio (i.e., turning on the primary radio and turning off the wake-up receiver) in order to send a scheduling request 512 (or some other transmission), the UE may keep the primary radio turned on (awake). In some configurations, if the UE receives an indication from a network node (e.g., after communication via the primary radio is completed) signaling the UE to switch to the wake-up receiver (i.e., turn on the wake-up receiver and turn off the primary radio), the UE may switch to the wake-up receiver in response to the indication from the network node.

[0078] In another configuration, as shown at 520, after switching to the primary radio to send a scheduling request 522 (or some other transmission), the UE may keep the primary radio on (awake) for a predetermined duration (e.g., a maximum duration 524). After the predetermined duration (e.g., the maximum duration 524) has expired, the UE may switch to a wake-up receiver. The network node communicating with the UE may have enough time to receive the scheduling request 522 to know that the UE has autonomously switched on the primary radio. In some configurations, before the predetermined duration (e.g., the maximum duration 524) expires, the network node may signal the UE (e.g., using a signaling indication) to switch to the wake-up receiver.

[0079] In some configurations, if the UE receives the scheduling PDCCH within a predetermined duration, the UE may keep the primary radio on and may communicate with the network node based on the scheduling information included in the scheduling PDCCH. If the communication with the network node is completed before the predetermined duration (e.g., the maximum duration 524) expires, the UE may continue to wait for the predetermined duration (e.g., the maximum duration 524) to expire and then switch to the wake-up receiver. On the other hand, if the communication with the network node is not completed before the predetermined duration (e.g., the maximum duration 524) expires, the UE may keep the primary radio on after the predetermined duration expires in order to complete the communication. If the pre-configured duration has expired, the UE may switch to the wake-up receiver after the communication with the network node is completed.

[0080] In yet another configuration, as shown at 530, a plurality of opportunities 536 may be preconfigured (each opportunity 536 may correspond to a plurality of symbols / time slots), wherein the network node may not send a WUS during the preconfigured opportunities 536. Thus, if the UE intends to send a scheduling request 532 (or some other transmission), the UE may autonomously switch to (activate) the primary radio to send the scheduling request 532 (or some other transmission) during one of the preconfigured opportunities 536. Once the transmission is complete (e.g., before the current opportunity 536 expires), the UE may switch back to waking up the receiver. In some configurations, the plurality of opportunities 536 may be periodic opportunities (i.e., the opportunities 536 may be associated with a periodicity). For example, the period between two adjacent opportunities 536 may be a period 534. In some configurations, the opportunity 536 may be associated with a starting offset within the period.

[0081] In some configurations, during opportunity 536, the UE may turn on (activate) the primary radio based on an indication from the network node.

[0082] In some aspects, the low power WUS may be suitable for dynamically scheduling or triggering data channels or reference signals. In other words, when the network node wants the UE to dynamically send or receive a channel or reference signal, the network node may use the WUS to signal the UE to turn on the primary radio and communicate with the network node using the primary radio.

[0083] In some configurations, there may be a collision between WUS monitoring and (potential) transmission or reception configured in a higher layer (e.g., RRC configured transmission or reception) (such as periodic communication, SPS-based communication, or CG-based communication), where the transmission or reception may correspond to data and / or signals (e.g., signals for measurement, positioning, and / or sensing, etc.). The UE may resolve the collision in various ways.

[0084] In one configuration, if the wake-up receiver of the UE is turned on (active) and the primary radio of the UE is turned off (dormant), and there is an opportunity for higher layer (e.g., RRC) configuration to transmit or receive using the primary radio, the UE may keep the wake-up receiver turned on and may ignore the opportunity for higher layer configuration to transmit or receive.

[0085] In one configuration, if the UE's wake-up receiver is turned on and the UE's primary radio is turned off, and there is a higher layer (e.g., RRC) configured opportunity for using the primary radio to transmit or receive, the UE may turn on (wake up) the primary radio based on the higher layer configuration to transmit or receive at that opportunity. In addition, in some configurations, the network node may avoid sending a WUS at that opportunity.

[0086] However, for an opportunity configured for potential UL transmission, if the UE has no data to send at that opportunity, the UE may keep the wake-up receiver turned on and may not turn on the primary radio for that opportunity. Therefore, if appropriate (e.g., there is an upcoming scheduled PDCCH for the UE), the network node may still send a WUS to the UE within that opportunity.

[0087] In some configurations, for a collision between WUS monitoring and the transmission or reception of a higher layer configuration of data or signals, the UE may, based on a configuration received from a network node, select between 1) keeping the wake-up receiver turned on and ignoring the transmission or reception of the higher layer configuration or 2) switching to the primary radio and performing the transmission or reception of the higher layer configuration. In some other configurations, for a collision between WUS monitoring and the transmission or reception of a higher layer configuration of data or signals, the UE may autonomously select between 1) keeping the wake-up receiver turned on and ignoring the transmission or reception of the higher layer configuration or 2) switching to the primary radio and performing the transmission or reception of the higher layer configuration. Generally speaking, if the priority associated with the transmission or reception of the higher layer configuration is low (e.g., less than a threshold), the UE may choose to keep the wake-up receiver turned on and ignore the transmission or reception of the higher layer configuration. On the other hand, if the priority associated with the transmission or reception of the higher layer configuration is high (e.g., greater than a threshold), the UE may choose to switch to the primary radio and perform the transmission or reception of the higher layer configuration. Furthermore, the UE may report to the network (eg, via capability signaling) the UE's expected behavior related to resolution of collisions between WUS monitoring and higher layer configured transmission or reception (eg, keeping the wake-up receiver on or switching to the primary radio).

[0088] In one configuration, a configuration from a network node or a report from a UE associated with a UE behavior configuration related to a solution to a collision between WUS monitoring and the transmission or reception of a higher layer configuration (e.g., keeping a wake-up receiver on or switching to a primary radio) may apply to the transmission or reception of all higher layer configurations of data or signals for the UE. In another configuration, a configuration from a network node or a report from a UE associated with a UE behavior configuration related to a solution to a collision between WUS monitoring and the transmission or reception of a higher layer configuration (e.g., keeping a wake-up receiver on or switching to a primary radio) may apply to the transmission or reception of one or more separate higher layer configurations of data or signals for the UE. Thus, multiple configurations or reports are possible for the transmission or reception of different higher layer configurations of data or signals for the UE.

[0089] Figure 6600 is a diagram of a communication flow of a method of wireless communication. In one configuration, at 618, the UE 602 may send a first indication of a UE behavior configuration associated with a potential communication to the network node 604, or may receive a second indication of a UE behavior configuration associated with the potential communication from the network node 604. In one configuration, the UE behavior configuration may be associated with all communications associated with the UE configured by the RRC. In one configuration, the UE behavior configuration may be associated with one or more separate communications associated with the UE configured by the RRC. In one or more configurations, the potential communication may be one of a periodic communication, an SPS-based communication, or a CG-based communication.

[0090] At 606, UE 602 may identify potential communications associated with a first radio of UE 602 while a second radio of UE 602 is on. The potential communications may be independent of (eg, may not be based on) the indication received via the second radio.

[0091] In one configuration, the first radio of the UE 602 may be a primary radio. The second radio of the UE 602 may be a (low power) wake-up receiver.

[0092] At 608, the UE 602 may select whether to perform the potential communication. Performing the potential communication may be associated with turning on the first radio. A single radio between the first radio and the second radio may be turned on at a time.

[0093] In one configuration, at 610, the UE 602 may turn on a first radio to perform potential communications.

[0094] In one configuration, at 612a , the UE 602 may receive an indication from the network node 604 to turn on the second radio after performing the potential communication at 610 .

[0095] At 612b, UE 602 may turn on the second radio in response to the indication at 612a to turn on the second radio.

[0096] In one configuration, at 614, the UE 602 may turn on the second radio after the first radio has been turned on for the preconfigured duration without receiving scheduling information for another communication associated with the first radio via the first radio while the first radio is turned on for the preconfigured duration.

[0097] In one configuration, at 616a, the UE 602 may receive, from the network node 604 via the first radio within a preconfigured duration after the first radio is turned on, scheduling information for another communication associated with the first radio.

[0098] At 616b, UE 602 may perform another communication via the first radio based on scheduling information 616a.

[0099] At 616c, if the preconfigured duration has expired, the UE 602 may turn on the second radio after completing another communication at 616b.

[0100] In one configuration, the first radio may be turned on at one of a plurality of preconfigured occasions to perform potential communications at 610. In one configuration, the plurality of preconfigured occasions may be associated with a periodicity or a starting offset.

[0101] In one configuration, the potential communications at 610 may include uplink transmissions or sidelink transmissions.

[0102] In one configuration, the potential communication at 606 may be RRC configured. The potential communication may be associated with a pre-configured opportunity.

[0103] In one configuration, at 620a, the UE 602 may elect not to perform potential communications at the preconfigured occasions.

[0104] At 620b, UE 602 may keep the second radio on at preconfigured occasions.

[0105] In one configuration, 622 may include 622a or 622b. At 622a, the UE 602 may turn on the first radio at a preconfigured opportunity to perform the potential communication if the potential communication does not correspond to an uplink transmission in which the UE 602 has no data to send.

[0106] At 622b, the UE 602 may keep the second radio on at the pre-configured occasions if the potential communication corresponds to an uplink transmission in which the UE 602 has no data to send.

[0107] Figure 7 700 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104 / 350 / 602; device 1004). At 702, the UE may identify a potential communication associated with a first radio of the UE while a second radio of the UE is turned on. The potential communication may be independent of an indication received via the second radio. For example, 702 may be performed by Fig.10 Component 198 in the implementation. Reference Figure 6 At 606, UE 602 may identify potential communications associated with a first radio of UE 602 while a second radio of UE 602 is turned on.

[0108] At 704, the UE may select whether to perform the potential communication. Performing the potential communication may be associated with turning on the first radio. A single radio between the first radio and the second radio may be turned on at a time. For example, 704 may be performed by Fig.10 Component 198 in the implementation. Figure 6 At 608, UE 602 may select whether to perform the potential communication.

[0109] Figure 8 800 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104 / 350 / 602; device 1004). At 802, the UE may identify a potential communication associated with a first radio of the UE while a second radio of the UE is turned on. The potential communication may be independent of an indication received via the second radio. For example, 802 may be performed by Fig.10 Component 198 in the implementation. Figure 6 At 606, UE 602 may identify potential communications associated with a first radio of UE 602 while a second radio of UE 602 is turned on.

[0110] At 804, the UE may select whether to perform the potential communication. Performing the potential communication may be associated with turning on the first radio. A single radio between the first radio and the second radio may be turned on at a time. For example, 804 may be performed by Fig.10 Component 198 in the implementation. Reference Figure 6 At 608, UE 602 may select whether to perform the potential communication.

[0111] In one configuration, at 806, the UE may turn on the first radio to perform potential communications. For example, 806 may be performed by Fig.10 Component 198 in the implementation. Figure 6 At 610, UE 602 may turn on a first radio to perform potential communications.

[0112] In one configuration, at 808, the UE may receive an indication from the network node to turn on the second radio after performing the potential communication. Fig.10 Component 198 in the implementation. Reference Figure 6 At 612a, UE 602 may receive an indication from network node 604 to turn on the second radio after performing the potential communication at 610.

[0113] At 810, the UE may turn on the second radio in response to the instruction to turn on the second radio. For example, 810 may be performed by Fig.10 Component 198 in the implementation. Reference Figure 6At 612b, UE 602 may turn on the second radio in response to the indication at 612a to turn on the second radio.

[0114] In one configuration, at 812, the UE may turn on the second radio after the first radio has been turned on for the preconfigured duration if scheduling information for another communication associated with the first radio is not received via the first radio while the first radio is turned on for the preconfigured duration. For example, 812 may be performed by Fig.10 Component 198 in the implementation. Reference Figure 6 At 614, UE 602 may turn on the second radio after the first radio has been turned on for the preconfigured duration if scheduling information for another communication associated with the first radio is not received via the first radio while the first radio is turned on for the preconfigured duration.

[0115] In one configuration, at 814, the UE may receive scheduling information for another communication associated with the first radio from the network node via the first radio within a preconfigured duration after the first radio is turned on. For example, 814 may be performed by Fig.10 Component 198 in the implementation. Reference Figure 6 At 616a, the UE 602 may receive scheduling information for another communication associated with the first radio from the network node 604 via the first radio within a preconfigured duration after the first radio is turned on.

[0116] At 816, the UE may perform another communication via the first wireless unit based on the scheduling information. For example, 816 may be performed by Fig.10 Component 198 in the implementation. Reference Figure 6 At 616b, the UE 602 may perform another communication via the first radio based on the scheduling information 616a.

[0117] At 818, if the preconfigured duration has expired, the UE may turn on the second radio after performing another communication. Fig.10 Component 198 in the implementation. Reference Figure 6 At 616c, if the preconfigured duration has expired, the UE 602 may turn on the second radio after completing another communication at 616b.

[0118] In one configuration, reference Figure 6 At 610, the first radio is turned on at one of a plurality of preconfigured occasions to perform potential communications.

[0119] In one configuration, multiple preconfigured occasions may be associated with a periodicity or a starting offset.

[0120] In one configuration, potential communications may include uplink transmissions or sidelink transmissions.

[0121] In one configuration, reference Figure 6 , the first radio of UE 602 may be the primary radio. The second radio of UE 602 may be the wake-up receiver.

[0122] Fig. 9 900 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104 / 350 / 602; device 1004). At 904, the UE may identify potential communications associated with a first radio of the UE while a second radio of the UE is turned on. The potential communications may be independent of indications received via the second radio. For example, 904 may be performed by Fig.10 Component 198 in the implementation. Reference Figure 6 At 606, UE 602 may identify potential communications associated with a first radio of UE 602 while a second radio of UE 602 is turned on.

[0123] At 906, the UE may select whether to perform the potential communication. Performing the potential communication may be associated with turning on the first radio. A single radio between the first radio and the second radio may be turned on at a time. For example, 906 may be performed by Fig.10 Component 198 in the implementation. Reference Figure 6 At 608, UE 602 may select whether to perform the potential communication.

[0124] In one configuration, the potential communication may be RRC configured.The potential communication may be associated with a pre-configured opportunity.

[0125] In one configuration, at 908, the UE may choose not to perform potential communications at a preconfigured opportunity. For example, 908 may be performed by Fig.10 Component 198 in the implementation. Reference Figure 6 At 620a, UE 602 may choose not to perform potential communications at the preconfigured occasion.

[0126] At 910, the UE may keep the second radio on at preconfigured times. For example, 910 may be Fig.10 Component 198 in the implementation. Reference Figure 6 At 620b, UE 602 may keep the second radio turned on at pre-configured occasions.

[0127] In one configuration, at 912a, the UE may turn on the first radio at a preconfigured opportunity to perform the potential communication if the potential communication does not correspond to an uplink transmission in which the UE has no data to send. For example, 912a may be performed by Fig.10 Component 198 in the implementation. Reference Figure 6 At 622a, the UE 602 may turn on the first radio at a preconfigured opportunity to perform the potential communication if the potential communication does not correspond to an uplink transmission in which the UE 602 has no data to send.

[0128] At 912b, the UE may keep the second radio on at pre-configured times if the potential communication corresponds to an uplink transmission in which the UE has no data to send. For example, 912b may be Fig.10 Component 198 in the implementation. Reference Figure 6 At 622b, the UE 602 may keep the second radio on at the pre-configured occasions if the potential communication corresponds to an uplink transmission in which the UE 602 has no data to send.

[0129] In one configuration, at 902, the UE may send a first indication of a UE behavior configuration associated with a potential communication to a network node, or may receive a second indication of a UE behavior configuration associated with a potential communication from a network node. Fig.10 Component 198 in the implementation. Reference Figure 6 At 618, UE 602 may send a first indication of UE behavior configuration associated with the potential communication to network node 604, or may receive a second indication of UE behavior configuration associated with the potential communication from network node 604.

[0130] In one configuration, reference Figure 6 , the UE behavior configuration at 618 may be associated with all communications associated with the UE configured by the RRC.

[0131] In one configuration, reference Figure 6 , the UE behavior configuration at 618 may be associated with one or more separate communications associated with the UE configured by the RRC.

[0132] In one configuration, the potential communication may be one of periodic communication, SPS-based communication, or CG-based communication.

[0133] In one configuration, reference Figure 6 , the first radio of UE 602 may be the primary radio. The second radio of UE 602 may be the wake-up receiver.

[0134] Fig.101000 is a diagram illustrating an example of a hardware implementation for an apparatus 1004. The apparatus 1004 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1004 may include a cellular baseband processor 1024 (also referred to as a modem) coupled to one or more transceivers 1022 (e.g., a cellular RF transceiver). The cellular baseband processor 1024 may include on-chip memory 1024'. In some aspects, the apparatus 1004 may also include one or more subscriber identity module (SIM) cards 1020 and an application processor 1006 coupled to a secure digital (SD) card 1008 and a screen 1010. The application processor 1006 may include on-chip memory 1006'. In some aspects, the device 1004 may also include a Bluetooth module 1012, a WLAN module 1014, an SPS module 1016 (e.g., a GNSS module), one or more sensor modules 1018 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio for positioning, and / or other technologies), an additional memory module 1026, a power source 1030, and / or a camera 1032. The Bluetooth module 1012, the WLAN module 1014, and the SPS module 1016 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1012, the WLAN module 1014, and the SPS module 1016 may include their own dedicated antennas and / or communicate using an antenna 1080. The cellular baseband processor 1024 communicates with the UE 104 and / or with the RU associated with the network entity 1002 through the transceiver 1022 via one or more antennas 1080. The cellular baseband processor 1024 and the application processor 1006 may each include a computer-readable medium / memory 1024', 1006', respectively. The additional memory module 1026 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1024', 1006', 1026 may be non-transitory. The cellular baseband processor 1024 and the application processor 1006 are each responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1024 / application processor 1006, enables the cellular baseband processor 1024 / application processor 1006 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1024 / application processor 1006 when executing the software.The cellular baseband processor 1024 / application processor 1006 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1004 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1024 and / or the application processor 1006, and in another configuration, the device 1004 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 1004.

[0135] As discussed above, component 198 is configured to identify potential communications associated with the first radio of the UE while the second radio of the UE is turned on. The potential communication may be independent of the indication received via the second radio. Component 198 may be configured to select whether to perform potential communications. Performing the potential communication may be associated with turning on the first radio. A single radio between the first radio and the second radio may be turned on at one time. Component 198 may be within the cellular baseband processor 1024, the application processor 1006, or within both the cellular baseband processor 1024 and the application processor 1006. Component 198 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination thereof. As shown, device 1004 may include multiple components configured for various functions. In one configuration, device 1004 (and in particular cellular baseband processor 1024 and / or application processor 1006) includes a component for identifying potential communications associated with the first radio of the UE while the second radio of the UE is turned on. The potential communication may be independent of the indication received via the second radio. The device 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) includes means for selecting whether to perform the potential communication. Performing the potential communication may be associated with turning on the first radio. A single radio between the first radio and the second radio may be turned on at a time.

[0136] In one configuration, the apparatus 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) includes means for turning on the first radio to perform a potential communication. In one configuration, the apparatus 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) includes means for receiving an indication from a network node to turn on a second radio after performing the potential communication. The apparatus 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) includes means for turning on the second radio in response to the indication to turn on the second radio. In one configuration, the apparatus 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) includes means for turning on the second radio after the first radio has been turned on for a preconfigured duration if scheduling information for another communication associated with the first radio is not received via the first radio while the first radio is turned on for a preconfigured duration. In one configuration, the device 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) includes a component for receiving scheduling information for another communication associated with the first radio from the network node via the first radio within a preconfigured duration after the first radio is turned on. The device 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) includes a component for performing another communication via the first radio based on the scheduling information. The device 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) includes a component for turning on the second radio after the execution of the other communication is completed if the preconfigured duration has expired. In one configuration, the first radio may be turned on at one of a plurality of preconfigured timings to perform the potential communication. In one configuration, the plurality of preconfigured timings may be associated with a periodicity or a starting offset. In one configuration, the potential communication may include an uplink transmission or a sidelink transmission. In one configuration, the potential communication may be RRC configured. The potential communication may be associated with a preconfigured timing. In one configuration, the apparatus 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) includes means for selecting not to perform potential communications at preconfigured occasions. The apparatus 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) includes means for keeping the second radio on at preconfigured occasions. In one configuration, the apparatus 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) includes means for turning on the first radio to perform potential communications at preconfigured occasions if the potential communications do not correspond to uplink transmissions in which the UE has no data to send.The device 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) includes a component for keeping the second radio turned on at a preconfigured time when the potential communication corresponds to an uplink transmission in which the UE has no data to send. In one configuration, the device 1004 (and in particular the cellular baseband processor 1024 and / or the application processor 1006) includes a component for sending a first indication of a UE behavior configuration associated with the potential communication to a network node, or a component for receiving a second indication of a UE behavior configuration associated with the potential communication from a network node. In one configuration, the UE behavior configuration may be associated with all communications associated with the UE configured by the RRC. In one configuration, the UE behavior configuration may be associated with one or more separate communications associated with the UE configured by the RRC. In one configuration, the potential communication may be one of a periodic communication, an SPS-based communication, or a CG-based communication. In one configuration, the first radio of the UE may be a primary radio. The second radio of the UE may be a wake-up receiver.

[0137] A means may be a component 198 of the apparatus 1004 configured to perform the functions recited by the means. As described above, the apparatus 1004 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, a means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0138] Return to reference Figures 4 to 10 , the UE may identify potential communications associated with the UE's first radio while the UE's second radio is turned on. The potential communication may be independent of an indication received via the second radio. The UE may choose whether to perform the potential communication. Performing the potential communication may be associated with turning on the first radio. A single radio between the first radio and the second radio may be turned on at a time. The first radio of the UE may be a primary radio. The second radio of the UE may be a wake-up receiver. Therefore, collisions between WUS monitoring and wireless communications via the primary radio may be resolved based on one or more factors and / or criteria. In addition, power savings associated with a low-power wake-up receiver architecture may be achieved.

[0139] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. In addition, some blocks can be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not limited to the specific order or hierarchy provided.

[0140] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. 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. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while..." do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when...", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data can be directly received / sent between the first device and the second device, or indirectly received / sent between the first device and the second device through a set of devices. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will be known later to those of ordinary skill in the art are expressly incorporated herein by reference and are 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. Words such as "module", "mechanism", "element", "device" cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for...".

[0141] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0142] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein, but are not limiting.

[0143] Aspect 1 is a method for wireless communication at a UE, comprising: identifying a potential communication component associated with a first radio of the UE while a second radio of the UE is turned on, the potential communication being independent of an indication received via the second radio; and selecting whether to perform the potential communication, performing the potential communication being associated with turning on the first radio, wherein a single radio between the first radio and the second radio is turned on at a time.

[0144] Aspect 2 is a method according to aspect 1, further comprising: turning on the first radio to perform the potential communication.

[0145] Aspect 3 is a method according to aspect 2, further comprising: receiving an indication from a network node to turn on the second radio after performing the potential communication; and turning on the second radio in response to the indication to turn on the second radio.

[0146] Aspect 4 is a method according to Aspect 2, further comprising: turning on the second radio after the first radio has been turned on for a preconfigured duration if no scheduling information for another communication associated with the first radio is received via the first radio while the first radio is turned on for the preconfigured duration.

[0147] Aspect 5 is a method according to aspect 2, further comprising: receiving scheduling information for another communication associated with the first radio from a network node via the first radio within a preconfigured duration after the first radio is turned on; performing the other communication via the first radio based on the scheduling information; and turning on the second radio after the execution of the other communication is completed if the preconfigured duration has expired.

[0148] Aspect 6 is a method according to aspect 2, wherein the first radio is turned on at one of a plurality of preconfigured occasions to perform the potential communication.

[0149] Aspect 7 is a method according to aspect 6, wherein the plurality of preconfigured occasions are associated with a periodicity or a starting offset.

[0150] Aspect 8 is a method according to any one of Aspects 2 to 7, wherein the potential communication includes uplink transmission or sidelink transmission.

[0151] Aspect 9 is a method according to aspect 1, wherein the potential communication is RRC configured and the potential communication is associated with a pre-configured opportunity.

[0152] Aspect 10 is a method according to aspect 9, further comprising: selecting not to perform the potential communication at the preconfigured occasion; and keeping the second radio on at the preconfigured occasion.

[0153] Aspect 11 is a method according to Aspect 9, further comprising: turning on the first radio at the preconfigured timing to perform the potential communication when the potential communication does not correspond to an uplink transmission in which the UE has no data to send; or keeping the second radio turned on at the preconfigured timing when the potential communication corresponds to the uplink transmission in which the UE has no data to send.

[0154] Aspect 12 is a method according to any one of Aspects 9 to 11, further comprising: sending a first indication of a UE behavior configuration associated with the potential communication to a network node; or receiving a second indication of the UE behavior configuration associated with the potential communication from the network node.

[0155] Aspect 13 is a method according to aspect 12, wherein the UE behavior configuration is associated with all communications associated with the UE configured by RRC.

[0156] Aspect 14 is a method according to aspect 12, wherein the UE behavior configuration is associated with one or more separate communications associated with the UE configured by RRC.

[0157] Aspect 15 is a method according to any one of Aspects 9 to 14, wherein the potential communication is one of periodic communication, SPS-based communication, or CG-based communication.

[0158] Aspect 16 is a method according to any one of aspects 1 to 15, wherein the first radio of the UE is a primary radio and the second radio of the UE is a wake-up receiver.

[0159] Aspect 17 is an apparatus for wireless communication, comprising: at least one processor, the at least one processor being coupled to a memory, and the at least one processor being configured to implement a method as described in any one of Aspects 1 to 16 based at least in part on information stored in the memory.

[0160] Aspect 18 may be combined with Aspect 17, and further comprises: a transceiver coupled to the at least one processor.

[0161] Aspect 19 is an apparatus for wireless communication, comprising: a component for implementing any one of aspects 1 to 16.

[0162] Aspect 20 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 16.

[0163] Various aspects have been described herein. These and other aspects are within the scope of the following claims.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: identifying potential communications associated with a first radio of the UE while a second radio of the UE is on, the potential communications being independent of indications received via the second radio; and Selecting whether to perform the potential communication, performing the potential communication being associated with turning on the first radio, wherein a single radio between the first radio and the second radio is turned on at a time.

2. The apparatus of claim 1 , wherein the at least one processor is further configured to: The first radio is turned on to perform the potential communication.

3. The apparatus of claim 2, wherein the at least one processor is further configured to: receiving an indication from a network node to turn on the second radio after performing the potential communication; and The second radio is turned on in response to the indication to turn on the second radio.

4. The apparatus of claim 2, wherein the at least one processor is further configured to: In an event that scheduling information for another communication associated with the first radio is not received via the first radio while the first radio is on for a preconfigured duration, turning on the second radio after the first radio has been on for the preconfigured duration.

5. The apparatus of claim 2, wherein the at least one processor is further configured to: receiving, from a network node via the first radio within a preconfigured duration after the first radio is turned on, scheduling information for another communication associated with the first radio; performing the another communication via the first radio based on the scheduling information; as well as In the event that the preconfigured duration has expired, the second radio is turned on after performing the other communication is complete.

6. The apparatus of claim 2, wherein the first radio is turned on at one of a plurality of preconfigured occasions to perform the potential communication. The apparatus of claim 6 , wherein the plurality of preconfigured occasions are associated with a periodicity or a start offset.

8. The apparatus of claim 2, wherein the potential communication comprises an uplink transmission or a sidelink transmission.

9. The apparatus of claim 1, wherein the potential communication is radio resource control (RRC) configured and the potential communication is associated with a pre-configured opportunity.

10. The apparatus of claim 9, wherein the at least one processor is further configured to: selecting not to perform the potential communication at the preconfigured occasion; and The second radio is kept turned on at the preconfigured occasions.

11. The apparatus of claim 9, wherein the at least one processor is further configured to: In a case where the potential communication does not correspond to an uplink transmission in which the UE has no data to send, switching on the first radio at the preconfigured occasion to perform the potential communication; or Keeping the second radio on at the pre-configured occasions at the pre-configured occasions in case the potential communication corresponds to the uplink transmission in which the UE has no data to send.

12. The apparatus of claim 9, wherein the at least one processor is further configured to: sending a first indication of a UE behavior configuration associated with the potential communication to a network node; or A second indication of the UE behavior configuration associated with the potential communication is received from the network node.

13. The apparatus of claim 12, wherein the UE behavior configuration is associated with all communications associated with the UE configured by RRC.

14. The apparatus of claim 12, wherein the UE behavior configuration is associated with one or more separate communications associated with the UE configured by RRC.

15. The apparatus of claim 9, wherein the potential communication is one of a periodic communication, a semi-persistent scheduling (SPS) based communication, or a configuration grant (CG) based communication.

16. The apparatus of claim 1, wherein the first radio of the UE is a primary radio and the second radio of the UE is a wake-up receiver.

17. The apparatus according to claim 1, further comprising: A transceiver is coupled to the at least one processor.

18. A method of wireless communication at a user equipment (UE), the method comprising: identifying potential communications associated with a first radio of the UE while a second radio of the UE is on, the potential communications being independent of indications received via the second radio; and Selecting whether to perform the potential communication, performing the potential communication being associated with turning on the first radio, wherein a single radio between the first radio and the second radio is turned on at a time.

19. The method according to claim 18, further comprising: The first radio is turned on to perform the potential communication.

20. The method according to claim 19, further comprising: receiving an indication from a network node to turn on the second radio after performing the potential communication; as well as The second radio is turned on in response to the indication to turn on the second radio.

21. The method according to claim 19, further comprising: In an event that scheduling information for another communication associated with the first radio is not received via the first radio while the first radio is on for a preconfigured duration, turning on the second radio after the first radio has been on for the preconfigured duration.

22. The method according to claim 19, further comprising: receiving, from a network node via the first radio within a preconfigured duration after the first radio is turned on, scheduling information for another communication associated with the first radio; performing the another communication via the first radio based on the scheduling information; as well as In the event that the preconfigured duration has expired, the second radio is turned on after performing the other communication is complete.

23. The method of claim 19, wherein the first radio is turned on at one of a plurality of preconfigured occasions to perform the potential communication.

24. The method of claim 23, wherein the plurality of preconfigured occasions are associated with a periodicity or a start offset.

25. The method of claim 19, wherein the potential communication comprises an uplink transmission or a sidelink transmission.

26. The method of claim 18, wherein the potential communication is radio resource control (RRC) configured and the potential communication is associated with a preconfigured opportunity.

27. The method according to claim 26, further comprising: selecting not to perform the potential communication at the preconfigured occasion; as well as The second radio is kept turned on at the preconfigured occasions.

28. The method according to claim 26, further comprising: In a case where the potential communication does not correspond to an uplink transmission in which the UE has no data to transmit, switching on the first radio at the preconfigured occasion to perform the potential communication; or Keeping the second radio on at the pre-configured occasions at the pre-configured occasions in case the potential communication corresponds to the uplink transmission in which the UE has no data to send.

29. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: means for identifying potential communications associated with a first radio of the UE while a second radio of the UE is on, the potential communications being independent of indications received via the second radio; and Means for selecting whether to perform the potential communication, performing the potential communication being associated with turning on the first radio, wherein a single radio between the first radio and the second radio is turned on at a time.

30. A computer readable medium storing computer executable code at a user equipment (UE) which, when executed by a processor, causes the processor to: identifying potential communications associated with a first radio of the UE while a second radio of the UE is on, the potential communications being independent of indications received via the second radio; and Selecting whether to perform the potential communication, performing the potential communication being associated with turning on the first radio, wherein a single radio between the first radio and the second radio is turned on at a time.