A-iot device frequency error control

Abstract

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

Description

Technical Field

[0001] This disclosure relates in general to communication systems, and more specifically to wireless communication systems with environmental Internet of Things (A-IoT) devices. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. 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.

[0003] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CWB) program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0004] The following is a simplified summary of one or more aspects to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all conceived aspects. It neither identifies key or essential elements of all aspects nor describes 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 descriptions that follow.

[0005] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided at a user equipment (UE) or network entity. 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 is configured, individually or in any combination, to transmit forward link packets including information for oscillator adjustment (OA) to a second wireless device. Based at least in part on information stored in the at least one memory, the at least one processor is configured, individually or in any combination, to communicate with the second wireless device after transmitting the forward link packet.

[0006] In another aspect of this disclosure, a method, computer-readable medium, and apparatus are provided at an Environmental Internet of Things (A-IoT) device. 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 stored in the at least one memory. Based at least in part on the information stored in the at least one memory, the at least one processor is configured, individually or in any combination, to receive forward link packets including information for OA from a second wireless device. Based at least in part on the information stored in the at least one memory, the at least one processor is configured, individually or in any combination, to adjust the oscillator based on the information for the OA.

[0007] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth some exemplary features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of the various aspects may be employed. Attached Figure Description

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

[0009] Figure 2A This is an illustration of an example of the first frame according to various aspects of this disclosure.

[0010] Figure 2B This is a diagram illustrating examples of downlink (DL) channels within a subframe according to various aspects of this disclosure.

[0011] Figure 2C This is an illustration of an example of a second frame according to various aspects of this disclosure.

[0012] Figure 2D This is a diagram illustrating examples of uplink (UL) channels within a subframe according to various aspects of this disclosure.

[0013] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network according to various aspects of this disclosure.

[0014] Figure 4 This is an illustration of an example radio frequency identification (RFID) system according to various aspects of this disclosure.

[0015] Figure 5A The diagram illustrates an example implementation of zero-power IoT (ZP IoT) communication according to various aspects of this disclosure.

[0016] Figure 5B This is a diagram illustrating another example of a specific implementation of ZP IoT communication according to various aspects of this disclosure.

[0017] Figure 6A This is a diagram illustrating examples of monostatic backscattering according to various aspects of this disclosure.

[0018] Figure 6B This is a diagram illustrating examples of bistatic backscattering according to various aspects of this disclosure.

[0019] Figure 7 This is a diagram illustrating another example of bistatic backscattering according to various aspects of this disclosure.

[0020] Figure 8 This is a diagram illustrating example reverse link (BL) communication with and without frequency uncertainty according to various aspects of this disclosure.

[0021] Figure 9 This is a diagram illustrating an example forward link (FL) packet for oscillator adjustment according to various aspects of this disclosure.

[0022] Figure 10 This is a diagram illustrating example time-frequency synchronization signals in a FL used to facilitate BL communication according to various aspects of this disclosure.

[0023] Figure 11 These are illustrations of example time-domain synchronization signals and frequency-domain synchronization signals according to various aspects of this disclosure.

[0024] Figure 12 This is a diagram illustrating example oscillator adjustments related to synchronization signals according to various aspects of this disclosure.

[0025] Figure 13 This is a diagram illustrating example frequencies with oscillator adjustment and time-frequency synchronization according to various aspects of this disclosure.

[0026] Figure 14This is a diagram illustrating example communication between a first wireless device and a second wireless device according to various aspects of this disclosure.

[0027] Figure 15 This is a diagram illustrating example communication between a first wireless device and a second wireless device according to various aspects of this disclosure.

[0028] Figure 16 This is a diagram illustrating example communication between a first wireless device and a second wireless device according to various aspects of this disclosure.

[0029] Figure 17 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0030] Figure 18 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0031] Figure 19 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0032] Figure 20 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0033] Figure 21 These are illustrations of examples of hardware implementations of example devices and / or network entities.

[0034] Figure 22 This is a diagram illustrating an example of a hardware implementation used for an example network entity.

[0035] Figure 23 This is a diagram illustrating an example of a hardware implementation used in an example device. Detailed Implementation

[0036] In addition to high-capacity devices, wireless communication systems can also support devices with reduced capabilities or complexity. Such devices can be configured for lower power consumption and can have less complex architectures, while also exhibiting higher frequency domain uncertainty.

[0037] To address frequency domain uncertainties associated with lower-capability devices, guard bands occupying frequency domain resources are provided in some wireless communication systems. The aspects presented herein enable oscillator tuning, allowing for better communication reliability and data rates in wireless communication independently of the guard band. In some aspects, clock error adjustment methods can be used, and wireless devices (e.g., user equipment (UE) or readers in the form of base stations) can tune the Ambient Internet of Things (A-IoT) oscillator via explicit signaling. For example, one or more bits can be included in a forward link (FL) packet to qualitatively or quantitatively indicate oscillator tuning (OA) performed for the A-IoT device in the frequency domain. The one or more bits that qualitatively or quantitatively indicate OA may be referred to as "information for OA" or "OA information." In some aspects, OA information may be in the form of a single bit indicating whether the oscillator can be tuned to be faster or slower. In some aspects, OA information may be in the form of one or more bits indicating the degree of tuning (e.g., frequency magnitude).

[0038] The detailed descriptions following, illustrated with reference to the accompanying drawings, describe various configurations and do not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed descriptions include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0039] Various apparatuses and methods are presented with reference to several aspects of a telecommunications system. These apparatuses and methods are described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0040] As an example, an element, any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. When multiple processors are implemented, the multiple processors may perform 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, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0041] Therefore, in one or more example aspects, specific implementations, and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of these 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 accessible by a computer.

[0042] While aspects, implementations, and / or use cases are described herein by way of example, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the described examples may exhibit broad applicability. Aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and configurations.

[0043] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)) or one or more units (or components) performing base station functions can be implemented in aggregated or decomposed architectures. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0044] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across 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 respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0045] Base station operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units of a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0046] Figure 1 Figure 100 illustrates an example of a wireless communication system and access network. The illustrated wireless communication system includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 via one or more decomposed 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. CUs 110 may communicate with one or more DUs 130 via a corresponding midhaul link (such as an F1 interface). DUs 130 may communicate with one or more RUs 140 via a corresponding fronthaul link. RUs 140 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0047] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO frame 105) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals via wired transmission media or transmit signals to one or more other units. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals via wireless transmission media or transmit signals to one or more other units, or both.

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

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

[0050] Lower-layer functionality can be implemented by one or more RU 140s. In some deployments, an RU140 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, or Physical Random Access Channel (PRACH) extraction and filtering, or both, at least in part based on functional decomposition (such as lower-layer functional decomposition). In this architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration enables the implementation of the DU 130 and CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

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

[0052] The non-RT RIC 115 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence (AI) / machine learning (ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or communicate with the near-RT RIC 125, such as via an A1 interface. The near-RT RIC 125 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via data collection and actions through an interface such as an E2 interface, connecting one or more CU 110s, one or more DU 130s, or both, and O-eNBs to the near-RT RIC 125.

[0053] 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 an external server. This information can be utilized by the near-RT RIC 125 and may be received from non-network data sources or network functions at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 105 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

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

[0055] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL wireless wide area network (WWAN) spectrum. D2D communication link 158 can use one or more sidelink channels, such as Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be performed through various wireless D2D communication systems, such as Bluetooth. ™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG), and is based on the IEEE 802.11 standard for Wi-Fi.)™ (Wi-Fi is a trademark of the Wi-Fi Alliance), LTE, or NR.

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

[0057] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6GHz" band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is distinct from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

[0058] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, 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 the frequency range designations FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0059] In view of the above, unless otherwise specifically stated, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, the term "millimeter wave" as used herein can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR2-2 and / or FR5, or within the EHF band.

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

[0061] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, transceiver base station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, network equipment, or some other suitable terminology. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, aggregated (monolithic) base station with baseband units (BBU) (including CU and DU) and RU, or may be implemented as a decomposed base station including one or more of CU, DU, and / or RU. A collection of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as Next Generation (NG) RAN (NG-RAN).

