WO2025189457A1

WO2025189457A1 - A-iot device frequency error control

Info

Publication number: WO2025189457A1
Application number: PCT/CN2024/081915
Authority: WO
Inventors: Zhikun WU; Yuchul Kim
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2024-03-15
Filing date: 2024-03-15
Publication date: 2025-09-18
Anticipated expiration: 2026-09-15

Abstract

Apparatus, methods, and computer program products for wireless communication are provided. An example method may include transmitting, for a second wireless device, a forward link packet including information for oscillator adjustment (OA). The example method may further include communicating with the second wireless device after transmission of the forward link packet.

Description

A-IOT DEVICE FREQUENCY ERROR CONTROL

TECHNICAL FIELD

The present disclosure relates generally to communication systems, and more particularly, to wireless communication systems with ambient Internet of Things (A-IoT) devices.

INTRODUCTION

Wireless communication systems are widely deployed to provide various 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.

These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR) . 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with 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) . Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

BRIEF SUMMARY

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates 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 the more detailed description that is presented later.

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus at a user equipment (UE) or a network entity are provided. The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to transmit, for a second wireless device, a forward link packet including information for oscillator adjustment (OA) . Based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to communicate with the second wireless device after transmission of the forward link packet.

In another aspect of the disclosure, a method, a computer-readable medium, and an apparatus at an ambient Internet of Things (A-IoT) device are provided. The apparatus may include at least one memory at least one processor coupled to the at least one memory and an oscillator, based at least in part on stored information that is stored in the at least one memory. Based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to receive, from a second wireless device, a forward link packet including information for OA. Based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to adjust the oscillator based on the information for the OA.

To the accomplishment of the foregoing and related ends, the one or more aspects include the features hereinafter fully described and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.

FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.

FIG. 2B is a diagram illustrating an example of downlink (DL) channels within a subframe, in accordance with various aspects of the present disclosure.

FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.

FIG. 2D is a diagram illustrating an example of uplink (UL) channels within a subframe, in accordance with various aspects of the present disclosure.

FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network, in accordance with various aspects of the present disclosure.

FIG. 4 is a diagram illustrating an example radio frequency identification (RFID) system, in accordance with various aspects of the present disclosure.

FIG. 5A is a diagram illustrating an example implementation of zero power IoT (ZP IoT) communication, in accordance with various aspects of the present disclosure.

FIG. 5B is a diagram illustrating another example implementation of ZP IoT communication, in accordance with various aspects of the present disclosure.

FIG. 6A is a diagram illustrating an example of monostatic backscatter, in accordance with various aspects of the present disclosure.

FIG. 6B is a diagram illustrating an example of bistatic backscatter, in accordance with various aspects of the present disclosure.

FIG. 7 is a diagram illustrating another example of bistatic backscatter, in accordance with various aspects of the present disclosure.

FIG. 8 is a diagram illustrating example backlink (BL) communications with and without frequency uncertainty, in accordance with various aspects of the present disclosure.

FIG. 9 is a diagram illustrating example forward link (FL) packet used for oscillator adjustment, in accordance with various aspects of the present disclosure.

FIG. 10 is a diagram illustrating example time-frequency synchronization signal in FL used for facilitating BL communications, in accordance with various aspects of the present disclosure.

FIG. 11 is a diagram illustrating example time domain synchronization signal and frequency domain synchronization signal, in accordance with various aspects of the present disclosure.

FIG. 12 is a diagram illustrating example oscillator adjustment in connection with synchronization signals, in accordance with various aspects of the present disclosure.

FIG. 13 is a diagram illustrating example frequencies with oscillator adjustment and time-frequency synchronization, in accordance with various aspects of the present disclosure.

FIG. 14 is a diagram illustrating example communications between a first wireless device and a second wireless device, in accordance with various aspects of the present disclosure.

FIG. 15 is a diagram illustrating example communications between a first wireless device and a second wireless device, in accordance with various aspects of the present disclosure.

FIG. 16 is a diagram illustrating example communications between a first wireless device and a second wireless device, in accordance with various aspects of the present disclosure.

FIG. 17 is a flowchart of a method of wireless communication, in accordance with various aspects of the present disclosure.

FIG. 18 is a flowchart of a method of wireless communication, in accordance with various aspects of the present disclosure.

FIG. 19 is a flowchart of a method of wireless communication, in accordance with various aspects of the present disclosure.

FIG. 20 is a flowchart of a method of wireless communication, in accordance with various aspects of the present disclosure.

FIG. 21 is a diagram illustrating an example of a hardware implementation for an example apparatus and/or network entity.

FIG. 22 is a diagram illustrating an example of a hardware implementation for an example network entity

FIG. 23 is a diagram illustrating an example of a hardware implementation for an example apparatus.

DETAILED DESCRIPTION

In addition to higher capability devices, wireless communication systems may support devices having reduced capabilities or reduced complexity. Such devices may be configured for lower power consumption and may have a less complicated structure, while also having a higher frequency domain uncertainty

To address the frequency domain uncertainty associated with lower capability devices, in some wireless communication systems, a guard band may be provided that occupies frequency domain resources. Aspects provided herein may enable oscillator adjustment so that better communication reliability and data rate for wireless communication may be achieved independent of using a guard band. In some aspects, a clock error adjust method may be used and a wireless device (e.g., a reader in the form of a user equipment (UE) or a base station) may adjust an ambient Internet of Things (A-IoT) oscillator by explicit signaling. For example, one or more bits may be included in a forward link (FL) packet to qualitatively or quantitatively indicate an oscillator adjustment (OA) in the frequency domain for the A-IoT device. The one or more bits that may qualitatively or quantitatively indicate the OA may be referred to as “information for OA” or “OA information. ” In some aspects, the OA information may be in the form of a single bit indicating whether the oscillator may be adjusted to be faster or slower. In some aspects, the OA information may be in the form of one or more bits indicating the degree (e.g., a quantity in frequency) of adjustment.

The detailed description set forth below in connection with the drawings describes various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus 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 such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. When multiple processors are implemented, the multiple processors may perform the functions individually or in combination. 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 a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

Accordingly, in one or more example aspects, implementations, and/or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes 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 can include a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

While aspects, implementations, and/or use cases are described in this application by illustration to some examples, additional or different aspects, implementations and/or use cases may come about in many different arrangements and scenarios. Aspects, implementations, and/or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations, and/or use cases may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI) -enabled devices, etc. ) . While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described examples may occur. Aspects, implementations, and/or use cases may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques herein. In some practical settings, devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor (s) , interleaver, adders/summers, etc. ) . Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution.

Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. 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 a network equipment, such as a base station (BS) , or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB) , evolved NB (eNB) , NR BS, 5G NB, access point (AP) , a transmission reception point (TRP) , or a cell, etc. ) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.

An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among 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 throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU can be implemented as virtual units, i.e., a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) .

Base station operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance) ) , or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN) ) . Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.

FIG. 1 is a diagram 100 illustrating an example of a wireless communications system and an access network. The illustrated wireless communications system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that can 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) . A CU 110 may communicate with one or more DUs 130 via respective midhaul links, such as an F1 interface. The DUs 130 may communicate with one or more RUs 140 via respective fronthaul links. The RUs 140 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 140.

Each of the units, i.e., the CUs 110, the DUs 130, the RUs 140, as well as the Near-RT RICs 125, the Non-RT RICs 115, and the SMO Framework 105, may include one or more interfaces or be coupled to one or more interfaces configured to receive or to transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or to transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) , configured to receive or to transmit signals, or both, over a wireless transmission medium to one or more of the other units.

In some aspects, the CU 110 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) , packet data convergence protocol (PDCP) , service data adaptation protocol (SDAP) , or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 110. The 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 implementations, the CU 110 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface when implemented in an O-RAN configuration. The CU 110 can be implemented to communicate with the DU 130, as necessary, for network control and signaling.

The DU 130 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 140. In some aspects, the 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) encoding and decoding, scrambling, modulation, demodulation, or the like) depending, at least in part, on a functional split, such as those defined by 3GPP. In some aspects, the DU 130 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 130, or with the control functions hosted by the CU 110.

Lower-layer functionality can be implemented by one or more RUs 140. In some deployments, an RU 140, controlled by a 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, or the like) , or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU (s) 140 can be implemented to handle over the air (OTA) communication with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU (s) 140 can be controlled by the corresponding DU 130. In some scenarios, this configuration can enable the DU (s) 130 and the CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

The SMO Framework 105 may be configured to support RAN deployment and provisioning of non-virtualized 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 that may be managed via an operations 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 life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface) . Such virtualized network elements can include, but are not limited to, CUs 110, DUs 130, RUs 140 and Near-RT RICs 125. In some implementations, the SMO Framework 105 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 111, via an O1 interface. Additionally, in some implementations, the SMO Framework 105 can communicate directly with one or more RUs 140 via an O1 interface. The SMO Framework 105 also may include a Non-RT RIC 115 configured to support functionality of the SMO Framework 105.

The Non-RT RIC 115 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) /machine learning (ML) (AI/ML) workflows including model training and updates, 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 (such as via an A1 interface) the Near-RT RIC 125. The Near-RT RIC 125 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 110, one or more DUs 130, or both, as well as an O-eNB, with the Near-RT RIC 125.

In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC 125, the Non-RT RIC 115 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 125 and may be received at the SMO Framework 105 or the Non-RT RIC 115 from non-network data sources or from network functions. 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 for performance and employ AI/ML models to perform corrective actions through the SMO Framework 105 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies) .