[0062] The core network 120 may include Access and Mobility Management Function (AMF) 161, Session Management Function (SMF) 162, User Plane Function (UPF) 163, Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is the control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports authentication and key agreement (AKA) credential generation, user identity processing, access authorization, and subscription management. One or more location servers 168 are exemplified as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, one or more location servers 168 may include one or more location / positioning servers, which may include one or more of GMLC 165, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Location Center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. LMF 166 receives measurement and auxiliary information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may use one or more positioning methods to determine the location of UE 104. Positioning UE 104 may involve signal measurement, location estimation, and optional speed calculation based on these measurements. Signal measurement may be performed by UE 104 and / or base station 102 serving UE 104. The measured signals may be based on one or more of the following: Satellite Positioning System (SPS) 170 (e.g., one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN) or other satellite positioning / location systems), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR Enhanced Cell ID (NR E-CID) method, NR signals (e.g., multiple round-trip time (multiple RTT), DL departure angle (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.

[0063] Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking timers, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network together and / or individually.

[0064] In some respects, UE 104 or base station 102 may communicate with tag 142. In some respects, the term "tag" may refer to a wireless device that supports ambient-powered transmission, energy harvesting, passive transmission, backscatter transmission, etc. In some respects, "tag" may also be referred to as a passive UE, a passive device, an ambient IoT (which may also be referred to as passive IoT) (A-IoT) device, or any other similar device of any shape or form.

[0065] Refer again Figure 1 In some aspects, tag 142 may include an oscillator adjustment (OA) component 199. In some aspects, OA component 199 may be configured to receive forward link packets from a second wireless device that include information for OA. In some aspects, OA component 199 may also be configured to communicate with the second wireless device after transmitting a forward link packet.

[0066] In some aspects, base station 102 or UE 104 may include OA component 198. In some aspects, OA component 198 may be configured to transmit forward link packets including information for OA to a second radio device. In some aspects, OA component 198 may also be configured to communicate with the second radio device after transmitting the forward link packets.

[0067] While the following description may focus 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.

[0068] As described herein, a node (which may be referred to as a node, network node, network entity, or wireless node) may include, may be included in, or may 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, apparatus, device, computing system, integrated access and backhaul (IAB) node, distributed unit (DU), central unit (CU), 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. Alternatively, a network node may be a base station or a network entity. Alternatively, a first network node may be configured to communicate with a second or 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 other aspects of this example, the first network node, the second network node, and the third network node may differ from these examples. Similarly, references to UE, base station, device, equipment, computing system, etc., may include disclosures of UE, base station, device, equipment, computing system, etc., as network nodes. For example, a disclosure of a UE being 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 particular example is extended according to this disclosure (e.g., a disclosure of a UE being 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), a wider example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where the UE is configured to receive information from the base station and the first network node is configured to receive information from the second network node, the first network node may refer to the first UE configured to receive information, the first base station, the first device, the first equipment, the first computing system, a first set of one or more components or a first processing entity, etc.; and the second network node may refer to the second UE, the second base station, the second device, the second equipment, the second computing system, a second set of one or more components or a second processing entity, etc.

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

[0070] Figure 2A Figure 200 illustrates an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 illustrates an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 is an example of a second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL) or Time Division Duplex (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). Figure 2A , Figure 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible and can be used between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured using the slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0071] Figures 2A to 2DThe frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. Symbols on the DL can be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and a parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled by 1 / SCS.

[0072] For a normal CP (14 symbols / slot), different parameter sets µ 0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For the extended CP, parameter set 2 allows 4 slots per subframe. Therefore, for a normal CP and parameter set µ, there are 14 symbols per slot and 2 slots per subframe. µ One time slot. The subcarrier spacing can be equal to ,in The parameter sets are 0 to 4. Therefore, the subcarrier spacing is 15 kHz for parameter set µ=0 and 240 kHz for parameter set µ=4. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A to 2D Examples of a normal frequency division multiplexing (CP) with 14 symbols per time slot and a parameter set of µ=2 with 4 time slots per subframe are provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more distinct bandwidth portions (BWPs) of frequency division multiplexing (see [link to relevant documentation]). Figure 2B Each BWP can have a specific set of parameters and CP (normal or extended).

[0073] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

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

[0075] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 coherent REs in the OFDM symbol of the RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., the common search space, the UE-specific search space) during PDCCH monitoring timing on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and the Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the System Frame Number (SFN) and the number of Restricted Frames (RBs) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0076] like Figure 2CAs illustrated, some REs in 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 can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb teeth. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0077] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCIs.

[0078] Figure 3This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, Internet Protocol (IP) packets can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

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

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

[0081] The controller / processor 359 may be associated with at least one memory 360 storing program code 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, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

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

[0083] The TX processor 368 can use the reference signal transmitted from the base station 310 or the channel estimate derived from feedback by the channel estimator 358 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354Tx. Each transmitter 354Tx can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0084] UL transmission is processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318Rx receives signals via its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides that information to RX processor 370.

[0085] The controller / processor 375 may be associated with at least one memory 376 storing program code 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, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0086] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to combine Figure 1 The OA component 198 is used to perform various aspects.

[0087] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to combine Figure 1 The OA component 198 is used to perform various aspects.

[0088] In addition to higher-capacity devices, wireless communication systems can also support lower-capacity (RedCap) devices. Examples of higher-capacity devices include advanced smartphones, V2X devices, URLLC devices, eMBB devices, etc. Examples of lower-capacity devices include wearable devices (e.g., smartwatches, augmented reality glasses, virtual reality glasses, health and medical monitoring devices, etc.), industrial wireless sensor networks (IWSNs) (e.g., pressure sensors, humidity sensors, motion sensors, thermal sensors, accelerometers, actuators, etc.), surveillance cameras, low-end smartphones, etc. For example, NR communication systems can support both higher-capacity and lower-capacity devices. Lower-capacity devices can be referred to by various names (such as NR lightweight devices, low-level devices, or lower-level devices, etc.). Lower-capacity UEs can communicate based on various types of wireless communication. For example, smart wearable devices can transmit or receive communication based on low-power wide-area networks (LPWA) / mMTC, loose IoT devices can transmit or receive communication based on URLLC, sensors / cameras can transmit or receive communication based on eMBB, etc.

[0089] In addition to devices with reduced capabilities, wireless communication systems may also include devices with even lower capabilities than those with reduced capabilities, including lower power consumption and less complex architectures. Some wireless communication systems may include passive wireless devices (such as zero-power passive IoT wireless devices). Such passive wireless devices may lack active RF components and may perform transmission based on backscatter communication and reception based on envelope detection or envelope detectors. Backscatter communication modulates information on the incoming RF signal (which may be a carrier wave capable of carrying communication between other devices) by adapting the antenna load impedance. Passive wireless devices may be battery-free or battery-assisted. For example, passive wireless devices may operate based on energy harvesting from incoming radio waves, with or without a battery as an additional power source. Passive wireless devices may have low power consumption, such as between 1 microwatt and 1000 microwatts. Such passive wireless devices may be used for inventory management, wireless sensors, etc. Passive devices may use backscatter communication to communicate with another network entity, such as a base station.

[0090] Backscatter communication enables radio frequency identification (RFID). For example, a reader can transmit a continuous waveform signal along with an interrogation command. As a non-limiting example of a passive or semi-passive device, an RF tag can harvest energy from a continuous waveform signal and respond to an interrogation by changing its input impedance (e.g., between conjugate matching and strong mismatch), thus modulating the backscattered signal. RFID is a rapidly evolving technology impacting many industries due to its potential for inventory / asset management inside and outside warehouses, IoT, sustainable sensor networks in factories and / or agriculture, and smart homes. RFID systems may include small transponders that transmit information-bearing signals when a signal is received; these small transponders may be referred to as tags. RFID can operate with low operating expenses (OPEX) without batteries and can utilize minimal resources. Such RFID devices can involve less maintenance and can have long lifecycles.

[0091] Figure 4 This is illustration 400, illustrating an example RFID system. For example... Figure 4As shown, an RFID system may include a reader 402 and a tag 404. The reader 402 transmits electromagnetic (EM) signals to the tag 404 via an antenna through a forward link (FL). The tag 404 may detect the EM signal from the reader 402, for example, using an envelope detector, and reflect or scatter the encountered EM signal back to the reader 402 via a reverse link (BL). The reflected EM signal may be modulated by the tag 404 to include backscattered data from the reader 402. The term "FL" may refer to the link from the RF source to the tag. The term "RF source" may refer to a transmitter of a signal (e.g., a modulated or unmodulated signal, which may be referred to as an FL carrier in the form of a continuous wave to power the tag) to the tag, which may reflect the signal as a backscattered wave. The term "BL" may refer to the link from the tag to the reader. The term "reader" may refer to a receiver of the backscattered wave. FL data, such as FL information, may be present on the FL, which may be a command, acknowledgment (ACK), or negative acknowledgment (NACK), etc. On the BL, BL data such as BL information may exist, which can be ACK / NACK or data from the tag. As used herein, the term "tag" can be used to refer to various types of devices that use ambient power or received RF power to transmit signals. A tag is one example of a device that can be configured to perform the aspects described herein, and these concepts are not limited to tags. Such devices may also be referred to as supporting ambient-powered transmission, supporting energy harvesting, supporting passive transmission, supporting backscatter transmission, environmental IoT (which may also be referred to as passive IoT) (A-IoT) devices (which may include active A-IoT devices or passive A-IoT devices), passive UEs, etc. In some respects, A-IoT devices may be useful for supporting ultra-low complexity and ultra-low power devices, thus providing several orders of magnitude lower complexity and power consumption than other types of IoT.

[0092] Figure 5A Figure 500 illustrates an example implementation of zero-power IoT (ZP IoT) communication, such as backscatter communication or passive communication. Figure 5A As shown, network node 502 can communicate directly with tag 504 via DL communication and UL communication. Figure 5B Figure 550 is another example of a specific implementation of ZP IoT communication. For example... Figure 5B As shown, network node 552 can communicate with tag 554 via UE 556. UE 556 can act as a relay between network node 552 and tag 554. That is, network node 552 can communicate with UE 556 via the Uu interface (the radio interface that connects UE 556 to network node 552), and UE 556 can communicate with tag 554 via the FL link and BL link.

[0093] Figure 6A Figure 600 illustrates examples of single-station backscatter communication according to various aspects of this disclosure. For example... Figure 6A As illustrated, in a single-station backscatter system, the RF source and the reader can be part of the same device, or the RF source function and the reader function can be performed by the same device. The RF source can be a transmitter 604, and the reader can be a receiver 614; they can share the same antenna and can communicate with the tag 610. For example, the antenna can send a signal (e.g., a modulated signal or an unmodulated signal) to the tag 610 and then receive the reflected signal (backscattered wave) from the tag 610.

[0094] Figure 6B Figure 650 illustrates examples of bistationary backscatter communication according to various aspects of this disclosure. For example... Figure 6B As illustrated, in a bistatic backscatter system, the RF source and the reader can be different devices. For example, the RF source can be transmitted by a first device, and the second device can be used as a reader by receiving the backscattered signal. The RF source can be a transmitter 654, which can be connected to a transmitting antenna 652, and the reader can be a receiver 664, which can be connected to a receiving antenna 662. The RF source can transmit a signal to the tag 670, and the reader can receive the backscattered wave from the tag 670.

[0095] Figure 7 Figure 700 is another example illustrating bistatic backscatter communication according to various aspects of this disclosure. As... Figure 7 As illustrated, network node 702 can be an RF source and can transmit signals to tag 704 via FL 708. Tag 704 can reflect the signal via BL 710, which can be received by a second device (e.g., reader 706 can receive the reflected signal).

[0096] A low-power receiver can be a separate receiver from the main radio unit on a wireless device. The low-power receiver can be used to achieve lower power consumption at the wireless device and can have significantly lower power consumption than the main radio unit. To save power, the main radio unit can enter a sleep mode, and the low-power receiver can periodically listen to (or "monitor") the low-power receiver. The wireless device can periodically listen to the low-power receiver (e.g., periodically monitor signals via the low-power receiver), and the main radio unit can 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 can turn on the main radio unit to enable data communication via the main radio unit.

[0097] As an example, a low-power receiver could be a companion receiver that supports monitoring at a lower power than the main radio component when the main radio component is in sleep mode. The low-power receiver can wake the main radio component to enable data communication. For example, the low-power receiver can monitor the LP WUS at a first time point 62. Based on the absence of LP WUS, the main radio component may not wake up at the first time point. Alternatively, the low-power receiver can monitor the LP WUS at a time point. Based on the receipt of LP WUS, the main radio component can wake up. The low-power receiver can consume less power than the main radio component and can be powered separately from the main radio component. In some aspects, the low-power receiver may not be used for bidirectional communication with network entities (such as base stations) and can be used to monitor paging information, allowing the main radio component to be woken up for communication.

[0098] The use of a low-power receiver reduces overall power consumption because it reduces the wake-up time of the high-power main radio component. The use of a low-power receiver also reduces overall latency. Because a low-power receiver consumes less power, it allows for more frequent low-power receiver monitoring while maintaining power efficiency and reduces average latency (e.g., less average latency compared to less frequent wake-ups of the main radio component). Example performance metrics for a low-power receiver may include power consumption (which may be lower than the sleep power of the main radio component for extended operation). Example performance metrics for a low-power receiver may include sensitivity, where higher sensitivity achieves better coverage. For low-power operation, power-consuming blocks are avoided, which can lead to poor sensitivity and potential coverage mismatch between the low-power radio component and the main radio component. Therefore, sensitivity at the low-power receiver can be a performance metric. Example performance metrics for a low-power receiver may also include data rate, false alarm or false wake-up probability (false wake-ups can lead to higher power consumption), missed detection probability (missed detections can lead to poor reliability and increased latency), and main radio component wake-up time (which is related to overall latency).

[0099] LP WUS is used for paging reception and can be associated with early paging indication. To enable low-power receivers at the wireless device to perform radio resource management, time or frequency (T / F) tracking, and resynchronization, the aspects described herein provide LP RS. Wireless devices can use such LP RS in a variety of different configurations. For example, if the low-power receiver supports the OOK waveform and has a bandwidth of less than or equal to 5 MHz with a noise figure of approximately 7 dB, then LP RS can be based on the OOK waveform used for T / F synchronization. As another example, if the low-power receiver supports the OOK waveform and has a bandwidth of approximately 1 MHz with a noise figure of approximately 5 dB, then LP RS can be used with a minimum coupling loss (MCL) of 164 dB or less. MCL can be the minimum distance loss including antenna gain measured between antenna connectors. In another example, if the low-power receiver supports the OOK waveform and has a bandwidth of approximately 5 MHz with a noise figure of approximately 5 dB, the wireless device may not be able to use LP RS to meet an MCL of 140 dB. As used herein, the term "LP RS" can refer to a signal received via a low-power receiver for T / F tracking and radio resource management. LP RS can be carried on LP RS resources (which can be arranged as LP RS resource sets). The term "LP WUS" can refer to a signal received via a low-power receiver for waking up the primary radio component, and can be associated with early paging indication, idle discontinuous reception (DRX) cycles (e.g., associated with paging monitoring timing), or wake-up monitoring timing associated with connected mode DRX cycles. In some aspects, the term "monitoring timing" can refer to a configured time timing in which the UE is configured to monitor transmission. In some aspects, a low-power wake-up receiver can be referred to as a low-power wake-up radio component, and a primary receiver can be referred to as the primary radio component, and vice versa. As described herein, references to radio components can include references to radio components, receivers, or transceivers; and vice versa. For example, a low-power receiver can also be referred to as a low-power radio component or a low-power transceiver, etc. As another example, a primary receiver can also be referred to as the primary radio component or the primary transceiver, etc. As another example, the main radio component may also be referred to as the main receiver or main transceiver, etc. The term "power state" can refer to the power state of the main radio component. For example, the main radio component may wake up from a sleep state, a powered-off state, or another state to an powered-on state or a wake-up state in which the main radio component is configured to avoid receiving or transmitting some (or all) communications to conserve power.