At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Accordingly, a base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component indicated with dotted lines to signify 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 a UE 104. The base station 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station) . The small cells include femtocells, picocells, and microcells. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) . The communication links between the RUs 140 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to an RU 140 and/or downlink (DL) (also referred to as forward link) transmissions from an RU 140 to a UE 104. The communication links may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base station 102 /UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL) . The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .

Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the 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) . D2D communication may be through a variety of wireless D2D communications systems, such as for example, Bluetooth^TM (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG) ) , Wi-Fi^TM (Wi-Fi is a trademark of the Wi-Fi Alliance) based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

The wireless communications system may further include a Wi-Fi AP 150 in communication with UEs 104 (also referred to as Wi-Fi stations (STAs) ) via communication link 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the UEs 104 /AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. 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 a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz –300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz –24.25 GHz) . Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz –71 GHz) , FR4 (71 GHz –114.25 GHz) , and FR5 (114.25 GHz –300 GHz) . Each of these higher frequency bands falls within the EHF band.

With the above aspects in mind, unless specifically stated otherwise, the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and/or FR5, or may be within the EHF band.

The base station 102 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate beamforming. The base station 102 may transmit 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 transmit 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 and transmit directions for each of the base station 102 /UE 104. The transmit and receive directions for the base station 102 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

The base station 102 may include and/or be referred to as a gNB, Node B, 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 TRP, network node, network entity, network equipment, or some other suitable terminology. The base station 102 can be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and an RU, or as a disaggregated base station including one or more of a CU, a DU, and/or an RU. The set of base stations, which may include disaggregated base stations and/or aggregated base stations, may be referred to as next generation (NG) RAN (NG-RAN) .

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. The AMF 161 is the control node that processes the signaling between the UEs 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management. The 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, generally, 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, a position determination entity (PDE) , a serving mobile location center (SMLC) , a mobile positioning center (MPC) , or the like. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients/applications (e.g., emergency services) for accessing UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to compute the position of the UE 104. The NG-RAN may utilize one or more positioning methods in order to determine the position of the UE 104. Positioning the UE 104 may involve signal measurements, a position estimate, and an optional velocity computation based on the measurements. The signal measurements may be made by the UE 104 and/or the base station 102 serving the UE 104. The signals measured may be based on one or more of a satellite positioning system (SPS) 170 (e.g., one or more of a Global Navigation Satellite System (GNSS) , global position system (GPS) , non-terrestrial network (NTN) , or other satellite position/location system) , LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS) , sensor-based information (e.g., barometric pressure sensor, motion sensor) , NR enhanced cell ID (NR E-CID) methods, 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 other systems/signals/sensors.

Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player) , a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc. ) . The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices such as in a device constellation arrangement. One or more of these devices may collectively access the network and/or individually access the network.

In some aspects, the UE 104 or the base station 102 may be in communication with a tag 142. In some aspects, the term “tag” may refer to a wireless device that may support ambient powered transmission, support energy harvesting, support passive transmission, support backscatter transmission, or the like. In some aspects, a “tag” may also be referred to as a passive UE, passive devices, ambient IoT (which may also be referred to as passive IoT) (A-IoT) device, or other similar devices in any shape or form.

Referring again to FIG. 1, in some aspects, the tag 142 may include an oscillator adjustment (OA) component 199. In some aspects, the OA component 199 may be configured to receive, from a second wireless device, a forward link packet including information for OA. In some aspects, the OA component 199 may be further configured to communicate with the second wireless device after transmission of the forward link packet.

In certain aspects, the base station 102 or the UE 104 may include a OA component 198. In some aspects, the OA component 198 may be configured transmit, for a second wireless device, a forward link packet including information for OA. In some aspects, the OA component 198 may be further configured to communicate with the second wireless device after transmission of the forward link packet.

Although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, be, or be included in (e.g., be a component of) a base station (e.g., any base station described herein) , a UE (e.g., any UE described herein) , a network controller, an apparatus, a device, a computing system, an integrated access and backhauling (IAB) node, a distributed unit (DU) , a central unit (CU) , a remote/radio unit (RU) (which may also be referred to as a remote radio unit (RRU) ) , and/or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station or network entity. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first, second, and third network nodes may be different relative to these examples. Similarly, reference to a UE, base station, apparatus, device, computing system, or the like may include disclosure of the UE, base station, apparatus, device, computing system, or the like being a network node. For example, disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a specific example is broadened in accordance with this disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node) , the broader example of the narrower example may be interpreted in the reverse, but in a broad open-ended way. In the example above where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, a first set of one or more one or more components, a first processing entity, or the like configured to receive the information; and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second set of one or more components, a second processing entity, or the like.

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

FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by FIGs. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL) , where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe 3 being configured with slot format 1 (with all UL) . While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI) , or semi- statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI) . Note that the description infra applies also to a 5G NR frame structure that is TDD.

FIGs. 2A-2D illustrate a frame structure, and the aspects of the present disclosure may be applicable to other wireless communication technologies, which may have a different frame structure and/or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms) . Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for extended CP, each slot may include 12 symbols. The symbols on DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (for power limited scenarios; limited to a single stream transmission) . The number of slots within a subframe is based on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) (see Table 1) . The symbol length/duration may scale with 1/SCS.

Table 1: Numerology, SCS, and CP

For normal CP (14 symbols/slot) , different numerologies μ 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extended CP, the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology μ, there are 14 symbols/slot and 2^μ slots/subframe. The subcarrier spacing may be equal to 2^μ* 15 kHz, where μ is the numerology 0 to 4. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing. FIGs. 2A-2D provide an example of normal CP with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a particular numerology and CP (normal or extended) .

A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs) ) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs) . The number of bits carried by each RE depends on the modulation scheme.

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

FIG. 2B illustrates an example of various DL channels within a subframe of a frame. The 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 one BWP may be referred to as a control resource set (CORESET) . A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and/or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the DM-RS. The physical broadcast channel (PBCH) , which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) /PBCH block (also referred to as SS block (SSB) ) . The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) . The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and paging messages.

As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH) . The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRS) . The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACK and/or negative ACK (NACK) ) . The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and/or UCI.

FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. 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, SIBs) , 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 (ciphering, deciphering, integrity protection, integrity verification) , and handover support functions; RLC layer functionality associated with the transfer 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.

The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M-QAM) ) . The coded and modulated symbols may then be split into parallel streams. Each stream may 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 together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted 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 respective spatial stream for transmission.

At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the 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 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. 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 symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.

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

Similar to the functionality described in connection with the DL transmission by the base station 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression /decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC 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 TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 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 antenna 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.

The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

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

At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects in connection with OA component 198 of FIG. 1.

At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 may be configured to perform aspects in connection with OA component 198 of FIG. 1.

In addition to higher capability devices, wireless communication systems may support reduced capability (RedCap) devices. Among others, examples of higher capability devices include premium smartphones, V2X devices, URLLC devices, eMBB devices, etc. Among other examples, reduced capability devices may include wearables (e.g., smart watches, augmented reality glasses, virtual reality glasses, health and medical monitoring devices, etc. ) , industrial wireless sensor networks (IWSN) (e.g., pressure sensors, humidity sensors, motion sensors, thermal sensors, accelerometers, actuators, etc. ) , surveillance cameras, low-end smartphones, etc. For example, NR communication systems may support both higher capability devices and reduced capability devices. A reduced capability device may be referred to by various names, such as an NR light device, a low-tier device, or a lower tier device, among other examples. Reduced capability UEs may communicate based on various types of wireless communication. For example, smart wearables may transmit or receive communication based on low power wide area (LPWA) /mMTC, relaxed IoT devices may transmit or receive communication based on URLLC, sensors/cameras may transmit or receive communication based on eMBB, etc.

In addition to reduced capability devices, some devices having a lower capability than reduced capability devices including lower power consumption and a less complicated structure may be included in wireless communication systems. In some wireless communication systems, passive wireless devices such as zero-power passive IoT wireless devices may be included. Such passive wireless devices may be without active RF components and may perform transmissions based on backscatter communication and reception based on envelope detection or an envelope detector. Backscatter communication may modulate information on an incoming RF signal (which may be a carrier wave that may carry communication between other devices) by an adaptation of antenna load impedance. A passive wireless device may be battery-less or battery assisted. For example, a passive wireless device may operate based on energy harvesting from an incoming radio wave with or without a battery as an additional power source. A passive wireless device may have low power consumption, such as between 1 microwatt to 1000 microwatts. Such passive wireless devices may be devices for inventory management, wireless sensors, or the like. Passive devices may use backscatter communication to communicate with another network entity, such as a base station.

Backscatter communication may enable radio frequency identification (RFID) . For example, a reader may send a continuous waveform signal and interrogate commands. As a non-limiting example of a passive or semi-passive device, an RF tag may harvest energy from the continuous waveform signal and may respond to the interrogation by varying its input impedance (e.g., between conjugate match and strongly mismatched) , therefore modulating the backscattered signals. RFID is a rapidly growing technology impacting many industries due to its potential for inventory/asset management inside and outside warehouse, IoT, sustainable sensor networks in factories and/or agriculture, and smart home. RFID systems may include small transponders, which may be referred to as tags, emitting an information-bearing signal upon receiving a signal. RFID may be operated without battery at low operational expenditures (OPEX) and may use small amount of resources. Such RFID devices may involve less maintenance and may have a long life-cycle.