[0100] Different A-IoT devices can send or receive signaling based on various forms of modulation, such as Frequency Shift Keying (FSK), Amplitude Shift Keying (ASK), Phase Shift Keying (PSK), On / Off Keying (OOK), etc. As an example, an A-IoT active device may include a crystal oscillator with a frequency offset, such as a 20 parts per million (PPM) frequency offset. For time-domain synchronization, LP RS (such as an LP synchronization signal (LP SS)) can be used in combination with LP SS correlation and detection to facilitate time-domain synchronization. For the frequency domain, with an offset of 20 PPM and using 3.5 GHz for BL communication, there may be an uncertainty of 70 kHz in BL communication. As an example, the maximum permissible frequency uncertainty may be equal to 100 kHz. Therefore, for a 20 PPM frequency offset, an A-IoT active device may still be able to have a frequency uncertainty lower than the maximum permissible frequency uncertainty without frequency-domain synchronization. However, if the oscillator has a larger offset, for example, above 30 PPM, the A-IoT device may have a frequency uncertainty higher than the maximum permissible frequency uncertainty without frequency-domain synchronization. Therefore, whether an A-IoT device, including a crystal oscillator, will use frequency domain synchronization may depend on the frequency offset.

[0101] Some A-IoT active devices may include crystal-free oscillators instead of crystal oscillators. As an example, a crystal-free oscillator may have a frequency offset of plus or minus one percent. In the time domain, various reference signals such as LP SS or preambles can be used to facilitate time-domain synchronization. In the frequency domain, with an offset of plus or minus one percent and using 3.5 GHz for BL communication, there may be an uncertainty of 70 MHz in BL communication. As an example, the maximum permissible frequency uncertainty may be equal to 100 kHz. Therefore, for a frequency offset of plus or minus one percent, an A-IoT device may have a frequency uncertainty higher than the maximum permissible frequency uncertainty without frequency-domain synchronization. Therefore, A-IoT active devices including crystal-free oscillators can use frequency-domain synchronization.

[0102] For A-IoT passive or semi-passive devices including crystal-free oscillators, as an example, the frequency offset can be positive or negative ten percent before calibration, etc. With such a frequency offset, the A-IoT device can have a frequency uncertainty higher than the maximum permissible frequency uncertainty without frequency domain synchronization. Therefore, A-IoT passive or semi-passive devices including crystal-free oscillators can use frequency domain synchronization or calibration. As used herein, frequency error may be caused by frequency uncertainty and can be the frequency difference between the frequency transmitted from the A-IoT device and the frequency in which the A-IoT device can be configured to transmit, after adjustments for the effects of modulation and phase errors. For example, a network entity can measure the frequency error associated with an A-IoT device based on a specific transmission, because the network entity may have information about the frequency in which the A-IoT device can be configured to transmit.

[0103] For some A-IoT devices (e.g., passive, semi-passive, or active devices), frequency domain uncertainty can be significant due to clock quality. As an example, some A-IoT active devices may have an internal oscillator that generates a local oscillator (LO) signal (e.g., 700MHz) with an uncertainty close to ±200ppm. As another example, some A-IoT passive or semi-passive devices may receive an external carrier (CW) signal (e.g., 700MHz and 0.5ppm) with a frequency shift of no more than 20MHz (<1% error). Unlike fully capable devices, A-IoT devices may not support FFTs that can self-correct frequency errors using a reference signal. Figure 8 Figure 800 illustrates example BL communications with and without frequency uncertainty according to various aspects of this disclosure. Figure 8 As illustrated, in the absence of frequency domain uncertainty, the BL channel of the first device 802 and the BL channel of the second device 804 may not overlap. However, due to the possible presence of frequency domain uncertainty at both devices, in practice, with frequency domain uncertainty, the BL channel 812 of the first device and the BL channel 814 of the second device may overlap, leading to potential collisions and packet loss.

[0104] To address frequency domain uncertainties associated with lower-capability devices, guard bands occupying frequency domain resources are provided in some wireless communication systems. The aspects presented herein enable oscillator tuning, allowing for better communication reliability and data rates in wireless communication independently of guard bands. In some aspects, clock error adjustment methods can be used, and wireless devices (e.g., readers in the form of UEs or base stations) can tune the A-IoT oscillator via explicit signaling. For example, one or more bits can be included in an FL packet to qualitatively or quantitatively indicate the degree of oscillator tuning (OA) performed for the A-IoT device in the frequency domain. The one or more bits that qualitatively or quantitatively indicate the degree of OA may be referred to as "information for OA" or "OA information." In some aspects, OA information can be in the form of a single bit indicating whether the oscillator should be tuned to be faster or slower. In some aspects, OA information can be in the form of one or more bits indicating the degree of tuning. For example, in some aspects, the degree of tuning can be based on granularity based on SCS, granularity based on one divided by N times SCS (where N is an integer), or based on different configured granularities (configured without signaling or configured based on signaling). As a specific example, if the OA information includes two bits, "00" can indicate an adjustment of positive 50KHz, "01" can indicate an adjustment of positive 100KHz, "10" can indicate an adjustment of negative 100KHz, and "11" can indicate an adjustment of negative 50KHz.

[0105] Figure 9 Figure 900 illustrates an example FL group for oscillator adjustment according to various aspects of this disclosure. Figure 9 As illustrated, FL group 902 may include one or more bits 904 to qualitatively or quantitatively indicate the degree of OA in the frequency domain for adjusting the oscillator 906 of the A-IoT device.

[0106] Explicit signaling used to indicate OA can be used in conjunction with time-frequency synchronization signals (e.g., OOK or single-frequency modulation). Figure 10 Figure 1000 illustrates an example time-frequency synchronization signal in a FL used to facilitate BL communication according to various aspects of this disclosure. Figure 10As illustrated, on the FL, CW 1002 can be transmitted to power on the A-IoT device. A time synchronization signal 1004 and a frequency synchronization signal 1006 can follow CW 1002. Following the time synchronization signal 1004 and the frequency synchronization signal 1006, an FL control or data channel 1008 can be transmitted. On the BL, the A-IoT device can transmit BL control or data channels 1012, 1014, and 1016. In some aspects, the A-IoT device can also transmit a UL scheduling trigger signal 1018 to schedule another transmission. In some aspects, the time-frequency synchronization signal can be transmitted periodically, allowing the A-IoT device to periodically correct frequency domain errors or time domain errors. In some aspects, the time-frequency synchronization signal can be transmitted non-periodically, allowing the A-IoT device to non-periodically correct frequency domain errors or time domain errors.

[0107] Figure 11 Figure 1100 illustrates example time-domain synchronization signals and frequency-domain synchronization signals according to various aspects of this disclosure. For example... Figure 11 As illustrated, the OOK preamble 1102 associated with the OOK payload 1104 can be used for time-domain synchronization, and the single-frequency modulation 1106 can be used for frequency-domain synchronization.

[0108] In some respects, if the oscillator frequency of an A-IoT device changes, for example, due to temperature variations, then a reader (e.g., in the form of a UE or base station) can instruct the A-IoT device to change the oscillator frequency accordingly (e.g., based on OA). Figure 12 Figure 1200 illustrates an example oscillator adjustment related to a synchronization signal according to various aspects of this disclosure. For example... Figure 12 As illustrated, the time-frequency synchronization signals, including synchronization signals 1202A, 1202B, and 1202C, can be periodically sent to the A-IoT device at an example period of one second. Temperature changes (such as...) Figure 12 (As indicated by the arrow in the diagram) This can occur before BL packet 1212A, thus causing frequency variations in BL packets 1212A and BL packet 1212B. The reader can detect these frequency variations, and based on them, can send an FL packet including OA information 1204 to the A-IoT device. The A-IoT device can receive the FL packet including OA information 1204 and BL packet 1212C, and can correct subsequent BL packets, such as BL packet 1214A, BL packet 1214B, and BL packet 1214C.

[0109] Figure 13 Figure 1300 illustrates an example synchronization signal used in conjunction with oscillator adjustment according to various aspects of this disclosure. Figure 13As illustrated, an initial frequency (e.g., without any adjustments) can be provided at 1302. In the case of time and frequency synchronization, the frequency can be adjusted to 1304, which may still differ from the target frequency by more than a threshold. In some aspects, after performing OA based on OA information included in the FL group, the frequency can be adjusted to 1306, which can be consistent with the target frequency. As an example, the threshold can be in the form of a specific number of PPMs or a specific number of Hertz.

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

[0111] Figure 14Figure 1400 illustrates example communication 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) according to various aspects of this disclosure. The first wireless device 1402 may send an OE measurement trigger 1412 to the second wireless device 1404. The first wireless device 1402 may also send a CW 1414 to the second wireless device 1404 to facilitate a response from the second wireless device 1404, since the second wireless device 1404 may be a passive or semi-passive device that can use the CW 1414 to reflect a response. Upon receiving the CW 1414, the second wireless device 1404 may send a response in the form of a CW plus a frequency shift 1416 (e.g., applying the frequency shift as a response to the CW). In some aspects, the second wireless device 1404 may apply a frequency shift plus a sequence known to the first wireless device 1402 as a response, wherein this sequence may be 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 a response. The frequency hopping mode for BL frequency hopping may be configured at both devices without signaling, or configured by the first wireless device 1402. Based on the received response (at 1416), the first wireless device 1402 may perform a measurement and send OA information 1418 to the second wireless device 1404 in an FL packet. After receiving the OA information 1418 in the FL packet, at 1420, the second wireless device 1404 may adjust its oscillator. Therefore, subsequent communication 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 communication between the first wireless device 1402 and the second wireless device 1404 may be based on an adjusted oscillator.

[0112] Figure 15 Figure 1500 illustrates example communication between a first wireless device and a second wireless device according to various aspects of this disclosure. Figure 15Figure 1500 illustrates example communication 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) according to various aspects of this disclosure. The first wireless device 1502 may send an OE measurement trigger 1512 to the second wireless device 1504. Upon receiving the OE measurement trigger 1512, the second wireless device 1504 may send a response 1516 to the first wireless device 1502. Based on the received response (at 1516), the first wireless device 1502 may perform a measurement and send OA information 1518 to the second wireless device 1504 in an FL packet. After receiving the OA information 1518 in the FL packet, at 1520, the second wireless device 1504 may adjust its oscillator. Therefore, subsequent communication 1522 between the first wireless device 1502 and the second wireless device 1504 may be based on the adjusted oscillator.

[0113] Figure 16 Figure 1600 illustrates example communication between a first wireless device 1602 and a second wireless device 1604 according to various aspects of this disclosure. The second wireless device 1604 can initiate a RACH procedure by sending a RACH preamble 1612 (Msg 1 or a first random access message) to the first wireless device 1602. In some aspects, the first wireless device 1602 can measure the RACH preamble 1612 to determine whether the oscillator at the second wireless device 1604 can be adjusted. If the first wireless device 1602 determines that the oscillator at the second wireless device 1604 can be adjusted based on the measurement of the RACH preamble 1612, the first wireless device can send OA adjustment information in conjunction with a RACH Msg 2 (e.g., included in or multiplexed with RACH Msg 2) (an acknowledgment 1614 associated with the preamble 1612, which may be referred to as a second random access message).

[0114] The second wireless device 1604 may send 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 RACH Msg 3 1616 to determine whether the oscillator at the second wireless device 1604 can be adjusted. If the first wireless device 1602 determines that the oscillator at the second wireless device 1604 can be adjusted based on the measurement of RACH Msg 3 1616, the first wireless device may combine RACH Msg 4 1618 (e.g., included in or multiplexed with RACH Msg 4) (e.g., a fourth random access message) to send OA adjustment information.

[0115] Subsequent communications, including reads 1620 and 1624, and associated responses, including responses 1622 and 1626, may exist. In some aspects, the first wireless device 1602 may measure responses 1622 and 1626 to determine whether the oscillator at the second wireless device 1604 can be adjusted.

[0116] Figure 17 This is a flowchart 1700 of a wireless communication method. The method can be performed by wireless devices (e.g., base stations 102, 310, network entity 2102, network entity 2202, UE 104, 350, first wireless device 1402, first wireless device 1502, first wireless device 1602, device 2104). This method can enable OA for A-IoT devices, enabling better communication reliability and data rates in wireless communication.

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

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

[0119] Figure 18 This is a flowchart 1800 of a wireless communication method. This method can be performed by wireless devices (e.g., base stations 102, 310, network entity 2102, network entity 2202, UE 104, 350, first wireless device 1402, first wireless device 1502, first wireless device 1602, device 2104). This method can enable OA for A-IoT devices, enabling better communication reliability and data rates in wireless communication.

[0120] In some aspects, at 1802A, the first wireless device may send a trigger for initiating a dedicated OE measurement. For example, the first wireless device may (e.g., at 1412 or 1512) send a trigger for initiating a dedicated OE measurement. In some aspects, 1802A may be performed by OA component 198.

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

[0122] In some aspects, at 1802B, the first wireless device may receive reverse link packets from the second wireless device. For example, the first wireless device may receive reverse link packets from the second wireless device. In some aspects, 1802B may be performed by OA component 198. In some aspects, the reverse link packets may be random access messages.

[0123] In some aspects, at 1804B, the first wireless device can measure the frequency error associated with the oscillator of the second wireless device based on reverse link packets from the second wireless device. For example, the first wireless device can measure the frequency error associated with the oscillator of the second wireless device based on reverse link packets from the second wireless device. In some aspects, 1804B can be performed by OA component 198.

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

[0125] In some aspects, as part of 1806, at 1812, the first wireless device may periodically transmit a time-frequency synchronization signal including a forward link packet, the forward link packet including information for OA. In some aspects, as part of 1806, at 1814, the first wireless device may non-periodically transmit a time-frequency synchronization signal with a forward link packet, the forward link packet including information for OA. In some aspects, as part of 1806, at 1816, the first wireless device may transmit a forward link packet based on the 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 a forward link packet based on a change in the oscillator frequency associated with the second wireless device. In some aspects, as part of 1806, the first wireless device may transmit a forward link packet including information for OA based on a response. In some aspects, the information includes at least one bit indicating an instruction for adjusting the frequency at the oscillator of the second wireless device based on frequency granularity or direction. In some respects, the first wireless device may send forward link packets containing information for OA based on the value of the frequency error exceeding a threshold (e.g., triggered by the value of the frequency error exceeding a threshold).

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

[0127] Figure 19 This is a flowchart 1900 of a wireless communication method. The method can be performed by a first wireless device (e.g., tag 142, wireless device 1404, 1504, or 1604, device 2304). This method can enable OA for A-IoT devices, enabling better communication reliability and data rates in wireless communication.

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

[0129] At 1908, the first wireless device may adjust the oscillator based on information for OA. For example, the first wireless device may adjust the oscillator based on information for 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.

[0130] Figure 20 This is a flowchart 2000 of a wireless communication method. The method can be performed by a first wireless device (e.g., tag 142, wireless device 1404, 1504, or 1604, device 2304). This method can enable OA for A-IoT devices, enabling better communication reliability and data rates in wireless communication.

[0131] In some aspects, at 2002A, the first wireless device may receive a trigger for initiating a dedicated OE measurement. For example, the first wireless device may receive a trigger for initiating a dedicated OE measurement. In some aspects, 2002A may be performed by OA component 198.

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

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

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

[0135] In some aspects, as part of 2006, at 2012, the first wireless device could periodically receive a time-frequency synchronization signal including a forward link packet containing information for OA. In some aspects, as part of 2006, at 2014, the first wireless device could non-periodically receive a time-frequency synchronization signal with a forward link packet containing information for OA. In some aspects, as part of 2006, at 2016, the first wireless device could receive the forward link packet after completing time-frequency synchronization with a second wireless device.

[0136] At 2008, the first wireless device may adjust the oscillator based on information used for OA. For example, the first wireless device may adjust the oscillator based on information used for 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.