FIG. 4 is a diagram 400 illustrating an example RFID system. As shown in FIG. 4, an RFID system may include a reader 402 and a tag 404. The reader 402 may transmit, through an antenna, an electromagnetic (EM) signal to the tag 404 through a forward link (FL) . The tag 404 may detect the EM signal from the reader 402, for example, through an envelope detector and reflect or scatter the EM signal it encounters through a backward link (BL) back to the reader 402. The reflected EM signal may be modulated by the tag 404 to include the backscatter data for the reader 402. The term “FL” may refer to a link from RF source to the tag. The term “RF source” may refer to a transmitter of a signal (e.g., a modulated signal or a unmodulated signal which may be referred to as a FL carrier wave in the form of a continuous wave to power up tag) to the tag which may reflect the signal into a backscatter wave. The term “BL” may refer to a link from the tag to a reader. The term “reader” may refer to a receiver of the backscatter wave. On the FL, there may be FL data such as FL information, which may be commands, acknowledgment (ACK) , negative acknowledgment (NACK) , or the like. On the BL, there may be BL data such as BL information, which may be ACK/NACK, data from the tag, or the like. As used herein, the term “tag” may be used to refer to various types of devices that use ambient power or received RF power to transmit a signal. A tag is one example of a device that may be configured to perform the aspects described herein, and the concepts are not limited to a tag. Such devices may be also referred to as supporting ambient powered transmission, supporting energy harvesting, supporting passive transmission, supporting backscatter transmission, ambient IoT (which may also be referred to as passive IoT) (A-IoT) device which may include active A-IoT device or passive A-IoT device, passive UE, or the like. In some aspects, A-IoT device may be useful for supporting ultra-low complexity and ultra-low power devices, providing complexity and power consumption orders of magnitude lower than other types of IoT.

FIG. 5A is a diagram 500 illustrating an example implementation of zero power IoT (ZP IoT) communication, e.g., as an example of backscatter communication or passive communication. As shown in FIG. 5A, a network node 502 may directly communicate with a tag 504 through DL and UL communication. FIG. 5B is a diagram 550 illustrating another example implementation of ZP IoT communication. As shown in FIG. 5B, a network node 552 may communicate with a tag 554 through a UE 556. The UE 556 may work as a relay between the network node 552 and the tag 554. That is, the network node 552 may communicate with the UE 556 via the Uu interface (awireless interface that connects the UE 556 to the network node 552) , and the UE 556 may communicate with the tag 554 via the FL link and the BL link.

FIG. 6A is a diagram 600 illustrating an example of monostatic backscatter communication, in accordance with various aspects of the present disclosure. As illustrated in FIG. 6A, in monostatic backscatter systems, the RF source and the reader may be part of a same device, or the RF source function and the reader function may be performed by the same device. The RF source may be the transmitter 604 and the reader may be the receiver 614, which may share a same antenna and may communicate with the tag 610. For example, the antenna may transmit a signal (e.g., a modulated signal or a unmodulated signal) to the tag 610, and then receive a reflected signal (backscatter wave) from the tag 610.

FIG. 6B is a diagram 650 illustrating an example of bistatic backscatter communication, in accordance with various aspects of the present disclosure. As illustrated in FIG. 6B, in bistatic backscatter systems, the RF source and the reader may be difference device, e.g., the RF source may be transmitted by a first device, and a second device may function as a reader by receiving the backscattered signal. The RF source may be the transmitter 654, which may be connected to a transmit antenna 652 and the reader may be the receiver 664, which may be connected to a receive antenna 662. The RF source may transmit a signal to the tag 670 and the reader may receive the backscattered wave from the tag 670.

FIG. 7 is a diagram 700 illustrating another example of bistatic backscatter communication, in accordance with various aspects of the present disclosure. As illustrated in FIG. 7, a network node 702 may be an RF source and may transmit a signal via the FL 708 to the tag 704. The tag 704 may reflect the signal via the BL 710, which may be received by a second device (e.g., the reader 706 may receive the reflected signal) .

A low-power receiver may be a receiver separate from the main radio on a wireless device. The low-power receiver may be used for enabling lower power consumption at the wireless device and may have a much lower power consumption than the main radio. To save power, the main radio may enter a sleep mode and the low-power receiver may be periodically listening (which may also be referred to as “monitoring” ) to low-power receiver. A wireless device may periodically listen to the low-power receiver (e.g., periodically monitoring for a signal via the low-power receiver) , and the main radio may be in a sleep mode (e.g., off) . Upon receiving a low-power wake up signal (LP WUS) via the low-power receiver, the wireless device may turn on the main radio to enable data communications via the main radio.

As an example, the low-power receiver may be a companion receiver that supports monitoring with lower power than the main radio while the main radio is in a sleep state. The low-power receiver may wake up the main radio so that data communication may occur. For example, the low-power receiver may monitor for LP WUS at a first time occasion 62. Based on not receiving a LP WUS, the main radio may not wake up at the first time occasion. The low-power receiver may monitor for an LP WUS at a time occasion. Based on receiving the LP WUS, the main radio may wake up. The low-power receiver may consume less power than the main radio and may be powered separately from the main radio. In some aspects, the low-power receiver may not be used for bidirectional communication with a network entity (such as a base station) , and may be used for monitoring paging information so that main radio may be woken up for communication.

Usage of low-power receiver may reduce total power consumption because the awake time of the more power consuming main radio may be reduced. Usage of the low-power receiver may also reduce total latency. Because the low-power receiver consumes less power, it may enable more frequent low-power receiver monitoring and reduced average latency (e.g., less average latency compared to waking up main radio less frequently) while maintaining power efficiency. Example performance metrics for low-power receivers may include power consumption (which may be lower than sleep power of main radio to enable extended operation) . Example performance metrics for low-power receivers may include sensitivity where higher sensitivity enable better coverage. Power hungry blocks may be avoided for low power operation, resulting in poor sensitivity and potential coverage mismatch between a low-power radio and a main radio. Therefore, sensitivity at the low-power receiver may be a performance metric. Example performance metrics for low-power receivers may also include data rate, false alarm or false wake up probability (false wake up may result in more power consumption) , miss detection probability (miss detection may lead to poor reliability and increase delay) , and main radio wake-up time (which is correlated to overall latency) .

An LP WUS be used for paging reception and may be associated with a paging early indication. To enable a low-power receiver at a wireless device to perform radio resource management, time or frequency (T/F) tracking, and resynchronization, aspects provided herein may provide LP RS. The wireless device may use such a LP RS in various different configurations. For example, if the low-power receiver supports OOK waveform and the low-power receiver bandwidth is less than or equal to 5 MHz with a noise figure around 7 decibels, LP RS may be based on OOK for T/F synchronization and the LP RS may be based on OOK waveform. As another example, if the low-power receiver supports OOK waveform and the low-power receiver bandwidth is approximately 1 MHz with a noise figure approximately 5 decibels, LP RS may be used if minimum coupling loss (MCL) is 164 decibel or lower. MCL may be the minimum distance loss including antenna gain measured between antenna connectors. In another example, if the low-power receiver supports OOK waveform and the low-power receiver bandwidth is approximately 5 MHz with a noise figure approximately 5 decibels, the wireless device might be able to not use LP RS to satisfy a MCL of 140 decibels. As used herein, the term “LP RS” may refer to a signal received via a low-power receiver that is used for T/F tracking and radio resource management. LP RS may be carried on LP RS resources (which may be arranged as LP RS resource sets) . The term “LP WUS” may refer to a signal received via a low-power receiver that is used for waking up the main radio and may be associated with a paging early indication, an idle discontinuous reception (DRX) cycle (e.g., associated with paging monitoring occasions) , wakeup monitoring occasions associated with a connected-mode DRX cycle, or the like. In some aspects, the term “monitoring occasion” may refer to a configured time occasion where a UE is configured to monitor a transmission. In some aspects a low power wakeup receiver may be referred to as a low power wakeup radio and a main receiver may be referred to as a main radio, and vice versa. As described herein, reference to a radio may include reference to a radio, a receiver, or a transceiver; and vice versa. For example, a low power receiver may also be referred to as a low power radio, a low power transceiver, or the like. As another example, a main receiver may also be referred to as a main radio, a main transceiver, or the like. As another example, a main radio may also be referred to as a main receiver, a main transceiver, or the like. The term “power state” may refer to a power state of a main radio. For example, the main radio may wake up from a sleep state, an off state, or another state where the main radio is configured to refrain from receiving or transmitting some (or all) communications to save power to an on state or an awake state.

Different A-IoT device may transmit or receive signaling based on various forms of modulation, such as frequency shift keying (FSK) , amplitude shift keying (ASK) , or phase shift keying (PSK) , on-off keying (OOK) , or the like. As an example, an A-IoT active device may include a crystal oscillator with a frequency offset, such as 20 parts per million (PPM) frequency offset. For time domain synchronization, a LP RS, such as a LP synchronization signal (LP SS) may be used in connection with LP SS correlation and detection to facilitate time domain synchronization. For the frequency domain, with an offset of 20 PPM and a 3.5 GHz being used for BL communications, there may be a 70KHz uncertainty in BL communications. As an example, a maximum allowed frequency uncertainty may be equal to 100 KHz. Therefore, for a 20 PPM frequency offset, the A-IoT active device may still be able to have a frequency uncertainty below the maximum allowed frequency uncertainty without frequency domain synchronization. However, if the oscillator has a larger offset, e.g., a offset higher than 30 PPM, the A-IoT device may be have a frequency uncertainty above the maximum allowed frequency uncertainty without frequency domain synchronization. Therefore, whether A-IoT device that includes a crystal oscillator would use frequency domain synchronization may depend on the frequency offset.

Some A-IoT active devices may include a crystal-free oscillator instead of a crystal oscillator. As an example, a crystal-free oscillator may have a frequency offset of plus or minus one percent. For the time domain, various reference signals such as LP SS or a preamble may be used to facilitate time domain synchronization. For the frequency domain, with an offset of plus or minus one percent and a 3.5 GHz being used for BL communications, there may be a 70MHz uncertainty in BL communications. As an example, a maximum allowed frequency uncertainty may be equal to 100 KHz. Therefore, for a plus or minus one percent frequency offset, the A-IoT device may have a frequency uncertainty above the maximum allowed frequency uncertainty without frequency domain synchronization. Therefore, an A-IoT active device that includes a crystal-free oscillator may use frequency domain synchronization.