[0137] Figure 21Figure 2100 illustrates an example of a hardware implementation of device 2104. Device 2104 may be a UE, a component of a UE, or implement UE functionality. In some aspects, device 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 transceivers). Cellular baseband processor 2124 may include at least one on-chip memory 2124'. In some aspects, device 2104 may also include one or more Subscriber Identity Module (SIM) cards 2120 and at least one application processor 2106 coupled to a Secure Digital Card (SD) card 2108 and a screen 2110. Application processor 2106 may include on-chip memory 2106'. In some aspects, device 2104 may also include a Bluetooth module 2112, a WLAN module 2114, an SPS module 2116 (e.g., a GNSS module), one or more sensor modules 2118 (e.g., a barometric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 2126, a power supply 2130, and / or a camera 2132. Bluetooth module 2112, WLAN module 2114, and SPS module 2116 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). Bluetooth module 2112, WLAN module 2114, and SPS module 2116 may include their own dedicated antennas and / or communicate using antenna 2180. Cellular baseband processor 2124 communicates with UE 104 and / or RU associated with network entity 2102 via transceiver 2122 through one or more antennas 2180. Cellular baseband processor 2124 and application processor 2106 may each include computer-readable media / memory 2124', 2106'. Additional memory module 2126 may also be considered as computer-readable media / memory. Each computer-readable media / memory 2124', 2106', 2126 may be non-transitory. Cellular baseband processor 2124 and application processor 2106 are each responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by cellular baseband processor 2124 / application processor 2106, the software causes cellular baseband processor 2124 / application processor 2106 to perform the various functions described above. The computer-readable media / memory can also be used to store data manipulated by cellular baseband processor 2124 / application processor 2106 during software execution.Cellular baseband processor 2124 / application processor 2106 may be a component of UE 350 and may include at least one of memory 360 and / or TX processor 368, RX processor 356 and controller / processor 359. In one configuration, device 2104 may be at least one processor chip (modem and / or application) and may only include cellular baseband processor 2124 and / or application processor 2106, while in another configuration, device 2104 may be the entire UE (e.g., see below). Figure 3 The UE 350 includes an additional module of the device 2104.

[0138] As discussed above, OA component 198 can be configured to send forward link packets including information for OA to a second wireless device. In some aspects, OA component 198 can also be configured to communicate with the second wireless device after sending the forward link packets. OA component 198 and / or device 2104 can also be configured to perform combination. Figure 17 and Figure 18 The flowchart described and / or by Figure 14 , Figure 15 or Figure 16The wireless devices 1402, 1502, or 1602 may perform any of the aspects described. The OA component 198 may reside within the cellular baseband processor 2124, the application processor 2106, or both. Component 198 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. As shown, the device 2104 may include a variety of components configured for various functions. In one configuration, the device 2104 (and specifically the cellular baseband processor 2124 and / or application processor 2106) may include components for transmitting forward link packets including information for oscillator adjustment (OA) to a second wireless device. In some aspects, apparatus 2104 may include components for communicating with a second wireless device after transmitting a forward link packet. In some aspects, apparatus 2104 may include components for periodically transmitting a time-frequency synchronization signal including a forward link packet containing information for OA (Automatic Oscillator Response). In some aspects, apparatus 2104 may include components for non-periodicly transmitting a time-frequency synchronization signal with a forward link packet containing information for OA. In some aspects, apparatus 2104 may include components for transmitting a forward link packet based on the completion of time-frequency synchronization with the second wireless device. In some aspects, apparatus 2104 may include components for transmitting a forward link packet based on a change in the oscillator frequency associated with the second wireless device. In some aspects, apparatus 2104 may include components for transmitting a trigger for initiating a dedicated oscillator error (OE) measurement. In some aspects, apparatus 2104 may include components for receiving a response associated with a dedicated OE measurement. In some aspects, apparatus 2104 may include components for: transmitting forward link packets including information for OA based on a response. In some aspects, apparatus 2104 may include components for: receiving a first random access message from a second wireless device. In some aspects, apparatus 2104 may include components 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, apparatus 2104 may include components for: transmitting forward link packets including information for OA in a second random access message based on a frequency error value exceeding a threshold. In some aspects, apparatus 2104 may include components for: receiving reverse link packets from the second wireless device.In some aspects, apparatus 2104 may include components for measuring a frequency error associated with the oscillator of the second wireless device based on reverse link packets from the second wireless device. In some aspects, apparatus 2104 may include components for transmitting a forward link packet including information for OA based on a frequency error value exceeding a threshold. Apparatus 2104 may include components for performing a combination. Figure 17 and Figure 18 The flowchart described and / or by Figure 14 , Figure 15 or Figure 16 Any aspect performed by the wireless devices 1402, 1502, or 1602. These components may be components 198 of device 2104 configured to perform the functions described thereby. As described above, device 2104 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, these components may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions described thereby.

[0139] Figure 22Figure 2200 illustrates an example of a hardware implementation of network entity 2202. Network entity 2202 may be a BS, a component of a BS, or implement BS functionality. Network entity 2202 may include at least one of CU 2210, DU 2230, or RU 2240. For example, depending on the layer functionality handled by component 198, network entity 2202 may include: CU 2210; both CU 2210 and DU 2230; each of CU 2210, DU 2230, and RU 2240; DU 2230; both DU 2230 and RU 2240; or RU 2240. CU 2210 may include at least one CU processor 2212. CU processor 2212 may include on-chip memory 2212'. In some aspects, CU 2210 may also include an additional memory module 2214 and a communication interface 2218. CU 2210 communicates with DU 2230 via a midhaul link (such as an F1 interface). DU 2230 may include at least one DU processor 2232. DU processor 2232 may include on-chip memory 2232'. In some aspects, DU 2230 may also include an additional memory module 2234 and a communication interface 2238. DU 2230 communicates with RU 2240 via a fronthaul link. RU 2240 may include at least one RU processor 2242. RU processor 2242 may include on-chip memory 2242'. In some aspects, RU 2240 may also include an additional memory module 2244, one or more transceivers 2246, an antenna 2280, and a communication interface 2248. RU 2240 communicates with UE 104. On-chip memories 2212', 2232', 2242' and additional memory modules 2214, 2234, 2244 may each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 2212, 2232, and 2242 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software causes that processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor while executing the software.

[0140] As discussed above, OA component 198 can be configured to send forward link packets including information for OA to the second wireless device. In some aspects, OA component 198 can also be configured to communicate with the second wireless device after sending the forward link packets. OA component 198 and / or network entity 2202 can also be configured to perform combination. Figure 17 or Figure 18 The flowchart described and / or by Figure 14 , Figure 15 or Figure 16The wireless devices 1402, 1502, or 1602 in the network can perform any aspect of the process / algorithm. The OA component 198 may be located within one or more processors of one or more of CU 2210, DU 2230, and RU 2240. Component 198 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. Network entity 2202 may include various components configured for various functions. In one configuration, network entity 2202 may include components for transmitting forward link packets including information for oscillator adjustment (OA) to a second wireless device. In some aspects, network entity 2202 may include components for communicating with the second wireless device after transmitting forward link packets. In some aspects, network entity 2202 may include components for: periodically transmitting a time-frequency synchronization signal including forward link packets, the forward link packets including information for OA. In some aspects, network entity 2202 may include components for: non-periodicly transmitting a time-frequency synchronization signal with forward link packets, the forward link packets including information for OA. In some aspects, network entity 2202 may include components for: transmitting forward link packets based on completion of time-frequency synchronization with a second wireless device. In some aspects, network entity 2202 may include components for: transmitting forward link packets based on changes in the oscillator frequency associated with the second wireless device. In some aspects, network entity 2202 may include components for: transmitting a trigger for initiating a dedicated oscillator error (OE) measurement. In some aspects, network entity 2202 may include components for: receiving a response associated with a dedicated OE measurement. In some aspects, network entity 2202 may include components for: transmitting forward link packets including information for OA based on the response. In some aspects, network entity 2202 may include components for receiving a first random access message from a second wireless device. In some aspects, network entity 2202 may include components for measuring a frequency error associated with the oscillator of the second wireless device based on the first random access message from the second wireless device. In some aspects, network entity 2202 may include components for sending a forward link packet including information for OA in a second random access message based on a frequency error value exceeding a threshold. In some aspects, network entity 2202 may include components for receiving a reverse link packet from the second wireless device.In some aspects, network entity 2202 may include components for measuring frequency errors associated with the oscillator of the second wireless device based on reverse link packets from the second wireless device. In some aspects, network entity 2202 may include components for transmitting forward link packets including information for OA based on a frequency error value exceeding a threshold. Network entity 2202 may include components for performing combination. Figure 17 or Figure 18 The flowchart described and / or by Figure 14 , Figure 15 or Figure 16 Any aspect performed by wireless devices 1402, 1502, or 1602 in the network. These components may be components 198 of network entity 2202 configured to perform the functions described thereby. As described above, network entity 2202 may include TX processor 316, RX processor 370, and controller / processor 375. Thus, in one configuration, these components may be TX processor 316, RX processor 370, and / or controller / processor 375 configured to perform the functions described thereby.

[0141] Figure 23 Figure 2300 illustrates an example of a hardware implementation of device 2304. This device can support energy harvesting, backscatter transmission, environmental communication, passive communication, etc. The device can be a tag, PUE, environmental IoT device, passive device, energy harvesting device, etc. The device may include... Figure 4 A to Figure 9C describes various aspects and other examples. In some aspects, device 2304 may be a UE, a component of a UE, or may enable UE functionality. In some aspects, device 2304 may include a processor 2324 coupled to one or more antennas 2380. The device may include an energy harvesting component 2320 that can provide power to storage device 2330 and / or processor 2324. Processor 2324 may include memory 2324'. In some aspects, device 2304 may also include an SPS module 2316 (e.g., a GNSS module), one or more sensor modules 2318 (e.g., a barometer / altimeter; motion sensors such as an inertial measurement unit (IMU), gyroscope, and / or accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio, and / or other technologies for positioning), an additional memory module 2326, and / or a power supply or storage device 2330. SPS module 2316 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). SPS modules 2316 may include their own dedicated antenna and / or communicate using antenna 2380. Processor 2324 may receive signals, such as backscattered signals, and the device may harvest energy from the received signals. Processor 2324 receives signals via one or more antennas 2380, for example, from UE 104, reader 2332 (e.g., which may be a base station, UE, or different device), and / or with RU associated with network entity 2302. Processor 2324 may include computer-readable medium / memory 2324'. Additional memory module 2326 may also be considered as computer-readable medium / memory. Each computer-readable medium / memory 2324', 2326 may be non-transitory. Processor 2324 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by processor 2324, the software causes processor 2324 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor 2324 during software execution. In some aspects, the processor 2324 may be a component of the UE 350 or other energy harvesting device and may include at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 and / or the memory 360. In one configuration, the device 2304 may be an energy harvesting device. In other configurations, the device 2304 may be an energy harvesting component of a device.

[0142] As discussed above, OA component 199 can be configured to receive forward link packets including information for OA from a second wireless device. In some aspects, OA component 199 can also be configured to communicate with the second wireless device after sending forward link packets. OA component 199 and / or device 2304 can also be configured to perform combination. Figure 19 and Figure 20 The flowchart described and / or by Figure 14 , Figure 15 or Figure 16 Any aspect of the aspects performed by wireless devices 1404, 1504, or 1604. OA component 199 may be within processor 2324. Component 199 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. As shown, device 2304 may include a variety of components configured for various functions. In one configuration, device 2304 (and particularly processor 2324) may include components for receiving forward link packets including information for OA from a second wireless device. In some aspects, device 2304 may include components for adjusting an oscillator based on information for OA. In some aspects, device 2304 may include components for periodically receiving a time-frequency synchronization signal including forward link packets containing information for OA. In some aspects, device 2304 may include components for: periodically receiving a time-frequency synchronization signal having a forward link packet, the forward link packet including information for OA. In some aspects, device 2304 may include components for: receiving the forward link packet after time-frequency synchronization with a second wireless device is completed. In some aspects, device 2304 may include components for: receiving a trigger for initiating a dedicated oscillator error (OE) measurement. In some aspects, device 2304 may include components for: generating a dedicated OE measurement. In some aspects, device 2304 may include components for: sending a response associated with the dedicated OE measurement. In some aspects, device 2304 may include components for: receiving a forward link packet including information for OA based on the response. In some aspects, device 2304 may include components for: sending a first random access message to the second wireless device. In some aspects, device 2304 may include components for: receiving a forward link packet including information for OA in a second random access message. Device 2304 may include components for: performing a combination. Figure 19 and Figure 20The flowchart described and / or by Figure 14 , Figure 15 or Figure 16 Any aspect performed by the wireless devices 1404, 1504, or 1604. As described above, device 2304 may include TX processor 368, RX processor 356, and controller / processor 359. Thus, in one configuration, these components may be TX processor 368, RX processor 356, and / or controller / processor 359 configured to perform the functions described therein.

[0143] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is merely an example of an exemplary approach. It should be understood that the specific order or hierarchy of the boxes in the process / flowcharts can be rearranged based on design preferences. Furthermore, some boxes can be combined or omitted. The appended method claims present the elements of various boxes in a sample order, but are not limited to the given specific order or hierarchy.

[0144] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but should be given the full scope consistent with the language of the claims. Unless specifically stated otherwise, references to elements in the singular form do not mean “one and only one” but rather “one or more.” Terms such as “if,” “when,” and “simultaneously” do not imply a direct temporal relationship or reaction. That is, these phrases, such as “when,” do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply suggest that if a condition is met, then the action will occur, without requiring a specific or immediate time limit for the occurrence of the action. 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 superior to other aspects. Unless specifically stated otherwise, the term “some” means 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, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a collection of elements, where the number of elements is one or more. Therefore, for a set of X, X will include one or more elements. When at least one processor is configured to execute a set of functions, the at least one processor is configured to execute the set of functions individually or in any combination. Therefore, each of the at least one processor can be configured to execute a specific subset of the set of functions, wherein the subset is the complete set, a suitable subset of the set, or an empty subset of the set. If the first device receives data from or sends data to the second device, data can be received / sent directly between the first and second devices, or indirectly between the first and second devices through a set of devices. A device configured to "output" data (such as transmission, signal, or message) can, for example, transmit the data using a transceiver, or can transmit the data to the device that sent the data.A device configured to "acquire" data (such as, transmit, signal, or message) may receive the data, for example, using a transceiver, or may obtain the data from a device that receives the data. Information stored in memory includes instructions and / or data. All structural and functional equivalents of the elements throughout the various aspects described herein that are known to those skilled in the art or will later be known are expressly incorporated herein by reference and are covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. The words "module," "mechanism," "element," "device," etc., cannot replace the word "component." Therefore, no claim element will be construed as a functional component unless the element is expressly recited using the phrase "component for..."

[0145] As used in this article, the phrase “based on” should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”, unless otherwise stated otherwise.

[0146] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0147] Aspect 1 is a method for wireless communication performed by a first wireless device, the method comprising: Send a forward link packet containing information for OA to the second wireless device; and communicate with the second wireless device after sending the forward link packet.

[0148] Aspect 2 is the method according to aspect 1, wherein sending the forward link packet further includes: periodically sending a time-frequency synchronization signal including the forward link packet, the forward link packet including the information for the OA.

[0149] Aspect 3 is the method according to aspect 1, wherein sending the forward link packet further includes: periodically sending a time-frequency synchronization signal having the forward link packet, the forward link packet including the information for the OA.

[0150] Aspect 4 is the method according to aspect 3, wherein sending the forward link packet further includes: sending the forward link packet based on completing time-frequency synchronization with the second wireless device.

[0151] Aspect 5 is the method according to any one of Aspects 1 to 4, wherein transmitting the forward link packet further includes: transmitting the forward link packet based on a change in the oscillator frequency associated with the second wireless device.

[0152] Aspect 6 is the method according to any one of Aspects 1 to 5, wherein sending the forward link packet further includes: sending a trigger for initiating a dedicated oscillator error (OE) measurement; receiving a response associated with the dedicated OE measurement; and sending the forward link packet including the information for the OE based on the response.

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

[0154] Aspect 8 is the method according to any one of Aspects 6 to 7, wherein the second wireless device is a passive Internet of Things (IoT) device, wherein the trigger is included in a carrier, and wherein the response is based on a frequency hopping mode configured for the dedicated OE measurement.