For A-IoT passive or semi-passive devices that include a crystal-free oscillator, as an example, the frequency offset may be plus or minus ten percent before calibration or the like. For such a frequency offset, the A-IoT device may have a frequency uncertainty above the maximum allowed frequency uncertainty without frequency domain synchronization. Therefore, A-IoT passive or semi-passive devices that include a crystal-free oscillator may use frequency domain synchronization or calibration. As used herein, a frequency error may be caused by a frequency uncertainty and may be a difference in frequency, after adjustment for the effect of the modulation and phase error, between the frequency of a transmission from the A-IoT device and a frequency in which the A-IoT device may be configured to transmit. For example, a network entity may measure a frequency error associated with the A-IoT device based on a particular transmission because the network entity may have information regarding the frequency in which the A-IoT device may be configured to transmit.

For some A-IoT devices (e.g., passive devices, semi-passive devices, or active devices) , due to clock quality, the frequency domain uncertainty may be large. As an example, some A-IoT active devices may have an internal oscillator that generates local oscillator (LO) (e.g., 700MHz) signal with nearly +-200ppm uncertainty. As another example, some A-IoT passive device or semi-passive device may receive external carrier wave (CW) signal (e.g., 700MHz and 0.5ppm) , with no larger than 20MHz frequency shift (<1%error) applied. Unlike full capability devices, the A-IoT device might not support FFT that may correct frequency error by itself with reference signals. FIG. 8 is a diagram 800 illustrating example BL communications with and without frequency uncertainty, in accordance with various aspects of the present disclosure. As illustrated in FIG. 8, BL channel of a first device 802 and BL channel of a second device 804 may not overlap without frequency domain uncertainty. However, due to frequency domain uncertainty that may be present at both devices, in reality, with frequency domain uncertainty, BL channel 812 of a first device and BL channel 814 of a second device may overlap, causing potential conflict and loss of packet.

To address the frequency domain uncertainty associated with lower capability devices, in some wireless communication systems, a guard band may be provided that occupies frequency domain resources. Aspects provided herein may enable oscillator adjustment so that better communication reliability and data rate for wireless communication may be achieved independent of using a guard band. In some aspects, a clock error adjust method may be used and a wireless device (e.g., a reader in the form of a UE or a base station) may adjust an A-IoT oscillator by explicit signaling. For example, one or more bits may be included in a FL packet to qualitatively or quantitatively indicate a degree of oscillator adjustment (OA) in the frequency domain for the A-IoT device. The one or more bits that may qualitatively or quantitatively indicate the degree of OA may be referred to as “information for OA” or “OA information. ” In some aspects, the OA information may be in the form of a single bit indicating whether oscillator is to be adjusted to be faster or slower. In some aspects, the OA information may be in the form of one or more bits indicating the degree of adjustment. For example, in some aspects, the degree of adjustment may be based on a granularity based on SCS, a granularity based on one divided by N times SCS (N being an integer) , or based on a different configured granularity (configured without signaling or based on signaling) . As a particular example, if the OA information includes two bits, “00” may indicate an adjustment of plus 50 KHz, “01” may indicate an adjustment of plus 100 KHz, “10” may indicate an adjustment of minus 100 KHz, “11” may indicate an adjustment of minus 50 KHz.

FIG. 9 is a diagram 900 illustrating example FL packet used for oscillator adjustment, in accordance with various aspects of the present disclosure. As illustrated in FIG. 9, the FL packet 902 may include one or more bits 904 to qualitatively or quantitatively indicate degree of OA in the frequency domain for adjustment of an oscillator 906 of an A-IoT device.

The explicit signaling for indicating OA may be used in connection with time-frequency synchronization signals (e.g., OOK or single tone) . FIG. 10 is a diagram 1000 illustrating an example time-frequency synchronization signal in FL used for facilitating BL communications, in accordance with various aspects of the present disclosure. As illustrated in FIG. 10, on the FL, the CW 1002 may be transmitted for powering up an A-IoT device. Time synchronization signal 1004 and frequency synchronization signal 1006 may follow after the CW 1002. After the time synchronization signal 1004 and the frequency synchronization signal 1006, the FL control or data channel 1008 may be transmitted. On the BL, the A-IoT device may transmit the BL control or data channel 1012, 1014, and 1016. In some aspects, the A-IoT device may also transmit an UL scheduling trigger signal 1018 to schedule another transmission. In some aspects, time-frequency synchronization signals may be transmitted periodically so that the A-IoT device may periodically correct frequency domain errors or time domain errors. In some aspects, time-frequency synchronization signals may be transmitted aperiodically so that the A-IoT device may aperiodically correct frequency domain error or time domain error.

FIG. 11 is a diagram 1100 illustrating an example time domain synchronization signal and frequency domain synchronization signal, in accordance with various aspects of the present disclosure. As illustrated in FIG. 11, OOK preamble 1102 associated with an OOK payload 1104 may be used for time domain synchronization and single tone 1106 may be used for frequency domain synchronization.

In some aspects, if the A-IoT device oscillator frequency changes, e.g., due to temperature change, the reader (e.g., in the form of a UE or a base station) may indicate the A-IoT device to change oscillator frequency (e.g., based on OA) accordingly. FIG. 12 is a diagram 1200 illustrating example oscillator adjustment in connection with synchronization signals, in accordance with various aspects of the present disclosure. As illustrated in FIG. 12, time-frequency synchronization signals including synchronization signal 1202A, synchronization signal 1202B, and synchronization signal 1202C may be periodically transmitted to an A-IoT device with an example periodicity of one second. A temperature change (as indicated by an arrow in FIG. 12) may occur before a BL packet 1212A, causing BL packet 1212A and BL packet 1212B to have a change in frequency. The reader may detect the change in frequency and based on the change in frequency, the reader may transmit a FL packet including OA information 1204 to the A-IoT device. The A-IoT device may receive the FL packet including OA information 1204 and BL packet 1212C, and subsequent BL packets, such as BL packet 1214A, BL packet 1214B, and BL packet 1214C may be corrected.

FIG. 13 is a diagram 1300 illustrating example synchronization signals used in connection with oscillator adjustment, in accordance with various aspects of the present disclosure. As illustrated in FIG. 13, an initial frequency (e.g., without any adjustment) may be provided at 1302. With time and frequency synchronization, the frequency may be adjusted to 1304, which may be still away from the target frequency by more than a threshold. In some aspects, after performing OA based on OA information included in FL packet, the frequency may be adjusted to 1306, which may be in line with the target frequency. As an example, the threshold may be a threshold in the form of a particular number of PPM or in the form of a particular number of Hertz.

In some aspects, the FL packet including the OA information may be initiated based on measurement of the oscillator at the A-IoT device performed by the reader. In some aspects, the measurement may be based on dedicated oscillator error (OE) measurement procedure, which may be initialized by the reader. In some aspect, the measurement may be based on measuring a BL packet from the A-IoT device that may have another purpose, such as measuring a BL packet that may be part of a RACH procedure (e.g., RACH message B or message 2) .

FIG. 14 is a diagram 1400 illustrating example communications between a first wireless device 1402, which may be a reader, and a second wireless device 1404, which may be an A-IoT device such as a passive A-IoT device, in accordance with various aspects of the present disclosure. The first wireless device 1402 may transmit an OE measurement trigger 1412 to the second wireless device 1404. The first wireless device 1402 may also transmit a CW 1414 to the second wireless device 1404 to facilitate a response from the second wireless device 1404 because the second wireless device 1404 may be a passive or semi-passive device that may use the CW 1414 to reflect a response. After receiving the CW 1414, the second wireless device 1404 may transmit a response in the form of the CW plus a frequency shift 1416 (e.g., apply frequency shift to CW as response) . In some aspects, the second wireless device 1404 may apply frequency shift plus a sequence known to the first wireless device 1402 as response, where the sequence may be either configured at both devices without signaling, or configured by the first wireless device 1402. In some aspects, the second wireless device 1404 may apply BL frequency hopping as response. A frequency hopping pattern used for the BL frequency hopping may be either configured at both devices without signaling, or configured by the first wireless device 1402. Based on receiving the response (at 1416) , the first wireless device 1402 may perform measurements and transmit OA information 1418 in a FL packet to the second wireless device 1404. After receiving the OA information 1418 in a FL packet, at 1420, the second wireless device 1404 may adjust an oscillator at the second wireless device 1404. Therefore, subsequent communications 1422 between the first wireless device 1402 and the second wireless device 1404 may be based on the adjusted oscillator. For example, subsequent UL/BL, or DL/FL communications between the first wireless device 1402 and the second wireless device 1404 may be based on the adjusted oscillator.

FIG. 15 is a diagram 1500 illustrating example communications between a first wireless device and a second wireless device, in accordance with various aspects of the present disclosure. FIG. 15 is a diagram 1500 illustrating example communications between a first wireless device 1502, which may be a reader, and a second wireless device 1504, which may be an A-IoT device such as an active A-IoT device, in accordance with various aspects of the present disclosure. The first wireless device 1502 may transmit an OE measurement trigger 1512 to the second wireless device 1504. After receiving the OE measurement trigger 1512 the second wireless device 1504 may transmit a response 1516 to the first wireless device 1502. Based on receiving the response (at 1516) , the first wireless device 1502 may perform measurements and transmit OA information 1518 in a FL packet to the second wireless device 1504. After receiving the OA information 1518 in a FL packet, at 1520, the second wireless device 1504 may adjust an oscillator at the second wireless device 1504. Therefore, subsequent communications 1522 between the first wireless device 1502 and the second wireless device 1504 may be based on the adjusted oscillator.

FIG. 16 is a diagram 1600 illustrating example communications between a first wireless device 1602 and a second wireless device 1604, in accordance with various aspects of the present disclosure. The second wireless device 1604 may initiate a RACH procedure by transmitting a RACH preamble 1612 (Msg 1 or first random access message) to the first wireless device 1602. In some aspects, the first wireless device 1602 may measure the RACH preamble 1612 to determine whether an oscillator at the second wireless device 1604 may be adjusted. If the first wireless device 1602 determines that an oscillator at the second wireless device 1604 may be adjusted based on the measurement of the RACH preamble 1612, the first wireless device may transmit the OA adjustment information in connection with (e.g., included in or multiplexed with) a RACH Msg 2 (acknowledgment 1614 associated with the preamble 1612, which may be referred to as a second random access message) .

The second wireless device 1604 may transmit a RACH Msg 3 1616 (e.g., a third random access message) to the first wireless device 1602. In some aspects, the first wireless device 1602 may measure the RACH Msg 3 1616 to determine whether an oscillator at the second wireless device 1604 may be adjusted. If the first wireless device 1602 determines that an oscillator at the second wireless device 1604 may be adjusted based on the measurement of the RACH Msg 3 1616, the first wireless device may transmit the OA adjustment information in connection with (e.g., included in or multiplexed with) a RACH Msg 4 1618 (e.g., a fourth random access message) .

There may be subsequent communications including read 1620 and read 1624, and associated responses including response 1622 and response 1626. In some aspects, the first wireless device 1602 may measure the response 1622 and the response 1626 to determine whether an oscillator at the second wireless device 1604 may be adjusted.

FIG. 17 is a flowchart 1700 of a method of wireless communication. The method may be performed by a wireless device (e.g., the base station 102, 310, the network entity 2102, the network entity 2202, the UE 104, 350, the first wireless device 1402, the first wireless device 1502, the first wireless device 1602, the apparatus 2104) . The method may enable OA for A-IoT device so that better communication reliability and data rate for wireless communication may be achieved.

At 1706, the first wireless device may transmit, for a second wireless device, a forward link packet including information for OA. For example, the first wireless device (e.g., 1402, 1502, or 1602) may transmit, for a second wireless device (e.g., 1404, 1504, or 1604) , a forward link packet (e.g., 1418, 1518, or in any of 1614, 1618, 1620, or 1624) including information for OA. In some aspects, 1706 may be performed by OA component 198.

At 1708, the first wireless device may communicate with the second wireless device after transmission of the forward link packet. For example, the first wireless device may communicate with the second wireless device after transmission of the forward link packet (e.g., 1418, 1518, or in any of 1616, 1622, or 1626) . In some aspects, 1708 may be performed by OA component 198.

FIG. 18 is a flowchart 1800 of a method of wireless communication. The method may be performed by a wireless device (e.g., the base station 102, 310, the network entity 2102, the network entity 2202, the UE 104, 350, the first wireless device 1402, the first wireless device 1502, the first wireless device 1602, the apparatus 2104) . The method may enable OA for A-IoT device so that better communication reliability and data rate for wireless communication may be achieved.

In some aspects, at 1802A, the first wireless device may transmit a trigger to start a dedicated OE measurement. For example, the first wireless device may transmit (e.g., at 1412 or 1512) a trigger to start a dedicated OE measurement. In some aspects, 1802A may be performed by OA component 198.

In some aspects, at 1804A, the first wireless device may receive a response associated with the dedicated OE measurement. For example, the first wireless device may receive (e.g., at 1416 or 1516) a response associated with the dedicated OE measurement. In some aspects, 1804A may be performed by OA component 198. In some aspects, the trigger is included in a carrier wave, and where the response is a sequence configured for the dedicated OE measurement. In some aspects, the trigger is included in a carrier wave, and where the response is based on a frequency hopping pattern configured for the dedicated OE measurement.

In some aspects, at 1802B, the first wireless device may receive a backlink packet from the second wireless device. For example, the first wireless device may receive a backlink packet from the second wireless device. In some aspects, 1802B may be performed by OA component 198. In some aspects, the backlink packet may be a random access message.

In some aspects, at 1804B, the first wireless device may measure a frequency error associated with an oscillator of the second wireless device based on the backlink packet from the second wireless device. For example, the first wireless device may measure a frequency error associated with an oscillator of the second wireless device based on the backlink packet from the second wireless device. In some aspects, 1804B may be performed by OA component 198.

At 1806, the first wireless device may transmit, for a second wireless device, a forward link packet including information for OA. For example, the first wireless device (e.g., 1402, 1502, or 1602) may transmit, for a second wireless device (e.g., 1404, 1504, or 1604) , a forward link packet (e.g., 1418, 1518, or in any of 1614, 1618, 1620, or 1624) including information for OA. In some aspects, 1806 may be performed by OA component 198.

In some aspects, as part of 1806, at 1812, the first wireless device may periodically transmit time-frequency synchronization signal including the forward link packet including the information for the OA. In some aspects, as part of 1806, at 1814, the first wireless device may aperiodically transmit a time-frequency synchronization signal with the forward link packet including the information for the OA. In some aspects, as part of 1806, at 1816, the first wireless device may transmit the forward link packet based on a completion of time-frequency synchronization with the second wireless device. In some aspects, as part of 1806, at 1818, the first wireless device may transmit the forward link packet based on a change in an oscillator frequency associated with the second wireless device. In some aspects, as part of 1806, the first wireless device may transmit the forward link packet including the information for the OA based on the response. In some aspects, the information includes at least one bit indicating an instruction to adjust a frequency at an oscillator of the second wireless device based on a frequency granularity or a direction. In some aspects, the first wireless device may transmit, based on (e.g., triggered by) a value of the frequency error exceeding a threshold, the forward link packet including the information for the OA.

At 1808, the first wireless device may communicate with the second wireless device after transmission of the forward link packet. For example, the first wireless device may communicate with the second wireless device after transmission of the forward link packet (e.g., 1418, 1518, or in any of 1616, 1622, or 1626) . In some aspects, 1808 may be performed by OA component 198.

FIG. 19 is a flowchart 1900 of a method of wireless communication. The method may be performed by a first wireless device (e.g., the tag 142, the wireless device 1404, 1504, or 1604, the apparatus 2304) . The method may enable OA for A-IoT device so that better communication reliability and data rate for wireless communication may be achieved.

At 1906, the first wireless device may receive, from a second wireless device, a forward link packet including information for OA. For example, the first wireless device (e.g., 1404, 1504, or 1604) may receive, from a second wireless device (e.g., 1402, 1502, or 1602) , a forward link packet (e.g., 1418, 1518, or in any of 1614, 1618, 1620, or 1624) including information for OA. In some aspects, 1906 may be performed by OA component 198.

At 1908, the first wireless device may adjust the oscillator based on the information for the OA. For example, the first wireless device may adjust the oscillator based on the information for the OA (e.g., at 1420, 1520, or after any of 1614, 1618, 1620, or 1624) . In some aspects, 1908 may be performed by OA component 198.

FIG. 20 is a flowchart 2000 of a method of wireless communication. The method may be performed by a first wireless device (e.g., the tag 142, the wireless device 1404, 1504, or 1604, the apparatus 2304) . The method may enable OA for A-IoT device so that better communication reliability and data rate for wireless communication may be achieved.

In some aspects, at 2002A, the first wireless device may receive a trigger to start a dedicated OE measurement. For example, the first wireless device may receive a trigger to start a dedicated OE measurement. In some aspects, 2002A may be performed by OA component 198.

In some aspects, at 2004A, the first wireless device may generate the dedicated OE measurement and transmit a response associated with the dedicated OE measurement. For example, the first wireless device may generate the dedicated OE measurement and transmit a response associated with the dedicated OE measurement. In some aspects, 2004A may be performed by OA component 198. In some aspects, the trigger is included in a carrier wave, and where the response is a sequence configured for the dedicated OE measurement. In some aspects, the trigger is included in a carrier wave, and where the response is based on a frequency hopping pattern configured for the dedicated OE measurement.

In some aspects, at 2002B, the first wireless device may transmit a first BL packet (e.g., in a random access message) to the second wireless device. In some aspects, 2002B may be performed by OA component 198. The first wireless device may receive the forward link packet including the information for the OA in a second random access message. The first wireless device may receive the forward link packet including the information for the OA based on the response.

At 2006, the first wireless device may receive, from a second wireless device, a forward link packet including information for OA. For example, the first wireless device (e.g., 1404, 1504, or 1604) may receive, from a second wireless device (e.g., 1402, 1502, or 1602) , a forward link packet (e.g., 1418, 1518, or in any of 1614, 1618, 1620, or 1624) including information for OA. In some aspects, 2006 may be performed by OA component 198.

In some aspects, as part of 2006, at 2012, the first wireless device may periodically receive time-frequency synchronization signal including the forward link packet including the information for the OA. In some aspects, as part of 2006, at 2014, the first wireless device may aperiodically receive a time-frequency synchronization signal with the forward link packet including the information for the OA. In some aspects, as part of 2006, at 2016, the first wireless device may receive the forward link packet after a completion of time-frequency synchronization with the second wireless device.

At 2008, the first wireless device may adjust the oscillator based on the information for the OA. For example, the first wireless device may adjust the oscillator based on the information for the OA (e.g., at 1420, 1520, or after any of 1614, 1618, 1620, or 1624) . In some aspects, 2008 may be performed by OA component 198.