[0155] Aspect 9 is a method according to any one of Aspects 1 to 8, wherein sending 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 sending the forward link packet including the information for the OA in a second random access message based on the value of the frequency error exceeding a threshold.

[0156] Aspect 10 is a method according to any one of aspects 1 to 9, wherein the information includes at least one bit indicating an instruction for adjusting the frequency at the oscillator of the second wireless device based on frequency granularity or direction.

[0157] Aspect 11 is a method according to any one of aspects 1 to 10, wherein transmitting the forward link packet further includes: receiving a reverse link packet from the second wireless device; measuring a frequency error associated with an oscillator of the second wireless device based on the reverse link packet from the second wireless device; and transmitting the forward link packet including the information for the OA based on the value of the frequency error exceeding a threshold.

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

[0159] Aspect 13 is the method according to aspect 12, wherein receiving the forward link packet further includes: periodically receiving a time-frequency synchronization signal including the forward link packet, the forward link packet including the information for the OA.

[0160] Aspect 14 is the method according to aspect 12, wherein receiving the forward link packet further includes: periodically receiving a time-frequency synchronization signal having the forward link packet, the forward link packet including the information for the OA.

[0161] Aspect 15 is the method according to aspect 14, wherein receiving the forward link packet further includes: receiving the forward link packet after completing time-frequency synchronization with the second wireless device.

[0162] Aspect 16 is a method according to any one of Aspects 12 to 15, wherein receiving the forward link packet further comprises: receiving a trigger for initiating a dedicated oscillator error (OE) measurement; generating the dedicated OE measurement; sending a response associated with the dedicated OE measurement; and receiving the forward link packet including the information for the OE based on the response.

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

[0164] Aspect 18 is the method according to any one of claims 16, wherein the first wireless device is a passive Internet of Things (IoT) device, wherein the trigger is included in a carrier, and wherein the response is based on a frequency hopping mode configured for the dedicated OE measurement.

[0165] Aspect 19 is a method according to any one of aspects 12 to 18, the method further comprising: sending a first random access message to the second wireless device; and receiving, in a second random access message, the forward link packet including the information for the OA.

[0166] Aspect 20 is a method according to any one of aspects 12 to 19, wherein the information includes at least one bit indicating an instruction for adjusting the frequency at the oscillator based on frequency granularity or direction.

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

[0168] Aspect 22 is the apparatus according to aspect 21, the apparatus further comprising one or more transceivers or one or more antennas coupled to the at least one processor.

[0169] Aspect 23 is an apparatus for wireless communication at a device, the apparatus including components for implementing any one of aspects 1 to 11.

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

[0171] Aspect 25 is an apparatus for wireless communication at a device, the apparatus 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 being configured, individually or in any combination, at least in part based on information stored in the at least one memory, to implement any one of aspects 12 to 20.

[0172] Aspect 26 is the apparatus according to aspect 21, the apparatus further comprising one or more transceivers or one or more antennas coupled to the at least one processor.

[0173] Aspect 27 is an apparatus for wireless communication at a device, the apparatus including components for implementing any one of aspects 12 to 20.

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

Claims

1. An apparatus for performing wireless communication at a first wireless device, the apparatus comprising: At least one memory; and At least one processor, coupled to at least one memory, the at least one processor being configured individually or in any combination to enable the first wireless device based at least in part on information stored in the at least one memory: Forward link packets including information for oscillator adjustment (OA) are sent to the second wireless device; and After sending the forward link packet, communication is initiated with the second wireless device.

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

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

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

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

6. The apparatus of claim 1, wherein, in order to transmit the forward link packet, the at least one processor is configured individually or in any combination to cause the first wireless device to: Send a trigger to initiate a dedicated oscillator error (OE) measurement; Receive a response associated with the dedicated OE measurement; and Based on the response, send the forward link packet including the information for the OA.

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

8. 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, and wherein the response is based on a frequency hopping mode configured for the dedicated OE measurement.

9. The apparatus of claim 1, wherein, in order to transmit the forward link packet, the at least one processor is configured individually or in any combination to cause the first wireless device to: Receive a first random access message from the second wireless device; The frequency error associated with the oscillator of the second wireless device is measured based on the first random access message from the second wireless device. as well as Based on the fact that the value of the frequency error exceeds the threshold, the forward link packet including the information for the OA is sent in the second random access message.

10. The apparatus of claim 1, wherein the information includes at least one bit indicating an instruction for adjusting the frequency at the oscillator of the second wireless device based on frequency granularity or direction.

11. The apparatus of claim 1, wherein, in order to transmit the forward link packet, the at least one processor is configured individually or in any combination to cause the first wireless device to: Receive reverse link packets from the second wireless device; The frequency error associated with the oscillator of the second wireless device is measured based on the reverse link packets from the second wireless device. as well as Based on the fact that the value of the frequency error exceeds the threshold, the forward link packet including the information for the OA is sent.

12. An apparatus for performing wireless communication at a first wireless device, the apparatus comprising: At least one memory; and At least one processor, coupled to at least one memory, the at least one processor being configured individually or in any combination to enable the first wireless device based at least in part on information stored in the at least one memory: Receive forward link packets from the second wireless device, including information for oscillator adjustment (OA); and The oscillator of the first wireless device is adjusted based on the information used for the OA.

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

14. The apparatus of claim 12, wherein, in order to receive the forward link packet, the at least one processor is configured individually or in any combination to cause the first wireless device to: The system receives time-frequency synchronization signals with the forward link packets aperiodically, the forward link packets including the information for the OA.

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

16. The apparatus of claim 12, wherein, in order to receive the forward link packet, the at least one processor is configured individually or in any combination to cause the first wireless device to: Receives a trigger to initiate a dedicated oscillator error (OE) measurement; Generate the dedicated OE measurement; Send a response associated with the dedicated OE measurement; and Based on the response, receive the forward link packet including the information for the OA.

17. 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.

18. 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, and wherein the response is based on a frequency hopping mode configured for the dedicated OE measurement.

19. The apparatus of claim 12, wherein the at least one processor is further configured, individually or in any combination, to cause the first wireless device to: Send a first random access message to the second wireless device; and The forward link packet, which includes the information for the OA, is received in the second random access message.

20. The apparatus of claim 12, wherein the information includes at least one bit indicating an instruction for adjusting the frequency at the oscillator based on frequency granularity or direction.

21. A method for wireless communication performed by a first wireless device, the method comprising: Forward link packets containing information for oscillator adjustment (OA) are sent to the second wireless device; as well as After sending the forward link packet, communication is initiated with the second wireless device.

22. The method of claim 21, wherein sending the forward link packet further comprises: A time-frequency synchronization signal, comprising the forward link packet, is periodically transmitted, the forward link packet including the information for the OA.

23. The method of claim 21, wherein sending the forward link packet further comprises: A time-frequency synchronization signal with the forward link packet is transmitted non-periodically, the forward link packet including the information for the OA.

24. The method of claim 23, wherein sending the forward link packet further comprises: The forward link packets are transmitted based on the completion of time-frequency synchronization with the second wireless device.

25. The method of claim 21, wherein sending the forward link packet further comprises: The forward link packets are transmitted based on changes in the oscillator frequency associated with the second wireless device.

26. The method of claim 21, wherein sending the forward link packet further comprises: Send a trigger to initiate a dedicated oscillator error (OE) measurement; Receive the response associated with the dedicated OE measurement; as well as Based on the response, send the forward link packet including the information for the OA.

27. 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, and wherein the response is a sequence configured for the dedicated OE measurement.

28. 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, and wherein the response is based on a frequency hopping mode configured for the dedicated OE measurement.

29. The method of claim 21, wherein sending the forward link packet further comprises: Receive a first random access message from the second wireless device; The frequency error associated with the oscillator of the second wireless device is measured based on the first random access message from the second wireless device; and Based on the frequency error being higher than the threshold, the forward link packet including the information for the OA is sent in the second random access message.

30. A method for wireless communication performed by a first wireless device, the method comprising: Receive forward link packets from the second wireless device, including information for oscillator adjustment (OA); as well as The oscillator is adjusted based on the information used for the OA.

Images