FIG. 21 is a diagram 2100 illustrating an example of a hardware implementation for an apparatus 2104. The apparatus 2104 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 2104 may include at least one cellular baseband processor 2124 (also referred to as a modem) coupled to one or more transceivers 2122 (e.g., cellular RF transceiver) . The cellular baseband processor (s) 2124 may include at least one on-chip memory 2124'. In some aspects, the apparatus 2104 may further include one or more subscriber identity modules (SIM) cards 2120 and at least one application processor 2106 coupled to a secure digital (SD) card 2108 and a screen 2110. The application processor (s) 2106 may include on-chip memory 2106'. In some aspects, the apparatus 2104 may further include a Bluetooth module 2112, a WLAN module 2114, an SPS module 2116 (e.g., GNSS module) , one or more sensor modules 2118 (e.g., barometric pressure sensor /altimeter; motion sensor such as inertial measurement unit (IMU) , gyroscope, and/or accelerometer (s) ; light detection and ranging (LIDAR) , radio assisted detection and ranging (RADAR) , sound navigation and ranging (SONAR) , magnetometer, audio and/or other technologies used for positioning) , additional memory modules 2126, a power supply 2130, and/or a camera 2132. The Bluetooth module 2112, the WLAN module 2114, and the SPS module 2116 may include an on-chip transceiver (TRX) (or in some cases, just a receiver (RX) ) . The Bluetooth module 2112, the WLAN module 2114, and the SPS module 2116 may include their own dedicated antennas and/or utilize the antennas 2180 for communication. The cellular baseband processor (s) 2124 communicates through the transceiver (s) 2122 via one or more antennas 2180 with the UE 104 and/or with an RU associated with a network entity 2102. The cellular baseband processor (s) 2124 and the application processor (s) 2106 may each include a computer-readable medium /memory 2124', 2106', respectively. The additional memory modules 2126 may also be considered a computer-readable medium /memory. Each computer-readable medium /memory 2124', 2106', 2126 may be non-transitory. The cellular baseband processor (s) 2124 and the application processor (s) 2106 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 (s) 2124 /application processor (s) 2106, causes the cellular baseband processor (s) 2124 /application processor (s) 2106 to perform the various functions described supra. The computer-readable medium /memory may also be used for storing data that is manipulated by the cellular baseband processor (s) 2124 /application processor (s) 2106 when executing software. The cellular baseband processor (s) 2124 /application processor (s) 2106 may be a component of the UE 350 and may include the at least one 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 apparatus 2104 may be at least one processor chip (modem and/or application) and include just the cellular baseband processor (s) 2124 and/or the application processor (s) 2106, and in another configuration, the apparatus 2104 may be the entire UE (e.g., see UE 350 of FIG. 3) and include the additional modules of the apparatus 2104.

As discussed supra, the OA component 198 may be configured transmit, for a second wireless device, a forward link packet including information for OA. In some aspects, the OA component 198 may be further configured to communicate with the second wireless device after transmission of the forward link packet. The OA component 198 and/or the apparatus 2104 may be further configured to perform any of the aspects described in connection with the flowchart in FIG. 17 and FIG. 18 and/or performed by the wireless device 1402, 1502, or 1602 in FIG. 14, FIG. 15, or FIG. 16. The OA component 198 may be within the cellular baseband processor (s) 2124, the application processor (s) 2106, or both the cellular baseband processor (s) 2124 and the application processor (s) 2106. The component 198 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes/algorithm individually or in combination. As shown, the apparatus 2104 may include a variety of components configured for various functions. In one configuration, the apparatus 2104, and in particular the cellular baseband processor (s) 2124 and/or the application processor (s) 2106, may include means for transmitting, for a second wireless device, a forward link packet including information for oscillator adjustment (OA) . In some aspects, the apparatus 2104 may include means for communicating with the second wireless device after transmission of the forward link packet. In some aspects, the apparatus 2104 may include means for periodically transmitting time-frequency synchronization signal including the forward link packet including the information for the OA. In some aspects, the apparatus 2104 may include means for aperiodically transmitting a time-frequency synchronization signal with the forward link packet including the information for the OA. In some aspects, the apparatus 2104 may include means for transmitting the forward link packet based on a completion of time-frequency synchronization with the second wireless device. In some aspects, the apparatus 2104 may include means for transmitting the forward link packet based on a change in an oscillator frequency associated with the second wireless device. In some aspects, the apparatus 2104 may include means for transmitting a trigger to start a dedicated oscillator error (OE) measurement. In some aspects, the apparatus 2104 may include means for receiving a response associated with the dedicated OE measurement. In some aspects, the apparatus 2104 may include means for transmitting the forward link packet including the information for the OA based on the response. In some aspects, the apparatus 2104 may include means for receiving a first random access message from the second wireless device. In some aspects, the apparatus 2104 may include means for measuring a frequency error associated with an oscillator of the second wireless device based on the first random access message from the second wireless device. In some aspects, the apparatus 2104 may include means for transmitting, based on a value of the frequency error exceeding a threshold, the forward link packet including the information for the OA in a second random access message. In some aspects, the apparatus 2104 may include means for receiving a backlink packet from the second wireless device. In some aspects, the apparatus 2104 may include means for measuring a frequency error associated with an oscillator of the second wireless device based on the backlink packet from the second wireless device. In some aspects, the apparatus 2104 may include means for transmitting, based on a value the frequency error exceeding a threshold, the forward link packet including the information for the OA. The apparatus 2104 may include means for performing any of the aspects described in connection with the flowchart in FIG. 17 and FIG. 18 and/or performed by the wireless device 1402, 1502, or 1602 in FIG. 14, FIG. 15, or FIG. 16. The means may be the component 198 of the apparatus 2104 configured to perform the functions recited by the means. As described supra, the apparatus 2104 may include the TX processor 368, the RX processor 356, and the controller/processor 359. As such, in one configuration, the 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.

FIG. 22 is a diagram 2200 illustrating an example of a hardware implementation for a network entity 2202. The network entity 2202 may be a BS, a component of a BS, or may implement BS functionality. The network entity 2202 may include at least one of a CU 2210, a DU 2230, or an RU 2240. For example, depending on the layer functionality handled by the component 198, the network entity 2202 may include the CU 2210; both the CU 2210 and the DU 2230; each of the CU 2210, the DU 2230, and the RU 2240; the DU 2230; both the DU 2230 and the RU 2240; or the RU 2240. The CU 2210 may include at least one CU processor 2212. The CU processor (s) 2212 may include on-chip memory 2212'. In some aspects, the CU 2210 may further include additional memory modules 2214 and a communications interface 2218. The CU 2210 communicates with the DU 2230 through a midhaul link, such as an F1 interface. The DU 2230 may include at least one DU processor 2232. The DU processor (s) 2232 may include on-chip memory 2232'. In some aspects, the DU 2230 may further include additional memory modules 2234 and a communications interface 2238. The DU 2230 communicates with the RU 2240 through a fronthaul link. The RU 2240 may include at least one RU processor 2242. The RU processor (s) 2242 may include on-chip memory 2242'. In some aspects, the RU 2240 may further include additional memory modules 2244, one or more transceivers 2246, antennas 2280, and a communications interface 2248. The RU 2240 communicates with the UE 104. The on-chip memory 2212', 2232', 2242'a nd the additional memory modules 2214, 2234, 2244 may each be considered a computer-readable medium /memory. Each computer-readable medium /memory may be non-transitory. Each of the processors 2212, 2232, 2242 is responsible for general processing, including the execution of software stored on the computer-readable medium /memory. The software, when executed by the corresponding processor (s) causes the processor (s) to perform the various functions described supra. The computer-readable medium /memory may also be used for storing data that is manipulated by the processor (s) when executing software.

As discussed supra, the OA component 198 may be configured transmit, for a second wireless device, a forward link packet including information for OA. In some aspects, the OA component 198 may be further configured to communicate with the second wireless device after transmission of the forward link packet. The OA component 198 and/or the network entity 2202 may be further configured to perform any of the aspects described in connection with the flowchart in FIG. 17 or FIG. 18 and/or performed by the wireless device 1402, 1502, or 1602 in FIG. 14, FIG. 15, or FIG.

16. The OA component 198 may be within one or more processors of one or more of the CU 2210, DU 2230, and the RU 2240. The component 198 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes/algorithm individually or in combination. The network entity 2202 may include a variety of components configured for various functions. In one configuration, the network entity 2202 may include means for transmitting, for a second wireless device, a forward link packet including information for oscillator adjustment (OA) . In some aspects, the network entity 2202 may include means for communicating with the second wireless device after transmission of the forward link packet. In some aspects, the network entity 2202 may include means for periodically transmitting time-frequency synchronization signal including the forward link packet including the information for the OA. In some aspects, the network entity 2202 may include means for aperiodically transmitting a time-frequency synchronization signal with the forward link packet including the information for the OA. In some aspects, the network entity 2202 may include means for transmitting the forward link packet based on a completion of time-frequency synchronization with the second wireless device. In some aspects, the network entity 2202 may include means for transmitting the forward link packet based on a change in an oscillator frequency associated with the second wireless device. In some aspects, the network entity 2202 may include means for transmitting a trigger to start a dedicated oscillator error (OE) measurement. In some aspects, the network entity 2202 may include means for receiving a response associated with the dedicated OE measurement. In some aspects, the network entity 2202 may include means for transmitting the forward link packet including the information for the OA based on the response. In some aspects, the network entity 2202 may include means for receiving a first random access message from the second wireless device. In some aspects, the network entity 2202 may include means for measuring a frequency error associated with an oscillator of the second wireless device based on the first random access message from the second wireless device. In some aspects, the network entity 2202 may include means for transmitting, based on a value of the frequency error exceeding a threshold, the forward link packet including the information for the OA in a second random access message. In some aspects, the network entity 2202 may include means for receiving a backlink packet from the second wireless device. In some aspects, the network entity 2202 may include means for measuring a frequency error associated with an oscillator of the second wireless device based on the backlink packet from the second wireless device. In some aspects, the network entity 2202 may include means for transmitting, based on a value of the frequency error exceeding a threshold, the forward link packet including the information for the OA. The network entity 2202 may include means for performing any of the aspects described in connection with the flowchart in FIG. 17 or FIG. 18 and/or performed by the wireless device 1402, 1502, or 1602 in FIG. 14, FIG. 15, or FIG. 16. The means may be the component 198 of the network entity 2202 configured to perform the functions recited by the means. As described supra, the network entity 2202 may include the TX processor 316, the RX processor 370, and the controller/processor 375. As such, in one configuration, the means may be the TX processor 316, the RX processor 370, and/or the controller/processor 375 configured to perform the functions recited by the means.

FIG. 23 is a diagram 2300 illustrating an example of a hardware implementation for an apparatus 2304. The apparatus may be support energy harvesting, backscatter transmissions, ambient communication, passive communication, etc. The apparatus may be a tag, a PUE, an ambient IoT device, a passive device, an energy harvesting device, etc. The apparatus may include aspects described in connection with FIG. 4A to 9C, among other examples. In some aspects, the apparatus 2304 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 2304 may include a processor 2324 coupled to one or more antennas 2380. The apparatus may include an energy harvesting component 2320, which may provide power to a storage device 2330 and/or to the processor 2324. The processor 2324 may include memory 2324'. In some aspects, the apparatus 2304 may further include an SPS module 2316 (e.g., GNSS module) , one or more sensor modules 2318 (e.g., barometric pressure sensor /altimeter; motion sensor such as inertial measurement unit (IMU) , gyroscope, and/or accelerometer (s) ; light detection and ranging (LIDAR) , radio assisted detection and ranging (RADAR) , sound navigation and ranging (SONAR) , magnetometer, audio and/or other technologies used for positioning) , additional memory modules 2326, and/or a power supply or storage device 2330. The SPS module 2316 may include an on-chip transceiver (TRX) (or in some cases, just a receiver (RX) ) . The SPS module 2316 may include its own dedicated antennas and/or utilize the antennas 2380 for communication. The processor 2324 may receive a signal, such as a backscatter signal, and the apparatus may harvest energy from the received signal. The processor 2324 receives the signal via the one or more antennas 2380, e.g., from the UE 104, reader 2332 (e.g., which may be a base station, a UE, or a different device) and/or with an RU associated with a network entity 2302. The processor 2324 may include a computer-readable medium /memory 2324'. The additional memory modules 2326 may also be considered a computer-readable medium /memory. Each computer-readable medium /memory 2324', 2326 may be non-transitory. The processor 2324 is responsible for general processing, including the execution of software stored on the computer-readable medium /memory. The software, when executed by the processor 2324, causes the processor 2324 to perform the various functions described supra. The computer-readable medium /memory may also be used for storing data that is manipulated by the processor 2324 when executing software. In some aspects, the processor 2324 may be a component of the UE 350, or other energy harvesting device, 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 apparatus 2304 may be an energy harvesting device. In other configurations, the apparatus 2304 may be an energy harvesting component of a device.

As discussed supra, the OA component 199 may be configured to receive, from a second wireless device, a forward link packet including information for OA. In some aspects, the OA component 199 may be further configured to communicate with the second wireless device after transmission of the forward link packet. The OA component 199 and/or the apparatus 2304 may be further configured to perform any of the aspects described in connection with the flowchart in FIG. 19 and FIG. 20 and/or performed by the wireless device 1404, 1504, or 1604 in FIG. 14, FIG. 15, or FIG. 16. The OA component 199 may be within the processor 2324. The component 199 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes/algorithm individually or in combination. As shown, the apparatus 2304 may include a variety of components configured for various functions. In one configuration, the apparatus 2304, and in particular the processor (s) 2324, may include means for receiving, from a second wireless device, a forward link packet including information for OA. In some aspects, the apparatus 2304 may include means for adjusting the oscillator based on the information for the OA. In some aspects, the apparatus 2304 may include means for periodically receiving time-frequency synchronization signal including the forward link packet including the information for the OA. In some aspects, the apparatus 2304 may include means for aperiodically receiving a time-frequency synchronization signal with the forward link packet including the information for the OA. In some aspects, the apparatus 2304 may include means for receiving the forward link packet after a completion of time-frequency synchronization with the second wireless device. In some aspects, the apparatus 2304 may include means for receiving a trigger to start a dedicated oscillator error (OE) measurement. In some aspects, the apparatus 2304 may include means for generating the dedicated OE measurement. In some aspects, the apparatus 2304 may include means for transmitting a response associated with the dedicated OE measurement. In some aspects, the apparatus 2304 may include means for receiving the forward link packet including the information for the OA based on the response. In some aspects, the apparatus 2304 may include means for transmitting a first random access message to the second wireless device. In some aspects, the apparatus 2304 may include means for receiving the forward link packet including the information for the OA in a second random access message. The apparatus 2304 may include means for performing any of the aspects described in connection with flowchart in FIG. 19 and FIG. 20 and/or performed by the wireless device 1404, 1504, or 1604 in FIG. 14, FIG. 15, or FIG. 16. As described supra, the apparatus 2304 may include the TX processor 368, the RX processor 356, and the controller/processor 359. As such, in one configuration, the 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.

It is understood that the specific order or hierarchy of blocks in the processes /flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes /flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not limited to the specific order or hierarchy presented.

The previous 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 readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims. Reference to an element in the singular does not mean “one and only one” unless specifically so stated, but rather “one or more. ” Terms such as “if, ” “when, ” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when, ” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration. ” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, 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 multiples of A, multiples of B, or multiples of 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 A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. Sets should be interpreted as a set of elements where the elements number one or more. Accordingly, for a set of X, X would include one or more elements. When at least one processor is configured to perform a set of functions, the at least one processor, individually or in any combination, is configured to perform the set of functions. Accordingly, each processor of the at least one processor may be configured to perform a particular subset of the set of functions, where the subset is the full set, a proper subset of the set, or an empty subset of the set. If a first apparatus receives data from or transmits data to a second apparatus, the data may be received/transmitted directly between the first and second apparatuses, or indirectly between the first and second apparatuses through a set of apparatuses. A device configured to “output” data, such as a transmission, signal, or message, may transmit the data, for example with a transceiver, or may send the data to a device that transmits the data. A device configured to “obtain” data, such as a transmission, signal, or message, may receive, for example with a transceiver, or may obtain the data from a device that receives the data. Information stored in a memory includes instructions and/or data. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module, ” “mechanism, ” “element, ” “device, ” and the like may not be a substitute for the word “means. ” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for. ”

As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently.

The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation.

Aspect 1 is a method for wireless communication performed by a first wireless device, including:

transmitting, for a second wireless device, a forward link packet including information for OA; and communicating with the second wireless device after transmission of the forward link packet.

Aspect 2 is the method of aspect 1, where transmitting the forward link packet further includes: periodically transmitting time-frequency synchronization signal including the forward link packet including the information for the OA.

Aspect 3 is the method of aspect 1, where transmitting the forward link packet further includes: aperiodically transmitting a time-frequency synchronization signal with the forward link packet including the information for the OA.

Aspect 4 is the method of aspect 3, where transmitting the forward link packet further includes: transmitting the forward link packet based on a completion of time-frequency synchronization with the second wireless device.

Aspect 5 is the method of any of aspects 1-4, where transmitting the forward link packet further includes transmitting the forward link packet based on a change in an oscillator frequency associated with the second wireless device.

Aspect 6 is the method of any of aspects 1-5, where transmitting the forward link packet further includes: transmitting a trigger to start a dedicated oscillator error (OE) measurement; receiving a response associated with the dedicated OE measurement; and transmitting the forward link packet including the information for the OA based on the response.

Aspect 7 is the method of aspect 6, where the second wireless device is a passive Internet of Things (IoT) device, where the trigger is included in a carrier wave, and where the response is a sequence configured for the dedicated OE measurement.

Aspect 8 is the method of any of aspects 6-7, where the second wireless device is a passive Internet of Things (IoT) device, where the trigger is included in a carrier wave, and where the response is based on a frequency hopping pattern configured for the dedicated OE measurement.

Aspect 9 is the method of any of aspects 1-8, where transmitting the forward link packet further includes: receiving a first random access message from the second wireless device; measuring a frequency error associated with an oscillator of the second wireless device based on the first random access message from the second wireless device; and transmitting, based on a value the frequency error exceeding a threshold, the forward link packet including the information for the OA in a second random access message.

Aspect 10 is the method of any of aspects 1-9, where the information includes at least one bit indicating an instruction to adjust a frequency at an oscillator of the second wireless device based on a frequency granularity or a direction.

Aspect 11 is the method of any of aspects 1-10, where transmitting the forward link packet further includes: receiving a backlink packet from the second wireless device; measuring a frequency error associated with an oscillator of the second wireless device based on the backlink packet from the second wireless device; and transmitting, based on a value the frequency error exceeding a threshold, the forward link packet including the information for the OA.

Aspect 12 is a method for wireless communication performed by a first wireless device, including: receiving, from a second wireless device, a forward link packet including information for OA; and adjusting the oscillator based on the information for the OA.

Aspect 13 is the method of aspect 12, where receiving the forward link packet further includes: periodically receiving time-frequency synchronization signal including the forward link packet including the information for the OA.

Aspect 14 is the method of aspect 12, where receiving the forward link packet further includes: aperiodically receiving a time-frequency synchronization signal with the forward link packet including the information for the OA.

Aspect 15 is the method of aspect 14, where receiving the forward link packet further includes: receiving the forward link packet after a completion of time-frequency synchronization with the second wireless device.

Aspect 16 is the method of any of aspects 12-15, where receiving the forward link packet further includes: receiving a trigger to start a dedicated oscillator error (OE) measurement; generating the dedicated OE measurement; transmitting a response associated with the dedicated OE measurement; and receiving the forward link packet including the information for the OA based on the response.

Aspect 17 is the method of aspect 16, where the first wireless device is a passive Internet of Things (IoT) device, where the trigger is included in a carrier wave, and where the response is a sequence configured for the dedicated OE measurement.

Aspect 18 is the method of any of aspects 16, where the first wireless device is a passive Internet of Things (IoT) device, where the trigger is included in a carrier wave, and where the response is based on a frequency hopping pattern configured for the dedicated OE measurement.

Aspect 19 is the method of any of aspects 12-18, further including: transmitting a first random access message to the second wireless device; and receiving the forward link packet including the information for the OA in a second random access message.

Aspect 20 is the method of any of aspects 12-19, where the information includes at least one bit indicating an instruction to adjust a frequency at the oscillator based on a frequency granularity or a direction.

Aspect 21 is an apparatus for wireless communication at a device including at least one memory and at least one processor coupled to the at least one memory and, the at least one processor, individually or in any combination, based at least in part on information stored in the at least one memory, the at least one processor is configured to implement any of aspects 1 to 11.

Aspect 22 is the apparatus of aspect 21, further including one or more transceivers or one or more antennas coupled to the at least one processor.

Aspect 23 is an apparatus for wireless communication at a device including means for implementing any of aspects 1 to 11.

Aspect 24 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code, where the code when executed by at least one processor causes the at least one processor to implement any of aspects 1 to 11.

Aspect 25 is an apparatus for wireless communication at a device including at least one memory and at least one processor coupled to the at least one memory and an oscillator and, the at least one processor, individually or in any combination, based at least in part on information stored in the at least one memory, the at least one processor is configured to implement any of aspects 12 to 20.

Aspect 26 is the apparatus of aspect 21, further including one or more transceivers or one or more antennas coupled to the at least one processor.

Aspect 27 is an apparatus for wireless communication at a device including means for implementing any of aspects 12 to 20.

Aspect 28 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code, where the code when executed by at least one processor causes the at least one processor to implement any of aspects 12 to 20.

Claims

An apparatus for wireless communication at a first wireless device, comprising:

at least one memory; and

at least one processor coupled to the at least one memory, the at least one processor, individually or in any combination, is configured, based at least in part on information stored in the at least one memory, to cause the first wireless device to:

transmit, for a second wireless device, a forward link packet comprising information for oscillator adjustment (OA) ; and

communicate with the second wireless device after transmission of the forward link packet.
The apparatus of claim 1, wherein to transmit the forward link packet, the at least one processor, individually or in any combination, is configured to cause the first wireless device to:

periodically transmit time-frequency synchronization signal comprising the forward link packet comprising the information for the OA.
The apparatus of claim 1, wherein to transmit the forward link packet, the at least one processor, individually or in any combination, is configured to cause the first wireless device to:

aperiodically transmit a time-frequency synchronization signal with the forward link packet comprising the information for the OA.
The apparatus of claim 3, wherein to transmit the forward link packet, the at least one processor, individually or in any combination, is configured to cause the first wireless device to:

transmit the forward link packet based on a completion of time-frequency synchronization with the second wireless device.
The apparatus of claim 1, wherein to transmit the forward link packet, the at least one processor, individually or in any combination, is configured to cause the first wireless device to:

transmit the forward link packet based on a change in an oscillator frequency associated with the second wireless device.
The apparatus of claim 1, wherein to transmit the forward link packet, the at least one processor, individually or in any combination, is configured to cause the first wireless device to:

transmit a trigger to start a dedicated oscillator error (OE) measurement;

receive a response associated with the dedicated OE measurement; and

transmit the forward link packet comprising the information for the OA based on the response.
The apparatus of claim 6, wherein the second wireless device is a passive Internet of Things (IoT) device, wherein the trigger is included in a carrier wave, and wherein the response is a sequence configured for the dedicated OE measurement.
The apparatus of claim 6, wherein the second wireless device is a passive Internet of Things (IoT) device, wherein the trigger is included in a carrier wave, and wherein the response is based on a frequency hopping pattern configured for the dedicated OE measurement.
The apparatus of claim 1, wherein to transmit the forward link packet, the at least one processor, individually or in any combination, is configured to cause the first wireless device to:

receive a first random access message from the second wireless device;

measure a frequency error associated with an oscillator of the second wireless device based on the first random access message from the second wireless device; and

transmit, based on a value of the frequency error exceeding a threshold, the forward link packet comprising the information for the OA in a second random access message.
The apparatus of claim 1, wherein the information comprises at least one bit indicating an instruction to adjust a frequency at an oscillator of the second wireless device based on a frequency granularity or a direction.
The apparatus of claim 1, wherein to transmit the forward link packet, the at least one processor, individually or in any combination, is configured to cause the first wireless device to:

receive a backlink packet from the second wireless device;

measure a frequency error associated with an oscillator of the second wireless device based on the backlink packet from the second wireless device; and

transmit, based on a value of the frequency error exceeding a threshold, the forward link packet comprising the information for the OA.
An apparatus for wireless communication at a first wireless device, comprising:

at least one memory; and

at least one processor coupled to the at least one memory, the at least one processor, individually or in any combination, is configured, based at least in part on information stored in the at least one memory, to cause the first wireless device to:

receive, from a second wireless device, a forward link packet comprising information for oscillator adjustment (OA) ; and

adjust an oscillator of the first wireless device based on the information for the OA.
The apparatus of claim 12, wherein to receive the forward link packet, the at least one processor, individually or in any combination, is configured to cause the first wireless device to:

periodically receive time-frequency synchronization signal comprising the forward link packet comprising the information for the OA.
The apparatus of claim 12, wherein to receive the forward link packet, the at least one processor, individually or in any combination, is configured to cause the first wireless device to:

aperiodically receive a time-frequency synchronization signal with the forward link packet comprising the information for the OA.
The apparatus of claim 14, wherein to receive the forward link packet, the at least one processor, individually or in any combination, is configured to cause the first wireless device to:

receive the forward link packet after a completion of time-frequency synchronization with the second wireless device.
The apparatus of claim 12, wherein to receive the forward link packet, the at least one processor, individually or in any combination, is configured to cause the first wireless device to:

receive a trigger to start a dedicated oscillator error (OE) measurement;

generate the dedicated OE measurement;

transmit a response associated with the dedicated OE measurement; and

receive the forward link packet comprising the information for the OA based on the response.
The apparatus of claim 16, wherein the first wireless device is a passive Internet of Things (IoT) device, wherein the trigger is included in a carrier wave, and wherein the response is a sequence configured for the dedicated OE measurement.
The apparatus of claim 16, wherein the first wireless device is a passive Internet of Things (IoT) device, wherein the trigger is included in a carrier wave, and wherein the response is based on a frequency hopping pattern configured for the dedicated OE measurement.
The apparatus of claim 12, wherein the at least one processor, individually or in any combination, is further configured to cause the first wireless device to:

transmit a first random access message to the second wireless device; and

receive the forward link packet comprising the information for the OA in a second random access message.
The apparatus of claim 12, wherein the information comprises at least one bit indicating an instruction to adjust a frequency at the oscillator based on a frequency granularity or a direction.
A method for wireless communication performed by a first wireless device, comprising:

transmitting, for a second wireless device, a forward link packet comprising information for oscillator adjustment (OA) ; and

communicating with the second wireless device after transmission of the forward link packet.
The method of claim 21, wherein transmitting the forward link packet further comprises:

periodically transmitting time-frequency synchronization signal comprising the forward link packet comprising the information for the OA.
The method of claim 21, wherein transmitting the forward link packet further comprises:

aperiodically transmitting a time-frequency synchronization signal with the forward link packet comprising the information for the OA.
The method of claim 23, wherein transmitting the forward link packet further comprises:

transmitting the forward link packet based on a completion of time-frequency synchronization with the second wireless device.
The method of claim 21, wherein transmitting the forward link packet further comprises:

transmitting the forward link packet based on a change in an oscillator frequency associated with the second wireless device.
The method of claim 21, wherein transmitting the forward link packet further comprises:

transmitting a trigger to start a dedicated oscillator error (OE) measurement;

receiving a response associated with the dedicated OE measurement; and

transmitting the forward link packet comprising the information for the OA based on the response.
The method of claim 26, wherein the second wireless device is a passive Internet of Things (IoT) device, wherein the trigger is included in a carrier wave, and wherein the response is a sequence configured for the dedicated OE measurement.
The method of claim 26, wherein the second wireless device is a passive Internet of Things (IoT) device, wherein the trigger is included in a carrier wave, and wherein the response is based on a frequency hopping pattern configured for the dedicated OE measurement.
The method of claim 21, wherein transmitting the forward link packet further comprises:

receiving a first random access message from the second wireless device;

measuring a frequency error associated with an oscillator of the second wireless device based on the first random access message from the second wireless device; and

transmitting, based on the frequency error being above a threshold, the forward link packet comprising the information for the OA in a second random access message.
A method for wireless communication performed by a first wireless device, comprising:

receiving, from a second wireless device, a forward link packet comprising information for oscillator adjustment (OA) ; and

adjusting an oscillator based on the information for the OA.